วีดีโอ

GA4 should receive data from a single source (web or server), thus GA4 does not support event deduplication.

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.

Hi! We have recently updated the power-up custom loader and now it can also protect /gtag/js and ‘collect’ requests from adblockers. You need to activate the "GA4 ad block bypass" toggle when setting up the custom loader.

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?

Please elaborate on your question. Or you can always write to our support team at support@stape.io with any questions you have about our service and they will be happy to help you.

Thank you so much for your feedback, we really appreciate it!

Thank you so much for your feedback! Happy tagging!

Thank you so much for your feedback, we really appreciate it! You are right, the video assumes that you already have experience with tracking, especially with GTM. Unfortunately, to describe everything in detail would be an hours long video We recommend you take a look at the Stape Academy, which is free for Stape users and where these and many other aspects are described and explained in more detail: academy.stape.io.

@ I did and I managed to learn GTM and configure correctly my server :) I think you guys have a lot of potential outside of the “experts” like me. I was a goofy guy now I’m tracking the s* out of my website.

We are very glad that our material has helped you on your way!

Multi-domain power-up allows you to connect multiple domains to your server GTM container. This is usually used if your sites have very similar or the same tracking plan, events, same data layer and this will not change in the near future. It is most often used if the domains differ just in language version and the site remains the same. One of the biggest advantages is the ease of maintenance of the container. for example if you need to introduce a new tracking/advertising platform - you just need to do it once in one container, instead of having to add it to 2, 3 or more containers. Any changes/bug fixes/improvements again need to be done just once. So it saves a lot of time and effort. Unfortunately, if you are using a custom loader, you will not be able to generate a custom loader code for a domain that is not added to the container on Stape.

Yes, of course you can use your data layer without any restrictions. _gcl_aw is a web conversion linker cookie, so it is used if you have Google ADS running in a web container. When using Google ADS on a server container, the FPGCLAW and FPGCLGB cookies are used - they are in the list of standard Cookie Keeper cookies for Google ADS. But of course you can add any other cookie you want to the list of cookies that Cookie Keeper restores. So if you want to use web tracking for Google ADS - you need to add _gcl_aw as a custom cookie.

Thank you so much ​@@Stape

No, not unless your DNS records are managed through Shopify.

@@Stape Awensome, thanks. But still missing to much data in purchase event ;/ Meybe soem video about stapeXshopify webhooks?

Make sure you are looking for this in the server container and not in your web container. Here's the direct link: tagmanager.google.com/gallery/#/owners/stape-io/templates/facebook-tag

mee too, solutions?

No, if the browser cuts the gclid you can't get it somehow. The only solution here is for Google, following the example of other platforms, to allow you to specify a custom url parameter name for click id. That way it won't be subject to these restrictions. But so far that hasn't happened.

@@Stape thanks!

Yes, of course. You can collect the data and DOM elements you need on the web container and pass it to the server container to trigger the right event tags based on it. You can pass the data through the Data tag or through the GA4 tag. Here is article: stape.io/blog/sending-data-from-google-tag-manager-web-container-to-the-server-container

It doesn't matter how you set up your Pixel events. The main thing is that they are set up. Meta Conversions API Gateway works based on the data that Meta pixel sends. It means that every time when CAPIG sees event triggered by Meta pixel, it sends server events.

Thank you for your feedback. We are working on new videos. Unfortunately, the process of making new videos requires a lot of time.

You can set up custom events for TikTok, but you can't use them to optimise campaigns.

@@Stape Thank you for the reply! I get the point.

Make sure you're watching this in a server container. You are probably trying to find it in the GTM web container.

The standard recommendation for GA4 is to use a trigger for just all GA4 events. That is, you need to use a trigger without a specific event name, just with the condition client name = GA4 (or whatever your GA4 client is called).

You do not need a new GA4 property for server-side tracking. GA4 does not support hybrid tracking (i.e. sending both web and server events for deduplication), the source of events must be one, either web or server. GA4 in server-side format works as a proxy. Data is not changed in any way, nothing happens to it (unless you have specially configured it, which is usually very rarely done), requests are simply redirected further to GA4.

In the tags where you plan to use this data.

@@Stape yes i know for the tag, but where to put it, what column spesific

Yes

Please refer to our article on this topic: stape.io/blog/how-to-switch-server-gtm-hosting-from-google-cloud-to-stape

Hi What are you triggering your Google Ads tag off of?

From the event data. if the email is available in a cookie or from the event where it is used, it will be passed.

