Meta introduces on-device conversion matching with a staged November rollout

What changed

Dario Zannoni has reported an announcement in Meta Events Manager for a feature labelled “Measure conversions on customer devices.” His screenshot says that eligible Meta Pixels would begin receiving the feature from 12 November 2026, with the setting shown as on.

Zannoni describes the feature as using first-party customer information, such as an email address or phone number, together with temporary device information to match ad interactions to website conversions on a customer’s device. In his account of the notice, only the attribution result is sent to Meta rather than the identifying information used in matching.

The potential measurement value, according to Zannoni, is attribution of website conversions that were previously not matched to earlier ad clicks or views. His post also says the feature requires sites where people log in using an email address or phone number, is not available for people in the EU or UK, and can be disabled in Events Manager settings.

Those technical and privacy descriptions are attributed to Zannoni’s post, not independently confirmed in official documentation reviewed so far. The supplied evidence does support the notice wording on eligible pixels and the 12 November rollout start, but it does not establish full account eligibility, precise regional treatment or the mechanics of local matching.

Zannoni also flags unanswered questions around checkout-only registration, anonymous earlier visits and cross-device matching. Advertisers should therefore treat this as a rollout notice requiring account-level review, rather than an assurance about measurement coverage or privacy outcomes.

For an affected account, record the notification, the eligible pixel and the displayed setting before deciding whether to keep the feature enabled. Review the organisation’s own consent, access and measurement requirements with the appropriate owner. The screenshot shows an On toggle in this account, but does not prove that every account is automatically enrolled. Compare any later reporting changes against other tracking or campaign changes rather than assume that the new setting caused them.