Google Tag Gateway vs Server-Side GTM

I see some confusion between Google Tag Gateway and server-side GTM tracking, with each often promoted as the solution that “fixes” tracking, using buzzwords like “privacy-focused” and “first-party.”

What it does in simple terms:

  • Loads Google tracking and analytics scripts and forwards requests through your first-party domain (e.g. yourcompany.com) instead of the Google domain (googletagmanager.com).
  • Can reduce the impact of browser tracking prevention and ad blockers (but not completely).
  • It is easy to implement, especially if you already use Cloudflare (even on the free plan).

Google scripts (gtag) loaded from a Google domain
Google scripts (gtag and GTM) loaded from a first-party domain

However, it’s important to understand what Google Tag Gateway does NOT do (unlike server-side tracking):

  • It does not extend cookie lifetime (which directly helps improve conversion attribution)
  • It does not allow you to control or transform the data you send to Google or other platforms
  • It works only with Google platforms

Do you need Google Tag Gateway or Server-Side Tracking?

Google Tag Gateway

If you rely mostly on the Google marketing stack and have a relatively small Google Ads budget, Google Tag Gateway can be a quick and simple improvement to your tracking setup.

That said, the impact might not be very noticeable. Instead of relying on the advertised benefits of Google Tag Gateway, make sure your fundamentals are in place:

  • Consent Mode is configured correctly
  • Proper campaign tagging and consistent naming conventions are used
  • Enhanced Conversions are implemented

Server-side GTM tracking

If you:

  • Run ads on platforms like Meta, TikTok, etc. with a significant budget, or spend heavily on Google Ads alone.
  • Want to extend cookie lifetime and improve attribution
  • Need better data governance (redaction, transformation, enrichment)
  • Require webhooks or various platform integrations
  • Want a more comprehensive approach to tracking prevention mitigation
  • Can move some heavy tracking scripts from web to server-side GTM to improve page speed

…then server-side GTM tracking is likely the better solution.

It does come with additional server GTM hosting costs (starting from around €20/month, depending on website traffic and event volumes) and a more complex setup. However, the benefits typically outweigh the cost.

For example, conversion improvements from server-side tracking can range from 5% to 10%, while the associated costs – just 0.5% or less of your ad spend, depending on your scale and event volume.

Read more about Google Tag Gateway