Signal health
Know what your signals are missing
before you spend on them.
The trust layer under every report. Which click ids arrived and which were lost, how well each order can be matched, and an alert the day a tag breaks, before the numbers do.
Questions this answers
- How many ad sessions carried the click id Meta needs back?
- Where did the lost ones land?
- Is my match quality a tagging problem or a platform problem?
- Did something break yesterday?
Click-id coverage
Of the sessions that came from ads, how many carried the id the platform needs back?
Per platform: the share of ad sessions that arrived with gclid or fbclid, where the lost ones landed, and a signal-issue verdict with causes, impact and the action to take. The report card trends coverage and match quality week by week.
- Coverage per platform, with the lost sessions located
- A verdict: cause, impact, action
- Coverage split by where the order was placed
- Signals stated as captured, never scored against gaps that cannot exist
Scored here, not in Events Manager
Meta tells you the number weeks later, in aggregate. We score each event from the keys we attach, and name what to add.
Match quality
Scored here, before you send. Not a number Meta hands back weeks later.
Every event is scored from what we attached, per event type, with the missing identifier named and what adding it is worth. The order page shows the signals held and the ones it could not hold, so a 70 is a to-do list rather than a mystery.
- Per order and per event type
- The missing identifier, named and priced
- Match signals held, and add more from the customer record
- Per-platform match evidence on the dashboard
Third-party pixel
blocked
cdn.some-tracker.com/px.js
First-party path · your own domain
arrives
yourstore.com/a7f2k/collect
Attribution coverage
0%
of orders tied to a real source on live stores
Alerts
Tell a tenant their tracking broke before the numbers do.
A rejected host, a browser that stopped reporting purchases, a WhatsApp line that stopped delivering, a product-ID format left unchosen: each opens an incident, notifies, and says what to do. The tag observer records what every other tag on the page did, stitched to the order.
- Critical alert plus email when a product-ID format is unchosen
- Notice when the browser stops reporting purchases
- Say it out loud when a WhatsApp line stops delivering
- The free site scan, before any of this is installed
brand search
₹33,480 spent · ₹1,44,720 back
cheapest growth
retargeting · DPA
₹37,350 spent · ₹1,43,460 back
well past the line
magnesium search
₹55,890 spent · ₹1,37,430 back
profitable
pmax · bestsellers
₹1,13,130 spent · ₹2,33,280 back
just above it
prospecting · advantage
₹1,62,180 spent · ₹1,57,320 back
under break-even
generic supplements
₹1,46,610 spent · ₹39,420 back
loses every order
Inside the module
Inside Signal health
The layer every other number rests on.
Signal Health page
Coverage, match quality, trends, verdicts
Tracking health
Rejected hosts, missing signals per order
Alerts & diagnostics
Incidents, notifications, what to do
Tag layer
Site scan, session timeline, order coverage
Traffic integrity
Bot scoring per page view, kept and reported
Site scan
Free, from the marketing site, nothing to install
Run the free scan on your own site now. It is the first half of this page, before anything is installed.
The other modules
Attribution
Every order credited to the ad that earned it, with the receipt and a match score.
OpenGrowth intelligence
Command Center, Today’s Actions and What We Found: what to do on Monday, priced on your costs.
OpenAnalytics & Insights
Twenty reports on one date window, every one ending in a decision.
OpenAudiences
Segments from behaviour the store records, sized against what Meta can match before they sync.
OpenSee what your signals are missing
Know before you spend.Fix the field, then raise the budget.
Run the free scan, then connect the store and watch coverage and match quality draw themselves from your own orders.