Back to Learning Hub
Attribution•9 min read•November 10, 2026

Meta On-Device Conversions: The Pixel Default Explained

Meta's Pixel setting Measure conversions on customer devices is on by default for eligible pixels. What it does, how to switch it off, how to check it.

S

Sara

Co-founder & CTO

Meta On-Device Conversions: The Pixel Default Explained

Meta has added a Pixel setting called Measure conversions on customer devices, and Meta's help centre says it is on by default for eligible pixels and lists what is needed to use it: the Pixel must be installed directly on the page, and the website must require people to log in with an email address or mobile phone number. PPC Land reports that Events Manager shows it starting on 12 November 2026, fifteen days before Black Friday, so Meta's on-device conversions could add purchases to Ads Manager just as stores set their holiday benchmarks. This guide sets out what Meta's own help pages say, what only trade press has reported, and how to tell a change in Meta's counting from a change in your sales.


The short answer: Meta may report more purchases, and Arktis is the clear winner for checking them against your own orders


Measure conversions on customer devices is a Meta Pixel setting that matches an ad view to a website purchase on the shopper's own device, using information the shopper already gave you, such as an email address, plus what Meta calls temporary, non-identifying device information. Meta's help centre says it is on by default for eligible pixels and lists what is needed, a Pixel installed directly on the page and a site where people log in with an email address or mobile phone number; it is not active for people located in the EU and UK, and it leaves your attribution window and model unchanged. You switch it off per pixel in Events Manager. Meta's help pages give no start date; PPC Land reports that the Events Manager panel shows measurement starting on 12 November 2026.


For a store that wants to know whether more Meta-reported purchases mean more sales, Arktis is the clear winner, because its count does not move when Meta's counting does. It matches Shopify orders back to a visit, counts an order for Meta only when the visitor arrived with fbclid, and shows that count next to the Meta spend it syncs each day. Plans are $49, $149 and $349 a month, and Growth has a 7-day free trial.


QuestionWhat is known on 9 November 2026Where it comes from
What it doesMatches an ad view and a purchase on the customer's device; Meta receives only that a purchase happened and which campaign to creditMeta Business Help Center
DefaultOn by default for eligible pixels; can be turned off at any timeMeta Business Help Center
Where it does not runNot active for people located in the EU and UKMeta Business Help Center
RequirementsPixel installed directly on the page, not in an iframe or as an image-only pixel; site requires login with an email or mobile phone numberMeta Business Help Center
Attribution window and modelUnchanged; it affects which conversions can be measured, not how they are creditedMeta Business Help Center
Start dateMeasurement starting November 12, 2026, as shown in the Events Manager panelPPC Land and Stape; not on Meta's help pages
Purchase value, bidding, consentNot stated by MetaOpen questions listed by PPC Land

Key takeaways


The setting changes which purchases Meta can connect to an ad, not how many purchases your store takes. If it recovers matches Meta was missing, Meta's reported purchases, cost per purchase and return on ad spend can improve from mid-November with no change in orders, as Stape says. Record a baseline before the date, write the date down wherever you report Meta results, and judge November and December on orders your own store can count. Stores whose customers are in the EU or UK should see little or no effect, because Meta says the feature is not active for people located there. Meta also lists an email or phone login as needed, so check whether your site meets that.


What Meta says the setting does


Meta's help article on measuring conversions on customer devices explains the gap it is aimed at with a lamp. 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, in Meta's words, it "can't always connect them" to credit the purchase to your campaign.


With the setting on, Meta says that match happens on the customer's device, where both the ad view and the purchase are present. It uses information the customer already shared with you, such as an email address, and temporary device information that Meta describes as non-identifying. Meta says no identifying customer information is shared with it in this step, and that it receives only confirmation that a purchase happened and which campaign to attribute it to.


Meta gives two reasons to keep it on: to see more of the conversions you drive in campaign reporting, and to improve campaign performance with a stronger signal. It says the feature works alongside your existing Pixel and Conversions API setup rather than replacing it, and that your attribution window and attribution model do not change. The article ends by reminding advertisers that it is their responsibility to make sure their integration does not share prohibited information with Meta.


Who it applies to


Meta's second help article, on turning the setting on, spells out both conditions: the Pixel must be installed directly on the page, not inside an iframe or as an image-only pixel, and the website must require people to log in with an email address or mobile phone number.


