What is server-side tracking with Google Tag Manager? Let me show you

[@LeonKorteweg]

Get started with server-side tracking via Stape: leonkorteweg.nl/link/stape (affiliate)

[@jimpannell2035]

Great to have you back. If these benchmark numbers are even remotely accurate, it sounds like it is worth it.

[@Vic-b22]

Hi Leon, Amazing content as always, very interested to learn more about server side especially via stape. please make this a series of tutorials :) :) :)

[@LeonKorteweg]

Yes that's the plan ;)

Welcome back Leon 🙌

[@ArturPakosch]

Awesome explanation Leon! But why people tend to build up their GA4 events in the serverside container, if the clientside eventtags already follwow the Config Tag (and URL) to the clientside container? I saw setups where almost everything was built up in the clientcontainer now.. There must be any benefit.

[@LeonKorteweg]

The server-side GTM container is for routing, modifying and transforming events. However you cannot create new events out of nothing. You don't have click, scroll or form triggers for example. That's why you still need a client-side GTM container along with it.

[@ArturPakosch]

@@LeonKorteweg So do I understand that right: you can have clientside-events without serverside but not vice versa?

[@victorsv7484]

cant be as simple as that, can it? why wouldnt be that a standard setting if its just as easy as putting your webpage in that part?

[@LeonKorteweg]

Of course there is more work involved. If you do not install server-side GTM on a subdomain, the server_container_url setting won't work. My point here was to show that server-side GTM can help you set up tracking to a first-party endpoint. In my other sGTM video's I go into much more detail what steps are needed. Check the playlist on my channel if you're interested.