Meta Pixel's "Measure Conversions on Customer Devices" Setting: What to Do Before November 12

TL;DR

• What it is: a Meta Pixel setting that matches some ad views to purchases on the shopper's own device. Meta says it's on by default for eligible pixels, and it isn't active for people in the EU and UK.
• Why it matters now: trade reports say measurement starts November 12, 15 days before Black Friday. Meta says the point is to show more of your conversions in reporting, so your reported purchases can rise with no change in real sales.
• What to do this week: record Meta-reported purchases next to your real orders, find the toggle on each pixel and decide on or off by November 20.
• The Shopify catch: Meta requires a pixel directly on the page, not in an iframe, and a site that requires login. Shopify says custom pixels run in an iframe, and most stores don't force login. So check your own toggle, and don't force login to qualify.
• Conversions API vs Pixel: the Pixel sends events from the browser, the Conversions API from your server. Meta recommends both, with matching event IDs. This setting replaces neither.
• Still unknown: whether recovered conversions affect bidding, whether they carry a purchase value and how consent signals are handled.

The Real Question: Will a Better ROAS This Month Be Real?

If you run Meta ads for a Shopify or DTC store, this is the scenario to plan for. Your reported purchases go up in mid-November, your ROAS looks better and you raise budgets just before Black Friday. But your store didn't get more orders. Meta simply got credit for orders it couldn't connect to an ad before.

That may not happen to your account. But you can only tell the difference if you write down your numbers first, and that window closes this week.

What Meta Confirms, and What It Doesn't

Meta explains the setting on two Business Help Center pages. It's called Measure conversions on customer devices.

What Meta says:

• Someone sees your ad on Instagram and buys on your site two days later. Meta may have both records, but "can't always connect them". With this setting on, that match happens on the customer's device.
• The match uses information the customer already shared with you, like an email, plus "temporary, non-identifying device information".
• Meta says it receives only confirmation that a purchase happened and which campaign to credit.
• It's on by default for eligible pixels, and you can turn it off at any time.
• It isn't active for people located in the EU and UK.
• Your attribution window and model don't change.
• It works alongside your Pixel and Conversions API and doesn't replace them.

The date: Meta's help pages don't give one. November 12 comes from trade reports. PPC Land quotes the Events Manager panel as reading "Measurement starting November 12, 2026", and Wortfilter reports an email to advertisers that describes a gradual rollout. So don't expect a sharp jump on one day.

Who said what on the numbers: Meta's own reasons to keep it on are to see more conversions in reporting and to "improve campaign performance with a stronger signal". The warning that CPA and ROAS can improve with no change in real sales comes from people outside Meta, including Stape and PPC Land. It follows from the math, but Meta hasn't published how many conversions this adds.

Does Your Shopify Store Even Qualify?

This is the part most coverage skips. Meta lists two requirements: the Pixel must be installed directly on the page, "not inside an iframe or as an image-only (img) pixel", and your website "must require people to log in to an account using an email or mobile phone number".

Set that against Shopify's own documentation:

Login is the bigger question. Shopify does have a setting, "Require customers to sign in to their account before checkout", under Settings, Checkout. Unless a store has turned it on, shoppers can check out without an account. Meta doesn't explain how its rule applies to optional accounts or guest checkout, and PPC Land reports that these requirements don't appear in the panel or the notice.

Two things to do with this:

1. Look at the toggle, don't assume. In Events Manager, go to Data sources, select your pixel, click Settings and look below the Meta Pixel settings section. Check each pixel, since the setting sits on the pixel. If it's on, plan as though your numbers could move, even if your store doesn't seem to meet the requirements.
2. Don't force login to get this. Shopify says that turning on required sign-in hides accelerated checkouts like Apple Pay from the cart and limits checkout to email. We wouldn't add that friction before Black Friday for a reporting feature.

What to Record Before November 12

This takes about 20 minutes. Do it for the 14 days from October 29 to November 11, by day.

1. Check for double counting first. If you send purchases through both the Pixel and the Conversions API without matching event IDs, Meta can count both. Fix that first, or your baseline is wrong (see below).
2. Export from Ads Manager: purchases, purchase conversion value, amount spent and your attribution setting.
3. Export from your store: paid orders and revenue, excluding cancelled orders.
4. Work out one number: Meta-reported purchases ÷ paid orders.
5. Write down what else is changing: sale dates, new creative and budget edits, so you don't blame the setting for them.

Then watch that ratio daily. Here's a made-up store with $12,000 in spend, where nothing changed but the count:

Each order is $60, so store revenue is $60,000 both times. The 15% lift is our example, not a Meta figure. Everything Ads Manager shows improved, and the store made no extra money. You can get the last column from our blended ROAS calculator.

