Meta Ads Update August 2026: The Reports That Went Blank

Meta ads update August 2026: three breakdowns went opt-in and now return blank, Messenger Stories ends August 27, and Meta AI rewrites your ad image text.

By Alex Neiman·Aug 26, 2026·11 min read

The Meta ads update for August 2026 is four changes, and three of them alter what your reports say without altering what your campaigns do. A breakdown you have used for years now returns an empty table and a success code. A placement disappears tomorrow. And Meta's AI has been rewriting the words printed on your ad images since late July, by default.

None of these arrived as a red banner in Ads Manager. Each one moves a number you rely on — or a creative you approved — while the interface keeps looking exactly the way it looked in July.

Why this matters more than a normal month

A change that breaks something is easy. You get an error, you fix it, you move on.

August's changes do the opposite. They return 200 OK. They render a report. They just render it empty, or they render it about a creative you did not write. The failure mode is silence, and silence reads as data.

If you make weekly decisions off device splits, hourly pacing, or frequency, there is a real chance you have been making them off zeroes for three weeks.

What changed (and when)

| Change | When | Acts on your account automatically? | What it distorts | |---|---|---|---| | Three Ads Insights breakdowns became opt-in | August 6, 2026 | Yes — non-enabled accounts return blank | Device splits, hourly pacing, frequency and fatigue calls | | Messenger Stories placement removed | August 27, 2026 (all API versions October 27) | Yes — budget redistributes on its own | Placement mix, blended CPA/ROAS after the shift | | Meta AI rewrites text inside ad images | Reported July 27, 2026 | Yes — on by default in Advantage+ Creative | Offer accuracy, creative-level attribution of wins | | Placement exclusions and device/OS targeting removed | Rolling out August 2026 | Yes — controls disappear from ad sets | Your ability to exclude a placement at all |

The breakdowns that went blank

On August 6, 2026, three Ads Insights breakdowns became per-account opt-in:

  • impression_device — the device split
  • hourly_stats_aggregated_by_audience_time_zone — hourly pacing
  • frequency_value — the frequency distribution

For an account that never opted in, the API "still returns HTTP 200. The Ads Manager UI still renders the report. But the rows are blank or zeroed," as Elevarus put it. No error. No warning. A dashboard that had numbers on August 5 shows zeroes on August 6 and reports itself healthy.

The fix takes about a minute per account. In the Ads Manager reporting view, open Breakdown → Additional Breakdowns and enable the affected breakdowns. There is no bulk toggle in the standard UI, so agencies with a roster should use the enablement endpoint instead: POST /act_<ad-account-id>/insights/feature-settings (AdBeacon).

One honest caveat on history: the sources disagree. AdBeacon says to "expect roughly a day for history to backfill once an account opts in." Elevarus says the opposite — "data does not backfill. Whatever range you cared about before you opted in stays empty." Meta has not published a line settling it. Treat the pessimistic version as your planning assumption: opt in today, then check tomorrow, and do not promise a client a device-level August retro until you have seen the rows come back.

This change has a deeper parent post on this site. The attribution and reporting mechanics behind it are covered in Meta attribution changes 2026: engage-through, explained, which names all three breakdowns and the empty-array behaviour. Start there if you want the full version rather than the checklist.

Messenger Stories ends tomorrow — and the API date is not the same date

Messenger Stories is permanently removed as an ad placement on August 27, 2026. Delivery for ad sets that included it in the eligible pool gets redistributed to remaining placements automatically (Common Thread Collective).

There is a second date, and most coverage skips it. Meta's own Graph API v26.0 changelog states that the story value in messenger_positions "is silently removed for versioned v26.0 or later calls and no longer appears in effective placements," and that this applies to all Marketing API versions on October 27, 2026.

So: if you build ad sets through the API on v26.0 or later, the value is already being stripped — you send it, you get a 200, and the ad set comes back without it. If you are on an older version, you have until October 27 before the same thing happens to you. Two dates, two audiences, and confusing them is how an agency tells a client "we're fine, we're on v25" and then is not fine.

