Study first
Review the ideas behind the questions
Review how Meta Ads reporting requests shape the numbers before you compare campaigns, rebuild dashboards, or change spend.
Match the report to the decision
Advanced reporting work starts with the level, date range, attribution basis, fields, and breakdowns used in the query.
- Insights requests can use fields, date presets, date ranges, levels, and breakdowns to shape the returned rows.
- Breakdowns split results into more detailed rows, so the same metric can look different from a summary report.
- Attribution windows should be aligned before two dashboards are compared for conversion performance.
Treat recent numbers with care
Fresh reports are useful for monitoring, but some metrics can keep updating after the first pull.
- Meta's Insights best practices note that Insights refresh often and may continue updating for a couple of days.
- Some reported metrics do not change after 28 days, which matters for late review and audit windows.
- Date presets can be more efficient than custom date ranges when they fit the reporting question.
Use async jobs for heavy reporting
Large exports should be designed so they finish reliably instead of timing out in a single synchronous call.
- Meta recommends trying synchronous calls first, then using async calls when large queries time out.
- Heavy reports can often be split by date, level, fields, or breakdowns to reduce query load.
- Async report jobs should be checked for completion before downstream dashboards use the data.