Meta Pixel Starts Counting More Sales From 12 November — Should You Opt Out?
In short: From 12 November 2026, Meta is turning on a new Events Manager setting called "Measure conversions on customer devices" by default for every ad account that already sends events — advertisers who don't want it have to opt out themselves. It adds a second, device-side path to recover purchases that today never reach Meta's reports, running alongside your existing server-side (Pixel/CAPI) tracking rather than replacing it. Eligibility is narrower than the default rollout suggests, and several important details — including whether it affects bidding — are still unconfirmed by Meta.
- A new setting, "Measure conversions on customer devices," turns on automatically from 12 November 2026 for datasets that already send events. You have to find it and switch it off if you don't want it.
- It works by matching an email address the customer already gave your business with temporary, non-identifying device data Meta holds. Only the fact of a purchase and which campaign gets credit for it flow back into your reports.
- Eligibility is narrower than "on by default" implies: it does nothing for users in the EU or UK, your Pixel has to sit directly on the page (not in an iframe or image pixel), and your site has to require login with an email or mobile number.
- Attribution windows and bidding models are unchanged on paper, but Meta hasn't confirmed whether these recovered conversions actually feed your bidding algorithm or whether purchase values are included.
- This lands about two weeks before Black Friday (27 November), which is exactly when a sudden jump in reported conversions is hardest to explain to a client without a plan already in place.
- Meta's own research has previously put the undervaluation from rules-based attribution at around 31% — this feature is part of closing that gap, not a one-off experiment.
What's actually changing
From 12 November 2026, Meta is switching on a new Events Manager setting — "Measure conversions on customer devices" — by default for any ad account whose dataset already sends events. It's opt-out, not opt-in: if you don't go looking for it in Events Manager, it's already on.
The idea is straightforward: some purchases happen but never get reported back to Meta, because the usual server-side signal (your Pixel, your Conversions API) doesn't always make the full round trip. This feature adds a second path that runs on the customer's own device, alongside your existing tracking, not instead of it. It works by matching an email address your customer already gave you with temporary device data Meta describes as non-identifying. What comes back to your reports is narrow — the fact that a purchase happened, and which campaign gets credited for it — not full event details.
Who this actually applies to
The "on by default for everyone" framing is misleading once you read the eligibility fine print:
- Geography: it does nothing for users in the EU or UK. If most of your traffic is there, this change is close to irrelevant for you regardless of the setting.
- Pixel placement: your Pixel has to sit directly on the page. If it's loaded inside an iframe or fired as an image pixel (a pattern some older or third-party checkout setups still use), it won't qualify.
- Login requirement: your site has to require the customer to log in with an email address or mobile number. A guest-checkout-only store won't see much benefit from this specific feature.
What Meta hasn't said
Attribution windows and bidding models are stated as unchanged, but Meta hasn't confirmed two things that actually matter for how you'd react to this: whether these newly-recovered conversions feed into your bidding algorithm the same way a normal tracked purchase does, and whether purchase value is included or just the binary fact of a sale. Until that's confirmed, a jump in reported purchases doesn't automatically mean a jump in reported revenue or a change in how campaigns optimize.
Should you opt out?
Not on day one, and not by default. The sensible approach, echoed by marketers quoted in the original coverage, is to treat this as something to verify rather than something to switch off reflexively:
- Keep your server-side tracking exactly as it is. This feature is additive, not a replacement for your Pixel/CAPI setup.
- Compare Meta-attributed purchases against your actual order source (Shopify, WooCommerce, your own order DB) over the next couple of weeks, and watch the ratio between the two rather than either number alone.
- Only opt out if the numbers stop agreeing — if Meta-reported purchases start running meaningfully ahead of real orders with no explanation, that's your signal, not a one-week bump on its own.
- Expect some reporting noise around Black Friday regardless. This rollout lands two weeks before the year's biggest spend period, so build in the expectation that reported-vs-actual sales may need reconciling with a client, rather than discovering the gap after the fact.
Running Meta Ads for ecommerce clients and want someone to sanity-check what this does to your reported numbers before Black Friday? Request a free account review.
Get new marketing updates in your inbox.
We email you when we publish something worth your time. No spam, unsubscribe anytime.
Sources
Facts in this article come from the sources above, checked on 12 November 2026. Platform features roll out in phases, so check your own account before acting. We update this page when official details change.