Check that tracking is healthy
Read the Tracking health score, the match-key coverage and the log of events sent to Meta, and fix what they flag.
On this page4 sections
The Tracking health card gives a score out of 100 from six checks. A check with a clock icon has nothing to judge yet, such as no visits or no registrations, and is left out of the score. The grade reads Excellent from 90, Good from 70, Needs work from 40 and Not tracking below that.
| Check | Points | Full marks when |
|---|---|---|
| Meta pixel | 20 | A pixel ID is saved. |
| Conversions API token | 20 | An access token is saved. |
| Tracker events | 15 | Visits arrived in the last hour. A quiet hour still scores well. A day of silence on a space that had traffic shows a warning. |
| Server events accepted | 15 | Meta accepted at least 98% of server events in the last 7 days. Below 90% turns red. |
| Match keys on registrations | 20 | Registration events carry email, phone, fbc, fbp and external ID (the average coverage of those five). |
| Deduplication | 10 | No event was sent twice, and a pixel is set so browser and server events can pair. |
The Event match quality card shows how often each customer detail is attached to your registration events over the last 7 days, and an estimated score out of 10. The estimate is Bottega's own. Meta's Event Match Quality score in Events Manager may differ, and Meta's is the one your ads use.
| Key | Why it can be low |
|---|---|
| Email, phone | Both come from the registration form, so they should be close to 100%. |
| Click ID (fbc) | Only exists when the visit came from a Meta ad click. Organic, email and TikTok traffic lowers it. |
| Browser ID (fbp) | Set by the pixel. Missing when an ad blocker stops the pixel. |
| External ID | Bottega's own visitor ID, hashed. It should be close to 100%. |
Server events · 7 days shows, per event name, how many Meta accepted and rejected. Below it on the page, Recent Conversions API events lists the last 40 server events with their Status (Accepted, Sending or Rejected), the number of Match keys sent, and a Detail column with Meta's error message for rejected events. Hover a cut-off error to read it in full.
For a visit-by-visit view with browser and server sides paired, open the Event debugger tab. The statuses are explained in Test your Meta tracking with Test Events.
| What you see | Why | What to do |
|---|---|---|
| Many rejected events | Meta refused the token or the pixel ID, often because the token was revoked or was generated for another pixel. | Read the Detail column, generate a new token on the right pixel, and click Replace on Setup & health. |
| Deduplication shows events sent twice | Bottega sent the same event ID to Meta more than once. Bottega is built to prevent this, so it points to a fault. | Contact GOATEDX with a screenshot of the card. |
| Event IDs set, add the pixel to pair them | Server events are flowing but there is no pixel ID. | Add the pixel ID in step 1. |
| Low Click ID (fbc) coverage | Many registrations don't come from Meta ads. | Nothing to fix. Check that your Meta ads use a tracked link so fbclid reaches the lander. |
| No server events yet | No token, or no visits since it was saved. | Save the token, then open a lander. |
Read next
Something here out of date? Tell us and we'll fix the guide.