If you run Facebook or Instagram ads, check your Meta Pixel settings before Thursday. Meta has added a setting called Measure conversions on customer devices. It is switched on by default, and the panel in Events Manager says "Measurement starting November 12, 2026."
Nothing about your ads changes. What changes is how many conversions Meta reports. That matters because it lands two weeks before Black Friday, the one period when everyone compares this year's numbers with last year's.
What the setting does
Meta's description in Events Manager says measurement "happens on your customer's device instead of exclusively on Meta servers." Based on Meta's notice as quoted by PPC Land, it works like this:
- When someone buys on your site, the match is made on their own phone or computer, using the email address they gave you plus temporary device data.
- That information stays on the device. Meta learns that a purchase happened and which campaign gets the credit.
- The words "instead of exclusively" suggest it adds a second path next to the one you have now. It doesn't replace server-side tracking such as the Conversions API.
The purpose is to recover conversions Meta currently misses, for example when browser privacy features block the usual matching.
Reports also say it isn't active for people in the EU and UK, and that your attribution window and model stay the same. Meta's help page didn't load fully for us, so we couldn't confirm the details on the page ourselves.
Why your numbers may jump on Nov. 12
If the setting recovers conversions Meta used to miss, your reported purchases, cost per purchase and ROAS will improve from Nov. 12, even if your actual sales don't change. Compare Black Friday week with the week before, or with last year, and the ads will look better than they are.
That isn't a reason to switch it off. More complete data can help Meta optimize. It's a reason to know exactly when the counting changed.
What to do before Thursday
- Record a baseline. Export Meta-reported purchases and revenue by day for the last 30 days, next to the orders and revenue in your store or CRM for the same days. The gap between the two is your normal "attribution gap."
- Annotate Nov. 12 in Ads Manager notes, your reporting dashboard and anywhere else you track results. Anyone reading the numbers in December should see why they moved.
- Keep server-side tracking on. If you use the Conversions API, leave it running. The new setting adds to it.
- After Nov. 12, compare the gap again. If Meta-reported purchases rise but store orders don't, the setting is finding conversions that were already happening. Judge your campaigns on store data during the sale.
How to turn it off
If you'd rather keep your reporting unchanged through the holiday season, you can switch the setting off for each pixel:
- Open Events Manager.
- Go to Data sources and select your pixel.
- Open Settings and find Measure conversions on customer devices, just below "Automatically include more detailed page and product info."
- Turn it off. Repeat for every pixel you use.
You can turn it back on at any time.
Our view
Leave it on for most stores, but record the baseline today. The risk isn't the setting. It's someone in December deciding the ads "worked better this year" because the counting changed on Nov. 12.
What we don't know yet
Meta hasn't said whether recovered conversions feed into bidding, whether purchase value is included, or which browsers and apps it works in. Reports also say the shopper may need to be signed in with an email or phone number, which would leave out guest checkouts. We'll update this guide when Meta's help page answers those questions.
