What changes in the Meta Pixel on November 12?

On Nov 12 the Meta Pixel may count more on-device conversions. Who it applies to, how to turn it off, and what to compare with store orders.

From November 12, 2026, the Meta Pixel may start counting more conversions on the customer's own device. The setting is called Measure conversions on customer devices, and Meta says it is on by default for eligible pixels. The number in Ads Manager can rise without the store selling more.

The November 12 date does not appear on Meta's Help Center pages. It has been reported in Events Manager, as the grey line "Measurement starting November 12, 2026," by PPC Land and Mintec. Check that line in your account. If measurement starts tomorrow, record the baseline today.

What is "Measure conversions on customer devices"?

On About measuring conversions on customer devices, Meta describes the feature this way: the system measures conversions on the customer's device, using information they already shared with you (like an email) and temporary, non-identifying device information.

Meta gives an example. Someone sees your ad for a lamp on Instagram, visits your website two days later, and buys it. Meta may have a record of the ad view and receive the purchase event, but cannot always connect them to attribute the purchase to your campaign. With the setting on, that match happens on the customer's device, where both the ad view and the purchase are present.

The same page says no identifying customer information is shared with Meta. Meta only receives confirmation that a purchase happened and which campaign to attribute it to. The feature works alongside your existing Pixel and Conversions API setup and does not replace it.

When does the change start?

On both help pages, read on November 11, 2026, Meta does not state a start date. November 12 comes from the grey text under the toggle in Events Manager, according to PPC Land and Mintec. Open your own panel and read what it says. A staggered rollout is possible; that is not in the help pages.

Does this apply to my store?

Not automatically. How to turn on measuring conversions on customer devices lists conditions before you use the feature:

  • You must install the Meta Pixel on your website, directly on the page, not inside an iframe or as an image-only (img) pixel.
  • Your website must require people to log in to an account using an email or mobile phone number.

Both help pages also state that the feature is not active for people located in the EU and the UK. Stores elsewhere can be affected if the pixel qualifies and the visitor is not in those territories. A shopper in the EU or the UK is excluded even if your store is elsewhere.

Meta requires the site to make people log in with an email or mobile number. It does not say what happens when the store also offers guest checkout. If you sell without an account, check whether the setting appears; the feature may not apply.

The control is per pixel, on by default for eligible pixels, and you can turn it off at any time.

Does this change the attribution window or ROAS?

The attribution window and model do not change. Meta says this clearly: the feature affects which conversions can be measured, not how they are credited to your ads. It is not a new window or a new model.

Report volume can change. If Meta starts connecting purchases that previously had no credit, Ads Manager can show more conversions. That does not prove the campaign started selling more. The store remains the source of paid orders.

On ROAS, the public documentation is incomplete. Meta says it receives confirmation that a purchase happened and which campaign to attribute it to. It does not say whether the value and currency enter the report. If value travels with the recovery, reported ROAS can rise with the count. If only the fact of the purchase travels, conversions rise and attributed revenue may not follow. Until Meta spells that out, compare against paid-order revenue from the store.

Meta also asks you to keep the setting on to see more conversions in campaign reporting and to "improve campaign performance with a stronger signal." That phrase points toward delivery, but it does not describe whether recovered conversions enter bidding, audiences, or value optimization.

Should I turn the setting off?

Not by reflex. First check whether your pixel qualifies and record the toggle state. Then compare Meta's report with paid store orders, before and after the date shown in your panel.

Leave it on if the pixel qualifies, you want matches that currently fall out of reports, and you will judge the account on paid orders, not only on Ads Manager ROAS. Turn it off if you need a stable number in Meta's report over the coming weeks (a close, a contract, a Black Friday comparison already agreed) or if, after the date, the gap between Meta and the store widens in a way you cannot explain.

Turning it off does not replace the Conversions API or the Pixel. Meta says the feature works alongside both. Keep the tracking you already use.

How do I turn it off in Events Manager?

The official path, from Meta's setup page, is the same place you would turn it on:

  1. Go to Meta Events Manager.
  2. Click Data sources.
  3. Select the name and ID of your pixel.
  4. Click Settings.
  5. Below the Meta Pixel settings section, turn off Measure conversions on customer devices.

Repeat for every pixel on the account. Note the date and whether the setting was on or off. Meta also reminds you that it is your responsibility to make sure your integration does not share prohibited information with Meta.

What should I compare before and after the date?

Use a short method. The aim is to separate a change in counting from a change in sales.

  1. In Events Manager, check whether the setting appears and which date is written under it. For each pixel, record whether it is on or off.
  2. For the weeks immediately before the panel date, log daily Ads Manager attributed purchases, spend, and paid store orders. Calculate the ratio of Meta purchases to paid orders.
  3. After the date, continue the same series, in the same time zone, using paid orders, not merely created orders (a delayed payment still pending is not revenue yet).
  4. Split the window into "before the change" and "after the change." Do not compare this November with last November as if the counting rule were the same.
  5. If Meta rises and paid orders stay flat, treat the movement as measurement. If paid orders rise too, there is a cash effect to investigate.

This kind of comparison was already needed when Ads Manager and the store disagreed. Why Meta Ads sales don't match your store covers attribution windows, report dates, and order status.

When does it make sense to look at orders another way?

When the question is "how much did the store actually sell, and which ad brought the paid order?", not only "how many conversions did the Pixel start attributing after the change?".

Clakta connects visits and clicks to the orders your store confirms and shows credit under the model you choose. Revenue comes from the same store orders, with status; a pending delayed payment does not count as revenue yet; refunds and cancellations update the same order. Your Meta Pixel stays in place: Clakta runs beside it and does not change the platform report (What is Clakta, How attribution works). For stores, see the ecommerce page.

Meta and the store remain different numbers. After November 12, that gap may change size. It remains useful to put the real order next to what the platform shows.

Frequently asked questions

Will my Meta conversions go up on the 12th?

They may, if the pixel qualifies and the feature starts connecting purchases that previously had no credit. They may also stay flat if the store does not require a login, the Pixel is not installed directly on the page, or much of your traffic comes from the EU or the UK. There is no official increase percentage.

Does a store that sells without an account qualify?

Meta requires people to log in to an account with an email or mobile number. It does not spell out guest checkout. If your store does not require a login, the feature may not apply. Check whether the setting appears on your pixel.

Does this apply outside the EU and the UK?

The exclusion Meta documents is for people located in the European Union and the United Kingdom. Visitors elsewhere can be included if the other conditions are met.

Do I need to change code or the Conversions API?

Meta describes the feature as a setting in Events Manager that works alongside the Pixel and the Conversions API and does not replace them. The help pages do not include a code-change step. Keep both as they are, unless you already had a tracking problem.

Should I turn it off before Black Friday?

Not automatically. Black Friday 2026 falls on November 27, two weeks after the date reported in the panel. The risk is mixing two counting rules in the same period comparison. Record a baseline, mark the date on your reports, and judge campaigns against paid orders as well.

Does Ads Manager ROAS become more reliable?

Not necessarily. The attribution window and model stay the same. What changes is the set of conversions Meta can measure. Use Ads Manager ROAS to compare ads with each other under the same rule, and paid store orders to decide whether the spend fits the cash account.