Growth & Performance Marketing
Meta Will Start Counting More Sales From 12 November: Should You Trust Your White Friday Numbers?
9 min read

From 12 November 2026, Meta will switch on a Pixel setting called “Measure conversions on customer devices” by default for advertisers that already send events. It matches some website purchases on the shopper’s device to recover sales Meta says it currently cannot see. Outside the EU (European Union) and the UK (United Kingdom), which includes Egypt, Saudi Arabia and the UAE (United Arab Emirates), you should expect Meta to report more purchases. That does not mean you sold more. Before White Friday, set a baseline, reconcile Meta’s numbers against your real orders, and make budget decisions on orders, not on platform-reported ROAS (Return on Ad Spend).
What Meta is changing on 12 November
The setting sits in Events Manager, inside each Pixel’s settings. According to the notice reported by PPC Land and Stape, it is on by default for datasets already sending events, needs no code change, and rolls out gradually. If you do not want it, you have to opt out, one pixel at a time.
As Meta describes it, the match uses information the customer already gave the business, such as an email address, together with “temporary, non-identifying device information”. Meta says only the fact that a purchase happened, and which campaign to credit, comes back to it. Meta’s panel says measurement happens on the device “instead of exclusively on Meta servers”, which reads as a second path next to the Pixel and the Conversions API (CAPI), not a replacement for them.
The conditions below come from Meta’s help pages, as summarised by Relevant Audience and by MetricMaven (cited in PPC Land):
- It is not active for people located in the EU and UK, so it does apply to shoppers in Egypt and the GCC (Gulf Cooperation Council).
- The Pixel must sit directly on the page, not inside an iframe or as an image-only pixel.
- The website must require customers to log in with an email address or mobile number.
- The attribution window and attribution model do not change.
The login condition matters in our region. Many stores allow guest checkout, so coverage may be partial or zero for some of you. Check whether your store meets the conditions before assuming your numbers will move.
What Meta has not said yet
This is the part to read carefully. At the time of writing, Meta has not said publicly whether recovered conversions feed bidding, delivery and audiences, or only reporting. It has not said whether purchase value is included, which decides whether your ROAS moves or only your conversion count. And it has not explained how consent is handled, for example whether visitors who declined tracking are excluded.
One of the reasons Meta gives for keeping the setting on is to “improve campaign performance with a stronger signal”. That suggests use beyond reporting, but it is not a confirmed answer. Check Meta’s help page and your own Events Manager before you plan around it, and review your privacy notice and consent setup with your legal advisor, since data protection rules apply in Saudi Arabia, the UAE and Egypt.
Why the timing is awkward for White Friday
12 November is about two weeks before Black Friday on 27 November, right in the run-up to White Friday sales in the Gulf and Egypt. That is when most teams lock budgets and start scaling the ads that look like winners. If reported purchases jump in the same week, it is very easy to credit the jump to better creative or a better audience.
There is also the learning phase. Meta’s guidance says an ad set needs about 50 optimisation events a week to exit learning. If recovered conversions count as optimisation events, which Meta has not confirmed, more ad sets could cross that line. That may help delivery stabilise. But the same campaign will also look more efficient on paper without one extra order in your store. More counted conversions can help the algorithm and still mislead you about where to put the next riyal or pound.
How to reconcile Meta against Salla, Shopify or your ERP
This is the routine I would run with any e-commerce team this month. It needs a spreadsheet, not new tools.
- Set a baseline now. Export Meta-attributed purchases and purchase value by day for the last 30 days, next to paid orders from Salla, Shopify or your ERP (Enterprise Resource Planning) system.
- Track one ratio: Meta-reported purchases divided by real orders for the same days. Write it down before 12 November.
- Watch that ratio after 12 November. If it rises while total orders and revenue stay flat, the change is in measurement, not in demand.
- Add a note on 12 November in every dashboard and weekly report, so nobody compares the week after with the week before as if nothing changed.
- Keep server-side tracking (CAPI) on. The new setting is meant to run alongside it.
- Judge White Friday on blended numbers from your store: total revenue divided by total marketing spend, and new customers acquired.
- Where budget allows, run a holdout or geo test before you give Meta credit for any lift.
Yiqi Wu of Aimerce, quoted by PPC Land, suggested a similar comparison against Shopify orders and said: “I wouldn’t opt out by default.” His company sells tracking for Shopify merchants, so read that with context. MetricMaven’s advice in the same report is close: record a baseline and run a holdout test.
Should you opt out?
I would not opt out on reflex. A stronger signal can help delivery, and you can always judge results on store data. But make the choice on purpose:
- Keep it on if your store meets the login condition, you have a clean baseline, and you already report on store orders.
- Consider switching it off for peak season if your team or agency is judged on platform ROAS, or if you cannot separate a measurement change from a performance change.
- Either way, review consent with your legal advisor while Meta’s answers are pending.
Based on Meta’s help pages as summarised by Relevant Audience, the switch is in Events Manager: Data sources, select the pixel, Settings, then turn off “Measure conversions on customer devices”. It works per pixel.
This is the same discipline I argue for in CAC, LTV and Payback: the number that pays salaries is the one in your bank, not the one in Ads Manager. For how Gulf campaigns should be built to pay back, see Performance Marketing in Saudi Arabia and the UAE.
FAQ
What is “Measure conversions on customer devices” in Meta Pixel?
It is a Pixel setting that matches some website purchases on the shopper’s device, using information like the email the customer gave the store plus temporary device data, so Meta can report sales it would otherwise miss. Meta says it receives only the fact of the purchase and the campaign to credit. It is on by default from 12 November 2026 for eligible pixels.
Does Meta on-device conversion measurement apply in Saudi Arabia and Egypt?
Yes, if your store is eligible. Meta says the feature is not active for people in the EU and UK, and no exclusion has been reported for Egypt or the GCC. Your Pixel must be installed directly on the page, and your site must require login with an email or mobile number.
How do I turn off on-device conversion measurement in Meta Events Manager?
Open Events Manager, go to Data sources, select your pixel, open Settings, and switch off “Measure conversions on customer devices” below the Meta Pixel settings. The setting is per pixel, so repeat it for each one. Record your baseline either way so you can compare before and after.
Will Meta’s on-device conversion measurement increase my ROAS?
Not necessarily, and Meta has not confirmed it. Meta has not said whether purchase value is included in recovered conversions, which decides whether your ROAS moves or only your conversion count. Either way, more reported purchases do not mean you sold more, so judge results on real store orders.
Do I need to change my code or replace the Conversions API for this Meta setting?
No. The setting needs no code change and rolls out gradually to datasets already sending events. It is meant to run alongside the Pixel and the Conversions API (CAPI), not replace them, so keep server-side tracking on.
Should I opt out of Meta’s on-device conversion measurement before White Friday?
Not on reflex. Keep it on if your store meets the login condition, you have a clean baseline and you already report on store orders. Consider switching it off for peak season if your team or agency is judged on platform ROAS, or if you cannot separate a measurement change from a performance change.
How can I tell if Meta’s higher purchase numbers are real sales?
Compare Meta-reported purchases with paid orders from Salla, Shopify or your ERP for the same days, starting with a baseline of the last 30 days before 12 November. If that ratio rises after 12 November while total orders and revenue stay flat, the change is in measurement, not in demand.
If you want a second pair of eyes on your White Friday measurement plan, get in touch. Setting up reporting that budget decisions can trust is a core part of my fractional CMO work with founders.
Sources
- Meta Pixel counts more sales from Nov 12 as AI ads go undisclosed (PPC Land)
- Meta Pixel will count more conversions from Nov 12 unless advertisers opt out (PPC Land)
- Meta Pixel turns on Measure conversions on customer devices by default outside the EU and UK (Relevant Audience)
- Meta on-device conversion measurement (Stape)
- About measuring conversions on customer devices (Meta Business Help Center)

