# The Client Reporting Dashboard That Replaces Your Monthly PDF

> How to give Meta Ads clients a live client reporting dashboard instead of a monthly PDF: what to show, what to hide, and whether to reveal spend.

Author: The DashOps Team  |  Published: 2026-09-12  |  Updated: 2026-09-17  |  Topic: Agency & Client Work

Your client emails on the eleventh of the month asking how last month went. You have not sent the report yet. It is half built in a spreadsheet, waiting on a screenshot you meant to grab on Friday. By the time it lands, the campaign it describes has already moved on, and the client has spent weeks with no idea whether their money was working.

That is the real cost of the monthly PDF. Not the time spent building it, though that matters. It is that the report is a photograph of something that has already changed, and it arrives when the client has stopped wondering and started worrying.

A client reporting dashboard fixes the timing problem. Instead of you pushing a document at them on a schedule, they open a link and see where things stand. The question shifts from "how did last month go" to "what should we do next", which is a much better conversation to be having.

![Client Reporting Dashboards Banner](https://pub-ae7c0247bc134935855f21b665422e27.r2.dev/posts/1789654382728-1a5ce385a8ab.png)

## What actually changes when the client can log in

The obvious change is that you stop assembling documents. The less obvious changes matter more.

**The client stops asking you for numbers and starts asking you for judgement.** When they can see spend and results themselves, the emails change character. Fewer "can you send me the figures", more "why did the cost go up in week three". You are being asked to do the thing you are actually good at.

**Bad news arrives early instead of late.** A monthly PDF lets a bad fortnight hide until it is a bad month. With a live client reporting portal, the client sees the dip when it happens, the same moment you saw it. If you are already on it, being visible is an advantage. If you are not, the dashboard has told you something about your process.

**The relationship becomes less about proof and more about progress.** Monthly reports carry a defensive tone: here is the evidence I did work. A dashboard the client can open any day removes that framing.

**You get an honest read on whether they care.** Some clients open the dashboard constantly. Some never open it and still want the summary email. Both are worth knowing, and both should change how you communicate with that client. More on adapting the format to the reader in [how to present Facebook Ads results to clients](/resources/how-to-present-facebook-ads-results-to-clients).

## What to show a client, and what to leave out

The instinct is to give them everything, on the grounds that transparency is good. Resist it. A client staring at an ad-level table with frequency, CPM and unique link clicks is not more informed, they are more anxious. They will fixate on the one metric that moved most, which is usually the one that matters least.

Show a small set of things that map to the outcome they hired you for.

- **The outcome metric.** Leads, purchases, or whatever the campaign exists to produce. Top of the page, biggest number on it.
- **Cost per outcome.** Cost per lead or cost per purchase. The number most clients use, rightly, to decide whether this is working.
- **Spend.** How much has gone out, over the period they are looking at.
- **A trend line.** Outcomes over time, so a good week and a bad week show up as shape rather than one flat average.
- **Campaign-level results.** Which campaigns are running and how each is doing. This is the level where a client can meaningfully have an opinion.

What to leave off the client's view:

- **Ad set and ad level detail by default.** This is your working layer, not theirs. Available if they want to dig, but not what they see first.
- **Frequency, CPM, reach, unique metrics.** All useful to you. To a client they are noise that invites the wrong questions.
- **Anything you cannot explain in one sentence.** If a metric needs a paragraph of context every time, it does not belong on a dashboard they read unsupervised.

The test is simple: if a number appears on the client's screen and they ask what it means, and your honest answer is "it does not really matter", take it off. Every metric on a client-facing reporting dashboard is a metric you have implicitly agreed to defend.

## The spend question

This is the one people get stuck on, so here it is plainly. There are two situations and they call for different answers.

**If the client pays the ad spend directly**, they see it on their card statement anyway. Hiding it in your dashboard creates a gap between two things they can both see, and gaps look like something is being concealed even when nothing is. Show spend. Show cost per result. There is nothing to protect.

**If you buy media on their behalf and bill a bundled fee**, showing raw spend exposes your margin structure, and that is not a conversation you want happening through a dashboard. In that case you can show results and cost per result while keeping the underlying spend figure off their view. DashOps has a per-client setting for exactly this: spend can be hidden from Client users while the outcome metrics stay visible.

Hiding spend is defensible, but it is not permanent. If a client eventually asks and you switch it on, the switch itself becomes the story. Decide early, and say so out loud rather than letting them discover it. "Your dashboard shows results and cost per result, spend is covered in your invoice" is a fine sentence in a kickoff call. It is a bad one in month seven, when they have noticed.

## Setting up the access without creating a mess

A client reporting portal only works if the permissions are right, because the failure mode is severe: one client seeing another's numbers.

In DashOps, a Client user is read-only and is assigned to specific ad accounts. They see those accounts and nothing else. They cannot sync, cannot edit, cannot see your other clients, and cannot see your team's activity. Your Managers are separate, also restricted to the ad accounts you assign them, but with the ability to actually run campaigns.

A sensible setup pattern:

- One Client user per person who needs a view, not a shared login for the whole company. Shared logins mean you do not know who is looking and cannot remove one person's access.
- Assign only the ad accounts that person's business owns. If Acme has two ad accounts and only one is your remit, assign one.
- Decide spend visibility per client when you invite them, not later.
- If you white label the dashboard with your own logo and colours, do it before the first invite.

## Keep the summary, drop the document

A live dashboard does not remove the need to tell clients things. It removes the need to tell them things in a document.

Most clients want a rhythm even when they have access. Something arriving on a Monday saying where we are, what changed, and what I am doing about it. That can be an email digest carrying the headline numbers, with a link into the live view for anyone who wants to dig. The digest does the reminding, the dashboard does the detail. The mechanics are covered in [the Facebook Ads weekly digest](/resources/facebook-ads-weekly-digest).

If a client genuinely needs a document, for a board meeting or a procurement file, generate a PDF from the same data rather than rebuilding it by hand. More on removing that manual step in [how to automate Facebook Ads reports](/resources/how-to-automate-facebook-ads-reports).

## The uncomfortable part

Live access changes what your client can see about your work, and some agencies quietly do not want that. If your value is in the strategy and the optimisation, a dashboard helps you: it removes the part of the job that looked like admin. If your value has drifted into being the person who holds the numbers, the thing to fix is the drift, not the dashboard.

## What to do next

Pick one client. Not your biggest, not your newest, one where the relationship can survive a change in format.

1. Decide what their view shows. Outcome, cost per outcome, spend or no spend, trend, campaign list. Write it down before you configure anything.
2. Set up a Client user for their main contact, assigned to their ad accounts only.
3. Walk them through it once on a call. Show them where the numbers are and tell them what you look at first.
4. Keep sending a short weekly note for a month. The dashboard does not replace communication straight away.
5. Then ask whether the monthly report is still useful. Their answer tells you whether to roll this out to everyone.

What you are aiming for is a client who checks in when they are curious rather than waiting to be told, and an agency that spends its reporting time explaining rather than assembling.

## Frequently asked questions

### What should a client reporting dashboard actually show?

Keep it to five things: the outcome metric the campaign exists to produce (leads or purchases), the cost per outcome, spend, a trend line so good and bad weeks are visible as shape, and campaign-level results. Leave ad set and ad level detail, frequency, CPM and reach off the default view. Those are your working metrics, not theirs. A useful test: if a client asks what a number means and your honest answer is that it does not really matter, take it off the page.

### Should I show clients how much they are spending on ads?

It depends on who pays the platform. If the client's own card is charged, they see the spend anyway, so hiding it in your dashboard creates a gap that looks like concealment. Show it. If you buy media and bill a bundled fee, showing raw spend exposes your margin structure, and you can hide spend while keeping outcome metrics visible. Decide at kickoff, say it out loud, and stay consistent. Switching it on later makes the switch itself the story.

### Will a live dashboard mean my clients stop needing me?

The opposite, in most cases. When clients can see the numbers themselves, the questions change from requests for figures to requests for judgement, which is the work you are actually paid for. The agencies who struggle after moving to live reporting are usually the ones who were relying on the monthly delay to smooth over a quiet fortnight. The delay was never protecting them, it was postponing the conversation.

### How do I stop one client seeing another client's data?

Use per-client read-only access rather than a shared login. In DashOps a Client user is assigned to specific ad accounts and sees only those, with no ability to sync, edit, or view your other clients or your team's activity. Create one Client user per person who needs a view, assign only the ad accounts their business owns, and set spend visibility at the point you invite them rather than afterwards.

### Do I still need to send reports if the client has a dashboard?

You still need a rhythm, just not a document. Most clients want something arriving regularly that says where things stand, what changed, and what you are doing about it. An email digest carrying the headline numbers with a link into the live view covers this without costing you an evening. Keep a generated PDF for the cases that genuinely need a file, such as a board meeting or a procurement record, but generate it from the same data rather than rebuilding it by hand.

---

Full page: https://dashops.io/resources/client-reporting-dashboard-agency