Agency client reporting: what to include and how to explain what changed

What should an agency client report include?

A useful agency client report answers four questions in order: how did we do against the goal, what changed, why did the numbers move, and what happens next. Everything else is an appendix.

Most reports get the first question right and skip the other three. The client sees a table of clicks, conversions and cost, but not the budget increase on day 9 or the form change on day 17 that explains the curve. Use a fixed structure so every report, for every client, reads the same way:

Keep the metric definitions stable. If last month's report counted leads from the CRM and this month's counts form submissions from GA4, the client will compare numbers that don't measure the same thing.

Why do clients stop reading marketing reports?

Clients stop reading reports that show numbers without reasons. A 20-page export of every metric tells the client you have data, not that you understand it.

The usual problems are easy to spot:

• No narrative. Charts go up and down with no sentence saying why.
• Platform metrics instead of business metrics. CTR and impression share matter to the media buyer; the client cares about leads, sales, cost per acquisition and revenue.
• Missing context. A sale, a price change, a site release or a tracking fix happened in the period and isn't mentioned.
• Changes reported vaguely. "Optimised bidding" says nothing. "Moved Search campaign to Target CPA €45 on 12 March, previously Maximise conversions" can be checked.

The fix is not more pages. It is one short section that lists what changed and one that links those changes to the results.

How do I write the "what changed and why" section?

List every change in the period with date, channel, before and after values, who made it and why, then group them so the client can scan them in a minute. This section is what turns a dashboard into a report.

1. Count first. "27 changes this month: 14 in Google Ads, 8 in Meta Ads, 5 on the site and tracking." The count alone shows how active the account was.
2. Group by kind. Investment (budgets, bids), campaigns, creatives and audiences, tracking and site, CRM and product, account incidents.
3. Show before → after. "Daily budget €80 → €120", not "budget increased".
4. Add owner and reason. Agency, client team, developer, or the platform itself (auto-applied recommendations, automated rules).
5. Flag the few that matter. Highlight the 3–5 changes that line up with a visible move in the KPI table.

Example (illustrative): "On 9 September we raised the Search budget from €80 to €120 a day; on 17 September the client's developer removed the phone field from the form. Leads rose 18% while cost per lead stayed flat, and form completion rate rose after the 17th."

Building this list by hand from memory, chat threads and platform histories is slow, and something is always missing. Our post on the marketing change report walks through the format in detail, and the marketing change log template gives you the columns to collect it all month. In Changeline, the Report button builds this section for any period as a two-page PDF from the changes logged or imported in a project, so you can generate a change report for a client in a few clicks.

How do I find which change caused a shift before the report goes out?

Put every change from the days before the shift on one timeline, rule out tracking first, then test one hypothesis at a time. Don't send a cause to the client until you can point at the date it started.

1. Date the shift. Find the first day the metric left its normal range, not the day someone noticed.
2. Collect every change from the 7–14 days before. Your team's edits, platform automations, site releases, tag and consent changes, CRM or pricing changes, and external events such as holidays or a competitor sale.
3. Rule out tracking. Check whether the conversion tag, consent setup or GA4 configuration changed. If conversions dropped but orders in the back office didn't, it's measurement, not demand.
4. Test one hypothesis at a time. Segment by campaign, device, country or landing page. A change that explains the shift should match its timing and its scope.
5. Write down the confidence level. "Confirmed", "likely" or "unclear" in the report is more honest than a confident guess.

The sources for that timeline are scattered. Google Ads change history shows changes from the past two years and who made them; the Google Ads API change_event resource covers only the past 30 days. GA4 annotations let users with the Analyst role or above mark dates on line charts, with up to 1,000 per property. See the Google Ads change history guide and the GA4 annotations guide for the details, and our root cause analysis method for the full process.

If you use Changeline, Google Ads edits can be imported into the project timeline automatically (with before → after values and the source of each change), and the team logs the rest: site, tracking, CRM and Meta Ads changes.

Which tools can automate agency client reporting?

Dashboards and scheduled exports can automate the numbers; the explanation of what changed still needs a record your team keeps. Use each tool for what it does well:

Looker Studio emails include a preview of the first page and a link to the full report, according to Google's documentation. Google Ads scheduling is covered in Create and manage reports. Automate the numbers, then spend the saved time on the summary and the cause analysis.

How do I present bad results in a client report?

Lead with the number, then the cause, then the fix. Clients accept a bad month far more easily than a surprise or a vague explanation.

• Say it in the first line. "Leads fell 22% vs August, below the 300 target."
• Give the dated cause and your confidence. "Likely cause: the checkout update released on 3 September, which coincides with the drop on mobile only."
• Separate what you controlled from what you didn't. Your bid change is yours; a client site release or a seasonal dip is context.
• End with actions and dates. "Rolled back the bid strategy on 20 September; reviewing results on 4 October."

The guide to explaining a conversion drop to a client has scripts and an email template for this conversation.

What should you check before sending a client report?

Run the same short checklist before every report goes out. It takes ten minutes and catches most of the errors clients notice.

1. Date range matches the agreed period and the comparison period is stated.
2. Metric definitions are the same as last report (source, attribution model, conversion actions included).
3. Every large move in the KPI table has a sentence explaining it, or says "cause unclear, investigating".
4. The change list includes client-side changes (site, prices, offers, CRM), not only the agency's work.
5. Next steps have an owner and a date.
6. The summary can be read in under a minute without the rest of the report.

Keeping a marketing change log all month makes steps 3 and 4 a lookup instead of an investigation.