09/11/2026
⚠️ Meta might be counting 1 order as 2 purchases.
That’s not a small tracking issue.
That’s a November budget problem.
If Pixel and CAPI aren’t deduplicating correctly, your Meta ROAS can look stronger than it is. Then your team starts scaling based on fiction right when BFCM spend gets expensive.
The setup is simple:
• 🖥️ Pixel reports browser-side purchases
• 🧩 CAPI reports server-side purchases
• ✅ Meta deduplicates them when the event IDs match
• ⚠️ Meta can count them separately when the event IDs don’t match
So 1 order can turn into 2 reported purchases.
Not because the customer bought twice.
Because the tracking setup told Meta 2 different events happened.
Another common issue:
🕵️ An old pixel is still running somewhere on the site.
Nobody thinks to look for it. It keeps firing. Your purchase numbers keep getting inflated.
Run this test before Black Friday:
1. 🧭 Go into Meta Events Manager
2. 🛒 Place a test order
3. 🔎 Check how many purchase IDs come back
4. 🚩 If you see multiple purchase IDs, investigate
5. 🕵️ Look for another pixel still firing
6. 🧩 Check whether CAPI event IDs are mismatched
7. 🧹 Remove or clear the extra setup
8. 🔁 Retest until 1 purchase ID comes through
That’s the goal.
✅ 1 real order.
✅ 1 purchase ID.
✅ 1 deduplicated event.
But don’t stop there.
Meta IDs only clean up the Meta view.
Real purchases may also touch Google, Klaviyo, TikTok, email, organic, or direct before the customer buys.
🌐 That’s why a unified first-party dashboard matters going into Q4.
AdBeacon helps teams connect those touchpoints across channels, so you’re not making BFCM budget calls from Meta’s version of the story alone.
Because if Meta is double-counting purchases now, your November ROAS won’t be a strategy.
⚠️ It’ll be fiction with a budget attached.
Have you tested purchase ID deduplication before BFCM, or are you trusting the setup?