Practical articles on EU hosting, first-party data collection, GTM setup and agency workflows, written for marketers and analytics teams.
From account to first hit: account, domain, DNS record, tracking script, power-ups, proof, tracking audit, alerts and an infrastructure check - in the order you'll actually do them.
New to server-side tagging? These take you from zero to live.
What a tagging server does, how it differs from browser tags, what it changes for cookies, ad blockers and consent, and what sGTM hosting means.
From account to first hit: account, domain, DNS record, tracking script, power-ups, proof, tracking audit, alerts and an infrastructure check - in the order you'll actually do them.
From empty container to published: the Google Analytics tag, a first-party loader and the switch that routes events to your server container.
Create the container, choose manual provisioning, then connect Google Tag Manager or paste its config into Measurebase, plus the two clients every setup needs.
Filtering, refreshing on demand, and exporting a CSV for any date range your plan's retention allows.
What each request type and status badge in your logs actually means · including why some 400s are shown as benign.
Requests per minute for the last 30 minutes: what counts, how fresh it is, and how to read a gap or a spike.
Adding a second GTM setup on the same main domain, how the DNS setup works, and what happens at your plan's domain limit.
Host the same container, keep or change the hostname, switch DNS without a gap, keep cookies and click IDs, verify, retire the old host.
One guide per platform: the IDs you need, what the Measurebase import creates in both containers, deduplication and what the audit checks.
Pixel and Conversions API as one deduplicated stream: IDs, the import, Event Match Quality, consent, testing and the audit checks.
Conversion Linker, server-side conversion tags, enhanced conversions, click IDs and what the Google Ads connection audits.
Pixel and Events API deduplicated on one event ID, ttclid recovery, testing and the audit checks.
Insight Tag plus server conversions for purchases and leads, li_fat_id, consent and the audit checks.
Tag ID, advertiser ID and token, the import, deduplication, epik recovery and the audit checks.
Snap pixel plus the Conversions API, deduplication on client_dedup_id, consent, testing and the audit checks.
UET tag ID, token and customer ID, the import, why the two sides do not deduplicate, msclkid recovery and the audit checks.
Pixel ID and API key, the import, the oppref click ID and its cookies, deduplication, testing and the audit checks.
The step-by-step guide and its chapters: property, tag, events, e-commerce, and what changes once you go server-side.
Property to key events in 14 steps, with what you should see after each one and a checklist at the end.
Property, data stream, retention and key events: the GA4 side of a clean setup, step by step.
The Google tag, the Initialization trigger, the Tag Assistant check and the double-install test.
What each toggle collects, which four to keep on, and why form interactions mislead.
Plan your groups, build a RegEx Table, send content_group with every event, and find it in your reports.
One property for every language, cross-domain tracking where needed, and a page_language dimension.
Few key events, the right counting method, and the hand-off to Google Ads.
The data layer, the purchase event and its items, the test order and the five mistakes that break revenue.
How events flow from your site through a server container to Google Analytics · and what to watch in debug mode.
Reprocessing delays, split tracking paths, server-to-server events without session data, missing referrers and consent: how to tell them apart and fix each one.
Install Measurebase where your shop runs: Shopify, WooCommerce, WordPress and Shopware.
Storefront, checkout and server-side order events through your own tagging host · one deduplicated purchase, identity that survives to the conversion.
Plugin, connection, web container ID, WooCommerce data layer and server-side purchase backup, matching GTM template, your own domain, test.
Connect once and the plugin installs your tags, pushes the full GA4 ecommerce and lead-form dataLayer, and backs every purchase up server-side with retries.
The first-party loader, ad-block protection and Consent Mode installed for you, GA4 ecommerce events, and a server-side purchase backup · for self-hosted Shopware 6.
The thinking behind first-party, EU hosting and healthy tracking.
What the Destination tags for GA4, Google Ads, Floodlight and Merchant Center change, how to switch a container over, and the defaults to check.
Which domain a cookie belongs to, what each browser does with it, why that decides your attribution windows and audiences, and what server-side changes.
How the linker works, what to configure in the Google tag and the Conversion Linker, how Measurebase domains fit, and what the audit checks.
Schrems II, data residency and what it means for your analytics stack when tags leave the browser · and the continent.
The four signals, basic versus advanced mode, and what your server container has to do with the consent state.
Plain definitions of the terms you meet when you set up server-side tracking, with a link to the article that goes deeper.
The issues our tracking audit finds most often, and how to fix them.
Safari 16.4 caps cookies from a tagging subdomain on another server at 7 days. How to check it, and how serving tracking from your own domain fixes it.
Tracking before the banner is answered, or after a refusal: the usual causes and how to fix them in Google Tag Manager.
The five causes of page views and conversions counted twice, and how to remove each.
GA4 and Google Ads hits that go straight to Google instead of your tagging server, and how to set the server container URL right.
What blockers block, what your own subdomain and masking recover, and what no setup recovers.
Where the debug session attaches, why the first server container URL matters, test hits from your site and from Shopify checkout, and what to check when the preview stays empty.
Connect Claude, ChatGPT, Cursor and other tools through the Measurebase MCP server: one guide per client, same server, same token.
Link an AI assistant to your account in two clicks and ask your tracking questions in plain language - read-only by default, revocable, roles respected.
Add Measurebase to ChatGPT as a custom connector and ask your tracking questions in plain language - the same read-only-by-default connection, in another assistant.
One config block adds Measurebase to your editor - OAuth handled automatically - so tracking answers arrive without leaving the file you're working in.
One command adds Measurebase to VS Code - OAuth in the browser - so Copilot Chat answers your tracking questions in agent mode, next to your code.
One command registers Measurebase in Google's Gemini CLI - OAuth in the browser - and your tracking answers arrive in the terminal.
One config block adds Measurebase to Windsurf's Cascade - OAuth handled automatically - so tracking answers arrive without leaving the file you're working in.
A pasted JSON block adds Measurebase to AI Assistant in PhpStorm, IntelliJ IDEA, WebStorm or PyCharm, authenticated with a personal API token.
The MCP Client Tool node gives an n8n AI Agent your Measurebase data - a scheduled digest of traffic, alerts and consent per client, delivered to Slack or email.
How each Measurebase power-up works and when to turn it on.
40+ checks across your web and server container, your site, your DNS and certificate · a site crawl for every script and pixel outside GTM · errors, warnings and info · proposed fixes that land in a workspace you publish yourself.
Why Safari caps your tagging subdomain's cookies at 7 days, and how serving tracking from a path on your own website keeps their full lifetime · setup per platform, the checks, and what to switch afterwards.
How your tagging server adds the profit of every order to the purchase event, so Google Ads and Meta bid on POAS instead of ROAS · cost prices from a feed, a file, Shopify, WooCommerce or Shopware.
How one Measurebase domain tracks a site that runs on several subdomains, like www., shop. and app.: one snippet, one tagging host, one session, and what to watch out for.
Why first-party server-side tagging helps with ITP restrictions · and what it can and cannot fix.
How Safari and Brave strip gclid, msclkid, fbclid, ttclid, epik and oppref from landing URLs, and how Click ID Restorer gets each one back.
How IP Anonymization masks addresses before they reach your server container · and how it differs from IP Filter.
How the masked Enhanced loader works, how it carries ad blocker protection, and when the standard gtm.js pattern is used instead.
How IP Filter blocks specific addresses or ranges from ever reaching your server container.
How Data Enrichment adds visitor location, device, bot, AI and ad blocker details as request headers you can read straight from GTM.
How to verify GA4, Ads and Floodlight tags under a granted state · and why this must never stay on for real traffic.
How Measurebase identifies and charts bot and crawler traffic by name · separately from real visitors.
How monitoring catches DNS drift, silent data outages, misdirected traffic and quota limits, and where those alerts show up.
How the guard in your tracking script masks every request so ad blockers can't fingerprint them by URL, and how to switch it on.
How Measurebase catches another customer's site accidentally sending its visitor data into your account.