Use case · marketing agencies
Where the monthly client report comes from.
Every agency builds this report the same way. Someone opens the ad platforms on the last Friday of the month and copies numbers into a deck, then writes the paragraph explaining what happened. The numbers are mechanical. The paragraph is the part clients actually read, so it tends to get written last and fastest.
- Company
- A performance marketing agency
- Team
- 19 people, 14 retained clients
- Region
- US
- Stack
- Google Ads, Meta Ads, Google Analytics, Slack
How the droid took it on.
Rather than build the report and hope someone spots the odd campaign, the agency handed the whole cycle over. On the 1st the droid reads every client’s accounts, compares the month against the one before, and writes the draft with anything that went wrong sitting at the top.
- Schedule
- 1st of each month, 06:00 local
- Scope
- One run per client account
- Reads
- Google Ads, Meta Ads, Google Analytics
- Writes
- Report doc + draft email to the account manager
- Escalates
- Broken connections, and any client with no spend at all
Set up by asking for it in a sentence, then narrowed once the first month came back too long.
Every client trips the same loop:
- 011st of the monthScheduled task wakes
- 02Pull two monthsAds, Meta, Analytics — by campaign
- 03CompareMonth over month, per campaign
- 04Anything gone wrong?Yes → top of the report
- 05Write the draftAgency's structure and tone
- 06Hand to the AMDraft only, never sent
How it ran, client after client.
One reporting morning as it unfolded. Fourteen clients, nine flags, and one account the droid refused to write up because the Meta connection had expired.
Pulled June and May for the first client. Nothing tripped a rule, so the draft went over as-is.
Search campaign held spend at $4,180 while conversions dropped from 61 to 19. Put it at the top of the report with both months side by side.
Meta token had expired, so rather than write the month up from Ads alone it stopped and asked for a reconnect.
Fourteen drafts waiting, nine flags across six clients, one account blocked on a reconnect.
It found a campaign we'd been quietly funding for six weeks after it stopped converting. Nobody had looked because the totals still looked fine.
What changed, by the numbers.
An illustrative workflow built from real product mechanics. The connected apps, the schedule and the flagging rules are how a droid actually runs; the agency, the quote and the figures are composites rather than a customer's numbers.
Run this workflow yourself.
Copy the brief below and paste it into Unify. It’ll walk you through the prerequisites, connect what it needs, and stand the workflow up with you.
We're a marketing agency and we send every client a performance report at the start of the month. Connect the client's Google Ads, Meta Ads and Google Analytics. Schedule a task for the 1st of each month. On each run, pull last month and the month before it — spend, impressions, clicks, conversions, cost per conversion, and revenue where it's tracked — broken down by campaign, and compare the two. Flag any campaign where spend held steady or rose while conversions fell by more than a third, any campaign where cost per conversion moved more than 40%, and anything that spent over $200 and converted nothing. Write it up as what happened, then why, then what we'd change, with the flagged campaigns at the top. Give me a doc and a draft email addressed to me, not to the client. Don't send anything to anyone.
Other jobs handed over
All use cases →What would you take off your desk?
Tell us the job that never gets done before close. We'll wire it up on a call and you can watch it work.