Skip to content
Adboostr

Meta Just Changed How It Counts Conversions — And Your Ad Defaults — Right Before Black Friday

On Nov 12, Meta quietly turned on device-side conversion measurement by default. On Nov 4, its API started defaulting two ad settings to "on." Here's what multi-channel advertisers need to check before Black Friday distorts their numbers.

Adboostr5 min read
Contents
  1. Change 1: Meta Is Now Measuring Conversions On Your Customers' Devices
  2. Change 2: The Marketing API Quietly Flipped Two Defaults to "On"
  3. Why the Timing Matters
  4. A Short Checklist Before Black Friday Week

Two changes landed in Meta's ad infrastructure within the same two weeks, and neither one requires you to touch a single campaign for it to affect your numbers. If you run Google Ads and Meta Ads side by side and you're about to lean on Meta's reporting to make Black Friday budget calls, both are worth five minutes of your attention this week.

Change 1: Meta Is Now Measuring Conversions On Your Customers' Devices

Starting November 12, 2026, Meta turned on a new Pixel setting called "Measure conversions on customer devices" for datasets that are already sending events — meaning any site with a working Pixel or Conversions API connection. There's no code change and no opt-in step. It's simply on by default.

Here's the idea: instead of relying only on Meta's servers to match a purchase back to an ad click, matching now also happens on the shopper's own device, using information the customer already gave the business (like an email address) plus temporary device signals that stay on the device itself. Meta's pitch is that this recovers purchases that never make it into today's reporting — browser restrictions, ad blockers, and broken server-side connections all cause real sales to go unattributed.

A few things worth knowing before you take that at face value:

  • It's additive, not a replacement. Device-side matching runs alongside server-side matching, not instead of it — so the practical effect for most accounts is simply more reported conversions, not a cleaner single number.
  • The EU and UK are excluded, at least for now. If you run separate reporting for European markets, don't expect the same bump there.
  • Attribution windows and models don't change. This affects how a conversion gets matched to an event, not how credit gets split between touchpoints.
  • There's no public confirmation yet on whether recovered conversions feed back into bidding and optimization, or sit in reporting only. That matters a lot for how much weight you put on any performance "improvement" you see starting mid-November.

What to do: If you want to isolate the effect, write down your current ratio of Meta-reported purchases to actual backend orders before November 12 passes you by (if you're reading this after the fact, use your last clean week). Keep tracking that ratio through Black Friday and Cyber Monday. If Meta-reported purchases climb relative to backend orders, that's very likely measurement, not performance. The setting lives in Events Manager → Data Sources → your pixel → Settings, if you decide the extra conversions are muddying more than they're helping.

Change 2: The Marketing API Quietly Flipped Two Defaults to "On"

Separately, Meta shipped Graph API and Marketing API v27.0 on November 4, 2026. Two changes in this release matter even if you've never written a line of code against Meta's API yourself, because they affect any tool, script, or catalog feed that creates ads on your behalf:

Product showcase can now switch itself on. For new ads created through the API whose creative has no explicit Product showcase setting, Meta may enable it automatically when its matching system has "high confidence" that a specific catalog product set fits the ad. In plain terms: your ad may start showing matched catalog products you didn't choose to feature. If that's not the message you want, the fix is for whatever platform builds your ads to send product_extensions.enroll_status as OPT_OUT in the creative features spec.

Device targeting got looser by default, too. For new Sales ad sets that target a specific device or OS and omit the device field, Meta now turns on "Reach more people across other mobile devices" automatically. If you deliberately scoped a campaign to iOS only, for example, this default can quietly widen it. The fix is sending targeting.targeting_automation.individual_setting.device as 0 to keep targeting strict. This particular default is currently limited to v27.0, but Meta says it will reach every API version by roughly February 2027 — so it's coming for your account either way.

A couple of smaller changes in the same release are worth a glance if you run catalog ads or lookalikes: lookalike audience creation requests that include country or location_spec are now rejected (set location on the ad set instead), and the old /batch catalog endpoint is being phased out in favor of /items_batch. None of this affects manual campaign-building inside Ads Manager — it's specific to anything built through the API.

What to do: You probably don't call Meta's API directly, but whatever software does — an in-house script, a feed management tool, or a multi-platform ad manager — does, on your behalf. This week, ask whoever runs that connection two questions: which API version are they on, and do they already send explicit values for product_extensions and device rather than leaving them blank. If the answer is "we don't know," that's your answer about whether these new defaults are already live in your account.

Why the Timing Matters

Neither change is dramatic on its own. Together, landing 15 and 23 days before Black Friday, respectively, they're exactly the kind of thing that gets misread as a campaign win or a targeting mistake during the one week of the year when everyone's budget decisions move fastest. A jump in reported conversions that's actually a measurement change can push you to scale a campaign that isn't really outperforming. A quietly widened device target can blow past a budget you set for a narrower audience. Both are easy to miss if you're only watching the headline numbers in Ads Manager.

A Short Checklist Before Black Friday Week

  • Record your Meta-reported-purchases-to-backend-orders ratio now, before more measurement changes land.
  • Check whether on-device conversion measurement is on for each pixel (Events Manager → Data Sources → Settings), and decide if you want it on through the holiday peak.
  • Ask your ad-ops tool or agency which Marketing API version they're running, and whether product_extensions and device are set explicitly.
  • If any Sales ad set is supposed to be device-restricted, confirm that restriction is still in place rather than assuming it is.
  • Keep server-side Conversions API tracking active regardless of what you decide on the Pixel setting — it's your most stable signal if reporting gets noisy.

None of this is a reason to panic about Black Friday performance. It's a reason to know, when your Meta numbers move next week, whether they moved because of your campaigns or because of Meta's infrastructure. That distinction is the whole game during the one stretch of the year when you can least afford to misread it.