For some Server Stape-Tags there are Consent Settings (Send data in case marketing consent given). And I read that consent State somehow is baked into the Web Data Tag. 1. For which Variables and value is the Consent Setting looking for? 2. Can I create a Consent Event Data Variable myself to control this setting? Thank you so much in advance!
The way Data Tag sends consent is in the consent_state object, for example: consent_state = { ad_storage: 'granted', ad_user_data: 'granted', ad_personalization: 'granted', analytics_storage: 'granted', functionality_storage: 'granted', personalization_storage: 'granted', security_storage: 'granted', }; so if you were to manually add consent_state key to your Data Tags and mimic the structure with a variable - server side tags would dithe gest it same as they do native object
so it should be enough to use a data tag on client side? so apart from wGTM there is no google script visible? does this tag collect all click ID's there will be?
Thanks! Very helpful. But what after claiming custom requests in sGTM? I need send a "refund" event from sGTM to GA4? I'm currently using Stape PHP SDK
You can use the GA4 tag to send a refund event from sGTM to GA4. It's important to add the correct transaction ID in the tag settings, the one that corresponds to the purchase transaction ID.
@@Stape Thanks! I already did that and it works, but I also realized that the Client ID has to be the one that corresponds to the Client ID that was sent with the purchase transaction ID as well. So, I had to send the Client ID to my backend, so when I need to cancel an order, I send the refund event to sGTM with the same transaction ID and Client ID. Am I wrong? if not, how can I avoid sending the Client ID to my backend? In other words, is there a way to generate a unique Client ID from sGTM instead of the ones generated automatically?
@@magedmohamed1843 What is the reason for sending the Client ID for refunds? From my experience, it's only transaction ID that matters for refunds since a refund event is needed to accurately track revenue in GA4. In my view, you can skip sending the Client ID for refunds. But if you want you can store a real Client ID on purchase and send it on refund event. Another recommendation is to include item information in your refund event to see item-level refund metrics in Analytics.
Thanks for the share ! on the previous version of the shopify application, it was possible to check the box "add user data to data layer events". Since this option is no longer available, do I need to reconfigure everything as in this video, or is there a special configuration for stape in shopify?
In the current version of the Shopify app, user data is added automatically if the data layer is enabled. Please check this post on debugging data layer checkout events stape.io/blog/server-side-tagging-for-shopify#debugging-data-layer-checkout-events we also recently had a webinar on setting up gAds and GA for Shopify ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-7ASTO--LNLE.html
![How to use Stape Data Tag and Data Client [Step-by-step guide]](/img/logo.svg){kind=logo}
