What is server-side tracking?
Server-side tracking sends measurement data from your own server to platforms such as GA4, Google Ads and Meta, instead of sending it only from the visitor’s browser. It makes data collection less dependent on ad blockers and browser restrictions and gives you control over what each platform receives.
What is server-side GTM?
Server-side Google Tag Manager is a tagging container that runs on a server instead of in the browser. The website sends events to this container on your own subdomain, and the container forwards them to GA4, Google Ads, the Meta Conversions API and other platforms.
What is Consent Mode v2?
Consent Mode v2 is Google’s mechanism for passing a visitor’s consent choices to Google tags. It adds two signals, ad_user_data and ad_personalization, to the existing analytics and ad storage signals, and Google requires it for advertisers who use personalised advertising with visitors in the European Economic Area.
How do I know if my purchases are being counted twice?
Group the purchase events by transaction ID instead of counting hits. If one order number appears more than once in GA4 or as more than one Google Ads conversion, purchases are being duplicated. Common causes are the same event sent on two transports and a confirmation page that fires again on reload.
What is the difference between GA4 and Google Tag Manager?
Google Analytics 4 is the tool that stores and reports the data; Google Tag Manager is the tool that decides which tags fire on the site and what they send. GTM sends events to GA4, Google Ads and other platforms, and GA4 is where you read the results.
When is server-side tracking worth it?
Server-side tracking is worth it when advertising decisions depend on conversion data: shops that spend steadily on Google Ads or Meta, sell in several markets or see a gap between orders and tracked purchases. It adds a server to run and maintain, so a small shop with little advertising may not need it yet.