Meta Pixel turns on 'Measure conversions on customer devices' by default outside the EU and UK

Meta has added a Pixel setting called "Measure conversions on customer devices" to Events Manager, and it is switched on by default for eligible pixels, though Meta says it is not active for people located in the EU and UK. According to Meta's Business Help Center article on measuring conversions on customer devices, the feature matches an ad view to a purchase on the shopper's own phone or computer, using information the customer already gave the advertiser (such as an email address) plus temporary device information, and sends Meta only the fact that a purchase happened and which campaign gets the credit. Advertisers in Thailand are inside the eligible area, so anyone running a Pixel on a site with an email or phone-number login should check this setting now.

This article sets out what Meta's two help pages actually say, how the matching works in Meta's own example, who qualifies, where the toggle sits, what trade press has reported about the start date, and which questions Meta has not answered. The final sections are labelled analysis: what a Thai advertiser should check before the November sales period, given what is and is not known.

What Meta says the setting does

Meta's help article opens with a geographic limit: measuring conversions on customer devices "is not active for people located in the EU and UK." Everywhere else, Meta describes the setting as a way for the Meta Pixel to "measure conversions that would otherwise go unmeasured."

When the setting is on, Meta says the system measures conversions on the customer's device. It uses two inputs: information the customer has already shared with the advertiser, with an email given as the example, and what Meta calls "temporary, non-identifying device information." Meta states that the setting is turned on by default and gives two reasons to leave it on. The first is to see more of the conversions a campaign drives in campaign reporting. The second is to "improve campaign performance with a stronger signal."

Meta also sets out what does not change. The help article says the feature works alongside an existing Pixel and Conversions API setup and does not replace either. It says the attribution window and attribution model stay the same, and that the setting affects which conversions can be measured, not how they are credited to ads. The article closes with a reminder that it is the advertiser's responsibility to make sure its integration does not share prohibited information with Meta.

How the on-device match works in Meta's example

Meta explains the mechanism with a lamp. A person sees an ad for a lamp on Instagram, then visits the advertiser's website two days later and buys it. Meta may have a record of the ad view and may also receive the purchase event, but, in Meta's words, it "can't always connect them" to attribute the purchase to the campaign.

With the setting on, Meta says the match happens on the customer's device, where both the ad view and the purchase are present. Meta's help page states that no identifying customer information is shared with Meta in this step, and that Meta only receives confirmation that a purchase happened and which campaign to attribute it to.

Put plainly, the gap Meta is describing sits between two records it already has. The ad view is on Meta's side. The purchase event arrives through the Pixel or the Conversions API.

Trade publication PPC Land, in an article by Luís Rijo published on 27 October 2026, quotes Meta's description in the Events Manager settings panel as saying the measurement happens on the customer's device "instead of exclusively on Meta servers." PPC Land reads that wording as a second, device-side path added next to the existing server-side one, which matches the help page's statement that the feature does not replace the Pixel or the Conversions API.

Who is eligible, and where the toggle is

A companion Meta help article, "How to turn on measuring conversions on customer devices," lists two conditions. The Meta Pixel must be installed directly on the page, and Meta specifies "not inside an iframe or as an image-only (img) pixel." The website must also require people to log in to an account using an email address or a mobile phone number.

The same page gives the path to the setting:

• Go to Meta Events Manager.
• Click Data sources.
• Select the name and ID of the pixel.
• Click Settings.
• Below the Meta Pixel settings section, find "Measure conversions on customer devices."

Meta says the setting is on by default for eligible pixels and can be turned off at any time. Because the control sits inside each pixel's settings, an advertiser with several pixels, for example one per brand or per country site, has a separate switch for each.

The login requirement narrows the field more than it first appears. A store where shoppers check out as guests, or a lead-generation site with no account system, does not meet Meta's stated condition. Meta's help pages do not say what happens on an eligible site when a particular shopper never logs in.

The 12 November date comes from the Events Manager panel, not the help pages

Neither Meta help article gives a start date. The date reported in trade press comes from the Events Manager interface itself. PPC Land reports that the line "Measurement starting November 12, 2026" appears in grey under the new toggle in the Meta Pixel settings panel. PPC Land also reports that the German blog Wortfilter and the Philippine news site ASTIG covered Meta's notice on 18 October 2026, and that the notice says no code changes or integration updates are needed.

Separately, the tagging-tool vendor Stape published a note on 22 October 2026 saying the feature is scheduled to roll out on 12 November 2026. Stape writes that it requires no new Conversions API integration and that no extra action is expected from advertisers.

Meta itself has not published the date on its help pages, so 12 November should be read as the date shown in Events Manager as reported by PPC Land and Stape, not as a date Meta has confirmed in writing. Advertisers can check their own Events Manager panel to see what it shows for each pixel.

