Meta advertisers may see a change in how eligible Pixel datasets measure purchases from November 12, 2026. Industry reporting says a setting called “Measure conversions on customer devices” is scheduled to become active by default for eligible datasets that already send events. The reported date and behavior should be checked against the notice shown in each advertiser’s Events Manager account.

What is being reported?

The reported feature is intended to help measure purchases that may not be captured through the usual browser-based event flow. The description says Meta can match an ad view with a later purchase using information a customer has already provided to the business and temporary device-related signals. Meta’s stated explanation, as reported, is that it receives confirmation of a purchase and the campaign attribution rather than identifying customer details.

The reported setting is called “Measure conversions on customer devices” and is expected to appear in Meta Events Manager. The change is described as applying to eligible Pixel datasets, not necessarily every website or every event type.

Who may be affected?

Reporting on the feature describes eligibility conditions that include a Pixel installed directly on the website and a site where customers log in using an email address or mobile number. The reporting also says the feature is not active for people located in the European Union and United Kingdom. Advertisers should confirm the current eligibility criteria and applicable regional restrictions in Meta’s own documentation and account notices.

What advertisers should check before November 12

  • Review Events Manager notices: Check the relevant data source and its settings for the feature name, effective date and eligibility information.
  • Review privacy disclosures: Confirm that website privacy notices and internal data-handling practices accurately describe the measurement technologies in use.
  • Check Pixel implementation: Verify that the Pixel is installed correctly and that events are not duplicated or incorrectly configured.
  • Keep Conversions API monitoring in place: This reported measurement change should not be treated as a reason to remove or neglect an existing server-side setup.
  • Annotate reporting dashboards: Record the date so that any change in platform-reported conversions can be interpreted in context.
  • Compare with business records: Monitor actual orders and qualified leads alongside Meta-reported conversions.

Could reported conversions increase without additional sales?

Potentially, yes. If a measurement system captures purchases that were previously missing from platform reporting, reported conversions may rise even when the underlying number of sales has not changed. Advertisers should separate measurement changes from genuine performance improvements by comparing platform data with order-management or CRM records.

Important limitations

The November 12 date and the described default behavior come from industry reporting of Events Manager notices and settings, rather than a public Meta announcement located for this article. The exact eligibility rules, event coverage and rollout may change. Advertisers should treat the notice inside their own account and Meta’s current help documentation as authoritative.

Sources

MarketNex editorial note: This is a reported upcoming measurement change, not a confirmed universal change for every Meta advertiser. Verify the feature and date in Events Manager before making account changes.