Ads Manager is good at telling you what Meta thinks happened. Your client is good at asking whether money actually landed. Those are related questions. They are not the same question.
This guide is for agency operators who want cleaner Facebook Ads reporting for themselves and for client conversations. Useful even if you never touch another tool. We will walk through what the report shows, which columns matter when you are reporting out, the mistakes that create awkward QBRs, a practical checklist, and a clearly labeled sample so you can see the shape of a weekly read.
What Facebook Ads reporting shows
When people say Facebook Ads reporting, they usually mean the tables inside Meta Ads Manager (and the Meta Ads reporting views that sit on top of the same data).
At a practical level, you are looking at a time range, a breakdown (campaign, ad set, ad, or delivery dimensions), and a set of columns. Meta credits results based on its own attribution settings for that account. The report answers: given that window and those rules, what did Meta count?
Common columns you will see:
- Results: the conversion or event you optimized for (Purchases, Leads, and so on), as Meta attributed them
- Amount spent: what you paid Meta in the selected dates
- Cost per result: spend divided by those attributed results
- Purchase ROAS (or similar ROAS columns): attributed purchase value divided by spend, when you have purchase value events set up
- Reach and Impressions: how many people saw the ads, and how many times
- Clicks, CTR, CPC: traffic and efficiency signals inside the account
- Frequency: average times people saw the ads in the period
Those numbers are real inside Meta's system. They help you kill weak creatives, protect budgets, and spot delivery issues before a client asks.
What they are not: a bank statement. Meta is scoring contribution under its rules. Your client's payment processor is scoring settled revenue. When those disagree, both can be "right" for different jobs.
Columns that matter when you report to clients
Agencies do not need every custom column Meta offers. You need a small set you can defend in plain language.
For the weekly client update
- 1Amount spent: always. Spend without context is how screenshots start fights.
- 2Results (the event you agreed to optimize): purchases, trials, booked demos, whatever the retainer defines.
- 3Cost per result: so the client sees efficiency, not only volume.
- 4Purchase value / Purchase ROAS: when the account has purchase value wired. Say which attribution setting the column uses.
- 5Reach + frequency: short note if creative fatigue or overspend on the same audience is a risk.
For the monthly or QBR slide
Keep the same core, then add:
- Trend vs prior period (same windows, same columns)
- Which campaigns drove most attributed results
- What you changed (budget, creative, audiences) and what you will try next
- One line on limitations: attribution window, view-through vs click-through, and that platform revenue can sit above payment revenue when journeys overlap
If a column needs a paragraph of caveats before a non-media client understands it, leave it off the client deck. Keep it in your internal view.
Common Facebook Ads reporting mistakes
These show up in agency Slack more than any feature request.
1. Attribution window confusion (Meta UI education)
Ads Manager lets you change attribution settings (for example click window and engaged-view / view-through options, depending on what Meta shows for that account). Change the window, and Results, Cost per result, and Purchase ROAS move.
That is expected. You did not "break" the account. You changed the rulebook Meta uses to credit events.
Mistake: exporting one week with a 7-day click window, comparing it to last month's deck that used a different setting, then arguing about which creative "won." Fix: pick a default for client reporting, write it on the slide, and only change it on purpose with a note.
This section is about reading Meta's UI honestly. It is not a claim about multi-touch models or any product's attribution engine.
2. Treating Facebook Ads reporting as the only revenue number
Platform Purchase ROAS is useful for in-account decisions. It is a weaker defense when the client opens Stripe (or another processor) and asks what cleared.
If Meta looks strong and the processor looks quieter, do not panic-rewrite history in Ads Manager. Explain the jobs: Meta credits contribution; payments record settlement.
3. Summing Facebook with other platforms later
You will be tempted, especially in a blended deck, to add Meta claimed revenue to Google claimed revenue. That invents money when the same sale sits in both reports. We cover that pattern in our Meta and Google double-count guide. For this page, the short rule is: do not treat summed platform claims as payment truth.
4. Screenshots without spend context
A Results spike with no Amount spent, no date range, and no attribution note is how retainers get tense. Always pair results with spend and the window.
5. Custom columns chaos
Every media buyer loves a personal column set. Fine for internal work. For client-facing Facebook Ads reporting, standardize. One shared template per account type beats five "my export" variants that disagree on ROAS definitions.
Practical checklist (agency weekly read)
Use this as a light routine, not a 40-tab ritual.
- Confirm date range (account timezone) matches what you will say in Slack or the deck
- Confirm attribution settings match last week's client report (or note the change)
- Export or screenshot: Amount spent, Results, Cost per result, Purchase ROAS / purchase value if relevant, Reach, Frequency
- Flag anything odd: spend with near-zero results, sudden frequency jumps, learning-limited delivery, broken pixels/events (as Meta shows them)
- Write one sentence: what worked, what you changed, what you will watch next
- Before you send: ask whether any revenue line needs payment context, not only Ads Manager
Sample weekly read (clearly labeled example)
Sample only. Invented for teaching. Not an industry average, not a Thexly customer story, not a benchmark.
| Line | Sample figure |
|---|---|
| Date range | Mon–Sun (account TZ) |
| Attribution note on slide | 7-day click (account default for client reports) |
| Amount spent | $4,200 |
| Purchases (Results) | 38 |
| Cost per purchase | $110.53 |
| Purchase ROAS (Ads Manager) | 2.4 |
| Reach | 61,000 |
| Frequency | 2.1 |
How you might narrate it to a client:
We spent $4,200. Meta attributed 38 purchases at about $111 each, with Purchase ROAS 2.4 under our usual 7-day click setting. Reach and frequency look steady. Next week we are rotating the two weakest ads and holding budget until those finish learning.
If that client's payment dashboard shows fewer settled purchases or lower revenue for the same calendar week, you already know why the conversation might come up. Platform credit and payment settlement are different lenses. For multi-client agencies, that gap is exactly why a payment-aware reporting layer exists beside Ads Manager. Soft pointer: Thexly for agencies is built around comparing platform-reported revenue to payment revenue across clients, without asking you to throw away Facebook Ads reporting.
When Facebook Ads reporting is not enough
Stay in Ads Manager when you are optimizing creatives, budgets, and delivery inside Meta.
Widen the view when:
- The client asks "how much money did we make?" and you only have Purchase ROAS from Meta
- You also run Google (or other channels) and someone wants one revenue story for the program
- QBRs keep turning into screenshot wars between Ads Manager and the processor
- You manage several clients and every Friday is a different export ritual
Facebook Ads reporting still belongs in the stack. The gap is usually "platform report versus payment reality," especially across a multi-client book. That is the job Thexly for agencies is aimed at: payment-verified ROAS reporting and multi-client dashboards that sit next to platform numbers. We do not claim Thexly replaces Ads Manager. You still need Meta's UI to buy media well.
If you want the cross-channel version of the revenue math, read blended ROAS and MER vs platform ROAS next. If the pain is Meta and Google both claiming one sale, start with why both platforms claim the same sale.
Further reading
- Why Meta and Google both claim the same sale: never-sum rule and what to show the client
- Blended ROAS and MER vs platform ROAS: which efficiency number answers which question
Wrap-up
Facebook Ads reporting is how you steer Meta. Learn the columns, lock your attribution note, stop sending context-free screenshots, and keep platform ROAS in the optimization seat.
When the client asks what cleared, bring payment truth into the conversation. Your Ads Manager export can still be excellent at its job.
What does your agency put on the weekly Facebook Ads reporting slide today, and what do you wish you could leave off?