Guide3 min

Find your server-side GTM domain

Server-side Tag Manager loads from your own domain instead of Google’s. The scan usually finds it by itself and shows it on its tagging server card. This guide is for checking by hand.

Open DevTools on your site

Go to a page where Tag Manager should load, your homepage is fine, and open the developer tools: F12 or Ctrl+Shift+I on Windows, Cmd+Option+I on a Mac. Right click and Inspect works too. Chrome, Firefox, Edge and Safari all have it.

Search for the snippet

In the Elements tab, open search with Ctrl+F or Cmd+F and type gtm.start. That string is in every Tag Manager snippet.

Read the j.src line

In the highlighted script, find j.src=. The address after it tells you which setup the site runs. www.googletagmanager.com is standard Tag Manager. Your own subdomain, like sgtm.yourcompany.com or data.yourshop.com, is server-side. Copy that address.

Enter it in the tag settings

Open the site and go to Monitors › Tags. On the Tag Manager row, open ··· › Change settings, tick Server-side container and paste the address. Every check now also asks your container, and you hear it the day it stops answering.

Tips

Cannot find the script?
Open the Network tab, reload, and filter on script. A request to a domain that is not googletagmanager.com is your server-side address.
Loaded by another tag
Some sites load Tag Manager from inside another tag. If you only see standard Tag Manager, look for a tag that loads a second container.
Two containers is possible
A site can run a standard and a server-side container. Each gets its own monitor.
Server-side GTM is not the same as server-side tagging in GA4
GA4 has its own server-side measurement with its own endpoint address. That is set on the GA4 tag, not on the Tag Manager row.
Stape and Taggrs
The scan decodes their loaders, so a site behind one is never reported as missing its Tag Manager.
Try it on your own site
First month 50% off on a monthly plan.