Ads and Commerce

Version 26.0

Updated: Jul 30, 2026
Copy for LLM
Ads in WhatsApp Status are available via the Marketing API. Learn more about ads in WhatsApp Status.

Marketing API

July 29, 2026
Available until TBD
Blog post

Ad Creative

WhatsApp Status ads: wamo_whatsapp_identity_spec

Applies to v26.0+.
The wamo_whatsapp_identity_spec field is now available on ad creative creation and readable on ad creative GET endpoints for GK-enabled ad accounts. This field allows advertisers to specify a WhatsApp identity when creating creatives for WhatsApp Status ad placements.
Additionally, if the WhatsApp Status placement is included and user_age_unknown is not set, it will default to true.
The following endpoints are affected:

Shops Ads default to WEBSITE_AND_SHOP

Applies to v26.0+.
Eligible Shops Ads creatives will now automatically default to destination_spec.destination_type = WEBSITE_AND_SHOP when the advertiser has an IAB offsite checkout-enabled shop. Advertisers can opt out by explicitly setting destination_type to WEBSITE_AND_SHOP_OPT_OUT.
The following endpoint is affected:

Poll ads deprecation

Applies to v26.0+. Will apply to all versions October 27, 2026.
Poll is no longer available in ad creative. The poll_spec field and the "poll" enum value for the type field under interactive_components_spec are no longer available when creating or updating ads. Poll-related fields should be removed from the creative spec.
The following endpoints are affected:

Ads

Applies to v26.0+. Will apply to all versions October 27, 2026.
The applink_treatment field set to web_only is deprecated for Web and App campaigns. Use automatic or deeplink_with_web_fallback instead.
The following endpoints are affected:

Advantage+ Campaigns

Explicit advantage_audience flag required for HEF campaigns

Applies to v26.0+. Will apply to all versions October 27, 2026.
Campaigns with Special Ad Categories for Housing, Employment, or Financial products and services (HEF) that use targeting automation via the Marketing API must now explicitly set the advantage_audience flag. Previously, HEF campaigns could create ad sets with constrained targeting setups without specifying this flag.
With this change, if a HEF campaign has constrained targeting (for example, custom audience inclusions or detailed targeting), the API will return an error when the advantage_audience flag is not explicitly provided. This aligns HEF campaign behavior with the existing requirement for non-HEF campaigns and ensures advertisers are making an intentional choice about Advantage+ Audience for regulated ad categories.
The following endpoints are affected:

Audiences

Lookalike country and location_spec deprecation

Applies to v26.0+. Will apply to all versions September 1, 2026.
The country and location_spec fields in lookalike_spec are deprecated when creating Lookalike audiences. These fields are now silently ignored and the API creates a parent (countryless) Lookalike audience. Location targeting is determined by the ad set, matching existing Audience Manager behavior. Callers passing deprecated fields will receive a deprecation warning but the request will succeed.
When country is specified on new Lookalikes, advertisers will see the following message:
The country and location_spec fields are no longer available in lookalike_spec. Your lookalike audiences will deliver to the locations selected in your ad sets’ audiences.
The following endpoint is affected:

Insights

Delivery Estimate: daily_outcomes_curve, budget_guardrail, estimate_dau deprecation

Applies to v26.0+. Will apply to all versions October 27, 2026.
The daily_outcomes_curve, budget_guardrail, and estimate_dau fields on the Delivery Estimate endpoint were originally powered by the Bison / Outcome Prediction backend, which has been fully deprecated. These fields currently return hardcoded 0 or empty data and provide no useful information to developers, so they are being removed.
The following endpoints are affected:

Placements

Instagram Explore Feed placement removed

Applies to v26.0+.
The Instagram Explore Feed placement is no longer available.
The following endpoints are affected:

Messenger Stories placement removed

Applies to v26.0+. Will apply to all versions late August 2026.
The Messenger Stories placement (story in messenger_positions) is no longer available. Campaigns using this placement will have it automatically removed from their effective placements.
Migration guidance: Remove "story" from the messenger_positions array in your targeting spec. If messenger_positions only contained "story", remove the messenger_positions field entirely. If you are using Advantage+ Placements (automatic placements), no action is needed — the system will automatically exclude this placement.
The following endpoints are affected: