All posts

Meta Marketing API v27 Turns On Two New Ad Defaults

Meta Marketing API v27 may add catalog products to new ads and widen device delivery by default. Here is what agencies should check before February 2027.

Bharath
10 min read
Meta Marketing API v27 turns on two new ad defaults, shown as two toggles for catalog products and mobile devices
On this page

Meta Marketing API v27, released November 4, 2026, switches two ad settings on by default for anything built through code. New ads without Product showcase settings may get catalog products attached, and new Sales ad sets that target specific devices now expand to other mobile devices. Any agency tool that omits those fields inherits Meta's choice.

Quick Answer

  • Meta released Graph API v27.0 and Marketing API v27.0 on November 4, 2026, and two changes turn ad settings on by default when an integration leaves a field out.
  • Product showcase may switch on for new ads with no product_extensions settings, and device expansion is on for new eligible Sales ad sets, reaching all API versions in about 90 days.
  • Agencies should confirm their tools send product_extensions.enroll_status as OPT_OUT where catalog items would be off-message, and set the device field to 0 where device targeting is deliberate.

Most API releases are housekeeping. You bump a version number, swap a deprecated endpoint, and move on. Version 27.0 is different because two of its changes don't break anything. They quietly change what a request means when a field is missing, so an integration that worked on v26.0 can produce a different ad on v27.0 without a single error in the logs.

That matters most to agencies, because agency tooling is where ads get built in bulk from templates. A template written before November 4 has no reason to carry a Product showcase field or a device expansion flag, and under v27 the absence of those fields is now a decision Meta makes for you.

Meta Added 2 Opt-Out Defaults to Marketing API v27 on November 4, 2026

The two defaults are Product showcase on new ads and device expansion on new Sales ad sets, and both apply only to objects created after an integration moves to v27.0. Meta's developer blog post, written by Ayyad Farah and Manjari Jain, says "Meta may turn on Product showcase" when a creative has no Product showcase settings. Existing ads and ad sets keep their current behavior.

Meta Marketing API v27.0, released on November 4, 2026, introduces a Product showcase default for new ads created through the POST /{ad-account-id}/ads and POST /{ad-account-id}/adcreatives endpoints. When a creative carries no Product showcase settings, Meta may enable the feature, which appears as "Show products" in Ads Manager and adds items from the advertiser's catalog to an ad built around the advertiser's own image or video. Meta states that it does this "only when it has high confidence that a specific product set in your catalog matches the ad." Advertisers who want to keep catalog items out of an ad must set degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status to OPT_OUT in the creative. Ads created on Marketing API v26.0 or earlier are not affected, and Meta has not published a date for extending this default to older versions. Meta's announcement does not define "high confidence" or list which campaign objectives qualify.

The second default is narrower. Starting with v27.0, new eligible Sales ad sets that target specific mobile devices or operating systems get "Reach more people across other mobile devices" switched on whenever the targeting_automation device field is omitted. Setting that field to 0 keeps delivery inside the devices you picked, as Relevant Audience's summary of the v27 defaults also notes. Meta excludes the Mobile App conversion location and Special Ad Categories, and it says the default reaches "all versions approximately 90 days later (February 2027), date to be confirmed."

The v27 Default Exposure Check Sorts 4 Changes by Silent Risk

The fastest way to size your exposure is to match each v27.0 change against what your campaigns actually run. I built the table below from Meta's announcement and the PPC Land breakdown of the release, and I call it the v27 Default Exposure Check because it sorts each change by who it touches and what your tool has to send.

Change in v27.0Who it touchesWhat your tool should sendWhen it applies
Product showcase defaultNew ads in accounts with a connected catalogproduct_extensions.enroll_status set to OPT_OUT where products are off-messagev27.0 now, no date for older versions
Device expansion defaultNew Sales ad sets targeting specific devices or OStargeting_automation device set to 0v27.0 now, all versions about February 2027
Lookalike location fields rejectedTools creating Lookalike audiencesDrop country and location_spec from lookalike_spec, set location on the ad setv27.0 now, all versions about 90 days later
Catalog batch endpointFeed sync jobsMove from /{catalog-id}/batch to /{catalog-id}/items_batchFails on v27.0 now

In practice, the two default rows bite hardest, because both fail silently. A lookalike audience call with a location field gets rejected with an error your engineers will see the same day. A creative that picks up catalog items, or an ad set that widens to new devices, returns success.

For example, picture an agency running a home goods client with a connected catalog and a clearance campaign built around one lifestyle photo. If the creative payload has no product_extensions block, Meta may add matching catalog items under that photo, and the client's approved clearance message now sits beside products that aren't on sale. Nobody changed the template, yet the ad changed.

We log changes like this one in our 2026 paid media platform tracker, which records every platform update that affects how agencies and advertisers run campaigns, so you can see v27 next to the Google changes that landed the same week.

Lead Forms Gain Phone OTP Verification in Business SDK v27

The v27 release also gives lead forms a phone_otp_verification_type setting, which Meta describes as "supporting required, optional, or disabled verification," with the optional mode limited to eligible ad accounts. It ships through the Meta Business SDK v27, which Meta says follows "shortly after" the Graph API release.

For anyone running Instant Forms, this is a lead quality lever rather than a default. Required verification is built to filter out fake and mistyped phone numbers. It will probably also cut form completions, because every extra step in a form costs some submissions. Meta hasn't published completion or quality data for the setting yet, so the right test is a split between verified and unverified forms on the same audience, judged on contact rate rather than form volume.

Author's Comment

