Meta advertising is changing quickly.
If you are running Facebook and Instagram campaigns manually through Ads Manager, you may not notice every technical change happening behind the scenes. But if your agency, business or marketing software uses Meta’s API to create campaigns, manage catalogs, control targeting or automate advertising tasks, these updates can become very important.
Meta has now released Graph API and Marketing API v27.0, and there are several changes that agencies and developers should know about.
Some of these changes are related to how new ads are created. Some affect device targeting. Others are important for ecommerce businesses using product catalogs and automated integrations.
The main point is simple:
If your Meta advertising setup uses an API or third-party integration, don’t assume everything will continue working exactly as before.
Let’s look at what this update means in simple language.
What Is Meta Marketing API?
Before getting into the changes, let’s quickly understand what the Marketing API actually does.
Most business owners know Meta through Facebook Ads Manager. You select your audience, create your advertisement, choose a budget and launch your campaign.
But agencies and software companies often need to do much more.
They may manage dozens or hundreds of advertising accounts. They may use software to create campaigns automatically, update product catalogs, generate reports, manage audiences or connect Meta Ads with other systems.
This is where the Marketing API comes in.
It allows software and other platforms to communicate with Meta’s advertising system.
For example, an ecommerce business may have thousands of products. Instead of manually updating every product in its Meta catalog, an integration can automatically send product information to Meta.
Similarly, an agency may use an internal system to create or manage campaigns for multiple clients.
That is why API updates matter.
A change that looks very technical to a normal advertiser can become a real issue for an agency’s automation or a client’s ecommerce system.
Meta Marketing API v27.0 Is Now Live
Meta Marketing API v27.0 went live on 4 November 2026.
The update includes changes to advertising behaviour, product catalog functionality, targeting and some older API features.
Not every business will be affected in the same way.
If you create everything manually inside Meta Ads Manager, there may be little for you to worry about immediately.
But if you use:
- Meta Ads automation
- Ecommerce integrations
- Product catalog software
- Custom advertising dashboards
- CRM integrations
- Third-party marketing platforms
- Custom API scripts
- Automated audience creation
then this update deserves your attention.
Product Showcase Can Be Enabled by Default
One of the changes agencies should understand is related to Product Showcase.
For certain new ads created through the API, Product Showcase can be enabled by default when the integration does not provide specific settings for it.
In simple terms, Meta can make certain product-related advertising features available automatically when it believes they are relevant to the advertisement.
For an ecommerce business, this could actually be useful.
Imagine a clothing company running an advertisement for a particular collection.
If Meta can connect the advertisement with relevant products from the company’s catalog, displaying those products could potentially give customers more ways to explore the brand.
But there is another side to this.
Agencies need to know what their integrations are doing.
If a marketing team intentionally creates a particular type of advertisement, they should understand whether additional product features can be activated automatically.
This is especially important when campaigns are being created by software rather than manually inside Ads Manager.
The takeaway isn’t that Product Showcase is bad.
The takeaway is that your integration should be reviewed so you know exactly what settings it is controlling.
Device Expansion Is Changing for Some Sales Campaigns
Another important change involves device expansion.
For certain eligible Sales ad sets created through the API, device expansion can now be enabled by default when the relevant device setting isn’t explicitly controlled.
What does this mean for an advertiser?
Let’s say a business has a particular reason for targeting certain mobile devices.
Previously, the campaign setup may have been designed around a specific device strategy.
With the new behaviour, Meta may have more flexibility to expand delivery across other eligible devices.
Again, this doesn’t automatically mean worse performance.
In fact, broader delivery can sometimes help Meta find additional customers.
But agencies need to understand the difference between:
deliberately testing broader device delivery
and
allowing a default setting to determine how the campaign expands.
When you’re spending a client’s money, that distinction matters.
Campaign settings should be intentional rather than accidental.
The Old Catalog /batch Endpoint Is Being Retired
For ecommerce businesses, this may be one of the most important changes in the update.
Meta is retiring the older catalog /batch endpoint in Marketing API v27.0.
The newer approach uses the items_batch endpoint.
If your business has a product catalog connected to Meta through an API, this is something your developer or integration provider should check.
Why?
Because product catalogs are often connected directly to advertising.
A typical ecommerce catalog may contain:
- Product names
- Product images
- Prices
- Product IDs
- Stock information
- Product descriptions
- Availability
If the system responsible for updating that information uses an outdated API method, the catalog may not update correctly.
And when your catalog isn’t updating properly, that can eventually affect advertising campaigns that depend on that product information.
For example, imagine your website has changed the price of a product from $100 to $80.
Your website shows $80.
But if your Meta catalog isn’t syncing correctly, Meta could potentially still have outdated information.
That creates an unnecessary problem.
This is why ecommerce businesses should make sure their developers or integration providers have checked their catalog connection against the new API version.
Lookalike Audience Requests Are Also Affected
Meta has also made changes related to new Lookalike Audience requests created through the API.
Certain location-related fields that were previously included in Lookalike Audience requests are no longer accepted in the same way.
This is mainly a technical issue for developers and systems that automatically create audiences.
For the average advertiser, there is no need to panic.
Existing audiences aren’t suddenly disappearing simply because the API has changed.
The bigger concern is for businesses or agencies whose software automatically creates new Lookalike Audiences.
If that software is still sending outdated information, the request could fail.
This is another example of why API updates need to be checked at the integration level.
Older API Features Are Also Being Phased Out
Marketing API v27.0 isn’t only about new features.
Some older Graph API functionality is also being phased out.
This matters particularly to developers maintaining older applications and marketing systems.
A business may have built a custom reporting dashboard several years ago.
An agency may have developed its own campaign management system.
A software company may have created a tool that connects directly with Meta.
These systems don’t always get rebuilt every time Meta changes something.
That’s where problems can start.
An integration may continue working for months or years until Meta removes or changes the functionality it depends on.
When that happens, something that has been running quietly in the background can suddenly stop working.
That’s why API maintenance should be part of normal digital marketing operations.
Should Every Advertiser Be Worried?
No.
This is important.
A Meta API update doesn’t mean every Facebook or Instagram advertiser needs to change their campaigns.
If you’re a local business owner who opens Ads Manager, creates a campaign yourself and manages everything manually, many of these technical changes may not directly affect you.
The businesses that need to pay closer attention are those using:
API-based advertising systems, automated campaign creation, product catalogs, custom software and third-party integrations.
If you’re not sure whether your business uses an API integration, ask your developer, agency or software provider.
A simple question can help:
“Is our Meta Ads setup using the Marketing API, and is it compatible with v27.0?”
That can quickly tell you whether further checking is necessary.
Why Agencies Should Take This Seriously
From an agency perspective, these changes are particularly important.
When you manage one advertising account, checking things manually isn’t always difficult.
But imagine managing 50, 100 or 200 client accounts.
Now imagine that several of those accounts use different ecommerce platforms, catalog systems and automation tools.
One small API change can potentially create a much bigger operational problem.
That’s why agencies should maintain a clear record of their integrations.
They should know:
- Which systems connect to Meta
- Which systems create campaigns
- Which systems update catalogs
- How audiences are created
- Which API versions are being used
- Which settings are controlled by the integration
- Which older endpoints are still being used
This isn’t just a developer responsibility.
It’s part of protecting your clients’ advertising campaigns.
Meta Is Giving Advertisers More Automation
There is a bigger trend behind many of these changes.
Meta is becoming increasingly automated.
The platform wants its systems to have more flexibility when finding customers, delivering ads and using available campaign signals.
For advertisers, this can be powerful.
Automation can help Meta find opportunities that a marketer may not have discovered manually.
But there is also a responsibility that comes with automation.
You need to understand what you’re giving the platform permission to change or expand.
This is particularly important when you’re running advertising for clients.
A client doesn’t want to hear:
“Meta changed something.”
They want to know that their agency is monitoring the account and understands what is happening.
What I Would Tell a Business Owner
If you’re running Meta Ads for your business, don’t panic because of the v27.0 update.
Instead, take five minutes and ask yourself one question:
How are my Meta campaigns and catalog connected to the platform?
If everything is being managed manually, you may not need to do much.
If you’re using automation, ecommerce integrations, a custom CRM, catalog software or an agency-managed API system, it’s worth asking your technical team to review the setup.
You don’t need to change something simply because Meta released a new version.
But you also shouldn’t wait until an integration stops working before checking it.
The Bigger Digital Marketing Lesson
This update is another reminder that digital marketing isn’t standing still.
Google changes its search systems.
AI search is changing how people discover businesses.
Meta is changing how advertising campaigns are created and delivered.
Tracking systems are evolving.
Automation is becoming a bigger part of marketing.
For businesses, this means one thing:
Your digital marketing setup needs regular attention.
SEO isn’t something you set once and forget.
Paid advertising isn’t something you launch and never review.
And technical integrations definitely shouldn’t be ignored until something breaks.
At Digi Ustad, I believe the best approach is simple: understand the changes, identify what actually affects your business and then take action where it matters.
Final Thoughts
Meta Marketing API v27.0 brings several changes that agencies, developers and businesses using Meta integrations should understand.
Product Showcase can become enabled by default for certain new API-created ads.
Device expansion is becoming the default for certain eligible Sales ad sets when the relevant setting isn’t explicitly controlled.
The older catalog /batch endpoint is being retired in v27.0.
Certain Lookalike Audience API requests have also changed.
And older API functionality is being phased out.
None of this means your Meta Ads campaigns are suddenly going to stop working.
But if your business relies on automation or integrations, this is a good time to check what’s happening behind the scenes.
Because in digital marketing, the biggest problems often aren’t the things you can see.
They are the small technical changes happening quietly in the background.
Stay updated. Stay prepared. And don’t wait for an integration problem to become a campaign problem.
