Quick answer: Meta’s latest Graph and Marketing API changes matter most to businesses and agencies that create or manage campaigns through third-party tools. From 4 November, some older Graph API features are no longer available to new apps. Meta has also introduced defaults that may expand device reach in certain API-created sales ad sets and enable product showcases on API-created ads. Before publishing, review the settings your tool sends and confirm that the resulting ad matches your plan. (Meta for Developers: Graph API v27.0 and Marketing API v27.0; Social Media Today’s summary)
What changed in Meta’s API update?
Meta announced Graph API v27.0 and Marketing API v27.0 on 4 November. The update includes developer-facing changes, so its effects depend on how your campaigns are built. If your team launches everything directly in Ads Manager, the API-specific items may not affect your usual workflow. If you use an agency dashboard, campaign automation, or an in-house integration, ask how it handles the new version and defaults.
One change applies to certain sales ad sets that target specific mobile devices or operating systems. Their delivery may now expand to other devices by default. Marketers who need strict device targeting should check whether their tool explicitly preserves that setting.
Meta may also enable product showcase on ads created through the API. This can change how products appear in an ad. It may suit some catalogue campaigns, but it should be reviewed against the creative, offer, and landing-page experience you intended.
There’s also a compatibility issue for developers: since 4 November, new apps can’t use several older Graph API features, including JSONP callbacks and asynchronous batch requests. Meta’s announcement also describes limits on new apps adopting these features in existing integrations. The specific impact depends on the code behind each tool, so integration owners should review Meta’s v27.0 notes and their own API usage. (Meta for Developers)
Why should campaign teams care?
A campaign can be strategically sound and still launch with an unintended setting if the tool creating it has changed how it sends requests. That’s an operational risk, not evidence that every advertiser’s account or Ads Manager setup has changed.
For agencies, the practical lesson is to include a settings review in campaign quality checks. For in-house teams, it’s a good time to ask whether campaign creation happens manually, through a partner platform, or through a custom API integration. The answer determines who should test the update.
Five checks to add to your launch routine
-
Identify how the campaign is created. Record whether the campaign is built in Ads Manager, an external platform, or custom software.
-
Review device targeting. For sales campaigns with device restrictions, confirm that the published ad set retains the intended audience.
-
Preview product showcases. Check the ad as customers will see it, including the selected products and their path to the landing page.
-
Compare the final settings with the brief. Keep a short checklist covering objective, audience, placements, device rules, catalogue, budget, and destination.
-
Save a change record. Note the API version, tool used, settings reviewed, and who approved publication. If performance shifts, this record helps separate creative or audience changes from setup differences.
These steps are practical recommendations based on the announced changes; they are not additional Meta requirements. Keep a test campaign or draft workflow available so the team can inspect new defaults before using them on a time-sensitive launch.
Which tools can help?
Start with the campaign preview and settings screen in the platform that creates the ad. If your provider offers an API version or release log, make sure the account owner or developer checks it. A shared launch checklist in a spreadsheet or project-management tool is often enough for a small team. Larger agencies can add an automated comparison that flags differences between a campaign brief and the settings returned after creation.
The goal is visibility: know what the tool submitted, what Meta accepted, and what the audience will see. Don’t assume the campaign brief alone proves the final setup is correct.
Meta’s API update is a reminder to treat campaign setup as part of marketing strategy. Creative, audience, and budget choices matter, and so do the settings that connect them to delivery. Add a brief integration and preview check to your launch process, especially when campaigns are created through third-party tools. That small habit can help catch unintended changes before they shape a live campaign.
FAQs
Not necessarily. Several changes concern Graph and Marketing API integrations, so the effect depends on how campaigns are created and which features a tool uses. Ask your provider whether it has reviewed v27.0.
There’s no universal answer. Preview the feature, check that it supports the campaign’s offer, and confirm that the product selection and destination make sense for customers.
Review Meta’s v27.0 announcement and changelog, identify whether the integration uses affected features, and test campaign creation with the new version before upgrading production workflows.