"Defaults are where integrations drift. An explicit field is a decision you can read in a diff, while an omitted field is a decision someone else makes on a schedule you don't control. Our rule for every ad payload is to write the value even when it matches today's default, because the default is the part Meta is allowed to change."
Bharath, Engineer, Hellyeah AI

What v27 Changes for Meta Campaigns Run on Hellyeah

Hellyeah runs Meta campaigns on two objectives, Awareness for impressions and Instant Forms for leads, and that scope decides which v27 rows matter on the platform. Hellyeah's AIMA engine writes the ad copy, builds the single-image creative in 4:5 and 1:1 with an optional 9:16 Stories version, sets up the Instant Form, and proposes targeting and budget. A person approves every launch and every optimization change before it goes live.

The device expansion default only applies to Sales ad sets, so it has nothing to attach to in the two objectives Hellyeah runs on Meta. The lead form verification setting lands directly on the Instant Forms side, where leads already arrive in the Hellyeah Leads inbox and the client assigns an owner and qualifies each one. That inbox is the right place to judge whether verified leads answer the phone more often.

Agencies running Meta ads through their own scripts or third-party tools carry the v27.0 upgrade themselves, while clients who build campaigns inside a web platform rely on the platform to handle the version change. Meta Marketing API v27.0, released November 4, 2026, makes this split visible, because its two new defaults only take effect when an integration omits a field. A team that maintains its own templates has to add product_extensions.enroll_status set to OPT_OUT to every creative where catalog items would be off-message, and set the targeting_automation device field to 0 on Sales ad sets where device targeting is deliberate. It also has to replace the /{catalog-id}/batch endpoint with /{catalog-id}/items_batch and strip country and location_spec from lookalike_spec. Graph API v21.0 is removed on January 21, 2027, and v22.0 on May 20, 2027, so older integrations face hard cutoffs as well.

If you'd rather not track Meta's version calendar per client, Hellyeah's Managed Growth pairs AIMA with senior operators who own the account setup. Agencies keep the client relationship and the platform keeps the plumbing current.

3 Checks to Run Before Device Expansion Reaches All Versions in February 2027

The window that matters is roughly 90 days, because Meta plans to extend the device expansion and lookalike changes to every API version around February 2027. These three checks cover it, and each one takes less than an afternoon for a team that owns its own integration code.

Search Your Ad Creation Code for product_extensions

Start by searching your ad creation code for product_extensions. If the string doesn't appear anywhere, every new ad your tool creates on v27.0 can pick up Product showcase whenever Meta finds a confident catalog match, subject to eligibility rules Meta hasn't published. Add the opt-out to templates for brand, clearance, and lead generation creative, and leave it off where catalog items genuinely help.

Pin Device Targeting on Sales Ad Sets

Next, list your Sales ad sets that target a specific device or operating system. Those are usually deliberate, such as an iOS-only offer or a test that isolates Android users. Set the device field to 0 on each one, and confirm the setting survived by reading the ad set back after creation. A field your code sends but Meta drops on write is just as risky as one you never sent, and a read-back is the only way to tell the two apart.

Replace total_video_consumption_rate in Client Reports

Then check your reporting for total_video_consumption_rate. Meta says that "starting in early November 2026, the metric will no longer be returned on any Graph API version," with no direct replacement. If a client dashboard leans on it, swap in a metric you control. Hellyeah's X-Ray tracks conversions on the advertiser's side, so a lost platform metric doesn't erase the outcome data clients actually pay for.

Teams that want a second pair of eyes on their Meta setup can book a demo and walk through the v27 checks against live accounts.

Frequently asked questions

  • What changed in Meta Marketing API v27?

    Meta released Graph API v27.0 and Marketing API v27.0 on November 4, 2026. Two settings now default on when an integration omits a field. Product showcase may add catalog products to new ads, and device expansion turns on for new eligible Sales ad sets. Lookalike location fields are rejected, and the catalog batch endpoint stops working on v27.0.

  • How do I stop Meta from adding catalog products to my ads?

    Set degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status to OPT_OUT in the ad creative. Meta only adds products when it has high confidence that a product set in your catalog matches the ad, but it does not show that decision in an API error, so the opt-out has to be written into every template where catalog items would be off-message.

  • When does the device expansion default reach older API versions?

    Meta says the device expansion default applies on v27.0 now and reaches all versions approximately 90 days later, around February 2027, with the exact date still to be confirmed. Setting the targeting_automation device field to 0 keeps a Sales ad set inside the devices it targets.

  • Does Marketing API v27 affect Meta campaigns run on Hellyeah?

    Hellyeah runs Meta campaigns on Awareness and Instant Forms leads, so the device expansion default, which only applies to Sales ad sets, does not attach to them. The new phone OTP option for lead forms is relevant to Instant Forms, and leads already land in the Hellyeah Leads inbox for qualification. A person approves every launch and optimization change.

Bharath

Engineering

Engineer at Hellyeah. Builds the runtime the marketing systems live in: pipelines, integrations, and the guardrails that keep them safe to ship.

AI Campaign Management Expands to 6 Ad Platforms

AI Campaign Management Expands to 6 Ad Platforms

Supermetrics now lets Claude create and edit campaigns across Google Ads, Meta, TikTok, LinkedIn, Microsoft Advertising, and Snapchat. Here is what the integration requires and how it compares to native AI campaign management.

Michael Guan
7 min read
Paid media platform updates 2026 tracker

Paid Media Platform Updates 2026

Daily tracker of Google Ads, Meta Ads and TikTok Ads platform changes affecting paid media teams and agencies in 2026. Updated every day by the Hellyeah team.

Jaya Muvania
12 min read

Your next campaign, handled.

Hellyeah takes care of strategy, creative, and optimization.