What Meta API v27 actually changes#
Meta API v27 shipped on 4 November 2026, and two of its changes are quiet by design. New ads can now get catalog products attached automatically. New Sales ad sets can get wider device delivery automatically. Neither needs you to touch a setting.
PPC Land reported the mechanics the same day. Meta "may turn on Product showcase" on a new ad or creative when no setting is specified, but only when it has high confidence a specific product set in your catalog matches the creative. Separately, new eligible Sales ad sets get "Reach more people across other mobile devices" switched on whenever the device targeting field is left blank. The same release deprecates the old catalog batch endpoint in favor of /items_batch and closes several legacy Graph API query parameters to new apps.
Neither default touches ads that already exist, and both can be switched off. Neither shows up as an error if you aren't specifically checking for it, which is the part worth sitting with. It's the same quiet pattern we saw in Meta's last account-wide terms change: nothing forces your hand, but nothing flags it for you either.
Does this affect your Sales campaigns?#
If you aren't running catalog-backed ads or Sales-objective ad sets through the API, this changes nothing for you today. Worth reading anyway. Catalog ads are the direction Meta has pushed commerce clients all year, and this won't be the last quiet default they add to that path.
If you are running catalog ads, the device default is the one that matters more. Product showcase only fires on a confident catalog match, so its reach is narrow. Device expansion fires any time the field is simply left unset, which on most API builds is the resting state unless someone wrote a value in on purpose.
At WebEpex we manage Meta ad accounts for GCC, European, US, Canadian and Indian businesses, and we pulled every one of them against these two fields this week. Most agencies never touch targeting_automation.device explicitly in the first place. That isn't a v27 problem so much as a v27 spotlight on how many builds were already leaving the choice to Meta.
The honest trade-off here#
The case for leaving these on: Meta says both activate "when it is likely to improve performance," and for the right account a catalog match or a wider device pool can genuinely lift results. For a small team with no bandwidth to micromanage targeting, letting the automation handle this one thing isn't a bad call.
The case against: you lose a clean read on why performance moved. If your CPA shifts next week, was that seasonality, your bid strategy, or a default Meta flipped on your behalf? You won't know unless you checked beforehand, which is the same attribution problem we flagged when Meta ad costs jumped 23% earlier this quarter and advertisers couldn't tell whether AI targeting was absorbing the hit or just the invoice was bigger.
There's a genuine unknown here too. Neither Meta's release notes nor the coverage of them, including Meta's own Graph API changelog, confirms whether either default is visible anywhere inside Ads Manager itself, only in the raw API fields. If you manage ads through Ads Manager and never touch the API, you may have no easy way to see which setting you're actually on.
How we're handling this in client accounts#
We checked two fields by hand on every client ad set built through the API or an API-backed tool: targeting_automation.individual_setting.device and degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status. Where either was blank, we set it explicitly instead of leaving the decision to Meta's confidence score.
That's the same account-level discipline behind the permissions sweep we ran when Meta's AI ad terms shifted more liability onto advertisers, and it's becoming a pattern worth naming: Meta's automation keeps getting smarter, and our checklist keeps getting one line longer. Fair trade, so far.
Going forward, every new Sales ad set we build gets a device value written in, every time. No exceptions, no leaving it to chance.
What I'd tell a client asking about this#
Check two fields this week if you run catalog or Sales-objective ads through the API:
targeting_automation.individual_setting.deviceon every Sales ad set — set it to0if you want delivery limited to what you chose.degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_statuson every ad creative — set it toOPT_OUTif you don't want catalog products attached automatically.
If you manage through Ads Manager only and can't see either one, ask your account rep directly whether anything changed on your account, because the interface won't flag it for you on its own.
If you've only got time for one fix, set the device field explicitly on anything new. That's the default with the wider reach and the February 2027 deadline attached, once it rolls out past v27.0 to every API version.
Doing nothing is a fine choice too, if your catalog match confidence and device delivery were already working for you. Just make it a decision, not an accident you discover in next month's numbers.
Close#
None of this is a crisis. It's Meta shipping a sensible default quietly, the way most of these changes ship. My read is it catches up with most catalog accounts eventually, one way or another, same as it always does.
If you want a straight answer on whether your account is actually exposed to this, send me what you're running and I'll tell you plainly. Two minutes, no pitch. Reach out here.