The data below compares what each source says.

What Meta has not said

Meta's two help pages are short, and several points that matter to advertisers are not covered. PPC Land listed open questions that Meta's notice does not answer, including:

• Whether conversions recovered this way feed bidding, delivery or audiences, or only reporting.
• Whether purchase value and currency are passed on, which decides whether reported ROAS moves as well as conversion counts.
• How consent is handled, and whether visitors who declined consent or sent opt-out signals are excluded.
• Which browsers and operating systems are supported, and whether it runs in apps, in the browser, or both.

One of those questions is partly addressed by Meta's own wording. The help article's second reason to keep the setting on is to "improve campaign performance with a stronger signal," which implies the extra matches are used beyond reporting. Meta does not say how, or whether that covers bidding, delivery or audience building. Meta also does not explain what the "temporary, non-identifying device information" consists of.

What could change in reporting

Stape's note spells out the most practical effect. It says reported cost per acquisition could fall and reported return on ad spend could rise even if actual sales and spend stay the same, and that more attributed conversions do not necessarily mean more actual conversions. Stape recommends monitoring reporting after rollout and investigating unexpected changes.

That follows from Meta's own description. If the feature only recovers the link between an ad view and a purchase that was already happening, the business sells the same amount, but Meta's reporting shows more of those sales as ad-driven. The attribution model has not changed, yet the number in the conversions column can still go up.

What this means for Thai marketers (analysis)

This section is Relevant Audience analysis based on the sources above, not a statement from Meta.

Thailand is outside the EU and UK, so Thai pixels are not covered by the regional exclusion. A Thai brand that meets the two conditions, a directly installed Pixel and an email or phone login, will have the setting on unless someone turns it off. The reported start date of 12 November falls one day after the 11.11 sale and about two weeks before Black Friday on 27 November. That means November reporting could mix days before and after the change, and a jump in Meta-reported purchases in the second half of the month could come partly from measurement rather than from the campaigns.

Practical checks before and after the reported start date:

• Record a baseline now. For each eligible pixel, note Meta-reported purchases, CPA and ROAS for a recent stable period, alongside the order count and revenue in the store's own back end or CRM. The ratio between the two is what to watch after 12 November.
• Open Events Manager and check the toggle on every pixel. Confirm which pixels Meta treats as eligible and what the panel says about the start date.
• Decide per pixel whether to keep it on. Meta's help page says it can be turned off at any time. The decision belongs with whoever owns measurement for that brand, and it is worth writing down so the November and December reports can be read correctly.
• Annotate the date in reporting dashboards and in any GA4 or Looker Studio reports that compare Meta-reported conversions with site data, so a step change is not read as a performance gain.
• Review consent and privacy notices with legal counsel. Meta says the advertiser is responsible for not sharing prohibited information, and it has not said how consent signals are handled for this feature.
• Keep the existing Pixel and Conversions API setup as it is. Meta says the new setting works alongside both and does not replace them.

Relevant Audience's earlier explainer on how the Meta Pixel and the Conversions API work together, published on 5 October 2026, covers event deduplication and setup checks. Those basics still apply, since Meta says this setting sits on top of the existing setup. Brands that want help reading their Meta numbers through the change can look at Relevant Audience's Facebook Ads management, its paid social advertising service, or its GA4 setup and measurement work for reconciling ad-platform data with site analytics.

Frequently asked questions

Is "Measure conversions on customer devices" active in Thailand?

Yes, Meta's help pages exclude only people located in the EU and UK, so Thai pixels that meet the requirements are eligible and the setting is on by default. Meta does not list a separate country rollout schedule.

Do I need to change my Pixel or Conversions API code?

No, according to Meta's notice as reported by PPC Land, no code changes or integration updates are needed. Meta's help page says the feature works alongside the existing Pixel and Conversions API setup and does not replace it.

When does measurement start?

The Events Manager panel shows "Measurement starting November 12, 2026," according to PPC Land's report of the notice and Stape's note. Meta's help pages themselves do not state a date.

Will my ROAS go up?

Reported ROAS may rise without any change in real sales, Stape warns, because more existing purchases can be credited to ads. Meta has not said whether purchase value and currency are included, so the size of any ROAS change is not known.

How do I turn it off?

In Meta Events Manager, go to Data sources, select the pixel, click Settings and switch off "Measure conversions on customer devices" below the Meta Pixel settings section. Meta says it can be turned off at any time, and the switch is per pixel.

Meta's change is small in code and large in reporting. Recording a baseline before 12 November costs an hour and makes the November numbers readable afterwards.