Watch purchases and ROAS separately. Meta's description mentions a purchase and a campaign. It doesn't mention a purchase value. If your reported purchases rise and your conversion value doesn't rise with them, that's worth knowing, and it's why the table above is only one possible outcome.

Read the ratio before your sale starts. Black Friday traffic changes the ratio on its own. The cleanest stretch to read is November 12 up to your first promotion.

If You Sell in the UK or EU, You Have a Control

Meta says the setting isn't active for people in the EU and UK. So if you sell in both places, break your Ads Manager results down by country and compare the ratio for the US with the ratio for the UK or EU. If the US moves and the UK doesn't, that points to measurement rather than demand. It's a rough check, and it only helps if the smaller market has enough orders to read. It's our own suggestion, not something Meta recommends.

On or Off: How to Decide

Meta says it can be turned off at any time, so this isn't a permanent choice. We'd leave it on for most stores, as long as you judge budgets on real orders. Meta says it can improve performance, and nobody outside Meta can yet show otherwise.

Make the call by November 20 and don't change it during the sale. That's already the date for your last grouped edit in our Black Friday Meta ads budget guide. Meta doesn't say whether changing this setting affects learning, and switching mid-sale would make your numbers impossible to compare anyway.

And when you compare this Black Friday with last year's in Ads Manager, remember the count may not be measured the same way. Use store revenue for that comparison.

What Meta Hasn't Said

Here's what we couldn't find in Meta's pages, so nobody should state it as fact yet:

• Bidding and delivery. "A stronger signal" suggests recovered conversions could feed optimization, but Meta doesn't say so directly.
• Purchase value. Whether a recovered conversion carries an amount. That decides how much ROAS moves.
• Consent. How consent banners and opt-out signals affect the match. Meta says only that it's your responsibility not to share prohibited information.
• Reporting. Whether recovered conversions are labeled separately in Ads Manager.
• Double counting. How a device match is reconciled with a server event for the same order.

We'll update this post if Meta publishes more. Meta's other big change this month is its new ad terms, which start November 20, so review both together.

Meta Conversions API vs Pixel: What's the Difference?

A lot of sellers looking this up are also asking how it fits with the Conversions API. Here's how the three compare:

Do you need both the Pixel and the Conversions API? Meta's developer docs say: "we recommend that advertisers implement the Conversions API alongside their Meta Pixel". On Shopify, the Facebook & Instagram channel's Standard data sharing level uses only the Pixel, while Enhanced and Maximum add the Conversions API. You'll find it under Sales channels, Facebook & Instagram, Settings, Data sharing settings.

How to avoid double counting: when you send the same event both ways, Meta matches them on event ID and event name. If it finds a match within 48 hours, it discards the later one. If the IDs don't match, both can count.

If you're not sure your setup is right, our Meta ads management team can check it.

FAQ

What is "Measure conversions on customer devices" in Meta Pixel?

It's a setting in Events Manager that matches an ad view to a purchase on the shopper's device, then tells Meta a purchase happened and which campaign to credit. Meta says no identifying customer information is shared.

How do I turn off Measure conversions on customer devices?

In Events Manager, go to Data sources, select your pixel, click Settings and switch it off below the Meta Pixel settings section. Do this for each pixel you want it off on.

When does it start?

Trade reports say November 12, 2026, quoting the Events Manager panel and a notice to advertisers. Meta's help pages don't give a date, and the notice reportedly describes a gradual rollout.

Should I turn it off before Black Friday?

Not by default. Most stores can leave it on and judge budgets on real orders. Turn it off if budget rules or reports rely on Ads Manager ROAS and you can't change them in time.

Will my ROAS go up?

It might. Meta says you'll see more conversions in reporting, but it doesn't say whether those conversions carry a purchase value. Reported purchases and CPA are the first things to watch.

Does it apply to my Shopify store?

Possibly. Meta's requirements are a pixel directly on the page and a site that requires login, and many Shopify setups don't clearly fit either. Check the toggle on your pixel rather than assuming.

Does this affect Meta ads that send traffic to Amazon?

Meta's requirement is a Pixel installed on your own website, and you can't install one on an Amazon listing. So it would only apply to purchases on your own site.

Meta conversions API vs pixel: which one should I use?

Use both, as Meta recommends, with matching event IDs so each purchase is only counted once.

Bottom Line

This setting may change what you see, not what you sell. Record Meta purchases next to your paid orders before November 12, find the toggle on each pixel, decide by November 20 and leave it alone during the sale. If your ROAS jumps, check it against your orders before you raise a budget.

Want someone to read the numbers with you? Talk to our Meta ads team.