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 usWatch Doc #23 Reviewed Oct 24, 2026
Watch: alerts and what to do about them
Every check Anacoic runs on a site, when it opens an alert, and what to look at when it does.
Every new site starts with a set of checks switched on. When a check finds a problem, Anacoic opens an alert. You see open alerts on the site’s overview and under Alerts in the sidebar. Each alert states the numbers it’s based on, where they come from (your store, Meta) and which days and timezone they cover. It never puts a money figure on a gap.
You can switch each check on or off, and change its settings, in Settings, then Alert settings, under the site. Owners, admins and members can do that; choosing where a check sends is for owners and admins (see alert channels).
How an alert moves along
- Open: the check found a problem.
- Acknowledged: someone on your team has seen it and marked it so. The alert stays until the problem goes away.
- Resolved: when the check no longer finds the problem, the alert resolves by itself. You can also resolve it yourself; then it doesn’t open again straight away, only once the problem has cleared and comes back.
Each alert is critical or a warning.
Messages about alerts go out by email and to Slack. You hear when an alert opens and when it resolves, with a reminder once a day (three at most) while it stays open and nobody has acknowledged it. Acknowledging stops the reminders. During quiet hours warnings wait and critical alerts still go out. The alert channels page has the details.
”Not checked”
A check we can’t run yet shows Not checked next to its name in Alert settings. It can’t open an alert, so it never sends anything, and it is never shown as fine. The same goes for a figure Meta didn’t answer for on the site’s overview: it reads Not checked, never On track.
The checks
Fewer purchases recorded than the store sold
Warning. Compares your store with Meta.
Opens when, on each of the last 2 complete days, Meta recorded noticeably fewer purchases than your store had eligible orders (a day that needs a look or is off track in the reconciliation). On quiet sites, with fewer than 10 orders on one of those days, it looks at the last seven complete days added together instead, and needs at least three of them. You can change the number of days, from 1 to 14.
What to check:
- That the Purchase event still fires on the order confirmation page (Meta Events Manager, Test events).
- If you send server events, that they still arrive and carry the same
event_idas the browser event. - Recent changes: a new theme, a checkout app, a consent banner or a tag manager publish.
More purchases recorded than the store sold
Warning. Compares your store with Meta.
Opens when, on the latest complete day, Meta recorded more purchases than your store had eligible orders, by more than your site’s “more than the store” setting (10% unless you change it). In the reconciliation, that day reads More than the store.
What to check:
- Purchase may be firing twice: once from the pixel and once from the server, without a shared
event_id. - A second pixel, or another app, sending Purchase for the same orders.
Meta’s Event Match Quality dropped
Warning. Meta’s own figure.
Opens when Meta’s Event Match Quality for Purchase fell by 1.0 or more since a week ago, or is below 5.0. You can change the size of the drop.
What to check: which customer details your server events send. A missing email or phone match key lowers Meta’s score.
Meta can’t deduplicate Purchase events
Warning. Meta’s own feedback.
Opens when Meta reports server Purchase events without a matching browser event ID.
What to check: the browser and the server Purchase events need the same event_id, so Meta can count each order once.
A connection needs attention
Critical.
Opens when a store or Meta connection has failed more than once in a row and we can’t read it any more. Until it’s fixed, the checks and reports that rely on it are paused.
What to check: reconnect the account from the site’s Connections. A changed password, a removed permission or an uninstalled app is the usual cause. The connection shows what went wrong in plain words.
No orders from the store
Warning. Your store’s connection.
Opens when we haven’t received a single order from your store in 24 hours, while the store took more than 5 orders a day on average over the last 28 days. You can change the number of hours, from 1 to 168.
What to check: that the store is taking orders, and that its connection or webhook still sends them.
A note on “Purchase events stopped arriving”
This check needs hour-by-hour event numbers, which Anacoic doesn’t collect yet. New sites don’t get it, and where it’s already in the list it shows Not checked. The two purchase checks above catch the same problem a day later.
When an alert surprises you
- Open the site’s overview and look at the days the alert names.
- Check that the site’s timezone matches your store’s and your ad account’s.
- Still unsure? Write to [email protected] with the site’s domain and the alert’s title.