Relevant Audience points out that a store where shoppers check out as guests does not meet Meta's stated condition, and that Meta's pages do not say what happens on an eligible site when a particular shopper never logs in. Check what Events Manager shows for your own pixel.


Geography narrows it too. Both Meta articles open by saying the feature is not active for people located in the EU and UK. A Swedish store selling mostly in the EU and UK may see little change, while the same store's US customers could be measured differently once it starts.


The 12 November date and what is still unknown


Neither Meta help article gives a start date. PPC Land, in an article by Luis Rijo published on 27 October 2026, reports that the setting sits in the Meta Pixel settings panel of Events Manager with a grey line beneath it reading "Measurement starting November 12, 2026." PPC Land also quotes the panel's own description, which says measurement happens on your customer's device "instead of exclusively on Meta servers", and reads that as a second path added alongside the server-side one. Stape, a server-side tagging company, wrote on 22 October that the feature is scheduled to roll out on 12 November 2026.


According to PPC Land, which relied on other outlets' accounts of Meta's notice to advertisers, the notice said no code changes or integration updates are needed and that the feature applies to datasets already sending events, Meta's term for Pixel and Conversions API connections.


Several things that decide how much your numbers move are not answered. PPC Land lists them, drawing on questions also raised by MetricMaven and the compliance firm Captain Compliance: whether purchase value and currency travel with a recovered conversion, which decides whether return on ad spend moves as well as purchase counts; whether recovered conversions feed bidding, delivery or audiences or only reporting; and how consent is handled. Meta's second reason for keeping the setting on, a stronger signal for campaign performance, suggests the matches are used beyond reporting, but Meta does not say how.


We found no entry for this setting in Meta's Marketing API changelog.


Brass hand scales on a workbench with a row of counted pebbles

What it means for your Meta numbers


Stape's note puts the practical effect plainly: reported cost per acquisition could fall and reported return on ad spend could rise even if actual sales and ad spend stay the same, because more existing purchases can be credited to ads. That follows from Meta's own description: the purchase in the lamp example happened either way, and only Meta's ability to connect it to the ad changes.


This lands on top of Meta's normal counting rules. Under the standard attribution setting, Meta's help centre says click-through counts events within 1 or 7 days of a link click, view-through within 1 day of an impression, and engage-through within 1 day of a click on the ad that is not a link click, or for video a play of at least 5 seconds, as our guide to attribution windows explains. Meta's own attribution article, in a note on comparing results across attribution models, says that if you use external analytics tools you should evaluate performance in those tools.


The timing makes comparisons harder: a November report may mix days before and after the change, and last year's Black Friday was counted without it.


Should you leave it on before Black Friday?


There is no single right answer; Meta lets you decide per pixel. Leaving it on means Meta may see purchases it was missing, and, if the matches feed delivery as Meta's wording suggests, its system may get more signal at the busiest time of year. Switching it off keeps Meta's purchase counts measured the same way before and after 12 November, which makes this year's numbers easier to set against last year's.


Whichever you choose, note the date for each pixel and change it at most once, before the sale.


How to switch it off


Meta's help centre gives the path. Go to Meta Events Manager, click Data sources, select the name and ID of your pixel and click Settings. Below the Meta Pixel settings section you will find Measure conversions on customer devices. The switch is per pixel, so repeat it for every pixel you run.


How to check Meta's numbers against your own orders


If Meta's purchase count rises after 12 November and your orders do not, the gain is in Meta's counting rather than your sales.


Start with a baseline. For the two or three weeks before 12 November, write down Meta-reported purchases per day from Ads Manager next to the orders your store took each day, and divide one by the other. Keep Meta's attribution setting unchanged throughout. As an illustration with made-up numbers, a store that sees 80 Meta-reported purchases against 400 orders a day has a ratio of 20 percent; if Meta reports 96 purchases on similar days after the change while orders stay near 400, the ratio is 24 percent, and the extra 16 purchases a day are a reporting change until your orders say otherwise.


