The busy owner who asks for only a monthly Google Ads report is asking for the format that makes inaction easiest to hide. I get the impulse. You want ads off your plate, not another meeting, dashboard or thread to babysit. But hands-off should mean fewer meetings and a verifiable record, not a prettier PDF.
A monthly report tells you what happened to the numbers. An action log tells you what your manager did about them. If you want an account you do not have to manage yourself, ask for the second one.
Why a monthly report is so easy to make look good
When a prospect told me, “I don’t want to be involved; just send a monthly report,” I relaxed. Every account manager does. That sentence buys 30 days of cover. The industry has standardized around it: many agencies send a full Google Ads report monthly plus a lighter weekly pacing check, leading with spend, conversions and ROAS versus the prior period, then campaign breakdowns.
The format decides what gets inspected. Results get summarized. Work does not get itemized. A typical template opens with an executive summary, shows ROAS and cost per conversion, adds month-over-month growth and recommendations, then skips vanity metrics. None of that requires a verifiable list of changes. No dates. No names. No reasons.
A report can make an account look managed without showing that it was. Spend is totaled. Conversions are charted. A green up-arrow goes next to whatever moved in the right direction. The reader feels informed without learning much they can check. I know because I built dozens of these by hand, and the structure did the spinning for me.
Take “impressions up 14%.” It sounds like growth. It might mean a budget went up, a match type loosened or broad match got more room to spend. None of those changes tells you whether qualified pipeline improved. One complaints playbook for B2B owners cites a WordStream study of 15,666 accounts in which 36 cents of every dollar was wasted and 29% of accounts drove zero conversions in 90 days. Clicks and impressions can rise while pipeline stays flat. The report can still read fine.
Here is what I left out when I built reports: the three weeks when I did nothing except check spend for ten minutes on a Tuesday. The negative keywords I should have added but did not get around to. The ad test that lost. What went in was what photographed well: spend pacing, a conversion chart, two screenshots and a recommendations section.
That last section deserves a warning. Increase budgets on top performers. Expand exact match coverage. Test new responsive search ad variations. All sensible. None done. Recommendations are cheap. Execution is the product. A report that lists ideas instead of completed changes risks making the ideas look like the deliverable.
A PPC oversight guide puts the problem cleanly: the typical retainer ships friendly charts, ongoing-optimization language and raise-budget advice without answering what the manager actually did that month. That is not just bad writing. It is what a summary format allows. Ask for the work, not another description of the work.
Your account already has a record the PDF cannot rewrite
Google’s Change History lists changes to the account, campaigns and ad groups for the past two years. It identifies the user email for interface edits, Google Ads system for automation, and the API or tool name for third-party edits. It also maps changes against impressions, clicks, conversions and cost. Your agency cannot edit that history to make the monthly PDF look better.
Change History is the receipt, not the explanation. Filter it by date, scan who did what and when, then compare it with the report. If a manager says they added negatives, look for the dated changes. If the report celebrates an in-account change you cannot find, ask where it happened. Do not guess from a chart.
Then ask for the missing half: an annotated action log. For each material change, you want the reason, the signal behind it, the expected effect and the result or next check date. Google Ads records the edit; the manager must explain the decision. Put those together and you can inspect the account without sitting through a strategy call narrated from slide 12.
The timing matters too. A managed account can show steady, varied work across weeks: negatives added, bids and budgets adjusted, weak ads paused, copy tested, spend shifted toward what converts. A neglected one can show a setup burst in month one, then silence or little beyond budget increases and Google Ads system entries. That heartbeat-versus-flatline test exposes something a monthly summary can miss. It is a prompt to ask why, not a contest to rack up edits.
Three quiet weeks and one busy night
Open Change History for the reporting period. Is the work spread across the month, with different kinds of changes? Or do you see 21 days of silence followed by a flurry just before the report goes out? A few bid tweaks. An ad paused and unpaused. A budget nudge that gives the chart something to show.
An audit guide for owners names the red flag: if an agency claims active management but the log shows no changes in weeks, something is wrong. I have seen the flurry version too. Say you spend $20k a month. Your manager touches nothing for three weeks while search terms pile up, then adds four negatives, changes two ad headlines and raises the Performance Max budget the night before your call. The PDF calls it “continuous optimization.” The log shows when the work happened. Ask what those changes were meant to fix.

