← Back to Knowledge Base
Affect Performance Team
|Meta Ads|Nov 22, 2026

Meta Marketing API v27.0: Product Showcase Defaults, Device Expansion, and Lookalike and Catalog API Changes

On November 4, 2026, Meta released Graph API v27.0 and Marketing API v27.0. For advertisers, agencies, and developers of ad integrations, the main changes are in the Marketing API. Two settings can now turn on by default for ads and ad sets created through the API, and some requests that previously worked are no longer accepted. The Meta Business SDK release notes also describe new lead form controls and changes to buying reserved inventory.

Across these updates, leaving a setting out of a request increasingly allows Meta to apply automation. Ad integrations therefore need to specify their intended behavior. The following sections cover what changed, where each setting applies, how to opt out where applicable, and when the changes take effect.

Product Showcase Can Turn On Automatically for New Ads

Starting with v27.0, Meta can enable Product showcase, called product_extensions in the API, when a new ad’s creative contains no Product showcase settings. Previously, advertisers had to add the setting to the creative to show catalog products alongside a standard ad. Meta now enables the format if it is highly confident that a particular product set from the advertiser’s catalog matches the ad. As a result, an ad created without catalog products can show related products from the catalog. Meta says this takes no additional integration work.

The setting applies at the creative level to POST /{ad-account-id}/ads and POST /{ad-account-id}/adcreatives requests. To keep the previous behavior, set degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status to OPT_OUT in the creative specification. Meta also published documentation for previewing the product set it might use.

The change applies to v27.0 and later. Requests to earlier versions are unaffected, and Meta has not announced a rollout date for those versions. Meta has not explained how it measures confidence, which placements will show the format, or how it affects performance. The announcement covers the API, and Meta did not say whether Ads Manager uses the same default.

Mobile Device Expansion Is On by Default for Sales Ad Sets

In the same release, Meta changed the default for device targeting. When a new ad set in a Sales campaign targets specific mobile devices or operating systems, omitting targeting.targeting_automation.individual_setting.device turns on Reach more people across other mobile devices. This option lets Meta deliver ads on other mobile devices and operating systems when it expects that to improve results.

Previously, omitting the setting kept delivery limited to the devices selected in targeting. Now, leaving it out enables expansion. To keep delivery limited to the selected devices and operating systems, explicitly set device to 0. The setting applies at the ad set level and leaves existing ad sets unchanged. It is unavailable for the Mobile App conversion location and for Special Ad Categories.

The new behavior took effect in v27.0 on November 4, 2026. Meta expects it to apply to all other API versions about 90 days later, around February 2027, with the exact date still to be confirmed. The announcement does not say what share of impressions might come from expansion or provide a separate reporting breakdown for those impressions.

Lookalike Audience Creation Rejects Location Fields

Starting with Marketing API v27.0, POST /act_{ad-account-id}/customaudiences requests fail if lookalike_spec contains country or location_spec. Meta says advertisers can remove these fields without replacing them because they did not affect delivery. Lookalike audiences receive ads in the locations selected in the ad set’s targeting. The ad set therefore determines the geography for delivery.

The change applies to the creation of new audiences. Existing lookalikes and the ads that use them continue to work as before. The v27.0 API rejects requests with these fields immediately, and Meta expects other versions to start rejecting them about 90 days later. The exact date is unconfirmed.

Agencies and teams with their own ad buying tools should update request templates that still include a country code in lookalike_spec. Otherwise, audience creation will fail after the move to v27.0 or when the transition period ends.

Catalog Batch API Migration From /batch to /items_batch

Meta deprecated /{catalog-id}/batch for product catalog integrations. Applications should use /{catalog-id}/items_batch instead. The change affects advertisers and agencies that use the Catalog API to maintain Meta product catalogs. Meta warns that applications may stop working if their code still uses the old endpoint.

The old endpoint stopped working in v27.0 on November 4, 2026. It remains available in v26.0 and earlier until support for v26.0 ends, and the announcement did not specify that date. An integration will encounter the breaking change when it moves to the new version. Meta published a separate migration guide for items_batch.

Meta Deprecates meta_moment_maker_spec for Third-Party Apps

The Meta Business SDK v27 release notes say that meta_moment_maker_spec is no longer supported for third-party apps. Developers requesting Ads Burst or Ads Super Burst inventory should now use product_type in reach and frequency predictions. These products let brands reserve inventory for limited delivery windows.

PPC Land reported that Ads Super Burst was announced in October 2026 and offers windows of 3 to 24 hours, with the option of category exclusivity. Meta presents both changes together without specifying whether meta_moment_maker_spec previously provided access to this inventory. Teams working with Reach and Frequency integrations should check where they still use the deprecated parameter.

Phone Verification With One-Time Codes in Lead Forms

The same SDK release adds phone_otp_verification_type to lead forms. It controls whether the form verifies the phone number by sending a one-time code. The three modes are required, optional, and disabled. Optional verification is available only to eligible ad accounts. Meta did not publish the eligibility criteria or list the supported markets.

For advertisers collecting leads through Meta forms, the setting lets users verify their phone numbers in the form itself. This can help when a sales representative follows up by phone. Meta has not published data on how verification affects lead volume or quality.

Graph API v21.0 and v22.0 Sunset Dates

Meta also confirmed its schedule for retiring older versions. Graph API v21.0 will be shut down and removed from the platform on January 21, 2027. Graph API v22.0 follows on May 20, 2027. Under the two-year Platform SDK support schedule, the corresponding Facebook Platform SDK versions will be deprecated in January and May 2027, respectively.

Teams whose integrations still use those versions should upgrade before the deadlines. Moving directly to v27.0 brings the new defaults and the restrictions for catalogs and lookalike audiences into effect.

What This Means for Advertisers

With v27.0, Meta makes more decisions when an integration leaves a setting unspecified. For ecommerce, new ads can show catalog products without explicit setup, and Sales campaigns targeting particular devices can reach a wider range of mobile devices. Agencies and teams using their own tools, scripts, or AI agents should review their ad creative and ad set templates. They can decide whether to opt out of product_extensions explicitly and set device to 0.

The release also calls for changes to existing integrations. Remove location fields from lookalike_spec, move catalog integrations to items_batch, and replace meta_moment_maker_spec with product_type. Meta did not publish performance data for the new defaults or explain how they appear in Ads Manager. Start by checking their impact across a limited set of campaigns.

Sources

  1. Meta for Developers, Introducing Graph API v27.0 and Marketing API v27.0, November 4, 2026
  2. PPC Land, Meta's API v27 may add catalog products to new ads by default, November 4, 2026
  3. Social Media Today, Meta Adds New Capabilities to Graph and Marketing API, November 2026

Monthly Overview

Stay ahead of the market. Every month.

Our practitioners pick the TOP 10–20 news from the world of Paid Media and MarTech for the month.

10–20Top news / month