What to do before tomorrow: pull a 90-day placement breakdown now, while you still can. Once the placement is gone, the comparison baseline gets harder to reconstruct — and you will want it when blended ROAS wobbles next week and someone asks why.

Meta AI is rewriting the text on your ad images

Reported July 27, 2026: Advantage+ Creative can now rewrite the text rendered inside your uploaded ad images — the price callout, the promo headline, the slogan — while preserving font, colour and layout. It is enabled by default across eligible Advantage+ campaigns (Common Thread Collective).

The reporting problem is subtle. You can review the variants in the Creative Report in Ads Manager and filter to image variants. But if a rewritten headline outperforms your original, the original may quietly stop running — and your creative learnings now describe a headline you did not write.

The compliance problem is not subtle. If the AI adjusts a discount percentage or a shipping promise printed on the image, that image no longer matches your landing page.

Turn it off per campaign in the Image Enhancements section of Advantage+ Creative settings, or leave it on deliberately and audit the Creative Report weekly. Both are defensible. Not knowing which one you picked is not.

Placement exclusions are going away

Meta is removing the ability to exclude individual placements, to exclude a whole platform and its placements, and to restrict campaigns by device or operating system (Social Samosa, August 21, 2026).

The replacements are narrower than what they replace: value rules, which adjust bids across seven eligible placements by device and mobile OS, and account-level placement controls under Advertising Settings → Account Controls.

Note the interaction with the first item on this list. Placement control is moving from a hard exclusion to a bid nudge, at the same moment the device breakdown stopped returning data by default. Less control, and less visibility into the thing you no longer control. Enable the breakdown.

Two smaller items worth logging

AI Connector security controls (August 11). Meta shipped granular scoping for AI agents connected to ad accounts — restrictions by Page, Instagram account and business portfolio. Several sensitive write actions default to enabled. That one has its own post: what the AI connector security controls changed.

Ad prices are up 12%. Meta's Q2 2026 results, published July 29, report that "average price per ad increased by 12% year-over-year," against ad impressions up 14% (Meta). This is the single most useful number for your Q4 planning conversation. A flat budget buys meaningfully less than it did a year ago, and a CPA that rose 12% year over year is holding steady in real terms, not degrading.

What this actually costs: a walkthrough

The arithmetic below is illustrative, not measured, but the shape is what these changes produce.

Take an account that runs mobile and desktop, with a standing rule to cut spend on any ad crossing frequency 3.5 on cold audiences.

On August 5, the frequency table showed a distribution and two ads flagged. On August 6, the account had not opted in, so the table returned empty. Empty is not a red row. Nothing flagged. The weekly review passed clean.

Three weeks later, the ads that would have been flagged are still running. The fatigue did not pause because the measurement did. And because impression_device also went blank, the "mobile is carrying this" assumption behind the budget split has been unverified for the same three weeks.

Nothing broke. Every report generated on schedule. That is precisely the problem: a blank frequency table does not read as no data, it reads as no fatigue. If you want the longer version of that specific failure, it is the subject of Meta native creative fatigue vs third-party detection.

Act today / This week / Monitor

Act today

  • Enable the three breakdowns on every ad account you touch. Ads Manager → Breakdown → Additional Breakdowns, or the feature-settings endpoint if you manage more than a handful.
  • Pull a 90-day placement breakdown before Messenger Stories disappears tomorrow.
  • Check whether image text rewriting is on in your Advantage+ campaigns. Decide on purpose.

This week

  • Re-run any device, hourly or frequency report dated after August 6 and confirm the rows are populated. If they are still empty, the opt-in did not take.
  • Audit anything downstream that consumes those breakdowns — automated rules, spreadsheets, client dashboards. A rule fed by an empty array does not fire.
  • Reprice your Q4 plan against +12% average price per ad.

