Meta Pixel on-device conversions: check this setting now

Meta Pixel has a new setting, "Measure conversions on customer devices", that is on by default and, according to Meta's Events Manager notice, started counting from 12 November 2026. It matches some ad views to purchases on the shopper's own phone or laptop and sends Meta only the fact that a purchase happened and which campaign should get credit. India is not excluded, so if your site qualifies, your Ads Manager purchase numbers can rise this month without any real change in sales.

Here is what is confirmed, what is still unclear, and what to check before you read too much into a better-looking ROAS.

What changed

Meta's Business Help Center article on the feature describes it as on-device conversion measurement. As reported by MetricMaven and Relevant Audience, which quote that page and a second help article on setup, Meta says:

• The setting is turned on by default for eligible pixels.
• Matching uses information the customer already gave the business (such as an email address) plus temporary device data, both kept on the device.
• Meta receives only confirmation of the purchase and the campaign to credit.
• Your attribution window and attribution model do not change.
• It is not active for people in the EU or the UK.

The 12 November start date comes from the Events Manager panel and Meta's email to advertisers, as reported by PPC Land. It is not stated in the help articles themselves.

Who it applies to

Per Meta's help pages as quoted by MetricMaven, a site qualifies only if:

1. The Pixel is installed directly on the page, not inside an iframe and not as an image-only pixel.
2. The website requires login with an email address or mobile number.

That second condition matters in India. Many D2C brands now use phone-number OTP logins, so a lot of Shopify and custom stores could qualify. Brands with guest-only checkout may not.

Our inference, not Meta's: if your checkout runs inside a third-party overlay or iframe (several one-click checkout tools work this way), check where the Pixel purchase event actually fires. If it fires inside the iframe, this setting may not apply to those purchases.

What is still unclear

Meta has not publicly answered these, and you should treat any vendor claim about them as unconfirmed:

• Whether purchase value and currency are passed, or only the purchase itself.
• Whether recovered conversions feed bidding and delivery, or only reporting.
• How it deduplicates with Conversions API events.
• Whether there is a column or breakdown to see on-device conversions separately. We have not found one.

What it means for Indian advertisers

If your Pixel qualifies, expect reported purchases to tick up. Because the attribution rules haven't changed, that lift can be a measurement change, not a performance change. CPA falls and ROAS rises on paper. If you set budgets by Ads Manager ROAS, you could scale a campaign that is not actually doing better.

The fix is the habit we push in Facebook ad analytics: the 12 metrics that matter: compare Meta's purchases with your backend. Track a daily ratio of Meta-reported purchases to Shopify or CRM orders. If the ratio jumps from, say, 0.55 to 0.70 around 12 November while backend orders stay flat, that's the setting, not your creative.

Lead-gen accounts are less exposed because the feature is about website purchases, but the same discipline applies. Our guide to fixing junk Meta leads covers matching platform numbers to CRM outcomes.

Should you turn it off?

There's no one answer. Arguments for leaving it on: more of your real sales may get credited, which can help Meta see what's working. Arguments for switching it off for now: cleaner year-on-year comparisons, and caution for regulated categories (healthcare, finance) until your legal team has read the help pages. Whatever you choose, record the decision and the date so your reports make sense in three months.

What to do this week

• Go to Events Manager → Data sources → [your Pixel] → Settings and find "Measure conversions on customer devices". Note whether it is on.
• Check the two eligibility conditions: direct Pixel install, and a login with email or phone.
• Add an annotation for 12 November to every dashboard that reports Meta purchases, CPA or ROAS.
• Start a daily Meta-to-backend purchase ratio if you don't have one, and watch it for four to six weeks.
• Don't make big budget moves on Meta ROAS alone this month. Check the backend first.
• If you also send purchases through Conversions API or Google's GA4 Data Manager, avoid changing those setups at the same time, so you can isolate the effect.

FAQ

Is Meta's on-device conversion measurement active in India?

Yes, as far as Meta's documentation shows. The only regions Meta's help page excludes are the EU and the UK.

Will this change my attribution window?

No. Meta's help page, as quoted by trade press, says the attribution window and model stay the same. Reported conversions can still rise because more purchases are matched.

Can I turn it off?

Yes. Meta says you can switch it off at any time, per Pixel, in that dataset's settings in Events Manager.