How to automate client reporting in an agency

Agency reporting is the same problem repeated: assemble numbers from several platforms, put them in a consistent format, and deliver them on a schedule. The repetition makes it an obvious candidate for automation, and the per-client variation is what makes it harder than it looks.

Each client has different platforms connected, different metrics that matter, a different definition of a conversion, and a different tolerance for detail. A template that ignores that produces twenty identical reports of which eighteen are partly irrelevant.

What we'll cover

• What actually varies between clients
• Access, which is the real blocker
• Templating with per-client configuration
• Building it with CodeWords
• Definitions, and why numbers disagree
• The report nobody reads
• Onboarding a new client
• What automation frees the team to do
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

What actually varies between clients

Which platforms are connected, so a template assuming five sources breaks for the client with three.

Which metrics matter. A lead generation client and an ecommerce client care about entirely different things, and a combined template serves neither.

The definition of a conversion, which is configured per client and frequently differs from what they think it is.

Reporting period. Calendar month, four-week cycle, or aligned to their financial year — and getting it wrong is immediately noticed.

Branding and delivery. Some want a document, some want a link, some want it in an email body.

Tolerance for detail. One client reads everything; another wants three numbers and a sentence.

Build for the variation deliberately, in configuration rather than in twenty copies of a template, because twenty copies diverge within a quarter.

Access, which is the real blocker

The unglamorous part where these projects actually stall.

Every platform needs access granted by the client, and each has its own permission model.

Access is granted to a person, frequently, which breaks when that person leaves your agency or theirs.

Ask for agency-level access where the platform supports it, rather than an individual login, since that survives staff changes.

Never share credentials. A client's password in your password manager is a liability for both parties and is usually against the platform's terms.

Track what you have and what expires, per client, because a revoked access token is discovered when a report is due.

Make it part of the contract. Access needed, granted at what level, and who maintains it, agreed at the start rather than negotiated during the first reporting cycle.

Templating with per-client configuration

One template, per-client configuration — not a template per client.

Configuration holds which sources are connected, which metrics to include, the period, the branding, and the delivery method.

Sections should be conditional, appearing only when the client has that source, rather than showing an empty panel.

Keep the configuration where an account manager can edit it, since they are the person who knows the client changed something.

Version the template, so an improvement reaches everybody and you can tell which clients have had it.

Report clients whose configuration is incomplete, which is how you find the one whose reporting has been quietly missing a channel for two months.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, which covers the platforms agencies typically report on, with connections made once per client and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which client, which sources, which period, and where it is delivered.
3. Authorize the connections per client, with read-only access wherever the automation only reports.
4. Describe the exceptions: a source that is unavailable, a metric with no data, a figure outside a plausible range.
5. Run it for one client against a month they already have a report for, and compare.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Definitions, and why numbers disagree

The conversation that consumes the most time and is entirely preventable.

Platforms count differently. Attribution windows, view-through, and what counts as a session all vary, so two sources reporting the same campaign will not match.

Your report and the client's own dashboard will disagree, and they will notice.

State the source of every number, in the report, so a discrepancy leads to an explanation rather than an accusation.

Agree the definitions once, at onboarding, and write them into the report as a standing note.

Do not reconcile silently. Adjusting a figure to match another source without saying so is how a small discrepancy becomes a trust problem.

Keep the methodology stable. A changed calculation looks like a changed result, and explaining that is harder than never changing it mid-engagement.

The report nobody reads

Worth confronting, since automated reporting makes it easy to produce reports at volume.

A monthly document of forty charts is not read. It is filed, and its existence is mistaken for communication.

Lead with what changed and what you did about it, in a few sentences, with the detail below for anybody who wants it.

Say what you will do next. A report with no recommendation is a record rather than a service.

Track whether it is opened, where delivery allows, since that is the honest measure of whether it is working.

Ask clients what they actually use, annually, and remove the rest. Most will name three numbers.

A shorter report that gets read is worth more than a comprehensive one that does not, and automation makes producing the comprehensive one so easy that nobody questions it.

Onboarding a new client

Where the per-client setup cost concentrates, and where automation pays off fastest.

A checklist of access needed, sent at signature rather than at the first reporting cycle.

Provision from a template — configuration, folder, delivery schedule — so a new client is set up the same way each time.