Monitor

  • Whether history backfills on the breakdowns you just enabled. The sources disagree; your account is the tiebreaker.
  • Delivery fluctuation in the week after August 27 as budget rebalances off Messenger Stories.
  • The October 27 API date if you build ad sets on a version below v26.0.

Common mistakes

  1. Reading a zero as a result. After August 6, a blank device or frequency table is a permissions state, not a performance finding. Confirm the breakdown is enabled before you interpret anything it returns.
  2. Opting in on one account and calling it done. The setting is per ad account, with no business-manager-level bulk toggle. An agency that fixes the account it noticed still has the rest of the roster reading zero.
  3. Assuming automatic redistribution is a strategy. Meta will move Messenger Stories budget for you. It will not tell you where it went, and you will be reconstructing that from a placement report you should have exported first.
  4. Letting the Creative Report go unread while AI rewriting is on. If you never look, your best-performing headline is a sentence nobody on your team approved.
  5. Treating the +12% price line as background news. It is the number that decides whether your Q4 budget is flat or is quietly a cut.

FAQ

Why did my Meta device or frequency report suddenly show zero? Because on August 6, 2026 those breakdowns became per-account opt-in, and non-enabled accounts get a success response with an empty data array instead of an error (Elevarus). Enable them under Breakdown → Additional Breakdowns.

Will my historical breakdown data come back after I opt in? Unclear, and the reporting on it conflicts. AdBeacon reports roughly a day for history to backfill; Elevarus reports that it does not backfill at all. Plan for the data being gone and treat a backfill as a bonus.

When exactly does Messenger Stories stop running? August 27, 2026 for the placement itself. Separately, Meta's v26.0 changelog applies the messenger_positions removal to all Marketing API versions on October 27, 2026.

Can I still exclude a placement I do not want? Decreasingly. Per-placement and per-platform exclusions are being removed from ad sets, replaced by value rules and account-level placement controls under Advertising Settings.

How do I stop Meta from rewriting text on my ad images? Turn off the relevant option in the Image Enhancements section of Advantage+ Creative settings, per campaign. It is on by default.

Did Meta ads get more expensive in 2026? Yes. Average price per ad rose 12% year over year in Q2 2026, with impressions up 14%, per Meta's own results release.

The shortest answer

Enable the three breakdowns today. Export your placement data before tomorrow. Then go look at what Advantage+ has been printing on your images.

The pattern across all four changes is the same one: the platform changed what your numbers mean, and left the dashboard looking normal. Catching that requires someone to check the things that did not raise an alarm — every week, on every account.

That is the job GoodMorning does. It reads your account on read-only access and hands back an urgency-tiered action list — act today, this week, monitor — with the analysis already done. Zero analysis required on your end. $50/mo with a 14-day trial, and it runs the same way whether you are one brand or an agency reporting across client accounts.

If you would rather do it by hand, the tooling questions are covered in Meta Ads audit tool for the account-level sweep and creative fatigue tool for the frequency half of this month's damage.

Previous months in this series: Meta Ads update July 2026 and Meta Ads update May 2026.

Sources

  1. Meta — Meta Reports Second Quarter 2026 Results (July 29, 2026)
  2. Meta for Developers — Graph API v26.0 changelog
  3. Elevarus — Meta Ads Breakdown Deprecation: Silent Reporting Break
  4. AdBeacon — Your Meta Device Report Might Have Quietly Gone to Zero (August 6)
  5. Common Thread Collective — Meta Is Removing Messenger Stories Ads on August 27
  6. Common Thread Collective — Meta Is Rewriting Your Ad Images by Default
  7. Social Samosa — Meta to remove placement controls from ad sets (August 21, 2026)
  8. AdsUploader — Meta Ads Updates (August 2026): What's Changing and What to Do
  9. Dataslayer — Understanding upcoming changes to metrics on Facebook

Related reading