How should PPC agencies reporting dashboard be set up for clients?

What to take away

The ICO's enforcement action register shows the regulator's appetite for action, and marketing data sits squarely in scope, so treat dashboard access as a data protection decision, not just a design one.
A dashboard is only as good as its definitions. Fix the metric list and the source of truth before anyone builds a view.
Clients need one primary outcome metric per account, with cost and volume metrics as context around it.
Refresh timing should match the decision cycle, not the data availability. Daily data for a monthly decision is noise.
Keep a written audit trail of who changed what, when and why. Dashboards drift quietly.

Start with the decisions the dashboard must support

Begin by listing the decisions your client actually makes each month. A retailer may decide how much to shift into a new product line. A lead-gen client may decide whether a channel deserves more budget. Each decision implies one or two metrics and a comparison period.

Decisions to dashboard metrics

List monthly client decisions
Retailer: shift budget to new product line
Lead-gen: decide if channel deserves more budget
Each decision implies one or two metrics
Add a comparison period
Write down before choosing platform

Write these down before choosing a platform. The tool matters far less than the question it answers. For a wider view of how measurement fits agency work, see the measurement and reporting guide.

Agree the metric set and its definitions

Most disputes about dashboards are disputes about definitions. Agree whether conversions are counted on click, on view, or after a fixed lag window. Agree whether revenue is gross or net of returns. Agree the currency and the timezone.

Agree metric definitions

Conversionson click, on view, or lag window
Revenuegross or net of returns
Currency agreed
Timezone agreed
Publish glossary inside dashboard

Publish the definitions inside the dashboard itself. A short glossary panel removes most of the back-and-forth in the first weeks.

Map data sources and refresh cycles

List every source feeding the dashboard: the ad platforms, the analytics tool, the CRM and any offline conversion file. Note how often each updates and whether it can be queried directly.

Some channels deserve separate treatment. LinkedIn, for instance, sells text ads with their own formats and reporting fields, as described on the LinkedIn Text Ads page.

Refresh cycles should follow the slowest reliable source. If CRM data lags by three days, a live spend figure next to a stale revenue figure misleads.

Which metrics belong on the top row

Put one primary outcome metric first: conversions, revenue, or a qualified lead count. Next to it place cost per outcome and total spend. Everything else belongs below the fold.

How to handle lagging CRM data

Flag the lag visibly. A small note stating that offline conversions update every Tuesday prevents a client reading a partial week as a collapse in performance.

Set access, permissions and an audit trail

Decide who sees which accounts before you share a link. Client-side finance teams rarely need campaign-level detail; account managers rarely need contract values.

Data protection duties apply here too. The ICO's enforcement action register is worth reading before you widen access, because consent and retention questions often surface when reporting touches personal data.

Build a decision table for dashboard scope

Build a decision table

Choose

Single client, one channel, small spend: Platform-native report with a shared view link
Multi-channel account with CRM data: A layered dashboard with a lag note
Client with finance stakeholders: Monthly summary plus a drill-down view
Regulated sector client: Documented definitions and access log
Agency running many small accounts: A template with locked metric definitions

Avoid

Single client, one channel, small spend: A bespoke warehouse build
Multi-channel account with CRM data: Mixing live and lagged figures without a label
Client with finance stakeholders: Giving everyone edit access
Regulated sector client: Anonymous shared logins
Agency running many small accounts: Rebuilding each dashboard by hand

Common questions

How often should a client dashboard refresh?

Match the refresh to the decision cycle. If the client reviews performance monthly, a weekly refresh with a clear data-as-of date is usually enough. Daily refreshes invite reactions to normal variation.

Should the dashboard include competitor or market data?

Only if someone will act on it. Competitor auction insights can explain a shift in cost per click, but they rarely change a budget decision on their own. Keep them in a supporting tab.

What should an agency do when a client disputes a number?

Return to the written definitions. If the definition is missing or ambiguous, fix it in the dashboard and note the change. Repeated disputes about the same metric usually point to a deeper tracking problem, which is covered in the piece on measurement mistakes.

Do agencies need to log dashboard changes?

Yes. A simple change log showing the date, the metric affected and the reason protects both sides. It also makes handovers between account managers far less painful.

Before you sign off on any dashboard build, run a compliance check on the advertisers appearing alongside your client's brand. The ASA's list of non-compliant online advertisers is a useful starting point for due diligence.