More tracking power, one toggle at a time.
Modules extend your server-side GTM container without touching a single tag. Each one runs at the gateway in front of your container, so it applies to every request the moment you enable it, no redeploy, no restart, no extra cost.
How modules work
They run before your container, not inside it
Your tagging domain terminates at our gateway. That is where modules act: rewriting headers, resolving data, reshaping paths. Your container, and every vendor downstream of it, only ever sees what the gateway decided to pass on. Nothing changes in Google Tag Manager.
Visitor
A browser fires a request to your own tagging domain, first-party by definition.
Gateway
Modules act here: IPs masked, headers added, paths rewritten, cookies re-issued.
Your container
Server-side GTM receives the request, already enriched and already cleaned up.
Vendors
GA4, Meta, TikTok and the rest receive exactly what your tags choose to send.
The catalog
Six modules, three jobs
Some modules remove data before it can leak. Some add data your tags would otherwise have to buy. Some keep measurement working when browsers and blockers get in the way. Pick the ones that match the problem you actually have.
Why we built them this way
Every module is a few lines of gateway configuration, not a plugin running inside your container. That design decision is what makes them fast, safe and free.
Zero latency cost
Modules are native gateway directives, header rewrites and lookups measured in microseconds. There is no extra hop, no sidecar process and no third-party API call in the request path.
No container restart
Enabling or reconfiguring a module updates the gateway configuration and propagates within seconds. Your container keeps serving traffic throughout; nothing is dropped.
Nothing to maintain
No tag templates to import, no custom variables to wire up, no library to keep patched. Modules are part of the platform, so they are updated with it.
Safe by default
Every setting is validated before it can reach the gateway, and every module fails closed: when a value cannot be resolved, the header is dropped rather than guessed.
All modules are included
Modules do not change your bill. Your container costs €15 per month, billed per started day, and every module in the catalog is available on it at no extra cost. There is no premium tier gating them and no per-request surcharge.
Common questions
Do modules require changes in Google Tag Manager?
No. Modules act on the request before it reaches your container, so nothing changes in your web or server container. The only exception is Custom Loader, which gives you a new script tag to paste into your website in place of the standard GTM snippet.
Can I use several modules at once?
Yes, and some are designed to be combined. Anonymizer plus GEO Headers is the clearest example: location is resolved from the real address first, then the address itself is masked, so your tags keep coarse geo data without ever seeing an IP.
How do my tags read the data a module adds?
Enrichment modules deliver their output as ordinary request headers. In server-side Google Tag Manager you read them with the built-in Request Header variable, using the header name listed on each module page.
What happens when I disable a module?
The gateway configuration is regenerated without it and propagates within seconds. Headers it was adding stop arriving, and headers it was rewriting go back to their original values. Nothing in your container needs to change.
Are module settings per container or per workspace?
Per container. Each container carries its own module configuration, which is what agencies need: one client can run the Anonymizer in remove mode while another masks, without any shared state between them.