Meta Marketing API v27 changes how some new ads, Sales ad sets, lookalike audiences and catalog integrations behave when they are created through software. Meta released Graph API v27.0 and Marketing API v27.0 on 4 November 2026. The important risk is not only a failed request: an omitted field can now produce a valid object with a setting that the advertiser did not explicitly choose.
This update matters to agencies, in-house developers, catalog-feed providers and businesses using third-party campaign tools. It does not mean every advertiser working directly in Ads Manager will see the same behaviour. This guide explains the practical checks to run before an integration moves to v27.
What Meta changed in v27
Meta’s official v27 announcement introduces two new defaults and two migration changes for marketing integrations. Product showcase may be enabled on a newly created ad when Meta has high confidence that a connected catalog product set matches the creative and the request does not specify a showcase setting.
For eligible new Sales ad sets that target specific mobile devices or operating systems, “Reach more people across other mobile devices” can start enabled when the automation field is omitted. Existing ad sets are not changed by that creation default. Meta also says Mobile App conversion locations and Special Ad Categories are exceptions to the opt-out behaviour described in the release.
Separately, v27 rejects country or location_spec fields inside a new lookalike audience request. Location belongs in the targeting of the ad set using that audience. Catalog integrations must move from the older /{catalog-id}/batch route to /{catalog-id}/items_batch.
v27 change
Main risk
Audit action
Product showcase default
Catalog products may be added to a new ad without an explicit selection.
Send an explicit showcase choice and preview the created ad.
Device expansion default
A new eligible Sales ad set may reach devices outside the selected list.
Set the device automation value deliberately and verify delivery settings.
Lookalike location fields
New audience creation can fail when legacy location inputs remain.
Remove location from the lookalike specification and retain it at ad-set level.
Catalog batch route
Feed updates can stop after a version upgrade.
Migrate to items_batch and reconcile product results.
Why omitted fields need attention
Traditional API testing often focuses on errors. The two default changes require a different control: checking successful responses and the objects created from them. A request can return success while product extensions or broader device delivery appear because the integration did not send a preference.
That matters when templates were written before v27. A tool may have omitted a field because the earlier API treated absence as no action. After the upgrade, absence can allow Meta to choose a default. Review generated payloads, not only interface screenshots or error logs.
This is also a governance issue. Kayaar’s Meta AI performance review guide recommends human approval before budget and targeting changes. The same principle applies here: automation should expose important platform defaults and record the advertiser’s decision.
A seven-step v27 readiness audit
1. Map every integration. List custom scripts, agency platforms, feed tools, CRM connectors and scheduled jobs that call Meta APIs. Record the API version, owner, authentication method, objects created and business accounts affected.
2. Inspect creative payloads. Find requests that create ads or ad creatives. Decide when Product showcase is appropriate. If catalog items must not be added, send the documented opt-out value rather than relying on a missing block. Preview products, prices and landing destinations before approval.
3. Review device rules. Identify Sales ad-set templates that specify devices or operating systems. Decide whether expansion supports the campaign goal. Make the automation field explicit, then confirm the saved setting on a test ad set. Do not assume existing ad sets prove how new ones will behave.
4. Update audience creation. Remove country and location_spec from lookalike specifications. Check that every ad set applying the audience still has the correct geographic targeting. A seed source does not replace ad-set location controls.
5. Migrate catalog jobs. Change the batch route and request body together. Test creates, updates, deletes, partial failures and retries. Reconcile a sample of item IDs, stock, prices and destinations after each run. For broader planning, Kayaar’s Meta campaign evaluation guide can help connect platform changes to business priorities.
6. Test in a controlled account. Create representative objects with v27, retrieve them again and compare requested values with saved values. Check ad previews, catalog associations, audience location and device settings. Delete or pause test objects according to your team’s procedure.
7. Add monitoring. Log the API version, payload template, created-object ID, explicit opt-out fields and response. Alert on catalog failure rates and unexpected setting changes. Keep a rollback plan until the new workflow is stable.
Checks for marketers using third-party tools
You do not need to write code to ask useful questions. Request the API version used by your platform and whether the vendor has tested Product showcase, device expansion, lookalike creation and catalog batch migration. Ask for the exact controls available to the advertiser and how saved settings are verified after creation.
Run a pre-launch review on newly created ads and ad sets. Confirm products, placements, devices, locations, budget, conversion destination and special-category status. Kayaar’s Facebook content strategy audit can help align the message with audience expectations, while the social media resource library provides wider channel guidance.
Do not share access tokens in screenshots, tickets or email. Use least-privilege access, approved secret storage and separate test credentials where possible.
Final quality-control checklist
Every integration and API version has an accountable owner.
Product showcase and device expansion choices are explicit.
Lookalike requests no longer carry location fields.
Catalog jobs use the supported batch route and reconcile results.
Successful creations are retrieved and compared with the request.
Marketers approve previews before campaigns go live.
If your team needs an independent migration or campaign-governance review, contact Kayaar with the tool type, campaign workflow and business objective. Never send access tokens or customer data through an unsecured form.
FAQs
What is Meta Marketing API v27?
It is Meta’s November 2026 API release for advertising integrations, introducing new defaults and migration requirements for several creation workflows.
Will Meta add catalog products to every new ad?
No. Meta says Product showcase may be enabled when it has high confidence in a catalog match and the request omits the setting.
Does v27 change existing Sales ad sets?
The device-expansion creation default applies to eligible new ad sets; Meta says existing ad sets keep their current configuration.
Where should location be set for a lookalike audience?
Set geography in the targeting of the ad set that uses the lookalike, not inside the v27 lookalike specification.
Who should audit Meta API v27?
Businesses, agencies and vendors using custom scripts, third-party ad tools, catalog feeds or audience integrations should review their workflows.