A busy log can hide bad management too
I do not want owners trading one bad shortcut for another. Activity is not quality. If your account is small, stable and well built, weeks can pass with no meaningful change. Leaving it alone may be the right decision. Four hundred entries might be one bulk edit across ad groups. Zero entries might mean the structure is holding.
Change History has another limit: it covers Google Ads, not landing pages, call tracking, CRM plumbing or Local Services settings. Real work can happen off-platform. An honest breakdown of those limits is worth keeping in mind before you accuse someone of doing nothing because you cannot see an edit. Ask them to account for off-platform work separately. Do not accept it as a vague explanation for an empty account log.
As a rough filter, I still use the B2B complaints benchmark: a healthy active account tends to show 30 to 150 changes a month; fewer than 10 is a warning; zero for 60 days demands an explanation. Those counts do not override the account’s circumstances. Below that range, ask for the reasoning. Above it, check whether the entries are varied decisions or one bulk find-and-replace plus automation rows.
The question is not how long the log is. It is whether the decisions make sense against cost per acquisition or pipeline. A manager who chose not to change a stable account should be able to say what they checked and why they held steady. That is accountability, too. What you should not buy is a page of activity presented as proof of good judgment.

Swipe file: ask for the record behind the report
Copy these when the next PDF arrives; you do not need to invent a new reporting process from scratch. The artefact I would insist on is the last one, because it makes the record a deliverable before there is an awkward month to explain.
Request an action log you can check
Use this when a report describes optimization but does not show the work. Send it as written:
Please send this month’s material Google Ads changes as a dated action log. For each change, include who made it, what changed, the account signal behind the decision, the expected effect, and the result or next check date. Please identify which entries I can find in Change History and list any off-platform work separately.
Adjustment that matters: ask for one row per change, not another paragraph of “ongoing optimization.” If you use Google Ads management through anyone, that distinction is the minimum proof behind the summary.
Give them the five fields
Use this when the manager agrees to send a log but asks what you want in it:
- Date + who: [date], [name / email], so you can match the in-account edit in Change History.
- What changed: paused [keyword / ad / audience], added [negatives], moved budget from [campaign] to [campaign].
- Why: [query] spent $[X] with zero conversions, or CPA on [campaign] reached $[Y] against a $[Z] target.
- Expected effect: reduce $[X] a week in waste, or shift spend toward [campaign] at $[CPA].
- Result or next check: CPA moved from $[A] to $[B] by [date], or revisit the change by [date].
Adjustment that matters: require a signal in the “why” field. “Improved performance” is a label, not a reason.
Ask four questions before the call
Use these the morning after the next report lands. They draw on an owner audit checklist; send them before anyone gets to narrate the charts:
- What did you change in my account this month, and why for each change?
- Where can I find each in-account change in Change History, with its date and author?
- What are the top three things blocking CPA or pipeline right now, and what search terms or auctions point to them?
- What is the 60-day improvement plan, and what will you check next to see whether it worked?
Adjustment that matters: if the answer starts with impressions, bring it back to the dated decisions.
Put the weekly log in the agreement
Use this before signing with an agency, freelancer or tool with a service layer. It makes the evidence part of the job rather than a favor you request after the PDF arrives:
Manager will provide a weekly action log listing every material in-account change to bids, budgets, keywords, negatives, audiences, ads and tracking, with date, author, reason tied to a cost or pipeline signal, expected effect, and result or next check date. In-account changes must be identifiable in Google Ads Change History. Material off-platform work will be listed separately. Summary performance charts do not substitute for this log.
Adjustment that matters: keep it weekly, not monthly. This is the artefact I rate most useful because it stops a flat month from hiding for 30 days.
The PDF is not the work
I run accounts now the way I wish my old clients had forced me to run them: actions logged with their reasoning, in plain language, against CPA and pipeline instead of impressions. That is what groas ships as standard: a weekly report of every action and why, plus a dedicated strategist who owns the number. No dashboards to interpret. No junior manager learning on your budget.
Keep the monthly report if you like the charts. Make the log the deliverable. Otherwise, you can keep paying for the same flurry: three quiet weeks, one busy night before the call, impressions up, pipeline flat. The owner who wants Google Ads off their plate does not need hands-off that still needs them. They need hands-off they can verify. I learned that building the reports. You can learn it reading the log.

