Servero Tracking Health Check

WHAT SERVERO IS, AND WHY THIS EXTENSION EXISTS Servero is a server-side tagging platform: it hosts your Google Tag Manager server container, GA4, Meta Conversions API, and TikTok Events API dispatch behind your own first-party domain, so tracking survives ad blockers, Safari/iOS Intelligent Tracking Prevention, and third-party cookie restrictions that otherwise quietly erase a large share of your conversion data. The pitch, in Servero's own words: recover the conversion data lost to ad blockers, browser restrictions, and missing click IDs, so your advertising and analytics platforms optimize with a complete picture — better match rates, better ROAS, less budget spent optimizing against data that was never actually collected. Pricing is deliberately simple: every plan includes every module — CNAME, SSL, Consent Mode V2, audit log, gateways, and a WordPress plugin — with no add-ons and no surprise bills, priced by traffic volume. Servero positions this as saving $400 to $1,000 a month versus comparable server-side tagging setups elsewhere. Getting started takes a free account, a container deployed under your own subdomain, and a CNAME pointed at it — no infrastructure to run yourself. Who Servero is for: any team running paid ads or first-party analytics that depends on accurate conversion data — ecommerce stores losing purchase events to ad blockers, agencies who need clean attribution to prove ROAS to clients, and any site that has already noticed its ad platforms' reported conversions don't match what actually happened. This extension is the free, no-account half of that story. Before you decide whether you need server-side tagging at all, you should be able to see — on your own site, or anyone else's — exactly what's firing, and whether it's already resilient (server-side) or still fragile (client-side, one ad-blocker update away from silently breaking). That's what Servero Tracking Health Check does, for free, with no account required, on any site. WHAT IT DETECTS A Meta Pixel Helper / GA Debugger equivalent, but for server-side tagging. It detects GA4, GTM, Meta Pixel, TikTok Pixel, and Google Ads on any site and labels every signal client-side or server-side — the one distinction that actually predicts whether that tracking survives real-world browsers, on any vendor's server-side setup, not just Servero's own containers. WHY CLIENT-SIDE VS SERVER-SIDE IS THE SIGNAL THAT MATTERS A GA4 hit sent to www.google-analytics.com is trivially blocked by every ad blocker and increasingly by browser-level tracking protection. The same hit, routed through a first-party subdomain running a server-side tagging container, survives those blocks because the browser sees it as a normal same-site request. Every detection this extension makes is tagged client-side or server-side for exactly this reason. RESULTS YOU CAN EXPECT FROM USING IT Open it on your own site and you'll immediately know whether your GA4/GTM/Meta/TikTok/Google Ads tracking is client-side-only (meaning a meaningful share of it is likely being silently dropped by ad blockers and ITP) or already running server-side (meaning it's resilient). If it's client-side, that's your answer for why ad-platform reported conversions have been running lower than what you know actually happened — and the case for moving to a server-side setup like Servero's. If it's already server-side, this extension confirms it's actually working, shows you the real tag/measurement IDs firing, and lets you inspect the exact payload — client ID, consent diagnostics, click IDs — going out on every hit. TWO TIERS, NO PRESSURE TO SIGN UP "This page" works instantly on any site, no account, no setup. "My container" is for a Servero account holder, adding a live event feed straight from your own container's server-side logs. The free tier isn't a crippled trial — it's a complete, standalone tool that also happens to be the on-ramp to Servero itself. WHAT "THIS PAGE" DETECTS, WITH NO LOGIN Live network classification, as it happens. GA4, GTM, Meta Pixel, TikTok Pixel, and Google Ads requests are classified in real time into a running list, with timestamps and hit-type badges you can filter by. Tag and measurement IDs, front and center. Every detection carries its actual ID — a GTM container ID (GTM-XXXXXXX), a GA4 measurement ID (G-XXXXXXXX), a Google Ads conversion ID (AW-XXXXXXXX), or a Meta Pixel ID — as its own monospace chip next to the vendor name. POST body parameters, not just the URL. Browser performance APIs only expose a request's URL, never its body — and GA4 puts most of a hit's real payload (client ID, engagement time, consent diagnostics, session fields) in the POST body. This extension reads those bodies properly via chrome.webRequest in the background service worker and merges the decoded parameters into each hit's param table — the same class of data a tool like Tag Assistant shows, and structurally impossible to get from a content script alone. Click IDs, from the URL and from cookies. Scans for gclid, fbclid, ttclid, msclkid, epik, fbc, and fbp and shows whichever are present — useful for confirming an ad click actually carried its attribution parameters onto the landing page. Consent state, read from the page's own gtag calls. A content script running in the page's real JavaScript context hooks dataLayer.push and reads the literal arguments passed to gtag('consent', 'default' | 'update', {...}) — Google's documented Consent Mode API — so the values shown are real granted/denied states, not a guess. The one check that genuinely needs a browser extension: HttpOnly cookie verification. Whether your FPID cookie is marked HttpOnly is one of the most reliable signals a server-side tagging setup is configured correctly, and it's structurally invisible to any page or content-script JavaScript by design. This extension checks it properly via the privileged chrome.cookies API in the background worker — no page-level script could ever do this…