Skip to content
🚀 Find us on Product Hunt

Server-Side Tracking for WooCommerce GA4

Quick answer: Check "Enable Server-Side Tracking" in the wizard and enter your server container URL - it sets your GA4 tag to route through your own first-party endpoint instead of directly to Google. This applies to GA4 only; Meta, TikTok, and other platforms ship as Custom HTML tags and need their own server-side setup (like Meta's Conversions API) outside this tool.

Build my container →

Google Tag Manager server-side (sGTM) routes tracking hits through a server you control - typically on Google Cloud Run or App Engine - instead of sending them directly from the browser to Google, Meta, or another platform. That first-party path helps recover data lost to ad blockers, Safari's Intelligent Tracking Prevention, and iOS App Tracking Transparency, and gives you a layer to enrich or filter events before they leave your infrastructure.

What this checkbox actually does

When enabled, the generated GA4 Configuration tag gets two extra parameters: enableFirstPartyMode set to true, and serverContainerUrl set to the address you provide. That's the standard native-tag setting for routing through a server container - GTM handles the rest once your server container is actually running.

What you need before checking this box

What this doesn't cover

This option only affects the GA4 tag. Meta, TikTok, Pinterest, LinkedIn, Microsoft UET, and X all ship as Custom HTML tags in the generated container and need their own separate server-side integration - for Meta specifically, that means the Conversions API, configured independently of this wizard.

Frequently asked questions

Do I need to set up the server container myself?

Yes - this wizard configures the client-side GA4 tag to point at a server container, it doesn't create or host the server container itself. You (or a developer) need to deploy that separately first.

Does this work for Meta, TikTok, or my other platforms too?

Not through this checkbox - it only sets the server container URL on the GA4 tag. Other platforms need their own server-side integration set up separately, such as Meta's Conversions API.

Will this fix conversions lost to ad blockers and iOS restrictions?

It helps for GA4 specifically, since first-party requests are harder for ad blockers and browser tracking prevention to intercept than third-party ones. It's not a complete fix on its own, but it's the standard first step.

Other advanced topics

← All advanced guides

Share with