Great video, thank you! Would love for you to follow-up with an other video on non-GA4 tags, such as using this server instance to implement Facebook CAPI and other server-side tags.
Hi there. Is there any difference between transport_url and server_container_url? As I see difference values in requests coming from different parameters (transport vs container) for example sst_system_parameters.
I have shown above video its helpful , i have one issue i want to create purchase event in gtm but my process is managed by backend webhook api then how to do in backend & server container in gtm?
Hi, to be honest, the ghostery chrome extension, find now even the GTM subdomain. Therefore this solution don’t attribute more data right? We can still remain on client side
can we send event data diectly to the server side url using fetch api in js as gtm is not working on shopify checkout page and then track on google analytics , meta and twiter ?
I wonder the same thing.. why "transport_url" instead of "server_container_url" which is the parameter name in the official ss documentation from google
The problem with Adblockers and cookies are that they refuse the gtag connection by default. So why to put a server in the middle if the first gtag script it's already been refused?
@@MeasureSchool Hey! Thank you for the video! So, if client-side should be kept anyway, then how server-side tracking makes website work faster as it promoted if you still have GTM code on a client-side?
I totally fail to see how this feature could be useful, why would you want to add yet another server between your website and analytics ? it doesn't solve anything in regards of blocked cookies or blocked google on the visitor browser, it still requires gtm script on the browser. At first when I saw this feature I thought it would work like the measurement protocol, to let us send all the infos from our backend to gtm/analytics, but it's just another step. Or I missed a step, i don't know :/
@@theduck17 I really don't understand how. It's the gtag script on browser that send the data. No matter where it is sent, if that script is blocked, it won't be sent anywhere (Brave blocks it by default for instance) Adding another step between the browser and analytics doesn't change anything. Server side tagging should be tags sent by the server side of the websites, thus eliminating the need to even install the script, making the page load faster etc... I really want to understand :/
Nervermind I think i understood... Brave is blocking the call to the google servers, if this url is on our subdomain, it won't get blocked.. right ? Everything would still be so muc heasier if we could send everything from the backend though...
@@YamiTatsu Correct, that's why Julian mentioned setting up the subdomain to maximize the implementation but even if you don't, the server isn't a google marketing cloud domain but a google cloud server and those shouldn't get blocked since they can be used for other things that aren't advertising related.
Amazing video! I followed your instructions - server is responding, but when I try to debugg the client and server at the same time, the server debugger does not respond. There is not hits. Any idea? Thanks :)
This exact video is perfect, you just haven't read the video title yet. How to Set Up GTM Server-Side Tagging (2024) -> Video is about setting up Server-Side Tagging, he showed us how to create a server GTM -> Client Side GA4 tag -> Server Side Ga4 Client and Tag. This is sufficient for what the video title suggests, of course he will not include the whole Ecommerce Setup for GA4, CAPI, TikTok and other platforms.
Check out our FREE TH-cam Exclusive Offer 👉bit.ly/yt-exclusive-offer
Great video, thank you! Would love for you to follow-up with an other video on non-GA4 tags, such as using this server instance to implement Facebook CAPI and other server-side tags.
Thank You Julio, as usual PRO guides, my respect )
Very well explained
@measureschool Do you teach how to build a manual server in Measure School?
Hi, why you set transport_url ? What is the defrence between server_container_url?
Appreciate this. However, it would be easier to understand if you create a chat about how the server-side tracking ecosystem works. Cheers!
So many same videos and no one show how to add custom domain in cloud platform... :( anyway, thanks for the video
Hi there. Is there any difference between transport_url and server_container_url? As I see difference values in requests coming from different parameters (transport vs container) for example sst_system_parameters.
I have shown above video its helpful , i have one issue i want to create purchase event in gtm but my process is managed by backend webhook api then how to do in backend & server container in gtm?
Will you show how you can "enhance" this data before passing to a platform? Like pulling "profit" by taking revenue - COGS in a ecommerce store.
All clear and working till the point where my GA4 Tag does not inherit data from GA4 client. Any clues how to solve this?
Hi, to be honest, the ghostery chrome extension, find now even the GTM subdomain. Therefore this solution don’t attribute more data right?
We can still remain on client side
can we send event data diectly to the server side url using fetch api in js as gtm is not working on shopify checkout page and then track on google analytics , meta and twiter ?
Why "transport_url" parameter instead of "server_container_url"?
I wonder the same thing.. why "transport_url" instead of "server_container_url" which is the parameter name in the official ss documentation from google
it might be the OLD name for this parameter - it would still work but the new proper name for this should be server_container_url
So will this help me see who is donating through PayPal? I am running ads for a non profit and I can’t add code to PayPal itself.
How to setup a custom tracking link?
Also wenn ich europäsche Server nutzen möchte, kann ich die automatische Erstellung aus dem Tag Manager heraus nicht benutzen?
The problem with Adblockers and cookies are that they refuse the gtag connection by default. So why to put a server in the middle if the first gtag script it's already been refused?
How to the duplicate ga4 purchase event if uniqe event id or transtaction id dosnt work ;3
Can you just set up all your tags server side and then disable the old client side GTM?
no, that's not how a gtm server works. You will still need a client side to get the initial data from the users browser
@@MeasureSchool Hey! Thank you for the video! So, if client-side should be kept anyway, then how server-side tracking makes website work faster as it promoted if you still have GTM code on a client-side?
I totally fail to see how this feature could be useful, why would you want to add yet another server between your website and analytics ? it doesn't solve anything in regards of blocked cookies or blocked google on the visitor browser, it still requires gtm script on the browser. At first when I saw this feature I thought it would work like the measurement protocol, to let us send all the infos from our backend to gtm/analytics, but it's just another step.
Or I missed a step, i don't know :/
Sending data directly to a server increases the chances it will make it. For example, ad blockers shouldn't be able to stop this data from being sent.
@@theduck17 I really don't understand how. It's the gtag script on browser that send the data. No matter where it is sent, if that script is blocked, it won't be sent anywhere (Brave blocks it by default for instance)
Adding another step between the browser and analytics doesn't change anything. Server side tagging should be tags sent by the server side of the websites, thus eliminating the need to even install the script, making the page load faster etc...
I really want to understand :/
Nervermind I think i understood... Brave is blocking the call to the google servers, if this url is on our subdomain, it won't get blocked.. right ?
Everything would still be so muc heasier if we could send everything from the backend though...
@@YamiTatsu Correct, that's why Julian mentioned setting up the subdomain to maximize the implementation but even if you don't, the server isn't a google marketing cloud domain but a google cloud server and those shouldn't get blocked since they can be used for other things that aren't advertising related.
@theduck17 thanks for the explanation. Couldn't have said it better
Amazing video! I followed your instructions - server is responding, but when I try to debugg the client and server at the same time, the server debugger does not respond. There is not hits. Any idea? Thanks :)
Did you find a solution for this? I am facing the same issue
I think this video can be made more detailed, pls try in next video
yea, there is always more to say. I try to keep it short and sweet
This exact video is perfect, you just haven't read the video title yet.
How to Set Up GTM Server-Side Tagging (2024) -> Video is about setting up Server-Side Tagging, he showed us how to create a server GTM -> Client Side GA4 tag -> Server Side Ga4 Client and Tag.
This is sufficient for what the video title suggests, of course he will not include the whole Ecommerce Setup for GA4, CAPI, TikTok and other platforms.
not using stape anymore?
I thing Google Cloud is cheaper
GTM so clunky!