Meta Marketing API v27.0: New Defaults for Device Reach and Product Showcase
Meta released Marketing API v27.0 on November 4, 2026. It turns on device reach expansion for some Sales ad sets by default, may switch on Product showcase, and rejects location fields in Lookalike specs.

Meta released version 27.0 of the Marketing API on November 4, 2026. At the same time, the older v24.0 reaches the end of its availability on November 10, 2026. Most of the v27.0 changes look technical, but several of them change what happens to your ads when a tool or script creates them without setting a specific field. If you or your tools launch ads through the API, it is worth checking these changes before your ad sets start behaving differently from what you planned.
What changed in v27.0
According to Meta's v27.0 changelog, these are the changes that matter most to people building and launching campaigns.
Reach more people across other mobile devices is now on by default. When an eligible ad set is created without a device setting under targeting automation, Meta now turns on Reach more people across other mobile devices. An ad set is eligible when it belongs to a Sales campaign that does not use the Mobile App conversion location and its targeting includes user devices or operating systems. In plain terms: if you target specific devices or operating systems in a Sales campaign, Meta may now deliver beyond them unless you say otherwise. Meta states that existing ad sets are not changed.
Product showcase may be turned on for your creatives. When you create ads with creatives that have no Product showcase settings, Meta may now turn on Product showcase for those creatives. Meta says it does this only when it has high confidence that a specific product set in your catalog matches the ad, for example a collections set that matches a collections URL. Otherwise Product showcase stays off. One detail is easy to miss: the setting stays on the creative, so later ads that reuse the same creative also have Product showcase turned on.
Lookalike audiences no longer accept location fields. The country and location_spec fields in lookalike_spec are no longer accepted when creating a Lookalike audience. Apps that send either field on v27.0 or later are rejected immediately.
Other changes. The Catalog Batch API is deprecated, and Meta points integrations to the Catalog Items Batch API instead. The meta_moment_maker_spec field is being deprecated for third-party apps on ad sets and reach and frequency predictions, and ad set create or update requests that include it on v27.0 or later return a version error. For lead ads, apps can now read a phone OTP verification setting on lead forms.
When the changes reach older versions
Normally a new API version only changes behavior for apps that move to it. Two of the v27.0 changes are different. For both the device reach default and the Lookalike location fields, Meta writes that the change applies to v27.0 and later and will apply to all versions approximately 90 days after the v27.0 launch, with the date still to be confirmed.
That means staying on an older version does not protect you from these two changes for long. If your tools still send location fields in Lookalike specs, or rely on device targeting in Sales campaigns staying tight, they will need an update even if they are not upgraded to v27.0.
Who it affects
- Advertisers running Sales campaigns with device or OS targeting. If you target, for example, only certain operating systems because your checkout or landing page works best there, new ad sets created without an explicit device setting can now deliver more widely.
- Ecommerce advertisers with a product catalog. New creatives without Product showcase settings may get Product showcase turned on, and every ad that reuses that creative will carry it.
- Anyone creating Lookalike audiences through the API with country or location settings inside the Lookalike spec.
- Agencies and in-house teams using scripts, internal tools or third-party platforms that create campaigns through the Marketing API. These tools are where defaults quietly apply, because fields that are left empty now lead to a different result.
What to do now
- Check which API version your tools use. v24.0 is available until November 10, 2026. Ask your tool vendors or developers which version they call and when they plan to move to v27.0.
- Decide on device reach for Sales campaigns. If you want delivery to stay within the devices and operating systems in your targeting, the device setting has to be set to off explicitly. Meta's changelog says: to keep delivery to the devices and operating systems in your targeting, set
deviceto0. Make sure your launch tools send this value, rather than leaving the field empty. - Decide on Product showcase per creative. If you do not want Product showcase on your ads, set the Product showcase enroll status to opt out on the creative. Because the setting stays on the creative, review any creatives you plan to reuse across many ads.
- Remove location fields from Lookalike specs. Requests that include
countryorlocation_specinlookalike_specare rejected on v27.0 and later, and this will reach all versions after the roughly 90-day window. - Move off the Catalog Batch API. If you update catalogs through it, plan the switch to the Catalog Items Batch API.
- Check new ad sets after launch. For the first launches after your tools move to v27.0, open a few new ad sets and creatives in Ads Manager and confirm that device reach and Product showcase are set the way you intended.
What this means for launching ads in bulk
Defaults matter more when you publish many ads at once, because one empty field is repeated across every ad set and ad in the batch. Kapao publishes ads through Meta's Marketing API, and ads are created paused by default. That gives you a natural checkpoint: after a bulk upload, review a sample of the new ad sets and creatives in Ads Manager for the settings above before you switch anything on. If you publish one batch to many countries or split ad sets by country or city, check at least one ad set per market. You can read more about the workflow on the bulk upload page and see the full feature list on /facts.