Tag Gateway for E-Commerce Brands

What is Tag Gateway?

Tag Gateway is a first-party tracking solution that routes your Google tracking requests through your own domain instead of directly to Google's servers. This makes tracking requests appear as first-party traffic, helping them bypass ad blockers and browser privacy restrictions.

Key Benefits

• Bypass ad blockers — Requests from your own domain aren't blocked
• Recover lost conversions — Capture 15–30% more conversion data
• First-party cookies — Longer cookie lifespans (90 days vs 7 days)
• Better attribution — More accurate ROAS and campaign data
• ITP compliance — Works with Safari's Intelligent Tracking Prevention

Why Tag Gateway Matters for E-Commerce

For Google Shopping advertisers, conversion tracking accuracy directly impacts campaign performance. When Google can't see your conversions, Smart Bidding can't optimise effectively.

The Impact on Google Ads

• Smart Bidding signals — Google needs conversion data to optimise bids. Missing conversions = suboptimal bidding.
• ROAS calculation — Understated conversions mean your reported ROAS is lower than reality, leading to conservative budget decisions.
• Audience building — Remarketing lists miss users who weren't tracked, reducing audience size and quality.
• Attribution accuracy — Cross-device and multi-touch attribution suffers without complete conversion data.

The Impact on Profit Optimisation

Accurate tracking isn't just about reporting — it directly affects profit-based bidding. When you use MarginStack to manage per-SKU costs and ProfitClarity to calculate profit-driven ROAS targets, the accuracy of those targets depends entirely on how many conversions you can see. If 30% of conversions are invisible, your ROAS calculations are 30% off.

How Tag Gateway Works

Tag Gateway acts as a reverse proxy between your website and Google's tracking servers. Here's the technical flow:

Technical Requirements

• Proxy endpoint — A server or edge function that forwards requests to Google
• HTTPS — Your proxy must use SSL (standard for all modern sites)
• Same domain — The proxy must be on your main domain or a subdomain
• Header forwarding — Client IP and user-agent must be passed to Google

Implementation Options

Tag Gateway vs Server-Side GTM

Tag Gateway is often confused with Server-Side Google Tag Manager (sGTM). They address the same problem — tracking loss — but at different levels of the stack. Understanding the difference helps you choose the right tool (or combine both).

Implementation Guide

Choose your implementation method below. We recommend Cloudflare Workers for most e-commerce sites due to its simplicity and generous free tier.

// Cloudflare Worker - Tag Gateway Proxy
export default {
  async fetch(request) {
    const url = new URL(request.url);
    if (!url.pathname.startsWith('/gtag/')) {
      return new Response('Not found', { status: 404 });
    }
    const googlePath = url.pathname.replace('/gtag/', '/');
    const googleUrl = 'https://www.googletagmanager.com' + googlePath + url.search;
    const response = await fetch(googleUrl, {
      method: request.method,
      headers: request.headers,
      body: request.method !== 'GET' ? request.body : undefined
    });
    const newHeaders = new Headers(response.headers);
    newHeaders.set('Access-Control-Allow-Origin', '*');
    return new Response(response.body, {
      status: response.status,
      headers: newHeaders
    });
  }
};

<!-- Old: Direct to Google (gets blocked) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=GT-XXXXX"></script>

<!-- New: Through your domain (not blocked) -->
<script async src="https://yourdomain.com/gtag/js?id=GT-XXXXX"></script>

// functions/gtag/[[path]].js
export async function onRequest(context) {
  const url = new URL(context.request.url);
  const targetUrl = new URL(
    url.pathname + url.search,
    'https://www.googletagmanager.com'
  );
  const proxyRequest = new Request(targetUrl.toString(), {
    method: context.request.method,
    headers: context.request.headers,
    body: context.request.method !== 'GET' ? context.request.body : undefined,
    redirect: 'follow'
  });
  const response = await fetch(proxyRequest);
  const newHeaders = new Headers(response.headers);
  newHeaders.set('Access-Control-Allow-Origin', '*');
  newHeaders.set('Access-Control-Allow-Methods', 'GET, POST, OPTIONS');
  return new Response(response.body, {
    status: response.status,
    headers: newHeaders
  });
}

# Nginx Tag Gateway Proxy
location /gtag/ {
    proxy_pass https://www.googletagmanager.com/;
    proxy_set_header Host www.googletagmanager.com;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_ssl_server_name on;
    add_header Access-Control-Allow-Origin *;
    add_header Access-Control-Allow-Methods "GET, POST, OPTIONS";
}

