Skip to content

Commit 6c88d8b

Browse files
update Enforce Email as Primary Identifier
The Enforce Email as Primary Identifier setting requires that an email be sent in on the payload. If that setting is enabled but an email isn't sent to Klaviyo then the payload will be rejected. This update clarifies that point.
1 parent f6425da commit 6c88d8b

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/klaviyo

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/klaviyo/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ If your `userId` is an email, or you provide an email in `traits.email`, Segment
7878

7979
#### Enforce email as primary identifier
8080

81-
This option is enabled by default to ensure duplicate profiles are not being created inside of Klaviyo. When enabled, Segment will never set the $id field to your `userId` when you call `.identify()` or `.track()`. Instead, Segment will only set $email as the primary identifier with your `traits.email` or `properties.email`.
81+
This option is enabled by default to ensure duplicate profiles are not being created inside of Klaviyo. When enabled, Segment will never set the $id field to your `userId` when you call `.identify()` or `.track()`. Instead, Segment will only set $email as the primary identifier with your `traits.email` or `properties.email`. Please note that if you have this setting toggled on you must send `email` in on your payloads or your events will not go through to Klaviyo.
8282

8383
#### Fallback on Anonymous ID
8484

0 commit comments

Comments
 (0)