Marketing dashboards for agencies: one for you, one for each client
An agency needs two dashboards: a portfolio view that ranks clients by what needs attention, and a client board with three numbers and a target.
On this page
An agency needs two dashboards, not one: a portfolio view for the team that lists every client with the ones needing attention first, and a client dashboard that opens on the three numbers the client pays for, against a target. Most agency dashboards are the second kind stretched to do both, and do neither well.
The pages that rank for this phrase are tool listings and vendor feature pages. This one is about what goes on each board, who should see it, and the access rules that save trouble when a client leaves.
The two boards
| Agency portfolio | Client dashboard | |
|---|---|---|
| Who reads it | Account managers, every morning | The client, whenever they wonder |
| Opens on | Clients sorted worst first | Three numbers against a target |
| Answers | Which client needs us today? | Is the money working? |
| Detail | One line per client, one action | One click to the full dashboard |
| Words | Ours: CPA, ROAS, sync errors | Theirs: leads, booked calls, sales |
The portfolio board
One row per client. The row says what is wrong in words, and the list is sorted so the worst is on top. What belongs on it:
| Signal | Why it is urgent |
|---|---|
| Site down or tracking stopped | Every number after this is wrong until it is fixed |
| Ads spending with no results | Money leaving with nothing to show; often a broken form or goal |
| Results down well outside the usual swing | Something changed; find it before the client does |
| A connection stopped syncing | Spend or sales will be missing from the next report |
| Certificate or domain about to expire | The site goes down on a date you can see coming |
| Cost per result up sharply | Budget is buying less; a fatigued ad or a broken audience |
"Well outside the usual swing" is the important part. A drop of 30 percent means nothing for a client with 20 leads a month and a lot for one with 2,000. Compare each client with its own normal weeks, and leave out clients too small for a change to mean anything.
Leave off the portfolio board anything that is fine. A list of 40 green rows trains the team to stop reading it. Uptime monitoring for agencies covers the site, certificate and domain checks.
The client board
Start from the client's business, not the channels:
| Client type | Three numbers | Target example |
|---|---|---|
| Online store | Revenue, blended ROAS, orders | Blended ROAS above 3.0 |
| Service and lead gen | Qualified leads, cost per lead, booked calls | 120 leads a month under $40 |
| Local business | Calls, form leads, direction requests | 60 calls a month |
| SaaS | Signups, cost per signup, new MRR | $3,000 new MRR a month |
(Example targets.) Under the three numbers, one line of pace says more than a chart: "On pace for 104 of 120 leads; needs 6 a day, getting 5." Then sources in plain words, then the campaigns. Most clients stop reading after the first screen, so the first screen has to be the answer.
Each business type has its own card list: see the lead generation dashboard, the ecommerce dashboard and the SaaS metrics dashboard.
Dashboard or report?
Both, for different jobs. A dashboard is for looking things up at any time; a report is a short story with a recommendation, sent on a schedule. Clients who get only a dashboard often log in once and forget it. Clients who get only a PDF email you for every number. Send the report, and put the live link in it. Client reporting for agencies covers the report.
Access rules that save trouble later
- The client owns the accounts. Ad accounts, analytics and the store belong to the client's business, with the agency added as a partner or user. When the work ends, the client keeps their history and the agency removes itself.
- Read-only by default. Reporting needs read access only. Meta's
ads_readpermission, for example, pulls ad reports; managing ads is a separate permission,ads_management(Meta). - Invites, not shared logins. A shared password cannot be taken back from one person. An invite can.
- A private link is a password. Anyone who has it can see the numbers. Use it for clients who forward reports, and replace it when someone leaves.
- White label only if you mean it. Your logo on the client's board helps; pretending you built the software does not. Say which tools you use if asked.
Common questions
What should an agency client dashboard show?
The three numbers the client pays you for, each against a target with its pace, then sources in plain words and the campaigns behind them. Leave channel metrics such as CTR and CPM for your own board.
How do agencies monitor many clients at once?
With a portfolio view that lists every client sorted by what needs attention: tracking stopped, spend with no results, results well below normal, broken connections. Fine clients drop to the bottom or out of the list.
Should clients get a login or a shared link?
A login by email invite when the numbers are sensitive, because you can revoke one person. A private link when the client wants to forward it. Either should be read-only.
Do clients want dashboards or reports?
Most want a short report on a fixed day, with a dashboard link for when they have a question. A dashboard on its own is easy to forget.
Sources
- Meta for Developers: Permissions reference (ads_read). Checked October 2026.
- The two-board structure is our recommendation from building agency tools. Example targets are made up for illustration.
Spotted something wrong or out of date? Email hello@sporetag.com and we will fix it.