Meta Pixel accounts now carry a setting called Measure conversions on customer devices, and Meta’s help center says it is "turned on by default." The setting lets Meta connect an ad view to a later conversion on the visitor’s own phone or computer. It is not active for people in the EU and UK.
For nonprofits and associations, the setting matters most on pages where people log in: member portals, course platforms and stores with accounts. This piece covers what the setting does, which sites qualify, where the toggle sits in Events Manager, what is still unclear, and a short checklist. Facts are as of November 2, 2026, from Meta’s Business Help Center.
The short version: the setting can add conversions to your Meta reports that Meta could not connect before. It does not change your attribution window or model. It does not replace the Meta Pixel or the Conversions API. It only applies to sites that require a login with an email or phone number, so many donation pages will not qualify. Decide whether to keep it on, and note the date in your reports so a jump in conversions is not read as better ads.
What the new Meta Pixel setting does
Meta explains the feature in its help article About measuring conversions on customer devices. With the setting on, the system measures conversions on the customer’s device. It uses information the person already shared with you, such as an email address. It also uses what Meta calls temporary, non-identifying device information.
Meta gives a simple example. Someone sees an ad for a lamp on Instagram. Two days later, they visit the advertiser’s site and buy it. Meta may hold both the ad view and the purchase event, but it cannot always connect them.
With the setting on, the match happens on the customer’s device, where both records are present. Meta’s article states: "No identifying customer information is shared with Meta." According to the same article, Meta receives only confirmation that a purchase happened and which campaign gets the credit.
That is Meta’s description. Meta has not published technical detail on how the matching works, and we have not tested it.
Two things stay the same, per Meta’s article:
- Your attribution window and attribution model do not change.
- The setting affects which conversions can be measured, not how they are credited to your ads.
How it fits with the Meta Pixel and Conversions API
Meta says the setting "works alongside your existing Pixel and Conversions API setup" and does not replace it. Nothing about your current install has to change for the setting to run.
As a refresher, the Meta Pixel is the script on your site that reports events such as a purchase or a sign-up. The Conversions API documentation describes a server-side link that sends events from your servers, website, apps or CRM to Meta. Many sites run both. Meta’s Conversions API docs include a step to confirm that events are deduplicated, which matters when both sources report the same action.
One gap to know about: Meta’s developer guide to Pixel conversion tracking does not mention the new setting as of November 2. The two help center articles are the only Meta sources we found.
Which sites qualify
Meta’s how-to article, How to turn on measuring conversions on customer devices, lists two requirements before the setting can work:
- The Meta Pixel must be installed directly on your page. A pixel inside an iframe, or an image-only pixel, does not meet the rule.
- Your website must require people to log in to an account with an email or mobile phone number.
The login rule narrows things for most of our readers. A typical donation page asks for an email address but does not require an account. Based on Meta’s wording, that page would not qualify.
A member portal is different. Many associations require members to sign in with an email address to renew, register for events or buy from the store. Those pages may qualify, if the pixel runs on them.
The iframe rule matters too. Many hosted donation, event and payment forms load inside an iframe on your page. A pixel placed inside that frame does not meet Meta’s rule.
| Page type | Our reading of Meta’s rules | Why |
|---|---|---|
| Donation page with no account required | Probably does not qualify | No login with email or phone |
| Member portal that requires sign-in | May qualify | Login with email; check how the pixel is installed |
| Registration form embedded in an iframe | Pixel inside the frame does not qualify | Iframe pixels are excluded |
| Online store with required accounts | May qualify | Login required; pixel must be on the page |
This table is our reading of two short rules. Meta does not publish a list of qualifying site types, so check your own Events Manager.
Where to find the toggle in Events Manager
The steps come from Meta’s how-to article:
- Go to Meta Events Manager.
- Click Data sources.
- Select the name and ID of your 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 that you can turn it off at any time. The steps run per pixel. An agency that manages pixels for many clients needs to open each one.
For context, the PPC Land report also notes open questions. It says Meta has not said which browsers are supported, or whether matching runs in Meta’s apps, the browser, or both. We found no answer to those questions on Meta’s pages either.
What could change in your Meta Pixel reports
Meta gives two reasons to keep the setting on. You may see more of the conversions your campaigns drive. And Meta says a stronger signal can improve campaign performance.
The first point has a practical side. If the setting starts adding conversions, your counts can rise with no change to your ads. A team that reads that rise as a creative win will draw the wrong lesson.
Three steps help:
- Note the date the setting took effect in your reporting file or dashboard.
- Compare a few weeks before and after before you change budgets.
- If you report Meta conversions to a board or funder, add a short footnote.
The gap between Meta’s numbers and your own analytics may also change. If you compare Meta against GA4, our guide to Microsoft Clarity and Google Analytics 4 explains why the tools count differently in the first place.
A Meta Pixel checklist for nonprofits and associations
Use this list for your own pixels or for each client account:
- List every pixel. Note which sites and pages each one runs on.
- Check the two rules. Does the site require a login with email or phone? Is the pixel on the page itself, not in an iframe?
- Decide on or off. Record who decided and when, so the next person knows.
Then look at what the pixel sends and how it loads:
- Review what the pixel sends. Meta’s article says it is your responsibility to make sure your integration does not share prohibited information with Meta. Look at event names and parameters on member, health and giving pages.
- Check your consent setup. The setting sits in your pixel’s settings and requires the pixel on the page. If a consent banner controls when your pixel loads, confirm it still behaves as you expect. Our Google Consent Mode v2 guide covers the Google side of the same setup.
- Mark the date in reports. Treat any change in conversion counts after the setting takes effect with care.
Another ad setting that arrives switched on
This is the second ad platform change in a month that arrives turned on. OpenAI’s help article on creative enhancements says they were enabled automatically for new and existing ChatGPT Ads campaigns starting October 30, 2026. We covered that in ChatGPT Ads creative enhancements. In both cases, the advertiser has to find the setting and decide.
If your team also runs ChatGPT Ads with customer lists, our post on ChatGPT Ads targeting covers what data those lists use. The habit is the same across platforms: check new defaults when they appear, and write down your decision.
Frequently Asked Questions
What is “Measure conversions on customer devices”?
It is a Meta Pixel setting in Meta Events Manager. Meta says it matches an ad view to a later conversion on the customer’s own device, using information the customer already shared with you and temporary device information.
Is the setting on by default?
Yes. Meta’s help center says it is turned on by default for eligible pixels. You can turn it off at any time in the pixel’s settings.
Does it apply in the EU and UK?
No. Meta says the setting is not active for people located in the EU and UK.
Will my donation page qualify?
Probably not, unless donors must log in to an account. Meta requires the website to make people log in with an email or mobile phone number, and the pixel must be on the page itself, not in an iframe.
Does it replace the Meta Pixel or the Conversions API?
No. Meta says it works alongside your existing Pixel and Conversions API setup and does not replace it.
Does it change how conversions are credited?
No. Meta says your attribution window and attribution model do not change. The setting affects which conversions can be measured, not how they are credited.
What does Meta receive when a match happens?
According to Meta’s help article, Meta receives only confirmation that a purchase happened and which campaign to attribute it to. Meta states that no identifying customer information is shared with it.
When does measurement start?
Meta’s help pages do not give a date as of November 2, 2026. PPC Land reported that the Events Manager panel shows November 12, 2026. Check the panel in your own account.
How do I turn it off?
In Meta Events Manager, click Data sources, select your pixel, click Settings, and find Measure conversions on customer devices below the Meta Pixel settings section. Repeat for each pixel you manage.
