Thanks for the great explanation. I have two questions: 1. Email ID and Purchase Event: >> Do we need to pass the email ID only with the purchase event? >> If not, how can we ensure that the email ID is available with the "Active on site" tag, which should fire on all pages? 2. Object Builder and Multiple Items: >> You mentioned using Object Builder to map the item array parameters. >> However, I noticed that you've only added the first object. >> How can we handle scenarios where the user has multiple items in their cart using Object Builder? Or I would suggest to send directly from GA4 tag to SGTM.
>> Do we need to pass the email ID only with the purchase event? It usually makes sense to transmit this whenever you have this data available. That is, for example, also when the user has authorised on the site. >> If not, how can we ensure that the email ID is available with the “Active on site” tag, which should fire on all pages? This should be available in your data layer or otherwise on the site (e.g. in localStorage or just in the site DOM, but of course data layer is preferred). >> How can we handle scenarios where the user has multiple items in their cart using Object Builder? Or I would suggest to send directly from GA4 tag to SGTM. You can see this in the official documentation: In case of multiple items, you can form and send an ‘Items’ array of objects: developers.klaviyo.com/en/v1-2/docs/guide-to-integrating-a-platform-without-a-pre-built-klaviyo-integration
The event is received from the web. That is, a tag is configured on your web GTM container that is triggered by the purchase event and this request is received by the server. You can also refer to our webinar recording, where the process of setting up server-side tracking for Klaviyo is shown more clearly th-cam.com/video/2iTI4-FpaHI/w-d-xo.html&ab_channel=Stape.
![[Stape & Meta Webinar] Conversion API Gateway vs. server GTM: what to use, why and when](http://i.ytimg.com/vi/mKU0FmMLt8A/mqdefault.jpg)
![[Stape & Meta Webinar] Conversion API Gateway vs. server GTM: what to use, why and when](/img/tr.png)
![[Stape Webinar] Enhanced conversions tracking - step-by-step setup for GA4 and Google Ads](http://i.ytimg.com/vi/J3Hr9ii6Ce4/mqdefault.jpg)
Thanks for the great explanation. I have two questions:
1. Email ID and Purchase Event:
>> Do we need to pass the email ID only with the purchase event?
>> If not, how can we ensure that the email ID is available with the "Active on site" tag, which should fire on all pages?
2. Object Builder and Multiple Items:
>> You mentioned using Object Builder to map the item array parameters.
>> However, I noticed that you've only added the first object.
>> How can we handle scenarios where the user has multiple items in their cart using Object Builder? Or I would suggest to send directly from GA4 tag to SGTM.
>> Do we need to pass the email ID only with the purchase event?
It usually makes sense to transmit this whenever you have this data available. That is, for example, also when the user has authorised on the site.
>> If not, how can we ensure that the email ID is available with the “Active on site” tag, which should fire on all pages?
This should be available in your data layer or otherwise on the site (e.g. in localStorage or just in the site DOM, but of course data layer is preferred).
>> How can we handle scenarios where the user has multiple items in their cart using Object Builder? Or I would suggest to send directly from GA4 tag to SGTM.
You can see this in the official documentation:
In case of multiple items, you can form and send an ‘Items’ array of objects: developers.klaviyo.com/en/v1-2/docs/guide-to-integrating-a-platform-without-a-pre-built-klaviyo-integration
yeah okey but you didnt mention how we get data from our custom web site(server side ,apı etc). well
The event is received from the web. That is, a tag is configured on your web GTM container that is triggered by the purchase event and this request is received by the server.
You can also refer to our webinar recording, where the process of setting up server-side tracking for Klaviyo is shown more clearly th-cam.com/video/2iTI4-FpaHI/w-d-xo.html&ab_channel=Stape.