A new way to set up a custom domain in server GTM

Dec 29, 2023
Dec 26, 2023

When setting up server-side tagging, the best practice was configuring a custom domain for your server Google Tag Manager environment. This approach primarily allows setting up first-party cookies, which have a longer lifespan than third-party cookies, enhancing user tracking and data collection consistency.

With the new restrictions coming from Safari, more than just setting up a custom domain is required to prolong cookie lifetime. Even if you map a custom domain, cookies in Safari will be shortened. To make it last longer, you must ensure the custom domain has the same IP address as your website’s primary domain by configuring Own CDN, or use stape Cookie Keeper power-up to store and restore cookies

However, Google has recently changed the preferred way of mapping a custom domain for the server Google Tag Manager container. Instead of using a subdomain (like sgtm.example.com) they encourage using the same origin (like example.com/sgtm). 

With the same origin custom domain for sGTM, you will have the main benefit of server-side tagging - setting up first-party cookies. And with the tagging server using the same origin domain, you do not need to configure any additional settings to prolong cookies. However, mapping the same origin will be more complicated than configuring a subdomain. 

I will show two examples of configuring the same origin custom domain for sGTM using Cloudflare or nginx.

These are prerequisites to configure the same origin custom domainCopy link to this section

  1. Server Google Tag Manager container set up. 
  2. A CDN or load balancer that can forward requests.
  3. If you use App Engine, the tagging server must run version 2.2.0 or later.
  4. Select the path for your sGTM custom domain, for example, example.com/sgtm, example.com/data, example.com/metrics etc. 

How to configure the same origin custom domain in sGTMCopy link to this section

1. CloudflareCopy link to this section

a. Create a worker in Cloudflare.

worker in cloudflare - stape

b. Add worker name.

add worker name in cloudflare - stape

c. Create js similar to the screenshot below, where:

/metrics/ - is a path you choose for your server container.

https://gtm.stape.dog/ - is your tagging server URL. There are two scenarios:

js code in cloudflare - stape

d. Go to the Workers Route and create a new Route. Add the URL you use for server GTM ending with *. In my case, it’s stape.dog/metrics* and select the worker you’ve created on the previous steps. 

create a new Route in cloudflare - stape

2. nginxCopy link to this section

Add to your server config, where:

/metrics - path you selected for server GTM.

https://gtm.mysimple.name - custom domain of your sGTM. 

location = /metrics { return 302 /metrics/; } location ~ ^/metrics(.*) { resolver valid=3600s; proxy_pass https://gtm.mysimple.name$1$is_args$args; proxy_set_header Host gtm.mysimple.name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }

Do you have any questions?

We've got you covered! Click Get help, fill-up the form, and we will send you a quote.

Get help

Host your GTM server at Stape