Meta on-device conversions start on November 12, 2026, fifteen days before Black Friday, on by default for eligible pixels. Meta can credit purchases it could not previously connect to an ad, so reported ROAS can rise and cost per purchase can fall while shop orders stay flat. Treating that jump as demand can misallocate holiday budget.
Updated November 11, 2026
Key Takeaways
- On-device matching starts November 12 and defaults on for eligible pixels.
- Reported cost per purchase can fall and ROAS can rise without new sales.
- The setting is not active for people in the EU and UK.
- Export four weeks of Ads Manager figures and shop orders before November 12.
What do Meta on-device conversions actually match?
Measurebase’s readout shows the Events Manager label “Measure conversions on customer devices,” with “Measurement starting November 12, 2026” under it. Meta’s example is an Instagram lamp ad and a site purchase two days later that its servers cannot always join. Part of the match then runs on the customer’s device, using details the customer already gave the business, such as an email, plus temporary device information Meta calls non-identifying.
Meta receives only that a conversion happened and which campaign is credited. No code change is required, and the attribution window, model, pixel and Conversions API stay in place.
Who is excluded from the match?
Measurebase, citing Meta, lists three conditions. The pixel must sit directly on the page, not in an iframe and not as an image-only pixel. The site must ask visitors to log in with an email or phone number. The setting is not active for people in the EU or the UK.
For a shop that mainly sells in the EU, the effect is small. Visitors from elsewhere, such as the United States, can be counted. Meta names the EU and the UK only, not Norway, Iceland, Liechtenstein or Switzerland, and shops where people buy without an account seem to fall outside the login condition.
CMe Media says the impact for UK advertisers may be limited. CMe also says the default covers any Pixel or Conversions API dataset already sending events. Measurebase says a Conversions API-only setup, without the browser pixel, does not appear to qualify, and Meta has not said so explicitly.
| Item | What the sources report |
|---|---|
| EU and UK visitors | Setting not active |
| Email or phone login | Required |
| Pixel placement | Directly on the page, not an iframe or image-only pixel |
| Attribution window and model | Unchanged |
Which reported gains are newly visible, not new?
CMe Media dates Black Friday to November 27, so the setting starts as budgets for the busiest weeks are set. Measurebase says to expect more attributed conversions from November 12 for the same campaigns and the same sales. Comparisons with last year’s Black Friday, and with the weeks before November 12, will look better than they are.
Code3’s briefing offers a hypothetical, not a reported result: $10,000 of spend and $40,000 of Meta-attributed revenue is a 4.0x ROAS, and becomes 4.5x if Meta recognizes an extra $5,000 of previously unreported value while actual revenue does not change. Reported CPA and ROAS can improve without additional sales.
Meta has not said whether the extra conversions feed bidding and delivery, whether purchase value travels with them, or how they are deduplicated against Conversions API events. Code3 says influence on optimization is also unknown, and not every advertiser will necessarily see a change. Read a jump as newly visible credit.
What should advertisers lock before November 12?
If a pixel shows another date, or no date, follow Events Manager. Meta’s help articles describe the setting without a date. Before the label flips:
- Confirm the switch on every pixel under Data sources and Settings, including other brands, countries and clients.
- Export the last four weeks per campaign: purchases, purchase value, cost per purchase and ROAS, beside real orders and revenue.
- Annotate November 12 and tell the people who read the reports, including agency clients, before the numbers move.
- Leave it on for more campaign credit if the site qualifies, or switch it off to keep holiday reporting comparable, if a privacy statement or client contract does not cover it, or to wait on the open questions.
- Keep the Conversions API, with the same event ID as the pixel, so each order counts once, including for EU visitors.
Scale on shop orders each week, not on Ads Manager alone, including before any Meta-versus-search revenue read. Code3 suggests platforms such as GA4 and Northbeam as a cross-check, because the methods differ and discrepancies may become more noticeable.
Meta has not explained consent or what the device code reads. Advertisers remain responsible, and the EU and UK exclusion does not retire the banner elsewhere.
Frequently asked questions
When do Meta on-device conversions start?
Events Manager shows measurement starting November 12, 2026, on by default for eligible pixels. If a pixel shows another date or no label, follow that screen, because Meta’s help articles describe the setting without a date.
Does a higher reported ROAS mean more orders?
Not necessarily. Attributed conversions can rise, and cost per purchase and ROAS can improve, while real sales stay the same.
Who is excluded from the setting?
It is not active for visitors in the EU or the UK. The pixel must sit directly on the page, not in an iframe or as an image-only pixel, and the site must ask visitors to log in with an email or phone number.
Does this replace the Conversions API or change the attribution window?
No. The attribution window and model stay the same, and the setting works alongside the pixel and the Conversions API. It can be switched off at any time, per pixel.
