First-party tagging in 15 minutes
Moving to server-side GTM on Measurebase is mostly DNS and copy-paste. You keep your existing GTM containers — we host the server container on EU infrastructure.
Before you start
- A GTM server container with a manually provisioned config string
- A GTM web container ID (e.g.
GTM-XXXXXXX) - Access to your domain's DNS settings
Step 1 — Add your domain
In the Measurebase dashboard, create a new domain subscription. Enter the root domain you want to cover (e.g. acme.nl) and choose a subdomain for the tagging server — the field defaults to mbase (e.g. mbase.acme.nl), or pick your own. Paste your server container config from GTM → Admin → Container settings.
Running a second GTM setup on the same root domain — a different property, or a separate container for a subsidiary brand — just add the domain again with a different subdomain. Each subdomain gets its own independent tagging server.
Step 2 — Point the A record
Create an A record for your chosen subdomain pointing at the IP shown in domain settings. An A record keeps the subdomain genuinely first-party — Safari caps cookies on CNAME-cloaked subdomains at 7 days, and an A record sidesteps that entirely. SSL is issued automatically once DNS propagates — usually within minutes.
Step 3 — Install the client loader
Open the domain in your dashboard and click Generate script. Enter your web container ID and choose the Standard or Enhanced loader. Replace your existing GTM snippet in <head> and <body> with the generated code.
Step 4 — Verify in GTM
In your server container, add a Google Tag Manager: Web Container client with your web container ID in Allowed Container IDs. Publish both containers and check the Measurebase request logs for incoming hits.
Once you're live: power-ups
With setup done, open the domain's Advanced tracking tab to turn on power-ups — nothing to reconfigure in GTM itself, though a few power-ups have their own settings beyond a bare toggle, right on the same subpage. Cookie Keeper extends first-party cookie lifetime past Safari and iOS ITP limits (with a toggle per cookie it recognizes), Click ID Restorer recovers gclid/msclkid stripped from landing URLs, and IP Filter or IP Anonymization handle excluding or masking specific visitor IPs. Switch any of them on or off at any time.
That's it. Your tags now load from your own subdomain, requests are processed in Amsterdam, and you have full visibility in the dashboard.