Meta Ads Breakdown Deprecation: The Silent Reporting Break

Three days ago, your Meta Ads dashboard broke. You probably did not notice, and neither did anyone else on your team. Since August 6, 2026, three reporting breakdowns that most media buyers use every week silently stopped returning data for any Meta ad account that never opted in. The device breakdown, the hourly breakdown, and the frequency breakdown all now return an empty result on non-opted accounts. The kicker: the API returns HTTP 200. Your dashboard shows zeroes. No error, no warning, no email.

This is the Meta ads breakdown deprecation, and it is the exact kind of change that punishes accounts that were not paying attention. The Improvado product update on August 6 confirms which breakdowns are affected, and AdMake AI’s August changelog walks through the operator implications. This post is the fix: what changed, who is exposed, and the audit you should run this week before the second monthly report comes out with the wrong numbers.

What the Meta Ads Breakdown Deprecation Actually Changed

The Meta ads breakdown deprecation covers three specific report breakdowns in the Marketing API and Ads Manager reporting view. The device breakdown, called impression_device in the API, tells you whether an impression served on mobile, desktop, or tablet. The hourly breakdown, called hourly_stats_aggregated_by_audience_time_zone, tells you when your ads got shown across the day. The frequency breakdown, called frequency_value, tells you how many times an average user saw your ads.

Before August 6, those three breakdowns worked in every account by default. Starting August 6, they only work for ad accounts that have opted in per account. If an account did not opt in before that date, any report that requests one of those breakdowns comes back with an empty data array. The API still returns HTTP 200. The Ads Manager UI still renders the report. But the rows are blank or zeroed.

The device breakdown is the widest hit. Any report that combines device with another field, like device by placement or device by age, dies the same way. A routine device-by-placement query that ran fine on August 5 returns empty on August 7. Nothing alerts. The report just looks like your ads suddenly stopped serving on mobile.

Who the Meta Ads Breakdown Deprecation Actually Hurts

Three profiles carry the most exposure. First, any team that reads Meta performance data through a third-party dashboard, whether that is Looker Studio, Power BI, Supermetrics, Funnel, Improvado, or an in-house Marketing API pipeline. If your dashboard renders a device breakdown or an hourly report as a headline chart, that chart is now zeroes on any account that did not opt in.

Second, any agency running multi-account programs where a central team pulls performance data across five, ten, or fifty client accounts. The Meta ads breakdown deprecation is per account. Every ad account has to be opted in individually, and there is no bulk toggle in Ads Manager. If your client onboarding checklist did not include this step, you now have a batch of accounts that report empty for the three affected breakdowns until someone touches each one.

Third, any advertiser who uses hourly bidding rules or dayparting logic tied to Meta reporting. If a rule reads the hourly breakdown to decide when to pause or lift bids, that rule is now firing on empty data. It will not error. It will just make decisions on a data set that no longer exists. That is the most dangerous version of this change, because the automation keeps running as if nothing broke.

How to Fix It Right Now

The fix is fast if you know where to look. In Meta Ads Manager, go into the reporting view for a single ad account, click Breakdown, and look under Additional Breakdowns. You will see toggles for the three affected breakdowns. Enable them. Meta will start collecting the data from roughly the next day forward. There is no help center article for the toggle yet. The setting lives inside the reporting UI, not the account settings panel.

This has to be done per account. You cannot enable it once at the business manager level and inherit it down. If you manage twenty client accounts, you enable it twenty times. Account admin access is required on each one, so if you are a report user without admin rights, you need someone with admin access to click through.

There is a programmatic path for agencies that manage a lot of accounts. POST to /act_<ad-account-id>/insights/feature-settings enables the breakdowns per account through the Marketing API. This endpoint is enable-only. You cannot disable through the API, only through the UI. Data appears within about a day of enabling. The feature names in the API do not match the breakdown names in the UI exactly, so plan a short mapping session before you deploy the script.

Data does not backfill. Whatever range you cared about before you opted in stays empty. Historical periods before your opt-in date are lost for these breakdowns on that account. If you have a September report that will look at August performance, and you opt in on August 10, the first four days of August are gone. That is the operator cost of this change, and it is why the audit matters this week.

