If you've opened your Meta Ads reporting in the last couple of weeks and found your device split, your hour-of-day report, or your frequency breakdown sitting at a flat zero, you're not looking at a collapse in performance. You're looking at a reporting change that Meta rolled out on 6 August 2026 — and it's one of the sneakier ones, because nothing warned you it happened. Three breakdowns that used to work for every account now return data only if you've opted in, and if you haven't, the numbers don't error out. They just vanish.
For a D2C brand, that's more dangerous than an outage, because an outage is loud and this is quiet. Device and dayparting splits are where a lot of budget decisions actually get made — mobile versus desktop performance, which hours drive cheap purchases, how frequency ties to creative fatigue. If those reads silently drop to zero, you can pause a segment that was converting or keep spending into one that wasn't, all off data that isn't really there. This post covers exactly what changed on 6 August, how to tell if your account is caught in it, and the two-minute fix to switch the breakdowns back on.
What actually changed on 6 August 2026
Three Meta Ads breakdowns became opt-in only: the device breakdown (impression_device), the hourly breakdown (hourly_stats_aggregated_by_audience_time_zone), and the frequency breakdown (frequency_value). Until that date, all three returned data for any account that asked for them. From 6 August onward, they return data only for accounts that have explicitly enabled them under Additional Breakdowns.
The change was flagged in Meta's Marketing API changelog and picked up by the reporting platforms that live off this data — advisories from tools like Dataslayer, AdBeacon and AppsFlyer all describe the same behaviour. Standard reporting is untouched: your spend, impressions, clicks, purchases and ROAS columns all report as normal. It's specifically these three splits that stopped serving data by default.
The silent-failure problem
Here's what makes it worth a whole post rather than a footnote. When a non-opted account requests one of these breakdowns, the request doesn't fail. It succeeds — the API returns a normal HTTP 200 response — and the data array simply comes back empty. A human in Ads Manager sees a blank or zeroed report; a dashboard renders it as zero; an automated rule reads it as "this segment did nothing." There's no red banner, no error code, no alert. The absence of data looks exactly like a real result of zero, and that's the whole problem.
Who's most exposed
Meta's change lands unevenly. The restriction targets non-sales-supported accounts — the smaller and mid-market advertisers who don't have a dedicated Meta sales relationship. Accounts with a named Meta rep may already be covered and never notice. In practice, that means the brands most likely to be caught are exactly the ones running lean: growing Indian D2C stores and the agencies managing a portfolio of them, rather than the enterprise accounts with hands-on Meta support.
| Breakdown | API field | What D2C brands use it for |
|---|---|---|
| Device | impression_device | Mobile vs desktop performance, bid and budget skew |
| Hourly | hourly_stats_aggregated_by_audience_time_zone | Dayparting — which hours convert cheapest |
| Frequency | frequency_value | Spotting fatigue as frequency climbs |
If your optimisation leans on any row in that table — and most D2C accounts lean on at least one — you have a reason to check today rather than next month.
What each split is actually worth to a D2C account
It's easy to shrug off "a breakdown went off by default" until you spell out what each one drives. These three aren't vanity splits; they sit under real spending decisions.
Device
For most Indian D2C stores, the overwhelming share of traffic and purchases comes from mobile — but desktop often converts at a higher rate for considered, higher-ticket products. The device split is how you see that gap and decide whether desktop deserves its own treatment or whether a clunky mobile checkout is quietly leaking sales. Lose the split and you're flying blind on the single biggest behavioural divide in your audience.
Hourly
Dayparting only works if you can see which hours actually convert. A lot of D2C accounts find a cheap-purchase window — late evenings, a weekend morning — and lean budget into it. If the hourly report reads zero, you can't find that window, and worse, an automated rule built to protect it can misfire, cutting spend in a slot that was doing the heavy lifting.
Frequency
This split is your early-warning system for creative fatigue. As the same person sees an ad more times, response usually decays and cost per purchase climbs. Watching frequency against performance tells you when to refresh creative before the numbers rot. A blank frequency split hides that curve, so fatigue shows up as a mysterious ROAS slide instead of a signal you saw coming.
How to tell if you're affected
You can't rely on an error, so you check by comparison. Pull a device or hourly report for a window that ends before 6 August, then pull the same report for a window after it. If the earlier one has data and the later one is blank or all-zero across those splits, your account isn't opted in. Do the same for any third-party dashboard or in-house script that reads device, hourly or frequency data from the Marketing API, because those have been quietly pulling nothing since the change — and a dashboard that shows zero rarely gets a second look.
Watch your automated rules especially
Manual reports you'll eventually eyeball. Automations you won't. If you run any rule that reads these breakdowns — pause a placement when a device's cost per purchase crosses a threshold, cut spend in low-converting hours, throttle a campaign when frequency gets high — that rule is now reading zero and may act on it. A frequency rule that sees "0" won't fire; a device rule that sees "0" purchases might pause a converting placement. Audit every rule tied to these three splits before you trust it to run unattended.
The fix
The good news is that switching the data back on takes minutes. In Ads Manager, open your reporting view and enable the affected splits under Additional Breakdowns. That opt-in is set per ad account, so if you manage several, you'll repeat it for each one. If you run a large portfolio or pull data through the API, Meta exposes a feature-settings endpoint on the account's insights so you can opt accounts in programmatically instead of clicking through every one. After you opt in, give it about a day for the historical data to backfill, and the splits will report normally again.
This is also the kind of quiet, account-level change that's easy to miss when you're heads-down on creative and scaling — which is precisely why a regular technical audit of your Meta setup pays for itself. It's a core part of how our performance marketing team keeps client accounts honest: catching the silent stuff before it turns into a budget decision made on missing data.
Why this keeps happening — and how to be ready
Meta changes what its API serves more often than most advertisers realise, and not every change comes with a headline. The pattern to internalise is that missing data and zero data look identical on a dashboard, so a silent cut to a breakdown can masquerade as a genuine result for weeks. The brands that get burned are the ones treating every number on a chart as real without checking whether the pipe behind it is still connected.
So build the habit. When a segment you know performs suddenly reads zero, your first question shouldn't be "did it collapse?" — it should be "is the data still coming through?" This 6 August breakdown change is a clean example of why that instinct matters.
Recap and what to do this week
All 3 Meta breakdowns — device, hourly and frequency — went opt-in only on 6 August 2026, and non-opted accounts get an empty result dressed up as a success, so the splits read zero with no warning. It hits smaller, non-sales-supported accounts hardest, which is most Indian D2C brands and their agencies. The device split drives your mobile-versus-desktop calls, the hourly split drives dayparting, and the frequency split flags fatigue — losing any of them silently means optimising on air.
Do three things this week. Compare a pre- and post-6-August device or hourly report to confirm whether you're opted in. Switch the breakdowns back on under Additional Breakdowns for every account you run, or via the API if you manage many. Then audit every automated rule that reads these splits, because a rule acting on a phantom zero is the real cost here — not the blank cell you can see, but the budget decision you can't.
Sources: Meta Marketing API changelog (documenting that the impression_device, hourly and frequency_value breakdowns became opt-in only from 6 August 2026, returning empty data arrays with a success response for non-opted accounts), and reporting-platform advisories from Dataslayer, AdBeacon and AppsFlyer describing the same behaviour, the affected account types, the Additional Breakdowns opt-in inside Ads Manager, the feature-settings API endpoint, and the roughly one-day backfill. Optimisation and audit recommendations are Digistex4u's applied performance-marketing guidance, not statements attributed to Meta.
Frequently asked questions
Which Meta Ads breakdowns changed on 6 August 2026?
How do I know if my account is affected — there's no error?
How do I turn the breakdowns back on?
Why did Meta do this, and should D2C brands worry?
Ready to put this into action?
Digistex4u runs performance, CRM, CRO and growth as one engine for D2C brands. Book a free 20-minute call and we'll map your fastest path to scale.
Get the D2C growth playbook
One practical teardown a week — the Meta, Google, SEO, CRM and retention tactics we run on real D2C brands. No fluff, no spam.
