Should You Turn Off Meta's Measure Conversions on Customer Devices?

There is no confirmed right answer yet. Meta's Measure conversions on customer devices setting turns on by default on November 12, 2026 and may raise reported conversions without adding sales. Keep it on if you want Meta's newest reporting; turn it off per pixel if you need a clean before-and-after comparison. Either way, judge results on store orders.

What does Measure conversions on customer devices do?

The setting moves part of Meta's conversion matching onto the shopper's own device. According to PPC Land's report, the match uses information a customer already gave the business, such as an email address, plus temporary device information, and Meta learns only that a purchase happened and which campaign to credit. Stape's write-up adds that attribution windows and models are unchanged and that no code changes are needed.

For what changes on the date itself and how to reconcile the numbers, see why Meta can report more conversions than your store has orders after November 12. This post covers the decision that follows: whether to leave the setting on.

Is the setting even on for your store?

Not necessarily. Coverage reports that it is not active for people in the EU and UK. PPC Land, citing a third-party summary of Meta's Business Help Center, also reports two conditions: the pixel must be installed directly on the page rather than in an iframe or as an image-only pixel, and the site must require login with an email address or mobile phone number. Relevant Audience reads that as meaning guest checkout may not qualify. Those conditions do not appear in the settings panel as quoted by that coverage, so check the panel in your own Events Manager before you decide anything.

When does leaving it on make sense?

Meta's stated reasons are to show more conversions in campaign reporting and to give campaigns a stronger signal. Leaving it on fits teams that already judge campaigns on store revenue and margin, keep server-side tracking in place, and can explain a one-time step in reported results to whoever reads their reports. One vendor, Aimerce's CEO, said in a post cited by PPC Land that he would not opt out by default and suggested tracking Meta-attributed purchases against Shopify orders. That vendor sells Pixel tracking, so weigh it accordingly.

When does turning it off make sense?

Turning it off fits teams that need Meta's numbers to stay comparable with earlier weeks, for example when client reports, budget targets or year-over-year reads run through Black Friday week. It also fits teams that want to review how the setting handles consent and device data before using it. Meta says the advertiser stays responsible for not sharing prohibited information, and it has not said how declined consent or opt-out signals are treated. The cost of switching off is that you may lose conversions Meta says it could not otherwise measure.

How do you test it instead of guessing?

Because the switch is per pixel, you can only compare time periods, not run both settings at once, and Black Friday week will add seasonal noise. A simple routine keeps the read honest:

1. Record a baseline. Note Meta-reported purchases and store orders by day for the 14 days before November 12.
2. Pick one ratio. Divide Meta-reported purchases by store orders for the same day and campaign group. A ratio that steps up on November 12 while orders stay flat points to a counting change, not demand.
3. Write your rule first. Before the date, decide what would make you turn it off, for example the ratio moving past a level you set, or reports you send clients no longer lining up with their orders.
4. Hold budget changes for a week. Black Friday is November 27, so the seasonal lift will blur any before-and-after read. Compare against store revenue and margin, not reported ROAS alone.
5. Switch it off if your rule trips. In Events Manager, open the pixel and go to Settings, where trade coverage places the Measure conversions on customer devices toggle. The switch is per pixel, so you compare periods rather than running both settings at once.

The gap between ad-platform numbers and store numbers is not new. Why your ROAS in the ad platform differs from your store data covers the usual causes, and what a consent banner does to your ecommerce data explains how consent choices change what any platform can see.

What has Meta not said yet?

As of the coverage cited here, the details that decide how much this matters for budgets are still open. Meta has not said:

• Whether recovered conversions feed bidding, delivery or audiences, or only reporting. Meta's own wording about a stronger signal suggests a wider use, but it does not say how.
• Whether purchase value and currency are included, which decides whether reported ROAS moves.
• How the setting interacts with Conversions API deduplication.
• How shoppers who declined consent or sent opt-out signals are handled.
• Which browsers, operating systems and apps are supported, and what the temporary device information consists of.

Until those are answered, treat any change in reported ROAS as unconfirmed.

What if the real problem is on your site?

A setting cannot fix paid visitors who leave before they order. If clicks are steady and orders are not, look at the pages shoppers land on; how to find Shopify site issues that waste ad spend shows where to start. Noibu's ROAS agent follows paid traffic from the visit to the order on your own site, builds the changes, and hands them back for your approval. It works in the Noibu console and in AI tools like Claude through Noibu MCP.

Whichever way you set the toggle, start with Noibu's free website audit to see what your paid visitors do after the click.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Frequently asked questions