Social Rocket
On Meta, ads can change from 4 November 2026 even though an agency hasn't touched its campaign template. The reason is Marketing API v27: new ads created via the API can gain product placements, and certain Sales ad sets reach additional mobile devices by default. If you automate Meta Ads creation, you need to check the requirements in your templates.
The changes mainly affect agencies, e-commerce companies and campaign software providers that create Facebook and Instagram ads via the API rather than exclusively in Ads Manager.
A missing parameter can alter the ad
The most notable change is called Product showcase. If the corresponding setting is missing on a new ad creative, Meta can display matching products from the stored catalogue – provided the system detects a high match. That may make sense for a shop, but it can seem unexpected with a tightly designed brand message.
Teams that don't want automatic product additions can explicitly prevent this in their integration: the field `degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status` is set to `OPT_OUT`. The new default applies to creatives created via v27; older API versions initially keep their previous behaviour.
Device targeting is also becoming broader. New eligible Sales ad sets that target specific smartphones or operating systems can now automatically be extended to other mobile devices. If you want to stay strictly on the chosen devices, set `targeting.targeting_automation.individual_setting.device` to `0`. Meta intends to apply this new default to older versions as well after about 90 days.
In practice, this means that after an API upgrade a green status in deployment is not enough. What matters is which ads and audiences the system actually creates. This ties into the broader development around Facebook targeting with Advantage+: platform automation is gaining ground, and explicitly excluding unwanted extensions is becoming more important.
AI self-labelling becomes editable via API
Graph API v27 also lets you set or remove your own AI label via `is_ai_generated` when editing Facebook Page posts. The parameter controls the publisher's self-declaration; Meta's other labelling and review mechanisms are separate from it.
This is useful for editorial systems and content approvals: if a company documents its production status, the label can be built into the publishing workflow instead of being added by hand in the post editor. An internal checklist should record who makes the decision about the label.
Old features disappear – integrations need testing
Meta is also restricting older Graph API patterns. Since 4 November, new applications may no longer use multi-ID queries, field aliases, JSONP callbacks or asynchronous batch requests, among other things. There are also changes to catalogue batch endpoints and lookalike specifications in v27. The metric `total_video_consumption_rate` is being discontinued.
For social teams, the technical effort becomes relevant when posts are no longer published, reports no longer populate, or ads are delivered differently than planned. A pragmatic acceptance test covers three cases: a post with AI self-labelling, a product ad with a catalogue, and a Sales ad set with a device restriction. Afterwards, the settings actually saved should be checked against the template.
Anyone using third-party business tools should request the v27 transition and change log from the provider. Our report on the removed Meta Access Verification shows that requirements for app providers are also changing in parallel. For creator campaigns, the Meta Creator Marketing Hub may also be relevant within your existing workflow.
Sources: Meta developer announcement from 4 November 2026, technical breakdown of Relevant Audience, Social Media Today.