Meta Ads Reporting Breakdowns: August 2026 Changes

Since August 6, 2026, Meta Ads Manager has been hiding device, hourly, and frequency breakdown data by default — and accounts that haven't opted in are silently showing empty results with no error message. This is one of the most quietly disruptive Meta changes in recent memory, and most ecommerce advertisers have no idea it happened.

What Changed in Meta Ads Reporting on August 6, 2026

Meta's reporting overhaul went live on August 6, 2026, shifting several previously automatic breakdown dimensions to an explicit opt-in model. The affected breakdowns include device type (mobile vs. desktop), hourly delivery data, and frequency segmentation — three of the most commonly used dimensions for ecommerce campaign optimization.

The change is part of Meta's broader push toward privacy-aligned measurement, similar to the signal loss changes introduced after iOS 14. The mechanics are different this time, but the operational impact is the same: data that used to appear automatically now requires you to take action.

What makes this particularly insidious is that Meta's interface doesn't throw an error. Affected columns simply return empty — no warning, no prompt to enable anything. Advertisers who rely on automated reporting dashboards connected via the Marketing API are especially exposed, since they may not notice blank dimensions until budget decisions have already been made on bad data.

Meta Q2 2026 ad revenue hit $59.36B, up 27% year-over-year — the platform isn't going anywhere. But that growth means Meta can afford to make breaking changes that put the burden on advertisers to adapt.

Why Your Device and Hourly Data Is Showing as Empty

If you've opened Ads Manager in the past two weeks and noticed that your device breakdown, time-of-day segmentation, or frequency data is missing, you're experiencing the opt-in gap — not a bug.

Here's exactly what's happening under the hood:

Device breakdown: Before August 6, segmenting by mobile vs. desktop was automatic. Now it requires enabling "Additional Breakdowns" at the account level before it populates.

Hourly breakdown: Ads Manager previously let you segment delivery by hour of day without any setup. This dimension now sits behind the same opt-in gate, meaning any time-based optimization you were doing — adjusting bids by peak hour, comparing morning vs. evening ROAS — is currently based on empty data if you haven't opted in.

Frequency breakdown: For awareness and retargeting campaigns where frequency management is critical, blank frequency data is a budget risk. Running retargeting without frequency caps informed by real data is how you burn budget on ad fatigue.

The reporting breakdown opt-in went live August 6, 2026, with historical data backfilling within approximately one day once you enable it. That means you won't permanently lose the data — but every day you haven't opted in is another day your optimization decisions are flying blind.

How to Enable Reporting Breakdowns in Ads Manager

The fix takes under two minutes. Here's the exact path:

1. Open Meta Ads Manager and navigate to the Campaigns, Ad Sets, or Ads view
2. Click "Columns" in the top-right of the data table
3. Select "Customize Columns" from the dropdown
4. Look for "Additional Breakdowns" — this is the new opt-in toggle introduced August 6
5. Enable the breakdown dimensions you need: Device, Time of Day, Frequency
6. Save your custom column view

Once enabled, historical data will backfill within roughly 24 hours. Going forward, the data will populate in real time.

For teams managing multiple ad accounts, you'll need to enable this per account — there's no global toggle across your Business Manager. If you're using a third-party dashboard tool (Northbeam, Triple Whale, Supermetrics), check whether those platforms have already pushed updates to handle the opt-in change. Some have; others haven't, which means your external dashboard may be pulling empty dimensions from the API.

Meta Ads Reporting Breakdown Status: Pre vs. Post August 6, 2026

Breakdown Type	Previous Behavior	Post-Aug 6 Behavior	Fix Required
Device (mobile/desktop)	Automatic	Hidden by default	Enable Additional Breakdowns
Hourly delivery	Automatic	Hidden by default	Enable Additional Breakdowns
Frequency	Automatic	Hidden by default	Enable Additional Breakdowns
Age & gender	Automatic	Unchanged	No action needed
Region/country	Automatic	Unchanged	No action needed
Placement (Explore, Messenger Stories)	Available via API	Removed in API v26.0	Update API queries

What the Marketing API v26.0 Changes Break in Automated Reports

If your team or agency is pulling Meta data via the Marketing API — for custom dashboards, automated reporting, or data warehouse syncs — there's a second issue running in parallel: Marketing API v26.0 has removed Instagram Explore Feed and Messenger Stories as distinct placement identifiers.

This matters for any report that breaks down performance by placement. If your query previously returned line items for INSTAGRAM_EXPLORE or MESSENGER_STORIES, those fields now either return null or throw errors depending on how your integration is built.

The practical impact: placement-level ROAS calculations in automated reports may be understating total spend and conversions if those placement IDs are still referenced in queries. Brands using Google Sheets + Supermetrics or custom Python/SQL pipelines should audit their placement dimension queries against the v26.0 deprecation list.

Meta's API versioning gives a sunset period for deprecated fields, but accounts using older integration setups may have already inherited the break without realizing it. For ecommerce brands spending significant volume on Meta, this is exactly the kind of technical debt that compounds silently. One broken placement dimension in an automated report can cascade into misleading budget recommendations across an entire quarter.

Building a Reporting Stack That Survives Platform Changes

The August 6 changes are a good forcing function for a broader audit. Meta has made three significant reporting changes in 2026 alone — this isn't a one-time event.

A resilient reporting setup for ecommerce brands running Meta ads has a few non-negotiable characteristics:

Use native Ads Manager as your source of truth. Third-party dashboards are useful for synthesis, but any optimization decision that touches budget should be verified against native data. Third-party tools lag on API changes; Meta's own interface is always current.

Build an "API health check" into your reporting cadence. Once a month, run a raw API pull and verify that key dimensions are returning data. Empty fields without errors are the most dangerous failure mode — they're invisible until you go looking.

Separate your reporting layers. Daily operational data (spend, CPC, CTR) and performance insight data (device mix, frequency, time-of-day trends) serve different purposes. The operational layer should be near-real-time and simple. The insight layer can tolerate a 24–48 hour lag and should be audited weekly, not daily.

Document your column sets. If you're running multiple custom column views in Ads Manager, document which views are used for which decision types. After the August 6 change, any saved view that relied on the now-opt-in breakdowns needs to be manually updated.

Our team at Atlas runs a reporting audit for every client account at the start of each month — exactly because Meta's platform changes frequently enough that a set-and-forget approach consistently produces stale or broken dashboards. If you're managing a meaningful Meta budget without a structured audit process, you're likely making some decisions on data that doesn't reflect reality.

For brands questioning whether their broader ecommerce retargeting strategy is working, clean reporting is the prerequisite — you can't optimize what you can't measure accurately. And if you've been following the Meta Advantage+ Creative AI text rewriting update from July 27, verifying that your creative-level breakdown data is accurate is now more important than ever, since the AI generates variants you didn't manually create.

FAQ: Meta Ads Reporting August 2026