Automate client performance reports

Agency owner / digital marketer managing multiple clients / head of growth · First report per client in ~20 min once data exports are wired; recurring runs take <5 min per client.

GTMEdit flowon X◆ new (unverified) 79

step 1connector

Define client roster and report config

⚡ Meta Marketing API

step 2partial

Pull raw metrics from analytics platforms

google-analytics-automation7 alts

step 3partial

Pull GSC organic search data

google-search-console7 alts

step 4connector

Pull paid and social channel data

⚡ GA4 / analytics

step 5ready

Analyse channel performance and attribution

campaign-analytics4 alts

step 6ready

Generate narrative performance report

performance-report20 alts

step 7connector

Deliver reports to clients

⚡ bring your own tool

Did this recipe work for you?

What you get

▸One branded narrative report per client (what happened / why / what next) covering GA4, GSC, paid, and social
▸Channel attribution breakdown with ROI and funnel conversion metrics
▸Delivered report log (who received what, when) for agency records
▸Reusable client config file that drives every future run with zero re-setup

tools: Supermetrics or Funnel.io ~$99-299/mo (optional aggregator); Composio MCP free tier for GA4 automation; Gmail/Drive via existing Google Workspace MCP (free)

tokens: ~$1-3 per client report at narrative-generation step; batch of 10 clients ~$10-25

≈ $20-50/mo in tokens for a 10-client agency running weekly; aggregator tool adds $100-300/mo if used

What stays yours

· Review each narrative report before sending — the agent drafts, a human approves tone and any client-sensitive framing
· Wire and maintain API credentials per client (GA4 property IDs, Meta ad account tokens) when clients onboard or rotate credentials
· Interpret anomalies that require business context the agent lacks (e.g., a traffic spike from a PR mention vs. a tracking bug)

The problem

When I send weekly/monthly performance reports across many clients, I want to auto-pull GA4/Meta/GSC/social data and have it written into a branded narrative summary and delivered on schedule, so I stop losing every Monday to spreadsheets and screenshots.

Cybernetic layers

Memorypartial

Client config list acts as external memory for roster and property IDs. Prior-period baselines (for WoW/MoM delta) must be retained in a Google Sheet or local CSV between runs — no harvested memory artifact covers multi-client metric history. This is the main supply gap.

Background-schedulingbyo

Recurring Monday/month-start runs need a cron trigger. Claude Code background tasks or a simple GitHub Actions / cron job invoking the harness covers this. No library artifact handles scheduled multi-client batch dispatch yet.

Harnessready

Claude Code is the runtime. Install skills 4085, 345, 386, and 255 into ~/.claude/skills/ and invoke sequentially per client row. Cowork also works for team-shared runs.

Click any step to see what fills it — and the ranked alternatives you can swap in.