Definition
Server-side tagging is a tracking setup in which the browser sends each event to a tagging server the store controls, usually a Google Tag Manager server container on a subdomain such as gtm.yourstore.com, and that server forwards the data on to GA4, Google Ads, Meta and any other destination. The browser loads one lightweight script instead of a pixel per vendor, and the store decides exactly which fields each vendor receives.
A Shopify store's server container, as configured
- Server container endpoint
- https://gtm.yourstore.com, a DNS record pointed at the container's Cloud Run service
- Browser side
- One Google tag with its server container URL set to the endpoint; the Meta pixel and Google Ads tag removed from the theme
- Clients on the server
- GA4 client claims requests on /g/collect; a Shopify custom pixel posts checkout and purchase events to the same endpoint
- Tags fired on the server
- GA4 event tag, Google Ads conversion with enhanced conversions, Meta Conversions API with an event_id for deduplication
- Fields stripped before Meta
- Full URL query strings and the raw user agent; hashed email and phone kept
- Hosting
- Cloud Run with autoscaling, billed monthly to the store's own Google Cloud project
An illustrative configuration, not a prescription. The point is that the store, not each vendor's script, decides what leaves the browser and what each destination is allowed to see.
Why it matters
Server-side tagging matters because a store's conversion data now passes through browsers that limit cookies, block third-party scripts and drop requests. Sending events through a first-party endpoint keeps more purchases attached to the session that produced them, gives Google Ads and Meta a more complete conversion record to bid on, and lets the store send hashed customer data for enhanced conversions and the Conversions API from one place. It also cuts the number of vendor scripts on the page, which helps Core Web Vitals on product and checkout pages. The trade is real work: a cloud service to host, a subdomain to manage and a mapping from Shopify or WooCommerce events into every destination, all of which the store now owns.
Where it goes wrong
- Treating it as a fix for consent: a server container still has to honour the visitor's choice, and events withheld by a consent banner are not recovered by moving the endpoint
- Hosting the endpoint on a bare Google-owned domain, which loses the first-party cookie benefit that justified the project in the first place
- Double counting purchases because the browser pixel was never removed and the server-side Conversions API event carries no matching event_id
- Forgetting Shopify's checkout: theme scripts do not run there, so checkout and purchase events must come from a custom pixel or a webhook route, or the funnel ends at begin_checkout
- Nobody owning the container: server-side setups fail quietly when a Cloud Run revision breaks or a certificate lapses, and the first sign is a revenue gap in GA4 weeks later
Questions about server-side tagging
Does server-side tagging replace Google Analytics 4 tracking?
No. GA4 still receives events; they arrive through the store's server container rather than straight from the browser. The GA4 client in the container reads the same measurement protocol request the browser would have sent and forwards it, so reports, audiences and Google Ads links keep working. What changes is the route and the control over what is included.
Can a Shopify store run a tagging server without Shopify Plus?
Yes. The server container is hosted outside Shopify, and the browser part is a theme script plus a custom pixel for checkout and order status events. Plus is not required, although a Plus store gains checkout extensibility, which makes the checkout-side events cleaner to wire. WooCommerce stores have the same options with direct template access.
How much does a tagging server cost to run?
The cost is the cloud hosting itself, billed by Google Cloud or another provider according to traffic, plus the setup and the monitoring. There is no separate licence for a Google Tag Manager server container. A store should budget for the ongoing hosting and for someone to check the container whenever a platform or app update changes the events it receives.