From 12 November 2026, the Meta PixelPixelA piece of code on a web page that tells the ad platform somebody opened the page or took an action.What is the Meta Pixel? can match ad views with purchases on the customer device, not only on Meta servers. The setting is on by default for eligible pixels outside the European Union and the United Kingdom, so advertisers in Indonesia get it too.
This feature can add conversionsConversionThe action you count as a result, for example a paid order, a sign-up, or a chat that becomes a qualified buyer.Open the glossary to your reports, but it does not add sales. Compare Ads Manager numbers with real orders every day, especially before you lock your Harbolnas 12.12 budget.
What is conversion measurement on customer devices?
Conversion measurement on customer devices is a Meta Pixel setting that matches ads with purchases on the phone or computer of the customer. In Events Manager, the setting name is Measure conversions on customer devices.
Meta gives an example on its Business Help Center page about measuring conversions on customer devices. A person sees an ad for a lamp on Instagram, then buys the lamp on your website 2 days later. Meta can have a record of the ad view and receive the purchase event, but it cannot always connect the two.
With this setting, the match occurs on the device, where the ad view data and the purchase data are both present. The device uses data that the customer already gave you, such as an email address, and temporary device data that Meta calls non-identifying. Meta receives only a confirmation that a purchase occurred and the campaign that gets the attributionAttributionHow a system decides which ad or channel receives the credit for 1 sale.High clicks, low sales: the tracking gap.

What changes and what stays the same from 12 November 2026?
The match location changes, but the attribution window, the attribution model, the Meta Pixel, and the Conversions APICAPIA server path that sends conversion data from your system to the ad platform, without depending on the buyer browser.What is the Conversions API (CAPI)? stay the same.
| Item | Before 12 November 2026 | From 12 November 2026 |
|---|---|---|
| Match location for ads and purchases | Meta servers | Meta servers and the customer device |
| Data from the device path to Meta | This path did not exist | Purchase confirmation and the campaign that gets attribution |
| Attribution window and model | As set in your account | No change |
| Meta Pixel and Conversions APIAPIThe official door 2 systems use to exchange data, without anybody copying it by hand.Open the glossary | Used for tracking | Still used; the new feature does not replace them |
| Setting status | The setting did not exist | On by default for eligible pixels |
| Regions | Not applicable | Not active for people in the EU and the UK |
The table comes from 2 Meta Business Help Center pages that we read on 12 November 2026. These help pages do not give a start date. The date 12 November 2026 shows in the pixel settings panel with the text "Measurement starting November 12, 2026".
Notices to advertisers started on 18 October 2026, according to a PPC Land report dated 27 October 2026.
Which pixels are eligible?
Only pixels that meet 2 Meta requirements get a benefit, although the toggle shows as on in many accounts.
The Meta page on how to turn on measuring conversions on customer devices gives 2 requirements:
- The Meta Pixel is installed directly on the page. A pixel inside an iframe or an image-only (img) pixel is not eligible.
- The website requires people to log in to an account with an email address or a mobile phone number.
| Site type | Eligible? | Reason |
|---|---|---|
| Online store with required login and the pixel on the page | Yes | It meets the 2 requirements |
| Online store with checkout without login | No | The site does not require login |
| Landing pageLanding pageThe page an ad points to. It carries 1 offer and 1 action, with no menu pulling the visitor elsewhere.What is a landing page? that sends people to a WhatsApp chat | No | No login, and the purchase occurs in the chat |
| Pixel inside an iframe or an img tag | No | The pixel is not installed directly on the page |
| Conversions API only, no pixel on the page | No | The feature is part of the Meta Pixel on the site |
If your business sells through a landing page and a WhatsApp chat, this feature probably adds no conversions. For such accounts, find a different cause if conversions jump after 12 November 2026.
How does it affect CPA, ROAS, and budget decisions?
Reported conversions can increase without more sales, so the reported CPACPAThe average cost of 1 result, for example 1 order or 1 qualified buyer.Open the glossary can decrease and ROASROASRevenue from ads divided by ad spend. A ROAS of 4 means each Rp 1,000 of ad spend returns Rp 4,000 of gross revenue.How to calculate ROAS and break-even ROAS can increase.
Meta writes that the feature changes which conversions it can measure, not how it gives credit to your ads. Stape, a server-side tagging vendor, wrote on 22 October 2026 that CPA can decrease and ROAS can increase while sales and spend stay the same.

Meta also writes that a stronger signal can improve campaign performance. Meta does not yet explain if device-path conversions go into bid optimization, if purchase value is sent, or how the feature reads visitor consent choices.
The operational effect touches 3 work areas:
- Cost: do not increase a budget only because ROAS increases in the first week after 12 November 2026. Use paid orders from your own system as the base.
- Measurement: numbers before and after 12 November 2026 are no longer equal in scope. Add a note for that date in dashboards and client reports.
- Team process: assign 1 person to decide this setting for each pixel. Record the decision and the date.
For the server-side tracking that you still need, read our guide to tracking Instagram and Messenger DM ads with the Conversions API. For other Meta default changes this month, read the default changes in Meta Marketing API v27.0.
How do you check and set this feature?
Open the pixel settings in Events Manager, check the 2 Meta requirements, then compare Meta numbers with real orders every day.
- Open Meta Events Manager, click Data sources, select the pixel name and ID, then click Settings.
- Find Measure conversions on customer devices below the Meta Pixel settings section. Record the status.
- Check how the pixel is installed. Make sure that the pixel code is directly on the page, not in an iframe or an img tag.
- Check if the site requires login with an email address or a mobile phone number. If not, this feature adds no conversions for you.
- Save a baseline for the 14 days before 12 November 2026: Purchase in Ads Manager and paid orders in your system.
- Compare the 2 numbers every day from 12 November 2026. Set the gap that you accept before you look at the data.
- Keep the Conversions API and event_id deduplication. Turn off this setting only if the gap goes above your limit, then record the date.
Meta writes that you can turn off this setting at any time from the same menu.
What did we find in the Rama Digital account?
On 12 November 2026, this setting was already on for our website pixel, with the text "Measurement starting November 12, 2026".
This status is the Meta default, and we did not change it. A toggle that is on does not prove that the pixel meets the 2 Meta requirements.
We send a Purchase event only for money that we received. That payment number is our reference if Purchase in Ads Manager changes after 12 November 2026.
What should you do today?
Check your pixel setting today, then save a baseline for the 14 days before 12 November 2026. Make your 12.12 budget decision from paid orders, not from ROAS in Ads Manager alone.
If you need an audit of your pixel and Conversions API, see the Rama Digital Meta Ads performance management service.
Questions and answers
Must I turn off this setting?
No. Keep it on while the gap between Meta numbers and real orders stays inside your limit. Turn it off if the gap goes above that limit.
Does this feature replace the Conversions API?
No. Meta writes that this feature works together with your current Meta Pixel and Conversions API setup, and does not replace it.
Is this feature active for visitors from Indonesia?
Yes, if the pixel is eligible. Meta gives an exception only for people in the European Union and the United Kingdom.
Does my attribution window change?
No. Meta writes that the attribution window and the attribution model stay the same. The feature changes only which conversions it can measure.
Why do reported conversions increase while sales stay the same?
The device path can connect purchases that were not connected to an ad before. The report then counts more purchases from ads, although your number of orders is the same.
