From ba74beab2948ebd635e4c6ecb9b4dfae44311274 Mon Sep 17 00:00:00 2001 From: Ashton Huxtable <78318468+ashton-huxtable@users.noreply.github.com> Date: Tue, 3 Oct 2023 09:23:53 -0600 Subject: [PATCH 1/2] Update client side identify --- src/connections/destinations/catalog/klaviyo/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/klaviyo/index.md b/src/connections/destinations/catalog/klaviyo/index.md index 5cfe57a496..deadaf525a 100644 --- a/src/connections/destinations/catalog/klaviyo/index.md +++ b/src/connections/destinations/catalog/klaviyo/index.md @@ -42,7 +42,7 @@ analytics.identify({ When you call `identify` on analytics.js, Segment calls Klaviyo's `identify` with the `traits` object. Segment then augments the `traits` object to have `traits.$id` be the `userId` since Klaviyo takes the user ID on the `traits` object itself. > info "" -> When you send data to Klaviyo using `analytics.js`, an initial `page` call is required. By default, this is already added in your [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet). +> When you send data to Klaviyo using `analytics.js`, an initial `page` call is required. By default, this is already added in your [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet). In addition to the `page` call, `identify` must be called on each subdomain where you want to track users. Klaviyo sets cookies on the subdomain rather than the top level domain, making this extra `identify` call necessary for tracking. The following Segment spec'd traits map to Klaviyo [special people properties](http://www.klaviyo.com/docs){:target="_blank"}: From 213d52b2889abad6619c83aad2c9c519a8c37016 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 10 Oct 2023 12:10:59 -0500 Subject: [PATCH 2/2] Update index.md --- src/connections/destinations/catalog/klaviyo/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/klaviyo/index.md b/src/connections/destinations/catalog/klaviyo/index.md index deadaf525a..9f53d5be60 100644 --- a/src/connections/destinations/catalog/klaviyo/index.md +++ b/src/connections/destinations/catalog/klaviyo/index.md @@ -42,7 +42,7 @@ analytics.identify({ When you call `identify` on analytics.js, Segment calls Klaviyo's `identify` with the `traits` object. Segment then augments the `traits` object to have `traits.$id` be the `userId` since Klaviyo takes the user ID on the `traits` object itself. > info "" -> When you send data to Klaviyo using `analytics.js`, an initial `page` call is required. By default, this is already added in your [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet). In addition to the `page` call, `identify` must be called on each subdomain where you want to track users. Klaviyo sets cookies on the subdomain rather than the top level domain, making this extra `identify` call necessary for tracking. +> When you send data to Klaviyo using `analytics.js`, an initial Page call is required. By default, this is already added in your [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet). In addition to the Page call, you must make an Identify call on each subdomain where you want to track users. Klaviyo sets cookies on the subdomain rather than the top-level domain, making this extra Identify call necessary for tracking. The following Segment spec'd traits map to Klaviyo [special people properties](http://www.klaviyo.com/docs){:target="_blank"}: