Meta's Graph and Marketing API v26.0 landed on July 29, 2026, and most of it read like routine changelog housekeeping. Then, on August 27, Messenger Stories disappeared as an ad placement for good, and the quieter part of the update became the part that actually costs advertisers money: the tools you used to trim wasted spend from a Meta campaign got smaller, right as CPMs are falling and it is easy to stop watching closely.
Meta's v26.0 update removed the Instagram Explore Feed and Messenger Stories placements, blocked new poll ad creatives, and replaced granular placement exclusions with Value Rules and account-level controls. You can no longer fully exclude a placement; you can only down-weight its bid, capped at a 90 percent reduction. If your ROAS strategy depended on hard exclusions, rebuild it this week.
What actually changed in the v26.0 update?
Meta pushed Graph API and Marketing API v26.0 on July 29, 2026. Several changes inside it touch performance marketing directly, and the biggest one, the Messenger Stories placement removal, only fully took effect on August 27, roughly two days before this was written.
| Change | Effective | What it means for you |
|---|---|---|
| Messenger Stories placement removed | August 27, 2026 | Permanently gone from the eligible placement pool; delivery for affected ad sets redistributes automatically |
| Instagram Explore Feed placement removed | With v26.0, July 29, 2026 | API calls that still specify it now return an error rather than being silently ignored |
| Poll ad creative creation blocked | With v26.0 | You can no longer create new poll ad creatives through the API |
| Placement-level exclusion controls reduced | With v26.0 | Value Rules and account-level controls become the primary way to influence delivery, replacing granular per-ad-set exclusions |
The Messenger Stories change is the one worth flagging separately from the rest, because Meta handled the two placement removals differently. Drop Instagram Explore Feed from a call and the API rejects it outright. Drop Messenger Stories and the API returns a 200 and quietly strips it from your targeting, which means a campaign built before August 27 can be running with a materially different placement mix than the one you configured, without an error to tell you so.
Why did Meta do this?
The stated direction is fewer placement-level decisions inside individual ad sets and more delivery optimization handled by the algorithm at the account level, the same direction Meta has pushed with Advantage+ campaigns since 2024. Fewer manual exclusions means fewer ways an advertiser can accidentally starve the delivery system of the volume it needs to optimize well. It also means less granular control at the exact moment you might want it most.
What does the 90 percent bid cap actually mean for your account?
Previously, excluding a low-performing placement, Audience Network is the classic example, meant zero budget could land there. Under Value Rules, the closest replacement, you can down-weight a placement's bid but the reduction caps at 90 percent. That leaves a residual 10 percent of your normal bid still eligible to win an impression on a placement you would have blocked entirely under the old system. On a small account that is rounding error. On a account spending five or six figures a month across placements, it is a real leak, and it will not show up as an obvious spike, it shows up as blended ROAS drifting a few points worse for reasons that do not match anything you changed.
| What you used to do | What replaces it now |
|---|---|
| Hard placement exclusion in an ad set | Value Rules bid adjustment, capped at a 90% reduction |
| Manual placement selection per ad set | Account-level placement controls |
| Poll ad creative | Deprecated; use another interactive format |
Pull a placement breakdown on the last 30 days before you do anything else. Any campaign that leaned on hard exclusions for brand safety or cost control needs a Value Rule rebuilt at the maximum available adjustment, then a delivery check a week later to confirm spend did not creep back into the placement you thought was blocked. This is a 30-minute audit, not a rebuild, but skipping it is how a quarter's ROAS quietly slips.
Does falling CPM hide this problem?
It can. Median Facebook CPM was reported at $16.47 in July 2026, about 12.7 percent below July 2025. Cheaper impressions are good news on their own, but they also make it easier to miss placement-level waste, because a blended account view can look healthy even while a growing share of spend leaks into placements you can no longer fully exclude. Falling CPMs are a reason to check placement-level ROAS more often right now, not less.
A two-week checklist for this change
- Export placement-level performance for the last 30 days, before and after August 27, and compare Messenger Stories and Explore Feed delivery specifically.
- Identify every campaign that relied on a hard placement exclusion and rebuild it as a Value Rule at the strongest available bid adjustment.
- Remove any API call that still references Instagram Explore Feed as a placement before it starts throwing errors on you.
- Retire any poll ad creative workflow that depended on API creation and move that budget to a supported format.
- Set a calendar reminder to re-check placement delivery in two weeks, since redistribution effects are not always immediate.
Frequently asked questions
What did Meta actually remove in the v26.0 update?
Meta's Graph and Marketing API v26.0, released July 29, 2026, removed the Instagram Explore Feed and Messenger Stories ad placements, blocked creation of new poll ad creatives, and cut back placement-level exclusion controls inside ad sets. Messenger Stories was fully retired as a placement on August 27, 2026.
Can I still exclude a bad-performing placement from my Meta ad sets?
Not the way you used to. Meta replaced granular placement exclusions with Value Rules and account-level controls, which let you down-weight a placement's bid rather than fully block it. Reported bid reductions cap at 90 percent, meaning some spend can still reach a placement you would previously have excluded outright.
What are Value Rules and how do they replace placement exclusions?
Value Rules let you adjust bids up or down based on conditions like placement, device or audience segment, applied at the account or campaign level rather than per ad set. They are Meta's suggested replacement for the placement exclusions removed in v26.0, but they cap how far you can down-weight a placement rather than letting you block it entirely.
Will this hurt my ROAS?
It can, if you relied on hard placement exclusions to keep spend off low-intent inventory like Audience Network or Messenger Stories. Since some budget can now reach those placements even after down-weighting, watch placement-level ROAS and CAC closely for the first two to three weeks after the change and rebuild your Value Rules accordingly.
Are Facebook and Instagram CPMs going up or down right now?
Down, broadly. Median Facebook CPM was reported at $16.47 in July 2026, about 12.7 percent lower than July 2025. Falling CPMs make it easy to miss placement-level waste, since blended ROAS can look fine even while budget leaks into placements you can no longer fully exclude.
What should I do about this change this week?
Pull a placement breakdown on your last 30 days of spend, identify any campaign that used to rely on hard placement exclusions, rebuild those as Value Rules with the maximum available bid adjustment, and check delivery reports over the next two weeks to confirm spend did not quietly redistribute into low-performing inventory.
The takeaway
None of this is a reason to panic about Meta ads. It is a reason to spend thirty minutes this week checking whether a campaign you built around hard placement exclusions is still doing what you think it is doing. The API stopped enforcing the boundary you set. Whether that costs you ROAS depends entirely on whether you noticed before your competitors did.