Silence alerts · Verification tier
Hear about a dead pixel in minutes, not weeks.
When a tag stops firing, TracerKit opens an alert on your dashboard, emails your team, and resolves it automatically when the tag recovers.
the problem
Why this breaks today.
Silence doesn't announce itself.
A broken tag produces no error anyone sees. The first signal is usually a campaign report that looks off, long after the money was spent.
Dashboards need someone to look.
A health page is only useful if someone checks it. Alerts come to you.
how it works
How TracerKit handles it.
An alert when a tag goes quiet.
When a tag goes quiet for longer than its silence window, TracerKit opens an alert on your dashboard and emails your organization's owners and admins. Set the window per tag, so a checkout pixel and a blog-only tag aren't held to the same clock.
Auto-resolved on recovery.
When beacons come back, the alert closes itself and you get told it recovered, so open alerts always mean something is still wrong.
Drift alerts too.
If a platform's reported count drifts from what TracerKit observed by more than 20% on a meaningful sample, that opens an alert as well.
Your channels, per organization (Agency plan).
On the Agency plan, route alerts to your own Slack webhook and inbox so each client's alerts go where they belong. At the Verification tier, alerts appear on your dashboard and are emailed to your owners and admins.
questions
Asked and answered.
How fast will I hear about a broken tag?+
Health runs every 15 minutes, so a tag going silent is caught on the next run rather than in next month's report.
Will low-traffic pages spam me?+
Drift alerts need a minimum sample before they fire, so a quiet hour with two events doesn't page anyone.
Which channels are supported?+
Slack (incoming webhook) and email. Configure your own channels on the Agency plan; at the Verification tier, alerts appear on your dashboard and are emailed to your owners and admins.
the terms behind it
What is server-side tracking?
Server-side tracking sends conversion events from your server to ad and analytics platforms, instead of relying only on scripts in the visitor's browser.
What is Event Match Quality?
Event Match Quality (EMQ) is Meta's 0 to 10 score for how well the customer information on your events lets Meta match them to Meta accounts.
more of what you get
Tag manager
A tag manager that lives outside your repo.
Version history
Every tag change, on the record.
Tag verification
Know every tag is actually firing.
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.