3rd floor, A-13, 3rd Phase, Thiru Vi Ka Industrial Estate, SIDCO Industrial Estate, Guindy, Chennai, Tamil Nadu 600032
+91 9944679414|connect@zingbizz.com|Get directions
© 2026 ZingBizz. All rights reserved.
ZingBizz AI
You seem pretty interested in what we do…
Ask me anything — branding, websites, marketing. I answer in seconds.

If you are weighing a meta pixel opt out november 12 decision, the short answer is to leave the new setting on and keep a simple daily log of Meta's purchase count against your real orders. The setting counts extra purchases in your ad reports and is on by default for pixels already sending events. Switch it off only if the two numbers stop agreeing and you cannot find out why.
TL;DR: The setting is called "Measure conversions on customer devices". It can raise the purchases Meta reports without a single extra sale. Opting out is per dataset, so a business with two pixels has two decisions. Write down 12 November as the date your reporting changed.
Not by reflex. Opting out feels like the cautious choice, but it also keeps Meta blind to some real purchases that your report was previously missing. The better question is whether you can still reconcile Meta's numbers with your orders after the change.
Here is the rule we would give a client:
One caveat before the detail. Meta's own Help Center page was not available to us when we wrote this, so what follows comes from the setting's on-screen wording as quoted by PPC Land, plus second-hand reporting. We mark every point below that we could not confirm directly.
In Events Manager, inside your Meta Pixel settings, there is a new toggle with that name. It sits under an older one, "Automatically include more detailed page and product info". The grey line beneath it reads "Measurement starting November 12, 2026".
The panel text, as quoted by PPC Land, says Meta measures conversions from your ads so you can see which ads are working. It adds that with the feature on, that measurement happens on your customer's device instead of exclusively on Meta's servers.
In plain terms, Meta matches a purchase to an ad on the shopper's own phone or computer, using an email address the customer gave your business plus temporary, non-identifying device data. Per the report, both stay on the device, and Meta receives only the fact that a purchase happened and which campaign gets the credit. Purchases that never reached Meta before can now show up in your reports.
Two things are not confirmed anywhere we could read:
Secondary reporting, citing Meta's Help Center, says the attribution window and model do not change. Treat that as likely, not settled.
Possibly yours. The same secondary reporting lists conditions that would stop the setting from doing anything:
We could not confirm these from Meta directly, and they did not appear in the panel text. If they hold, a shop where people check out as guests may see little or nothing from this. That is worth knowing before you spend an afternoon worrying about it: the log below will tell you within a week.
The path reported, citing Meta's Help Center: Events Manager, then Data sources, pick the pixel, then Settings, and switch off "Measure conversions on customer devices". Meta's notice says you can turn it off at any time, in each dataset's settings, so it is not an account-wide switch.
Practical points:
If you cannot find the toggle, do not hunt for it for an hour. It may not have reached your account yet, or your setup may not be eligible.
This is the most useful thing in this guide, and it needs only a spreadsheet. It follows the suggestion from Aimerce's CEO on X: compare Meta-attributed purchases against actual paid orders, and track the ratio.
Keep any server-side tracking you already have running while you do this, because switching several things at once makes the log useless. Meta's developer documentation describes the Conversions API as a server-side connection that works alongside the pixel, with server events tied to the same dataset, so the two are meant to run together rather than replace each other. If your numbers are already well above your orders for other reasons, our guide to Meta ads showing more purchases than orders covers how to reconcile the two.
We have not run this log on a client account for this change yet, and we are not going to quote you a before-and-after number we do not have. The method is the point: your own seven days are worth more than any average.
You pay an agency or freelancer against reported results. If a fee, a bonus or a renewal conversation hangs off Meta's purchase count, a default setting that raises the count without more sales muddies the deal for both sides. Switch it off, or agree in writing what the new baseline is.
You are comparing months for a decision. If you are deciding in December whether Meta is worth its budget compared with October, a mid-period change to how purchases are counted ruins the comparison. Either opt out until the comparison is done or mark 12 November clearly on every chart.
Your numbers stop matching and nobody can say why. Opting out is a sensible way to remove one variable. Turn it off, watch for a week, and see if the gap closes.
If you run modest spend, check orders yourself, and mostly use Meta to see which ad works better than another, extra recovered purchases make that comparison better, not worse. Meta's optimisation may also see more signal, though as noted above we cannot confirm that it does.
This is also not a reason to rebuild your tracking. If you are wondering whether the pixel alone is still enough for your business, that is a separate question, and for a small shop on a standard platform the platform's own integration is often enough.
Send these three questions today. A competent agency answers them in minutes.
If you want a second opinion on your tracking or your reports, that is work ZingBizz does as part of running paid campaigns, and we will say plainly if the setting makes no difference to your account. This sits alongside the other recent Meta changes, including the 20 November ad terms and Meta AI editing your ads.
For honesty's sake, in one place: we did not read Meta's own Help Center article. The setting name, date and panel wording come from PPC Land's report of the on-screen text. The opt-out path and the eligibility conditions come from secondary reporting that cites Meta. Whether recovered purchases affect bidding, whether value is sent, and how consent declines are treated were not stated. Check your own Events Manager before acting on any of this.
Want more of our writing in your Google feed?