No, the tag does not set cookies as it is intended to use this as an offline conversion. You need to save the cookie and pass it to the tag. It is usually most convenient to set the required cookie with the CookieMonster tag on the server container. Check if the url has the ‘msclkid’ parameter (Bing click id) and if it does, save its value.

The trigger is already configured, but the trigger description is present after adding it in the video. In this case, the trigger must be: Type: Custom Events Event name: purchase This trigger fires on: Client name contains or equals GA4

@@Stape thankyou for the reply, but please next time just make video uncut and start from scratch

>> 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

You can refer to our article on this topic, which is updated with any changes we or Shopify make. stape.io/blog/facebook-conversion-api-and-shopify

You can send these parameters to event data with any name and just overwrite them in the FB tag, user data section

The conversion data on the sGTM container should be send from somewhere. Usually the source of the signal is a GTM web container on which you can get data from the data layer, including the amount, pass it to the sGTM and based on that send the data to the right platforms, including Google ADS.

Hi. Thank you for your feedback. An outgoing request from the server happens if it has the gclid parameter. Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad.

@@Stape Thank you for your feedback! :)

Thank you for your feedback. Please check that you are using the Unique event ID variable in the web tags and the event data variable with Key Path event_id in the server tag. If this is the case and you still have an incorrect event id, please write to Stape support at support@stape.io with the tags and triggers settings. Also, please provide information on what you are using as a transport for Linkedin conversions.

This problem can also occur if you use tag sequencing.

@@Stape Thanks for your answer. I don't use tag sequencing neither in the web gtm or the sgtm container. Even if the unique event ID aren't identicals for a given conversion action in web and server container, can I still use the conversion action from the server container to optimise my LinkedIn Ads campaigns ? I see that my conversion action from server is in statut "Active". I did a conversion test, the statut of my tag from server is in 201 and I capture user-data in SHA256 correctly.

Thank you for your feedback. We will consider it in our next videos. In the meantime, you can try to find relevant information on our blog stape.io/blog. For GA4 and Google Ads, we recommend using the official Google tags and client and Data Tag and Data Client for all other platforms, including Meta.

Hi. You can update the existing document(merge document keys) if you write the same keys to the existing document. You can find a little more information in our article: stape.io/blog/write-data-to-firestore-from-server-google-tag-manager

Hi. Linkedin has changed its interface since the video was recorded. Unfortunately, it is not possible to update the video as quickly as the platform interfaces are updated. Please follow these instructions to generate a token: Analyse menu section -> Sources -> Google tag manager -> Generate token

HI, The cookie extener tag will only work with Own CDN or Same Origin custom domain and not with Global CDN. You set the expiration time in the tag settings and this is possible. You can find the article you need here: stape.io/blog/extend-cookie-lifetime-using-server-side-google-tag-manager

You need to create it on tagmanager.google.com and host it somewhere in order to set up Meta Conversion API.

Usually, after connecting a data source to the Gateway Hub, web events start arriving and being sent as server events within an hour. You can check this in your Gateway Hub UI. On the Meta(event manager) side, the delay can be up to 48 hours, just like with regular browser events.

You need to have two conversions on Linkedin. One for web and one for server source and accordingly you should have a tag on the web that works for the conversion and a tag on the server that works for the required conversion.

Google Ads Offline tag has fields for consent where you need to indicate where to take the status of the consent from, or set Granted as the default.

I meant for GA4 sending offline revenue, it comes via the web hook claimed by data client and then sent to GA4, however GA4 doesnt show this revenue for some reason I assume because of privacy

@@Stape Any update here we have purchase being claimed by DC and then tag sending to GA4 which is successful however its not showing in GA4 or Big query

This needs to be debugged and see exactly what the problem is with your setup. Unfortunately it is not possible to find out in TH-cam comments :) You can try to describe it more in our community: community.stape.io.

I see that case having multiple sub-domains configured in the same Server Container

Unfortunately, we cannot share the logic of the custom loader code with you. But I can tell you that the code that loads your GTM container cannot affect events match quality (if that's what you meant by “matching"). You can write a ticket to our support team and describe your issue in more detail and they will try to help you.

Google Ads Tag server-side will only properly work off of incoming GA4 signal. Normally conversions that happen outside of website engagement should be reported as Offline ones.

Usually, no. If these are new conversions for Google Ads, you don't need to pause your client side tags. Only if they are the same conversions that were set up on the web GTM.