Thank you for your feedback and suggestion. But the best practice is to do it manually. It doesn't take much time and gives you full control over the parameters passed to Klaviyo.
Love the webinar! Quick question... If we're using Shopify's Checkout Extensibility and our GTM is setup in Customer Events and subscribing to the default product_added_to_cart event from Shopify, how does the tag pickup the email address? According to Shopify's documentation, email isn't a variable they provide.
@@Stape Ah, got it. And what if the customer is not logged into the site? In my experience, most of our brands don't have logged in customers. Would revenue still be attributed to the Klaviyo flow even if not logged in?
I have a question that we usually get gmail value with purchase view product add to cart If I don't get it here, then I don't have to pay the value of the email.. and can I send the purchase and checkout events?
Here is a major question. When we add products to the cart or do the begin checkout event, there is no option to input an email. We can input email only for the purchase event. So how can we send email with "Add To Cart" and "Begin Checkout" events?
My guess is that this is more for users that are already on your list. So after you send a campaign, those users that view product or add to cart but don't buy will get added to the atc/viewed product abandoned flow. And since their email is already known from Klaviyo, the tag just carries it across all events.
This is often possible if the user is authorised on your site (then you probably have their email available at all events). Or if the user has subscribed to a mailing list - store the specified email in cookies/localStorage and pass it along with further events generated by the user.
Why don't stape create a server side variable template for converting parameter naming conventions from ga4 to klaviyo
Thank you for your feedback and suggestion.
But the best practice is to do it manually. It doesn't take much time and gives you full control over the parameters passed to Klaviyo.
@Stape everything possible manually but still u guys have template for so many things isn't it?
Love the webinar!
Quick question...
If we're using Shopify's Checkout Extensibility and our GTM is setup in Customer Events and subscribing to the default product_added_to_cart event from Shopify, how does the tag pickup the email address? According to Shopify's documentation, email isn't a variable they provide.
same question
@Stape same question
If you use the data layer added by our Shopify app, the email will be available on the add_to_cart event if the user is logged in.
@@Stape Ah, got it. And what if the customer is not logged into the site? In my experience, most of our brands don't have logged in customers. Would revenue still be attributed to the Klaviyo flow even if not logged in?
How are you getting email on the page view event?
From the event data. if the email is available in a cookie or from the event where it is used, it will be passed.
I have a question that we usually get gmail value with purchase view product add to cart If I don't get it here, then I don't have to pay the value of the email.. and can I send the purchase and checkout events?
Could you please clarify the question?
Here is a major question. When we add products to the cart or do the begin checkout event, there is no option to input an email. We can input email only for the purchase event. So how can we send email with "Add To Cart" and "Begin Checkout" events?
My guess is that this is more for users that are already on your list. So after you send a campaign, those users that view product or add to cart but don't buy will get added to the atc/viewed product abandoned flow. And since their email is already known from Klaviyo, the tag just carries it across all events.
This is often possible if the user is authorised on your site (then you probably have their email available at all events). Or if the user has subscribed to a mailing list - store the specified email in cookies/localStorage and pass it along with further events generated by the user.