Skip to content

Commit c395953

Browse files
sarahrudymarkzegarelli
andauthored
Add info section about client-side Klaviyo events (#4087)
* Add info section about client-side Klaviyo events Let customers know that some Klaviyo events (such as Added to Cart) require that a user be identified first (i.e. cookied) in order to track a subsequent event. * Update src/connections/destinations/catalog/klaviyo/index.md Co-authored-by: markzegarelli <[email protected]>
1 parent 69de38e commit c395953

File tree

1 file changed

+3
-0
lines changed
  • src/connections/destinations/catalog/klaviyo

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,9 @@ analytics.track({
142142

143143
When you call `track` on `analytics.js`, Segment calls Klaviyo's `track` with the same parameters.
144144

145+
> info ""
146+
> When you're tracking client-side, some Klaviyo events require you send an Identify call before a Track call.
147+
145148
### Server-side Track
146149

147150
When you call make a Track call from one of Segment's mobile or server-side libraries, Segment keys the user with the `userId` and also provides the Klaviyo `$email` `customer_property` if your `userId` is an email, or you provide `email` as one of your event `properties`.

0 commit comments

Comments
 (0)