Why raw numbers lie
Meta reports what it received. It has no way to report what it never got. So when events stop flowing, the count just drops — quietly, with no error, no alert, no red flag anywhere. Three of the most common failures are completely silent:
- A blocked domain. Meta restricts a domain or dataset, and events referencing it are dropped on their side. Your API call still returns success. Raw visit stats still count the traffic. Nothing surfaces the block except a fall in how many of those visits actually get attributed.
- An expired token. A Conversions API token lapses and server-side events stop arriving. The landing page still loads, the ad still spends — only the conversions vanish.
- A collapsed match rate. The match keys degrade, event match quality falls, and Meta throttles optimization even though events are technically landing.
What attribution health actually measures
Instead of trusting the delivered count, health monitoring compares what should have reached Meta against what did — per creator, per domain, per event.
- CoverageOf the conversions we can see on the account side, what share was successfully attributed at Meta? A sudden drop in coverage is the fingerprint of a blocked domain or dead token.
- Match qualityAre events arriving with strong keys? A falling match rate is an early warning that optimization is about to suffer.
- FreshnessAre events still flowing right now, or did they stop? A frozen last-synced timestamp is often the first visible tell of an upstream break.
When coverage collapses but raw visits hold steady, that gap is the alarm — the one number no Meta interface will ever show you.
Brand-free domains make health recoverable
Detection is only half the answer — you also need somewhere clean to go. Because OnlyFans Pixel routes traffic through private, brand-free domains, a domain that gets restricted can be rotated out without touching your funnel or your ads. Health monitoring finds the problem; the domain pool lets you fix it in minutes.
Questions
How can tracking be broken if my ad manager still shows conversions?
Meta’s reporting shows what it received, not what it missed. If a domain gets restricted or a token expires, events simply stop arriving — and the dashboard shows a lower number without any error. Nothing tells you the floor dropped; you only notice weeks later when performance “mysteriously” tanks. Attribution health watches the ratio of expected-to-delivered events so the drop is caught immediately.
What is a blocked domain and why is it invisible?
Meta can restrict a specific domain or dataset for policy reasons. When it does, events referencing that domain are silently dropped — the API still accepts your call and returns success, and raw stats still count the visit, so no interface reveals the block. It only shows up as a collapse in attribution coverage, which is exactly what this monitor measures.
What is event match quality?
It’s Meta’s score for how well your events can be tied back to a real person and click. Weak match keys (missing fbc/fbp, thin signals) lower the score, which throttles optimization even when events are technically arriving. Health monitoring surfaces a falling match rate before it drags delivery down.
What do I do when it flags a problem?
The fix depends on the cause: re-issue an expired Conversions API token, move traffic to a clean brand-free domain if one is blocked, or repair the match keys on the landing page. The value of monitoring is that you learn which one — and that there’s a problem at all — in hours instead of after a bad month.
Find the leak before it finds your budget
Monitor coverage and match quality so a silent break can’t quietly drain a month of spend.