Why Won't My Ads Reporting Data Load?

When ads reporting shows an error instead of numbers, Meta’s explanation is about the size of the request: you may be working with too much data, or using a filter or segmentation that is too broad or too specific. Its listed fixes all narrow the request. As checked on 2 Oct 2026, Meta lists a shorter date range, fewer high-row columns and breakdowns, and a narrower filter.

Which causes does Meta list, and what fixes them?

Cause	How to check	Fix
Date range too large	You are loading data across a big time or date range	Reduce the date range to 28 days or 7 days
Too many metrics	You selected too many metrics	Remove metrics, because there is a limit to how much information a report can include
Product ID breakdown	You ran catalog ads and the report groups potentially thousands of products	Remove the product ID breakdown
Ad ID breakdown	The report breaks down by ad ID; Meta says it depends on the ads you ran and the date range	Remove the ad ID breakdown
Demographic breakdown	You selected many countries, regions, ages and genders	Remove the demographic breakdown
Whole-account view	The report covers the entire account	Filter for one or two campaigns or ads

How do you work through it?

1. Reduce the date range to 28 days, then to 7 days if the error remains.
2. Remove breakdowns with a lot of rows, such as product ID, ad ID or a demographic breakdown.
3. Remove metrics you do not need, because Meta says a report can only hold so much information.
4. Filter for one or two specific campaigns or ads instead of the entire account.
5. Add back only the columns and breakdowns your question needs.

Meta’s advice is to be specific about how you want to analyse your data. It also says that if your data does not load in ads reporting, you may not be able to load it elsewhere either.

Why might a long date range cause the error?

Meta describes the problem as working with too much data, and narrowing the time and date range is the first fix it lists. It says you may be trying to load data across a big time or date range. The help page cited here does not give a row limit or a longest range that always works. Its figures are the two it names, 28 days and 7 days, so start there.

What if the report loads but shows no data?

That is a different problem, and Meta has a separate page for it. It lists these reasons you may not see data or metrics for an ad:

• The ad has just started running and metrics are not yet available because of a short delay, which Meta says is normal.
• The date range you are viewing covers a period when the ad was not running.
• The ad is not delivering.
• You altered your tracking specs, or copied an ad that contains altered tracking specs.
• The campaign or summary level has multiple attribution settings, in which case conversion metrics will not populate.

If the ad is new, Meta says to check back a little later. The reporting delay entry linked below covers the lag in more detail.

FAQ

How short should the date range be?

Meta’s page suggests reducing it to 28 days or 7 days. It does not give a maximum range that always loads, and it also lists metrics, breakdowns and filters as causes. If 28 days fails, try 7, and cut breakdowns at the same time.

Which breakdowns does Meta name as causes?

Meta names product ID for catalog ads, ad ID, and any demographic breakdown. Its reasons are that one group can hold thousands of products, that ad ID depends on the ads you ran and the date range, and that you may have selected too many countries, regions, ages and genders.

Can I get the data somewhere else instead?

Meta says that if your data does not load in ads reporting, you may not be able to load it elsewhere either. Narrow the date range, columns, breakdowns and filters first, then run the report again in the same place.