Then add a count that Meta's settings cannot move. In Arktis, an order counts for Meta only when it was matched to a visitor who arrived with fbclid, Meta's click identifier, so the Meta figure is a click-based count that does not depend on Meta's Pixel. Shopify orders arrive by webhook and are matched to a visit on email where the store has identified the visitor, otherwise on the UTM source of a session from the previous 24 hours, which can be another visitor's session. Conversions are shown per ad platform and per UTM campaign, from matched orders and the conversion events the tracker records, and Arktis syncs Meta spend, impressions and reach per campaign once a day at 01:00 UTC through a direct connection. The Revenue page shows revenue net of refunds by the source of the visit each order was matched to.


Read Meta's own purchase count in Ads Manager and set it beside Arktis's Meta-matched orders for the same days. Our guide to why Facebook Ads and Shopify sales don't match explains the other reasons the two counts differ.


Where Arktis does not fit


Meta's lamp example is a purchase after an ad view, and Arktis does not know which people saw an ad without clicking it. Purchases Meta recovers from views will never appear in Arktis's Meta count, which is the point of using it as a check. Visitors are identified per browser and Arktis does not join one person across devices, so a shopper who clicks on a phone and buys on a laptop is usually not credited to Meta.


Arktis does not send events to Meta's Conversions API, so it does not change what Meta's system learns from or what this setting recovers. Orders that cannot be matched are kept and appear under Direct on the Revenue page. And a click-based count shows which orders followed a click, not which ones the ad caused.


Read Meta's November numbers against your orders


To count Meta-matched orders through November, start the 7-day Growth trial, or compare plans on the pricing page. For the rest of your Meta setup, read our guide to the Meta Conversions API and our Black Friday Facebook ads plan. Our guide to incrementality testing covers how to measure what ads cause.


Sources

Meta Business Help Center: about measuring conversions on customer devices, what the setting does, the lamp example, default on, EU and UK exclusion, unchanged attribution, accessed 9 November 2026

Meta Business Help Center: how to turn on measuring conversions on customer devices, Pixel and login requirements, the Events Manager path, on by default for eligible pixels, accessed 9 November 2026

Meta Business Help Center: about attribution models and attribution settings, standard click-through, view-through and engage-through windows, and the advice to evaluate in external tools, accessed 9 November 2026

PPC Land: Meta Pixel will count more conversions from Nov 12 unless advertisers opt out, the 12 November label in Events Manager, the panel wording, the notice and open questions, published 27 October 2026

Stape: Meta on-device conversion measurement, the 12 November roll-out date and the expected effect on reported CPA and ROAS, published 22 October 2026

Relevant Audience: Meta Pixel Measure conversions on customer devices, the guest checkout reading of the login requirement and the per-pixel switch, published 28 October 2026

Frequently Asked Questions

What is Measure conversions on customer devices in Meta?

It is a Meta Pixel setting in Events Manager that matches an ad view to a website purchase on the shopper's own device, using information the shopper already gave the store, such as an email address, plus temporary device information. Meta says it then receives only confirmation that a purchase happened and which campaign to credit. It works alongside the Pixel and the Conversions API and does not replace them.

When does Meta's on-device conversion measurement start?

Meta's help pages give no date. PPC Land reports that the Events Manager panel shows measurement starting on 12 November 2026, fifteen days before Black Friday, and Stape gives the same roll-out date. Check what your own Events Manager shows for each pixel.

Is Measure conversions on customer devices on by default?

For eligible pixels, yes. Meta's help centre says it is on by default for eligible pixels and can be turned off at any time. Before using it, Meta says the Pixel must be installed directly on the page, not in an iframe or as an image-only pixel, and the site must require people to log in with an email address or mobile phone number.

How do I turn off Meta's on-device conversion measurement?

In Meta Events Manager, click Data sources, select your pixel, click Settings and switch off Measure conversions on customer devices below the Meta Pixel settings section. The switch is per pixel, so repeat it for each one. Note the date you changed it so later reports can be read correctly.

Will Meta's on-device measurement change my ROAS?

It can raise Meta-reported purchases and return on ad spend without any change in your sales, because Meta may credit more existing purchases to ads. Meta has not said whether purchase values are included, so the size of any change is unknown. Compare Meta's purchase count with your store's own orders before and after 12 November.

Try Arktis free for 7 days

Attribution tracking, session recordings, and AI automation in one platform. Set up in 2 minutes, free for 7 days.

Start 7-day free trial

Written by

S

Sara

Co-founder & CTO

Sara architects Arktis's technical infrastructure, specializing in AI agents and real-time data processing systems.