Meta Pixel’s “Measure conversions on customer devices” setting starts measuring on November 12, according to the Events Manager panel, as PPC Land quoted it, and the advertiser notice, as Wortfilter reported it on October 18. Both present the switch as on by default. Neither mentions the three conditions Meta’s Help Center attaches: the feature is not active for people located in the EU and UK, the Pixel must sit directly on the page, and the site must require people to log in with an email or mobile phone number. The Help Center example and the notice also describe the measurement gap in different words.
What is “Measure conversions on customer devices”?
It is a Meta Pixel setting in Events Manager. Meta’s Help Center says that when it is on, “the system measures conversions on your customer’s device. It uses information they already shared with you (like an email) and temporary, non-identifying device information.” It works alongside your existing Pixel and Conversions API setup and “doesn’t replace it.”
One switch, three descriptions
PPC Land describes the toggle in the Meta Pixel settings panel of Events Manager, shown as on, with a grey line beneath it: “Measurement starting November 12, 2026.” The panel text it quotes reads: “Meta measures conversions from your ads so you can see which ads are working. With this feature on, that measurement happens on your customer’s device instead of exclusively on Meta servers.” Per PPC Land, the notice reached advertisers in mid-October. As PPC Land and Wortfilter describe it, the notice says the feature needs no code changes, applies to datasets already sending events and can be turned off at any time in each dataset’s settings. Wortfilter adds a gradual rollout from November 12 and no opt-in step.
| Item | Events Manager panel (per PPC Land) | Advertiser notice (per Wortfilter) | Meta Help Center |
|---|---|---|---|
| Default state | Toggle shown as on | No opt-in step | “turned on by default” (page 1); “on by default for eligible pixels” (page 2) |
| Start date | November 12, 2026 | Gradual rollout from November 12 | Not stated |
| Eligibility conditions | Not stated | Only datasets already sending events; none of the Help Center conditions | Not active for people located in the EU and UK; Pixel installed directly, not in an iframe or as an image-only pixel; site requires login with an email or mobile phone number |
| How to turn it off | The toggle itself; the quoted text does not mention turning it off | Any time, per dataset | Events Manager, Data sources, your pixel, Settings; “you can turn it off at any time” |
The Help Center’s second page lists the conditions under “Before you turn on”: install the Meta Pixel on your website, install it “directly on your page, not inside an iframe or as an image-only (img) pixel”, and make sure “Your website must require people to log in to an account using an email or mobile phone number.” Neither Help Center page mentions November 12. PPC Land noted that none of these conditions appears in the settings panel text or in the notice as Wortfilter and the Philippine news site ASTIG reproduced it, and that the login condition, taken literally, would leave out shops where a purchase can be completed without an account.
Where did the missing conversions go?
PPC Land writes that Meta’s wording “leaves room for two readings”: purchases whose events never reach Meta at all, or events that reach Meta but cannot be tied to an ad. Describing the notice as Wortfilter and ASTIG reported it, the same article says the feature recovers conversions that are “missing from campaign reporting because they never make it back to Meta to be measured.” Wortfilter’s German summary says the same: conversions that do not appear in campaign reporting because they do not reach Meta.
The Help Center example is worded differently. Someone sees a lamp ad on Instagram, visits the website two days later and buys it. In Meta’s words: “Meta may have a record of the ad view and receive the purchase event, but can’t always connect them to attribute the purchase to your campaign.” So in Meta’s example the purchase event can reach Meta, while the notice, as reported, describes conversions that never do. We set the two side by side and do not pick one. Meta also says attribution windows and models do not change.
What Meta has not said
PPC Land and Wortfilter listed open questions, and Meta’s Help Center, panel text and notice, as reported, do not answer them. Whether purchase value and currency travel with a recovered conversion, which PPC Land says decides whether such conversions show up in ROAS reports and value-based bidding; the Help Center says Meta “only receives confirmation that a purchase happened and which campaign to attribute it to” and does not mention value or currency. Where the device gets its record of the ad view: PPC Land wrote that “Meta has not said”. Which browsers and operating systems are covered, a gap Wortfilter raised. Whether recovered conversions feed bidding: the Help Center says only that keeping the setting on helps “improve campaign performance with a stronger signal.” Wortfilter, in its own assessment, expects reported ROAS to rise and Meta’s optimization algorithm to get more signals from November 12, but cites no Meta statement for either.
The timing is tight. PPC Land pointed out that November 12 falls 15 days before Black Friday on November 27. A similar default appeared in August: ChatGPT Ads set automatic advanced matching to turn on for existing pixels unless advertisers opted out before August 17.
What to do before November 12
This is our advice, not a Meta statement; Wortfilter recommends the same first step. Record a baseline now: Meta-attributed purchases for a recent period next to the orders in your own backend. After November 12 the Meta number may rise because of the change in measurement, with no change in sales, and without a baseline you cannot tell.
Keep a second count that does not depend on Meta. Tag Meta ad URLs with UTM parameters so your site analytics holds its own Meta-referred sessions and purchases across the change. Then check, per dataset, whether your site meets the Help Center conditions.
