Tag verification · Verification tier
Know every tag is actually firing.
Per-tag health from real visitors: firing, degraded, silent or blocked by consent, with 24-hour counts and purchase-value checks.
the problem
Why this breaks today.
Installed is not the same as working.
A pixel can be on the page and still never fire: wrong trigger, a race with the data layer, or a consent rule that never lets it through.
Debug tools only see your own session.
Browser extensions and preview modes show what fired for you, right now. They say nothing about the thousands of real visits since.
Purchases with no value poison bidding.
A purchase event that fires before the order total is ready sends a value of zero, and ad platforms optimize on it.
how it works
How TracerKit handles it.
Health from production traffic.
The loader reports each tag's fires and errors. Every tag gets a status, firing, degraded, silent, waiting or blocked by consent, with its last fire and 24-hour counts.
Value integrity on purchases.
Fires that should carry a value but don't are counted separately, so a checkout sending zero shows up as a number, not a hunch.
Plain-English diagnosis.
Findings explain what's wrong, why it hurts your data and the fix, instead of a raw event log.
questions
Asked and answered.
How often is health updated?+
Health is evaluated every 15 minutes from the beacons the loader sends.
Does it work for tags I don't manage in TracerKit?+
Verification watches the tags the loader manages. Move a tag into the dashboard to get its health.
What does "blocked" mean?+
The tag is consent-gated and no visitor has granted its category yet, so it can't fire. That is a consent setup question, not a broken tag, and it's labeled separately.
the terms behind it
What is event deduplication?
Event deduplication is how ad platforms count one conversion once when the same event arrives from both the browser pixel and a server-side API.
What is data layer?
A data layer is a JavaScript object, usually an array called dataLayer, that your site pushes structured events into so tags can read them consistently.
What is Consent Mode?
Google Consent Mode tells Google tags what a visitor agreed to, using signals like ad_storage and analytics_storage, so tags adjust what they do.
more of what you get
Tag manager
A tag manager that lives outside your repo.
Version history
Every tag change, on the record.
Silence alerts
Hear about a dead pixel in minutes, not weeks.
Platform reconciliation
Your numbers, checked against theirs.
First-party proxy
Serve your tags from your own domain.
Server-side forwarding
Conversions that land even when the pixel doesn't.
Stop guessing whether your tracking works.
Tag management is free forever. Paid tiers start with a 14-day trial, no card.