# Apache Tag Gateway Proxy
<Location /gtag/>
    ProxyPass https://www.googletagmanager.com/
    ProxyPassReverse https://www.googletagmanager.com/
    Header set Access-Control-Allow-Origin "*"
    Header set Access-Control-Allow-Methods "GET, POST, OPTIONS"
</Location>

// server.js
const express = require('express');
const { createProxyMiddleware } = require('http-proxy-middleware');
const app = express();
app.use('/gtag', createProxyMiddleware({
  target: 'https://www.googletagmanager.com',
  changeOrigin: true,
  pathRewrite: { '^/gtag': '' },
  onProxyRes: (proxyRes) => {
    proxyRes.headers['access-control-allow-origin'] = '*';
  }
}));
app.listen(process.env.PORT || 8080);

gcloud run deploy gtag-proxy \
  --source . \
  --region europe-west1 \
  --allow-unauthenticated

E-Commerce Platform Setup

Once your Tag Gateway proxy is running, update your tracking code on your e-commerce platform.

<!-- Replace this: -->
<script async src="https://www.googletagmanager.com/gtag/js?id=GT-XXXXX"></script>

<!-- With this: -->
<script async src="https://yourdomain.com/gtag/js?id=GT-XXXXX"></script>

// Add Tag Gateway tracking to WooCommerce
add_action('wp_head', function() {
    ?>
    <script async src="https://<?php echo $_SERVER['HTTP_HOST']; ?>/gtag/js?id=GT-XXXXX"></script>
    <script>
        window.dataLayer = window.dataLayer || [];
        function gtag(){dataLayer.push(arguments);}
        gtag('js', new Date());
        gtag('config', 'GT-XXXXX');
    </script>
    <?php
}, 1);

<!-- app/design/frontend/[Theme]/[Theme]/Magento_Theme/layout/default_head_blocks.xml -->
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <head>
        <script src="https://yourdomain.com/gtag/js?id=GT-XXXXX"
                src_type="url" async="true"/>
    </head>
</page>

<!-- Standard implementation -->
<script async src="https://yourdomain.com/gtag/js?id=GT-XXXXX"></script>
<script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
    gtag('config', 'GT-XXXXX');
</script>

GCLID Tracking for Google Ads

A GCLID (Google Click Identifier) is a unique string automatically appended to your landing page URL when a user clicks a Google Ads ad — for example: ?gclid=Cj0KCQjw.... Capturing and storing this identifier links ad clicks to downstream conversions, powering offline conversion tracking and CAPI uploads.

For Google Shopping campaigns, capturing the GCLID is essential. This unique identifier links ad clicks to conversions and powers offline conversion tracking.

Why Capture It?

• Offline conversion tracking — Match sales data back to the original ad click
• Cross-domain tracking — Pass GCLID from marketing site to checkout
• CAPI integration — Required for server-side conversion uploads
• Extended attribution — 90-day attribution window with stored GCLIDs

Implementation

// GCLID Tracker - add to your site's <head>
(function() {
    const GCLID_KEY = 'grow_gclid';
    const EXPIRY_DAYS = 90;

    function getGclidFromUrl() {
        const params = new URLSearchParams(window.location.search);
        return params.get('gclid');
    }

    function storeGclid(gclid) {
        if (!gclid) return;
        localStorage.setItem(GCLID_KEY, gclid);
        localStorage.setItem(GCLID_KEY + '_ts', Date.now());
        const expires = new Date(Date.now() + EXPIRY_DAYS * 86400000);
        document.cookie = GCLID_KEY + '=' + gclid +
            ';expires=' + expires.toUTCString() +
            ';path=/;SameSite=Lax;Secure';
    }

    const gclid = getGclidFromUrl();
    if (gclid) storeGclid(gclid);
})();

Testing & Validation

After implementing Tag Gateway, verify it's working correctly.

Quick Tests

• Browser Network Tab — Open DevTools, check that gtag requests go to your domain, not googletagmanager.com
• Ad Blocker Test — Enable an ad blocker, verify your site still sends tracking requests
• Real-Time Reports — Check GA4 Real-Time to confirm hits are arriving
• Google Ads — In Tag Assistant or Diagnostics, verify conversions are recording

Checklist

Best Practices

Frequently Asked Questions

Next Steps

Tag Gateway is the browser-side foundation of a robust conversion tracking stack — it ensures your Google tracking signals reach their destination despite ad blockers and browser restrictions. But it's only the first layer.

Once Tag Gateway is live, the most impactful next step is CAPI (Conversion API) Tracking — server-side uploads that capture sales that even first-party tracking misses, including offline purchases, checkout drop-offs, and cross-device journeys. Together, Tag Gateway + CAPI gives you near-complete conversion data accuracy.