How to use same origin approach for server GTM

When working with server-side Google Tag Manager (sGTM), one of the key challenges is cookie lifetime and browser restrictions. Safari’s Intelligent Tracking Prevention (ITP) and other browser privacy features can shorten cookie duration when they’re set from a third-party or cross-domain source.

The Same Origin setup helps solve this problem. It allows your sGTM container to share the same domain as your website, for example, serving requests through example.com/metrics instead of a separate subdomain like metrics.example.com.

You can set up the same origin on the following providers:

• Deno Deploy
• Netlify
• Vercel
• AWS CloudFront
• Caddy
• Apache HTTP Server
• Cloudflare
• Ngnix

Same origin path in Stape

After setting up the same origin on your hosting platform, you can set it up in Stape as well. To use the same origin custom domain in Stape, you need to specify your same origin proxy path in the Custom Loader power-up. 

The Same Origin method means your tracking requests will appear to come directly from your main website domain, not from a separate tagging domain. This helps ensure cookies and GA4 encryption work as expected and are not limited by browser privacy rules. The proxy path ensures that requests to your server container are routed through the custom domain, making it look like part of the same content delivery network (CDN) or server, even though the data is being handled on the server-side.