Verify each connection by pulling data immediately rather than waiting for the first report to fail.

Agree definitions and the reporting period in the same conversation as access, since both are cheaper to settle before anybody has expectations.

Produce a first report early, even a partial one, because it surfaces disagreements while they are small.

Record who at the client receives it, and revisit it, since recipients change and reports continue to somebody who left.

What automation frees the team to do

Worth being clear about, since agency reporting automation is frequently sold internally as a cost saving and that framing undersells it.

The assembly was never the value. Nobody retains an agency because its reports are well formatted.

The analysis is the value, and it is what gets squeezed when somebody spends two days a month collecting numbers.

Report preparation time is the metric to watch, not report volume, and the point is for it to approach zero.

Use the freed time on fewer, better recommendations, which is what clients actually notice and what renewals depend on.

Automation also makes more frequent reporting possible, which is not automatically good — a weekly report on metrics that move monthly invites reactions to noise.

Resist reporting more just because you can. The same discipline that applies to any automated output applies here: the cost of producing it fell, the cost of reading it did not.

Making it survive

Handle the unavailable source by reporting the gap rather than omitting the section silently, which otherwise looks like a channel that produced nothing.

Check magnitudes before sending. A figure that has changed tenfold is more likely an integration problem than a result.

Never send automatically without a check for a client-facing report — a short review step catches the ones that would damage a relationship.

Track access expiry per client, ahead of the report date.

Report the outcome. Reports produced, sources that failed, clients whose configuration is incomplete, and anything held for review.

Limits worth knowing about

Platform rate limits apply per account, and running twenty clients' reports simultaneously will hit them.

Data availability lags differently per platform, so a report run on the first of the month may have incomplete figures for some sources.

Attribution across platforms cannot be reconciled, only explained, and promising otherwise creates a recurring argument.

Client data is the client's, and your obligations for holding and processing it should be in the contract rather than assumed.

Access removal at the end of an engagement is a step to build deliberately, since a departed client's data still flowing is a problem for both of you.

What to build first

One template with per-client configuration, for your most common client shape, delivering a short summary with the detail below. Do not start with the client who has the most unusual setup — start with the shape you have most of, since that is where the repetition is and the unusual ones will need attention regardless.

Two habits make the difference. State the source of every number in the report, since almost every reporting dispute is a definitional one and naming the source turns an accusation into an explanation. And keep a short review step before sending, because a client-facing report sent automatically with an integration-broken figure costs more than the minute it saves.

Frequently asked questions

What varies most between clients?

Which platforms are connected, which metrics matter, how a conversion is defined, the reporting period, and how much detail they want. Build for that in configuration rather than in a copy of the template per client.

Where do these projects usually stall?

Access. Every platform needs permission granted by the client, each has its own model, and access granted to an individual breaks when somebody leaves. Agree it in the contract rather than during the first reporting cycle.

Why does our report disagree with the client's dashboard?

Different attribution windows, different session definitions, and different counting rules. State the source of every number so a discrepancy leads to an explanation, and agree definitions at onboarding.

Should reports send automatically?

Produce automatically, send after a short check. A client-facing report with an integration-broken figure costs far more than the minute the review takes.

How long should a client report be?

Shorter than it is. Lead with what changed, what you did, and what happens next; put the detail below. Ask clients annually what they actually use — most will name three numbers.

How do I handle a source that failed?

Report the gap explicitly. Omitting the section silently looks like a channel that produced nothing, which is a considerably worse misunderstanding than a missing panel with an explanation.

What should happen when an engagement ends?

Remove access deliberately, as a step in the offboarding. A departed client's data still flowing into your systems is a problem for both parties and it persists until somebody notices.

What is the real benefit of automating agency reporting?

Not the saved hours in themselves — it is that analysis stops being squeezed by assembly. Nobody retains an agency for well-formatted reports, and the recommendations are what renewals depend on.

Should we report more often now that it is cheap?

Rarely. The cost of producing a report fell; the cost of reading one did not. A weekly report on metrics that move monthly invites reactions to noise, which is a service disbenefit rather than a benefit.

Related reading

• Automating report generation
• Google Analytics and CodeWords
• Connecting BigQuery to Google Sheets