Your Meta Ads ROAS looks wrong. Maybe it is suspiciously low. Maybe it is suspiciously high. Either way, before you blame the creative, the audience, or the algorithm, check the tracking.
Broken tracking is the most common reason I see advertisers make bad decisions. They kill winning ads because conversions were not recorded. They scale losing ads because conversions were double counted. The ads were fine — the data was lying.
Here are seven checks you can run yourself, in order. They take under an hour, and they will tell you whether your tracking is healthy or whether it needs fixing.
Check 1: Events Manager Overview and Diagnostics
Open Meta Events Manager and select your pixel / dataset. Start with the overview.
- Are events arriving at all? A flat line on a day with real sales is the most basic failure.
- Open the Diagnostics tab. Meta flags real problems here: missing parameters, low match quality, events that stopped arriving.
- Look at Event Match Quality. This score tells you how reliably Meta can tie your events to the people who saw your ads. Low match quality means your campaigns are optimizing on weak signals — a common cause of erratic performance.
If Diagnostics shows warnings, do not ignore them. They are Meta telling you exactly what is wrong.
Check 2: Test Events — Fire a Real Purchase
The Test Events tool shows you events as they arrive, in real time. Use it.
- Open Test Events in Events Manager.
- Go to your store in a separate tab and complete a test purchase (or submit a test lead, depending on your funnel).
- Watch the events arrive in Test Events.
You should see the full sequence: page view, add to cart, checkout, purchase — each once, with the right value and currency. If a step is missing, that event is not firing. If a step appears twice, you have a duplication problem (see Check 4).
This is the single most useful check on this list. Do it before you change anything else.
Check 3: Browser vs. Server — Is the Conversions API Running?
If you have server-side tracking set up (and you should — see our server-side tracking setup guide), verify both sources are sending.
In Events Manager, look at the event source breakdown for your Purchase event. You should see events arriving from both the browser pixel and the server (Conversions API). If you only see browser events, your server setup is not sending — or is not connected to the right dataset.
Also check the ratio. If server events are a tiny fraction of the total, the server connection is partially broken — often a misconfigured tag, a missing event, or a server container that stopped running.
Check 4: Deduplication — Are Purchases Counted Twice?
Deduplication is where most stores go wrong. When both the browser pixel and the Conversions API report the same purchase, Meta merges them into one conversion — but only if both events carry the same event ID.
How to check:
- In Test Events, click into a single purchase. It should show one merged event with both a browser and a server source.
- If you see two separate purchase events for one test order, deduplication is failing, and your ROAS is inflated.
The fix is technical but straightforward: make sure your pixel and your server send the same event_id for the same action. If you are using server-side GTM, this is a standard configuration — but it is also the step most setups get wrong.
Check 5: Domain Verification and Event Coverage
This one is easy to forget and painful to miss.
- Is your domain verified in Business Settings? It is no longer required for event configuration, but it is still worth doing for link ownership and brand safety.
- Do NOT look for the old Aggregated Event Measurement 8-event ranking — Meta removed manual AEM event configuration (the AEM tab was removed from Events Manager). Meta now aggregates eligible web events automatically, with no 8-event cap and nothing to prioritize manually.
- Instead of ranking events, make sure your Pixel + Conversions API send a clean, deduped event set: Purchase, AddToCart, InitiateCheckout and your other key events arriving with matching event IDs and good Event Match Quality. If the event set is clean, AEM handles the rest.
Check 6: Cross-Check Against Real Orders
This is the check that settles arguments. Compare three numbers for the same date range:
- Actual orders in your store (Shopify, WooCommerce, or your CRM) — the truth.
- Purchases reported in Meta Ads Manager — what Meta thinks happened.
- Purchases in GA4 — a second opinion. Run through our GA4 conversion tracking audit checklist if your GA4 numbers look off too.
A small gap is normal. Platforms attribute differently, and some conversions arrive late. But a persistent, large gap in either direction is a tracking problem:
- Meta reports far fewer purchases than your store → events are being lost (ad blockers, consent, broken tags, missing server events).
- Meta reports far more purchases than your store → deduplication is failing, or events are firing on page reloads and thank-you-page revisits.
Run this comparison over at least 7 days. One day of noise means nothing; a week of the same gap means something is broken.
Check 7: Attribution Window and Delayed Conversions
Before you conclude tracking is broken, rule out two normal causes of mismatch.
- Attribution window. Meta’s default window may differ from what you expect. A purchase 6 days after a click may be counted — or not — depending on your settings. Make sure you know which window you are looking at.
- Delayed conversions. Some purchases take days to appear. If you compare today’s Ads Manager numbers to today’s store orders, you are comparing two different things. Always compare settled periods — at least 3 days old — before judging.
What “Healthy” Tracking Looks Like
After running all seven checks, healthy tracking has these traits:
- Events arrive consistently, with no gaps on sales days
- Diagnostics shows no unresolved warnings
- Test Events shows each funnel step once, with correct values
- Deduplication merges browser and server events cleanly
- The gap between Meta-reported purchases and real orders is small and stable
- Your key funnel events are configured and firing consistently — with no legacy 8-event prioritization to maintain
If all of that is true, your tracking is not the problem — look at the ads, the offer, and the landing page. If any of it fails, fix tracking before you touch anything else. Optimizing on broken data is worse than not optimizing at all.
Quick Fix List
| Symptom | Most likely cause |
|---|---|
| No events at all | Pixel not installed, or wrong pixel ID |
| Missing purchases | Ad blockers + no server events, or broken purchase tag |
| Double-counted purchases | Deduplication failing — mismatched event IDs |
| Low match quality | Missing customer data in events (email/phone hashing) |
| Tiny remarketing audiences | Events lost upstream — check pixel + server coverage |
FAQ
How often should I check my tracking?
Run the full seven checks after any site change, platform change, or new campaign launch — and once a month as routine. Tracking breaks silently. Nobody gets an alert when a tag stops firing.
Do I need a developer for this?
For the checks, no — everything above uses Meta’s own tools. For fixes, it depends. Deduplication and server-side setup are technical, but they are standard work for anyone who does tracking professionally.
Is the Meta Pixel alone enough?
No — not anymore. The pixel catches browser-side events, but ad blockers, privacy settings, and closed tabs eat a growing share of them. The pixel plus the Conversions API, deduplicated properly, is the baseline in 2026.
My ROAS dropped suddenly. Is it tracking or the ads?
Run Check 6 first. If Meta-reported purchases fell but real orders did not, it is tracking. If both fell together, it is the ads, the offer, or the market. Never change creative until you know which one it is.
Get Your Tracking Checked
If these checks turned up gaps — missing purchases, duplicates, low match quality — that is exactly what a tracking audit is for. Book your free strategy audit and I will run the full diagnosis on your account and show you what to fix first. See our server-side tracking service, or book below. WhatsApp is also available via the site if you prefer to start there.
Further reading: Meta’s Pixel documentation.
