Meta is preparing a new way to measure purchases from Facebook and Instagram ads. Starting November 12, 2026, eligible Meta Pixels are expected to begin using the Measure conversions on customer devices feature, which allows certain purchases to be matched with ad interactions directly on the user’s device. The setting is enabled by default, and advertisers may see more conversions in reports even without an increase in actual sales.
Key Takeaways
- November 12, 2026, is the start date for measurement indicated in Meta Events Manager notifications for eligible Pixels.
- Measure conversions on customer devices matches ad interactions with purchases on the user’s device.
- The feature is enabled by default, but it can be turned off in an individual Pixel’s settings.
- Meta specifies two technical requirements: the Pixel must be installed directly on the page, and users must be required to log in with an email address or phone number.
- The feature is not active for users located in the European Union or the United Kingdom.
- Attribution windows and the attribution model remain unchanged, but the number of purchases attributed to ads could potentially increase.
What Changes in Meta Pixel on November 12
Advertisers can currently send Meta purchase information through the Pixel or Conversions API, but the system cannot always determine which ad interaction the purchase is connected to.
For example, a user sees an Instagram ad, returns to the website two days later, and buys a product. The website records the order, but Meta may not have enough signals to attribute it to the relevant campaign.
Measure conversions on customer devices adds another matching method. Some of the processing takes place on the user’s phone or computer, using information they previously provided to the business, such as an email address, along with temporary device data.
According to Meta’s description, the identifying information used for this matching is not transmitted to the company as part of the process. Meta receives confirmation of the purchase and information about the campaign to which it can be attributed.
This does not mean all conversion processing is moving from Meta’s servers to user devices. The new mechanism operates alongside the existing measurement system.
Who Can Use the Feature: Important Restrictions
The setting should not be considered universal for every advertising account and website. Meta’s help documentation sets out specific requirements for using it.
- Direct Pixel installation. The code must be installed directly on the page, not inside an iframe or through an image-only Pixel.
- User authentication. The website must require users to sign in to an account using an email address or phone number.
- User location. The mechanism does not work for people located in the EU or the United Kingdom.
- Existing event transmission. The update applies to eligible data sources that already use Meta Pixel to measure events.
Therefore, an online store that allows guest checkout without mandatory sign-in does not meet the stated authentication requirement. The presence of a toggle in Events Manager alone does not guarantee that the website will receive additional attributed purchases.
The geographic restriction also needs to be interpreted correctly. It refers to the user’s location. For example, a Ukrainian advertiser with customers in Poland and Ukraine could potentially see different measurement results for those audiences.
As of November 2, Meta has not published a detailed rollout schedule for every market and advertising account. The November 12 date appears in Events Manager and notifications to advertisers, while Meta’s public help pages do not specify it.
Will CPA and ROAS Change After the Update?
Potentially, yes, but primarily in reported metrics. If Meta can attribute more purchases to ads that were previously missing from attributed results, the conversion count in Ads Manager may increase.
With ad spend unchanged, a higher number of attributed purchases mathematically reduces Cost per Purchase. If the system also attributes additional purchase value, reported ROAS may rise.
However, this does not prove that the ads started generating more new orders. Some of the increase may be explained by better matching of purchases that had already happened to campaigns.
Meta has not published a universal forecast for conversion growth. There are also not yet enough official details about whether all purchases will pass their value through the new mechanism or exactly how the additional signals will affect the advertising algorithm’s learning.
It would therefore be incorrect to conclude that campaigns will automatically become more profitable in real terms after November 12.
What Happens to Conversions API and Attribution?
Measure conversions on customer devices does not replace Meta Pixel or Conversions API. Existing browser and server integrations continue to work, while the new mechanism adds the ability to match certain purchases locally.
Meta says attribution windows and the attribution model will remain unchanged. In other words, the new setting does not automatically extend the period during which a purchase may be attributed to an ad.
Notifications to advertisers also state that launching the feature does not require changing Pixel code or the CAPI integration. However, teams should review their existing event transmission setup rather than treat the new mechanism as a fix for every tracking problem.
In particular, deduplication of browser and server events remains important. If the same purchase is sent through both Pixel and CAPI, the system must correctly recognize it as one event.
UAGEEK has previously covered automatic event detection in Meta Pixel and the new AI settings for Automatic Events. These are different features: they concern detecting events on a website, whereas Measure conversions on customer devices is intended to match purchases to ads.
How to Check and Turn Off Measure Conversions on Customer Devices
Meta allows the feature to be disabled for the relevant Pixel. Before changing the setting, it is worth recording its current status and checking personal data processing requirements.
- Open Meta Events Manager.
- Go to Data sources.
- Select the relevant Pixel or associated data source.
- Open the Settings tab.
- Find Measure conversions on customer devices in the Meta Pixel settings.
- Check the toggle’s status and disable it if needed.
The setting must be checked separately for each Pixel. If a team manages multiple advertising assets, it should not assume that one change will automatically apply to all data sources.
The availability of a new measurement method does not remove obligations to inform users, obtain required permissions, and comply with data protection laws. Where necessary, its use should be reviewed with the legal team.
What Media Buyers Should Do Before November 12
The most important task is to establish a baseline for comparison. Without it, after the update it will be difficult to tell whether advertising performance has changed or only the number of conversions Meta was able to attribute.
- Record pre-launch metrics. Save spend, Purchases, Cost per Purchase, Purchase Conversion Value, and ROAS for a comparable period.
- Reconcile data with the business. Compare the number of purchases in Meta Ads with the CRM, payment system, or store backend.
- Check GEOs. Separate results for users in the EU and the United Kingdom from markets where the feature may be available.
- Check technical requirements. Confirm how the Pixel is installed and whether mandatory user sign-in is in place.
- Mark the change date. Add November 12 to the internal analytics update calendar.
- Monitor discrepancies. After launch, compare reported conversions with actual orders, without rushing to change budgets because of a single spike in ROAS.
To investigate technical issues with events, you can use the UAGEEK FIX guide: conversions, Meta Pixel, CAPI, and GA4.
What This Means for Affiliate Teams
For affiliate marketing, the biggest risk is mistaking improved attribution for an actual increase in the performance of a campaign setup.
If Meta starts reporting more purchases after November 12 with the same ad budget, a media buyer may see a lower CPA. However, the affiliate program or advertiser will not necessarily confirm more payable actions.
For e-commerce and affiliate campaigns, it is therefore worth monitoring ad attribution, confirmed conversions, and actual payouts separately. A similar effect should not automatically be assumed for lead generation: Meta’s public explanations primarily describe purchase matching, while support for other event types still needs clarification.
Conclusion: A New Measurement Method, Not New Sales
Measure conversions on customer devices may help Meta attribute purchases to ad campaigns more accurately. For advertisers, this could mean more complete statistics, but it also makes it harder to compare results before and after the rollout.
Before November 12, check whether the feature is available, record current metrics, and set up reconciliation with actual sales. Assessing campaign success solely by changes in CPA or ROAS in Meta Ads after the update will not be enough.
Sources for Verification
Sources for Verification
Meta Business Help Center — About measuring conversions on customer devices. Official description of local purchase matching, data usage, and how the feature works alongside Pixel and CAPI.
How Meta measures conversions on customer devices
Meta Business Help Center — How to turn on measuring conversions on customer devices. Official requirements for Pixel installation, user authentication, and control of the toggle.
Feature requirements and settings
PPC Land, October 28, 2026. Confirms the November 12 date shown in Events Manager, default activation, and feature restrictions.
Analysis of Meta Pixel’s new measurement method
Performance Marketing News, November 1, 2026. Compares Meta’s official documentation with Events Manager notifications and the practical implications for advertisers.
Rollout conditions and impact on reporting