The Meta Ads Breakdown Deprecation Audit for This Week

Here is the sequence.

Pull a list of every Meta ad account you touch through any reporting surface. Include your own accounts, every client account, and any account referenced by a dashboard, spreadsheet, or automation. That is your opt-in queue. Do not skip accounts that look inactive. If a dashboard or an API script points at them, they need the toggle.

For each account, decide which of the three breakdowns you actually use. If you never read the frequency breakdown, do not turn it on. But device and hourly are so widely used that most accounts should enable both. Pick your default before you start clicking so the work moves fast.

Enable the breakdowns in Ads Manager per account, or run the feature-settings API call if you have a script and account admin scope. Note the date you enabled each account, because that date is the earliest point your data resumes.

Audit every dashboard and report that reads Meta data. Any Looker Studio panel, Power BI model, Sheets connector, or in-house pipeline that requests device, hourly, or frequency breakdowns needs a sanity check. If a chart shows zeroes since August 6 that used to show data, you have a Meta ads breakdown deprecation hit, not a performance collapse. Fix the account opt-in first, then check whether the dashboard needs any query changes. Most tools will just pick up the data once the account is opted in. Your measurement dashboard hygiene discipline applies here directly.

Brief your clients and your team. A short proactive note about a Meta reporting change that is quietly zeroing three breakdowns beats explaining a strange August report at the next monthly review. If you produce monthly performance decks, add a line this cycle that names the affected accounts and the opt-in date. Reports that pre-date the opt-in should get a footnote about the coverage gap, not a made-up estimate.

Automations You Need to Check

Any automation that reads Meta reporting is now suspect until you verify. Hourly bidding rules, dayparting scripts, device-based budget shifts, frequency-cap enforcement rules, and creative rotation logic tied to reach breakdowns all need a quick check.

Start with any nightly job that pulls performance data and takes an action. If it uses one of the three affected breakdowns and hits an account that never opted in, the job is making decisions on empty data right now. That is closer to running blind than running conservatively, because the automation still fires but with no signal underneath. If you already use structured diagnostic patterns, add a check for empty-breakdown responses to your existing PPC prompt library so this pattern is caught the next time Meta ships something similar.

Also verify creative reporting. If your team uses the 3-second hook test or any device-specific creative diagnostic, the device breakdown drives that read. On non-opted accounts, that view is now empty. Your creative pass-fail signal disappears until you opt in.

The Meta lead event bucketing change earlier this year was a similar pattern of quiet reporting shift. So was the Advantage+ audience expansion behavior where audience settings could inflate reach in ways that were not obvious in default reports. Both taught the same lesson: Meta ships changes to defaults faster than help documentation catches up, and the accounts that had someone watching are the accounts that adjusted first.

The Bigger Point About Silent API Changes

The Meta ads breakdown deprecation is the third silent change in a row from Meta this year, and it will not be the last. The pattern is durable. Meta announces the change in an API changelog. The change ships on a Monday. Requests continue to return HTTP 200. Data quietly stops flowing. Dashboards look wrong. Media buyers notice on Wednesday or Thursday when a client asks why mobile impressions dropped to zero.

Meta is not the only platform that does this. The GA4 ad_storage consent change in June ran the same play at Google’s end. So did the Google Ads terms of service change that reclassified conversion labels. And the Meta Business Agent launch reshaped how default Ads Manager surfaces information without breaking any obvious workflow. Each one moves defaults, changes what a routine query returns, and rewards accounts with someone paying attention.

Set a monthly reminder to skim the Meta Marketing API changelog and the Google Ads announcements page. Not to read every entry. Just to catch the ones that quietly move defaults. The five minutes a month you spend there are the cheapest insurance you can buy against a client asking why the numbers look wrong at the exact moment you were hoping to talk about something else.

If you want a second set of eyes on your Meta account opt-ins and dashboard exposure this week, book a free consultation with our paid social team and we will walk through the audit with you. Let’s Grow!