Meta is adding a Pixel setting called "Measure conversions on customer devices" that credits campaigns with purchases its servers currently miss. Measurement starts November 12, 2026, rolls out gradually, and is switched on by default for datasets that already send events. Advertisers can turn it off per dataset in Events Manager.
What changes
Today Meta matches website conversions to ads mostly on its own servers, using Pixel and Conversions API events. The new setting adds a second path: when someone sees an ad and buys on your site days later, the match can happen on the shopper's device instead of only on Meta's side.
According to Meta's description, the match uses information the customer already gave the business, such as an email address, plus temporary, non-identifying device data. Meta says that information stays on the device and Meta only learns that a purchase happened and which campaign gets credit.
Who is affected
Any advertiser whose Pixel or Conversions API dataset is already sending events gets the setting turned on, with no opt-in step. Reporting summarised by PPC Land and Stape says it is not active for people in the EU or UK.
PPC Land, citing a reading of Meta's help pages by MetricMaven, adds further conditions: the Pixel must sit directly on the page rather than in an iframe or as an image-only pixel, and the site must have login by email or phone number. Treat those conditions as reported, not confirmed by Meta's own settings text.
- Start date: November 12, 2026, about two weeks before Black Friday
- Default: on for existing datasets that send events
- Location: Events Manager > Data sources > your Pixel > Settings
- No change to the attribution window or model, and no new CAPI integration needed
What is still unclear
Meta has not said whether these extra matches feed bidding, delivery and audiences, or only reporting. It also has not said whether purchase value is passed, which decides whether ROAS moves along with conversion counts, or how on-device matches are deduplicated against server events.
Stape's point is the one to keep in mind: more attributed conversions does not mean more real sales. It means Meta can link more of the sales you already had to your ads, so reported CPA can fall and ROAS can rise without anything changing in your bank account.
What to do before November 12
Decide deliberately rather than by default. Most buyers will want to leave it on, but set up a check first: pull a baseline of Meta-attributed purchases against actual paid orders in your store for the last few weeks, then watch that ratio after the rollout.
If the ratio jumps, adjust your target CPA and ROAS before you scale budgets on the new numbers. If Meta's figures stop reconciling with your orders, that is your signal to switch the setting off for that dataset. Keep server-side CAPI running either way; this sits alongside it, not in place of it.
What it means for you
- Check each Pixel's Settings tab in Events Manager before November 12
- Log a baseline of Meta-attributed vs. actual orders now so you can spot inflation
- Do not scale BFCM budgets on a sudden ROAS jump until it reconciles with real sales
- Keep the Conversions API live; the on-device path is an addition, not a replacement
Sources
- PPC Land: Meta Pixel will count more conversions from Nov 12 unless advertisers opt out
- Stape: Meta on-device conversion measurement
- Meta Business Help Center: About measuring conversions on customer devices
