SGTM.space power-ups: when to turn them on

Open a container and go to Add-ons. Each add-on is a card with an Enable button. For Better Loader you first enter your Web GTM container ID on the card. Once an add-on is on, Settings on its card opens its settings page. Changes usually reach the edge within a minute.

• Better Loader and Preview Mode are available on every plan, the free one included.
• Cookie Extender, Bot Filtering, Request Proxy and Request Enricher are included in every paid plan.
• Cookie Extender, Request Proxy and Bot Filtering's dataLayer option require Better Loader, as does every add-on that runs on your page. Request Enricher, Preview Mode and Bot Filtering itself work with any snippet. Turning Better Loader off turns its dependents off too.
• A card outside your plan shows which plan it is available from. If you move to a plan without an add-on, it is switched off and its settings are kept.

Live Logs requires Better Loader too: its script brings the page agent to the tester's page.

Live Logs Enhance, the last add-on on the Add-ons tab, is optional: two GTM tag templates that let Live Logs also show which tags fired in your web and server containers. Switch it on to open its setup page, with one part for the web container and one for the server container: the steps, the download and a check for each. The server check sends one test event through your server container, and only when you ask for it.

Normally the browser downloads gtm.js from googletagmanager.com, which ad blockers know well. Better Loader serves it from your own load domain, such as load.k7q2x.example.com, under a random script name with no GTM ID in the URL. Blockers that match on Google's domain have nothing to match, so more visits load your tags at all.

When to enable it: almost always. It is the base for the other add-ons and it recovers the data that is lost before any tag runs.

1. 1 On Add-ons, enter your Web GTM container ID on the Better Loader card (the GTM-XXXXXXX of the container on your website, not the server container) and click Enable.
2. 2
   Go to the DNS tab and find the CNAME for the load domain. The tab lists it from the start, so it may be verified already. If not, add it where your DNS is managed (DNS only on Cloudflare) and click Check DNS.

   Type

   CNAME

   Name

   load.k7q2x

   Value

   eu.sgtm.space

   Proxy

   DNS only

3. 3 Wait until the loader is live. After the DNS check passes, the HTTPS certificate is issued automatically, which usually takes a few minutes.
4. 4 Copy the Install snippet and replace your current GTM snippet in the <head> with it. Copy the Noscript fallback and put it right after the opening <body> tag in place of the old noscript block.
5. 5 Reload your site in a normal window (not GTM Preview) and open DevTools. A script with a random name should load from load.k7q2x.example.com, and requests should go to your tagging subdomain. With Request Proxy on they no longer contain collect, so filter by the domain.

Request Proxy (the Request Proxy + Bundle card) disguises the analytics requests (/collect, /g/collect, /data) and scripts sent to your tagging and loader domains, so ad blockers cannot match them by path. Without a tag serving path, Google tag scripts load through your loader domain with Google as the fallback. With a tag serving path set, they come from your tagging domain without that fallback, so a refused or slow request delays that tag. The proxy ships inside the Better Loader script, so there is nothing to configure or install.

When to enable it: when a noticeable share of your visitors use ad blockers, which is common for tech and younger audiences.

Cookie Extender re-issues the analytics and ad cookies your tags already set, from your tagging domain, and renews them on each page visit up to each vendor's own lifetime and your maximum (default 390 days). It never creates a cookie. You choose the vendors it covers (Google, Meta, TikTok, Microsoft, LinkedIn and more).

When to enable it: when you care about returning visitors and attribution over weeks, for example longer sales cycles or remarketing. It refreshes cookies whenever a request reaches your tagging or loader domain, so send your events to the tagging domain and turn on Request Proxy too, because a request stopped by a blocker refreshes nothing.

Bot Filtering recognises clearly automated traffic at the edge, for example requests with no User-Agent, crawler or HTTP library User-Agents, or requests missing the headers every browser sends. It is analytics hygiene, not a security control. It has two modes:

When to enable it: when bots inflate your reports or your request count. HTTP libraries look like bots, so in Block mode requests from your backend, app or webhooks need an exception. /mp/collect is on the Exceptions list by default. Add any other path your backend or webhooks send to.

Request Enricher adds visitor context to every request your server container receives: country, time zone, network, device, browser and a bot flag, as request headers. Read them in server GTM with a Request Header variable, for example X-SGTM-Geo-Country, and send them to GA4 or another destination. Detailed location, including the IP address, stays off until you opt in. It does not need Better Loader.

When to enable it: when a server tag needs data the browser hit does not carry, such as device type or country for a CRM or ad platform.

Server Preview only shows requests that carry the preview header of your Tag Assistant session. Requests from webhooks, CRMs or your own backend do not carry it, so they never show up there. Preview Mode forwards them into your open server Preview session for 60 minutes. It is on every plan, the free one included, and does not need Better Loader.

1. 1 Open Preview in your server container. In the top-right menu choose Send requests manually and copy the value of the X-Gtm-Server-Preview header.
2. 2 On Add-ons, click Settings on the Preview Mode card and paste the value as the Preview token.
3. 3 Optionally narrow it down with a Path prefix, such as /webhooks, and a Source IP. When both are set, both must match.
4. 4 Click Save and start for 60 minutes, then send a test request from your backend and look for it in server Preview.

When to enable it: when you test purchases or refunds sent from your backend, Measurement Protocol calls or webhooks from a payment provider or CRM.

Google Tag Gateway loads GTM and the Google tag from a path on your website itself, such as www.example.com/Tg7Kq2mXab/, through Google Tag Gateway in your own Cloudflare account or CDN. The Google tag also sends its Google Ads pings through that path. It is included in every paid plan and requires Better Loader: your snippet stays, and Better Loader loads GTM itself if the gateway fails.

When to enable it: when your website runs behind Cloudflare or another CDN that supports the gateway, and you want Google's scripts and Ads pings on your own domain. Lesson 11 walks you through the setup.