Meta is removing the Messenger Stories ad placement. If you have it active anywhere in your account, you have until August 27 to clean it up — and if you're already on Graph API v26.0, the placement may be silently failing right now.
What Meta is removing
Advertisers with Messenger Stories active in their campaigns received direct notification from Meta: the placement stops serving on August 27, 2026. The deprecation then extends to all Graph API versions — including unversioned calls — on October 27, 2026.
This affects anyone using messenger_positions: story in their ad sets, either through the Ads Manager UI or the Marketing API directly.
The silent failure on v26.0
Graph API v26.0 shipped on July 29, 2026, and it changed how the platform handles this placement before the formal end date. When you create or update an ad set and include story in messenger_positions, the API silently strips it from the response.
No error. No warning. HTTP 200 comes back, but Messenger Stories does not appear in the returned ad set object. Your ad set is saved without the placement and you have no way to know unless you explicitly check the response fields.
This is the intended migration behavior, not a bug Meta plans to fix. The API is treating the soon-deprecated placement as already gone.
Two dates, two changelogs, one confusing rollout
Meta's own documentation does not agree on timing. The Graph API changelog names October 27 as the deprecation date. The Marketing API changelog names August 27. Both are real dates that apply to different things:
- August 27: The placement stops serving for advertisers who received direct notification
- October 27: The placement becomes unavailable across all API versions globally
If you did not get a notification, you may assume you have until October. That assumption is risky. Meta's deprecation rollouts regularly affect accounts ahead of the stated global date.
What to do with your ad sets
The fix requires checking every ad set that touches Messenger placements:
If messenger_positions includes story alongside other values like inbox or reels, remove story only. The remaining placements keep working.
If story is the only value in messenger_positions, also remove messenger from publisher_platforms — unless you are using another Messenger placement like marketing messages. Leaving messenger in publisher_platforms with no valid messenger_positions value will cause the ad set to error on creation.
For API-managed campaigns, update your templates and any automation that builds ad sets to omit the story value entirely. After October 27, passing it in any API version will return an error instead of silently succeeding.
Why this matters beyond one placement
Messenger Stories has not been a high-volume placement for most advertisers. Meta's placement performance data has consistently shown inbox and Audience Network driving most Messenger-attributed conversions. The placement removal itself is not a major reach loss for the average account.
What matters is that Meta has now shown a new deprecation pattern: silent stripping on newer API versions before the formal end date, with no dedicated error code. Advertisers and tool builders who rely on API response validation to catch bad configurations will miss this entirely — the 200 status tells them nothing is wrong.
If you use Advantage+ placements and let Meta choose automatically, this change is handled for you. The risk sits entirely with manually configured placements, in Ads Manager or through the API.
What to check this week
Open Ads Manager and filter for active ad sets with Messenger Stories enabled. If you find any, update them before August 27.
If you use a third-party tool or custom API integration to manage campaigns, check your codebase for any reference to messenger_positions: story and remove it from your default templates now, not in October.
Running Graph API v26.0 already? Pull a recent ad set creation response. If Messenger Stories was supposed to be included and is missing without an error, that is the silent stripping behavior in action.
A free audit of your Meta account structure at gromerce.com/audit will surface any active Messenger Stories placements in about three minutes. It is a faster starting point than combing through ad sets manually.
The placement is already gone in the API — your campaigns just might not know it yet.
Sources: Meta Marketing API changelog, Meta Graph API changelog, PPC.Land, August 2026
