TL;DR: Most brands only track campaign outcomes. Signal health metrics track whether those outcomes are based on real data. Below 85% event capture rate, your ad platforms are optimizing blindly. This post breaks down the six metrics that tell you exactly where your signal is breaking down and what it is costing you.
Most performance marketing dashboards measure the same things: ROAS, CPM, CTR, conversion rate, spend by channel. All essential. None of them tell you whether the data underneath is actually correct.
A campaign can show a 4x ROAS while missing 35% of its actual conversions. An EMQ score can sit at 5.8 for months without anyone noticing. A consent misconfiguration can block legal US signals for six weeks before the ROAS decline surfaces.
Performance metrics measure outcomes. Signal health metrics measure whether those outcomes are based on reality.
Performance dashboards assume the data is correct. Signal health dashboards verify it.
Performance dashboards measure campaign results on the assumption that the underlying data is complete and accurate. Signal health dashboards measure whether that assumption holds.
You need both. Most teams only have one. That gap lets problems silently compound for months: signal loss, identity fragmentation, consent misconfiguration, bot contamination, and platform match degradation.
In over $1.2B GMV worth of audits, Blotout has found that 40% of signals are lost across Shopify stores due to incorrect consent setups alone.
A signal health dashboard tells you:
- Event accuracy. Whether the events your campaigns optimize against reflect real data or an incomplete version of it.
- Identity resolution. Whether returning users are recognized or showing up as strangers every session.
- Platform match quality. Whether Meta, TikTok, and Google receive data they can actually optimize against.
- Consent configuration. Whether your setup blocks legal signals you're entitled to send.
1. Event capture rate
Event capture rate is the first number to check. It measures the percentage of actual conversion events your tracking infrastructure captured relative to your source of truth.
For example: Shopify order records. If Shopify recorded 1,000 purchases and your tracking infrastructure captured 820 purchase events, your event capture rate is 82%.
Here's what this looks like in practice. A DTC skincare brand runs Meta prospecting campaigns driving $200K/month in revenue. Shopify shows 2,400 purchases. Their tracking infrastructure only captured 1,920. That's an 80% event capture rate.
The remaining 480 purchases never reached Meta's algorithm. Meta doesn't know those buyers exist, can't learn from their profiles, and can't find more people like them.
Anything below 85% is a structural problem. Below that threshold, ad platform algorithms optimize against a meaningfully incomplete picture of your converters. Attribution tools distribute credit across a fraction of real touchpoints. Everything downstream is compromised.
2. Known rate
Known rate measures the percentage of sessions or events where a first-party identity was successfully resolved. Out of the total users interacting with your store, how many did your infrastructure actually identify?
A high known rate means your identity graph is functioning:
- Cross-session recognition. Returning users are identified across sessions.
- Conversion matching. Conversion events tie to real customer profiles.
- Audience quality. Lookalike audiences are built on identified, high-quality user records.
Here's what this looks like in practice. A fashion ecommerce brand runs $150K/month on Meta and Google. Their known rate sits at 42%. That means 58% of their site traffic is anonymous to their infrastructure.
A returning customer who bought a jacket last month, now browsing new arrivals on a different device, shows up as a brand new visitor. Meta treats them as a prospecting conversion instead of a returning buyer. The brand's audience signals erode, and prospecting campaigns keep re-acquiring existing customers at full cost.
60% is the target for most ecommerce stores. A low known rate means a significant share of your traffic is anonymous to your infrastructure, even if those users have previously purchased from you.
3. Event Match Quality
EMQ is Meta's score for how reliably it can match your conversion events back to real Facebook and Instagram users. It runs from 0 to 10 and is one of the most direct levers on campaign optimization quality.
A low EMQ results from three things: low event capture rate, missing match parameters, or poor identity resolution. Strong server-side infrastructure drives EMQ up directly.
Here's what this looks like in practice. A DTC supplements brand spends $300K/month on Meta. Their EMQ sits stuck at 6.2. They send purchase events through the browser pixel, but the pixel fires inconsistently on mobile Safari and misses hashed email on 30% of checkout completions.
Meta matches roughly 60% of events to real users. The other 40% are unattributable. The brand's cost per acquisition creeps up by 15% over two months, and nobody connects it to signal quality because ROAS still looks "okay."
Brands running server-side CAPI with enriched customer data routinely hit 8 to 9. Pixel-only tracking typically produces scores between 5 and 7.
4. Consent opt-in rate by region
Consent opt-in rate measures the percentage of users who opt in to tracking in a given geographic market. It belongs in a signal health dashboard because consent configuration directly determines whether you send the signals you're legally allowed to send.
Track this by region because opt-in rates vary significantly by market. EU opt-in rates under GDPR are structurally lower. US opt-in rates in low-restriction markets should be significantly higher.
Here's what this looks like in practice. An apparel brand selling globally runs the same consent banner across all markets. Their EU opt-in rate is 38%. Their US opt-in rate is 41%.
Those numbers should not be that close. The US has far fewer consent restrictions, yet the brand's implementation applies the same GDPR-grade friction everywhere. The result: they voluntarily suppress 30%+ of legally collectible US signals. That's not user choice. That's a configuration error costing them signal volume every day.
A well-designed consent experience in a low-restriction US market produces opt-in rates above 70%. Anything below that points to an implementation problem, not user choice.
5. Server-side event coverage
This metric measures the percentage of your total conversion events captured server-side versus browser-side only. It tells you how much of your signal is protected from browser-level blocking in real time.
Browser pixels are necessary. They can also be blocked by ad blockers, iOS restrictions, or consent decline. Those lost events go undetected.
Here's what this looks like in practice. A home goods DTC brand runs both Meta and TikTok campaigns. They rely on browser pixels for 70% of their event capture. During a holiday sale, 25% of their mobile traffic uses browsers with aggressive tracking prevention.
Those purchase events never fire. The brand's Meta ad set underreports conversions by 18% for the entire sale period. Their server-side coverage sat at only 65%, leaving a third of their signal exposed to browser-level loss.
A store running full server-side CAPI has coverage approaching 100% regardless of browser state. Target above 90% server-side coverage for all events, especially purchase events.
6. Paid signal quality score
Paid signal quality is a composite metric that combines EMQ, event capture rate, and match parameter completeness into a single score. It represents how well your ad platforms receive and interpret your conversion data.
This metric most directly connects signal health to campaign performance. A low score means your budget feeds algorithms working with degraded data. The score only improves when the entire infrastructure layer improves together.
Here's what this looks like in practice. A fitness apparel brand spends $500K/month across Meta, Google, and TikTok. Their paid signal quality score is 6.1 out of 10. EMQ is at 7, event capture rate is 81%, and match parameter completeness is 72%.
Every platform receives a diluted picture of who's actually buying. Their prospecting campaigns over-index on easy-to-match profiles while missing high-value segments entirely. Fixing any one metric in isolation won't move the needle.
No single metric tells the full story
Signal health metrics don't reveal much in isolation. Each one points to a different layer of the infrastructure. Understanding how they align together is how you find the actual problem.
Event capture rate tells you if events are getting through. Known rate tells you if identities are resolving. EMQ tells you if Meta can use what you're sending. Consent opt-in tells you if configuration blocks legal signals. Server-side coverage tells you if you're protected from browser-level loss. Paid signal quality tells you if all of it adds up.
Stack them together and the diagnosis becomes clear.
EdgeTag surfaces every one of these metrics in a single view
EdgeTag's signal health dashboard covers all six:
- Event capture rate measured against Shopify order records.
- Known rate across sessions.
- EMQ by platform.
- Consent opt-in rates by region via ConsentIQ.
- Server-side coverage by event type.
- Paid signal quality score across Meta, Google, and TikTok.
Most brands running this audit for the first time find significant gaps they had no visibility into. EdgeTag is the growth infrastructure layer that fixes signal loss in a single implementation. Live in 15 minutes. No GTM. No GCP.
Run a free signal health audit on your store. See exactly where your events, identity, consent, and match quality stand today.
