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 #21 Reviewed Oct 24, 2026
Watch: reading the reconciliation
How Anacoic compares your store's orders with the purchases Meta recorded, what each status means, and why a day can say Not enough data.
The reconciliation is the heart of Watch. For each day, in your site’s timezone, it puts two numbers side by side:
- Orders: the eligible orders your store took that day. Source: your store.
- Recorded: the Purchase events Meta received for your dataset that day. Source: Meta.
Every number on the page carries its source (your store, Meta, or both) and its window (the day or days, with the site’s timezone). Hover over a number, or use a screen reader, to see them, for example “Source: Store. Window: Oct 21, 2026 (Europe/Prague)”. The card’s heading also names the whole window it shows. Meta’s numbers are Meta’s own; we show them as Meta reports them and never estimate what a gap is worth in money.
Which orders count
Only orders that should have produced a Purchase event on your site count as eligible:
- paid orders, including ones refunded later (the purchase still happened);
- from your online store. Point-of-sale orders, draft orders created by your team, subscription renewals and orders from other channels don’t fire a browser Purchase event, so they’re left out;
- not test orders.
Pending and cancelled orders don’t count either. Reconciliation compares counts of orders, not money, so a store that sells in several currencies is compared as one.
What each status means
The gap is the share of eligible orders Meta didn’t record: (orders − recorded) ÷ orders.
| Status | When |
|---|---|
| On track | Meta recorded within 10% of your orders, either way. |
| Needs a look | Meta recorded fewer, and the gap is more than 10% but no more than 25%. |
| Off track | Meta recorded fewer, and the gap is more than 25%. |
| More than the store | Meta recorded more than 10% more purchases than you had orders. This usually means the same purchase is being sent twice without a shared event ID. |
| Not final yet | The day isn’t settled. Meta keeps counting late events, so a day is judged from 06:00 the next morning, in your site’s timezone. The day says so next to its status. |
| Not enough data | We can’t compare this day honestly. The reason is always shown with it; see below. |
You can change the three thresholds for each site in Settings, then Alert settings, under Tolerances. “On track” can be set between 1% and 50%, “needs a look” above that and up to 100%, and “more than the store” between 1% and 100%.
Quiet days
On days with fewer than 10 orders, one missing event moves the gap a lot. Such days are still compared, but the alerts look at the last seven complete days added together instead of single days.
Why a day says “Not enough data”
We never show a missing number as zero. When we can’t compare a day, it reads Not enough data, followed by the reason in plain words, in the cell whose number is missing or next to the day’s status:
| What it says | What it means |
|---|---|
| ”the platform has not sent numbers for this day yet” | Meta gave us no exact count for the day. That happens for days older than the 7 days Meta shares, or when one of Meta’s hourly figures couldn’t be read. |
| ”Meta reports in whole hours, and your timezone’s day starts partway through an hour, so we can’t split that hour’s purchases between the two days” | Your site’s timezone is offset from UTC by a half or quarter hour, and Meta’s hour around your midnight held purchases. See the timezone case below. |
| ”the store had no eligible orders this day” | Nothing to compare: no eligible orders, and Meta recorded none either. The store’s cell reads Not enough data rather than 0. |
| ”we don’t have store orders for this day yet” | Before your store’s first orders reached us, while the first import is still running, or after the store connection stopped working. Unknown orders aren’t zero orders, so we don’t compare, and the store’s cell never shows 0. |
When no day is final yet, or nothing has synced, the card itself reads Not enough data, with “no day is final yet” or “waiting for the first sync”.
Half-hour and 45-minute timezones
Meta reports its counts in whole hours, in UTC. We move them into your site’s timezone so the days match your store’s. If your timezone is offset from UTC by a half or quarter hour (for example India, UTC+05:30, Nepal, UTC+05:45, or Adelaide, UTC+09:30 or +10:30), one of Meta’s hours starts before your midnight and ends after it. When that hour held purchases, we can’t tell which day they belong to, so both days show Not enough data, with the whole-hours reason above, instead of a guess. Days where that hour was empty are compared as usual. If your shop sells through the night, this can happen on most days.
How fresh it is
Each time new orders or Meta numbers arrive, we compare today and the seven days before again, so late orders and late Meta events are picked up. Days further back stay as they were, unless you import older orders, in which case those days are compared again too.
When it doesn’t look right
- Check that the site’s timezone matches the one your store and your Meta ad account use.
- If Meta records far fewer purchases, see Fewer purchases recorded than the store sold.
- If Meta records more, see More purchases recorded than the store sold.