Early access. Watch is open to a small group first, until our Meta app is live for everyone. Everything on this page works for them today.

Talk to us

Watch Doc #22 Reviewed Oct 24, 2026

Watch: the health score

What goes into a site's health score, how each part is weighted, and why a new site may not have a score yet.

The health score sums up a site’s tracking in one number from 0 to 100, with a grade. It’s built only from things we actually observed. Nothing in it is estimated.

What feeds it

PartWeightWhere it comes fromPoints
Meta reconciliation30Your store and Meta, the last 7 complete days added togetherOn track 100, needs a look 60, more than the store 40, off track 20
Event Match Quality for Purchase15Meta’s own score (0 to 10)Meta’s score × 10
Deduplication for Purchase10Meta’s deduplication feedbackOK 100, a warning 50, failing 0
Event coverage for Purchase10Meta’s coverage figure, against Meta’s own goalCoverage ÷ goal × 100, at most 100
Freshness5Anacoic100 when every connected source synced recently enough, else 0

Freshness looks at the sources we fetch from on a schedule, such as Shopify and Meta (a signed webhook sends to us, so it isn’t one). “Recently enough” means within two of the source’s normal sync intervals. A source that keeps failing counts as not fresh. A source that is still setting up and hasn’t synced yet isn’t counted either way.

Event Match Quality, coverage and deduplication are Meta’s numbers, read from Meta’s Dataset Quality once a day. Only Meta can calculate them; we show them as they are.

How the score is worked out

Only the parts we have data for take part, and their weights are scaled up to fill the whole. For example, if a site has the Meta reconciliation (30) and freshness (5) but no Dataset Quality figures yet, the score is (30 × reconciliation points + 5 × freshness points) ÷ 35.

The grade follows the score:

ScoreGrade
90 and aboveA
75 to 89B
60 to 74C
45 to 59D
Below 45F

When there is no score yet

A score needs at least two parts with data. With fewer, the site shows Not enough data with what to do next (“connect a store and Meta to get a score” in the list of sites, “connect Meta or GA4 to get a score” on the site itself) rather than a score, and never a zero. That’s normal for a new site: once the store and Meta are connected and the first complete days are in, the score appears.

When it’s updated

The score is worked out again every time the reconciliation runs, which is after new orders or new Meta numbers arrive. The site’s overview shows when it was last worked out, and Why this score lists each part with its points, its weight and its source. The weekly report shows the score at the start and the end of each week.

Raising the score

  • Reconciliation: see what the alerts suggest for a purchase gap or double counting.
  • Event Match Quality: send more of the match keys Meta asks for (such as a hashed email or phone) with your server Purchase events.
  • Deduplication: send the same event_id with the browser pixel’s Purchase and the server’s, so Meta counts each order once.
  • Coverage: make sure server Purchase events go out for most orders, not only some.
  • Freshness: reconnect any connection that shows Needs attention.