← All posts

  • agency
  • outsourcing
  • reporting
  • ad-ops

Reading your agency's ad report: the numbers to check first

The monthly report from your agency arrives and the numbers do not say much, so the unease of having delegated everything stays. The metrics an advertiser should check first, what a report tends not to show, and how to make the substance visible while still delegating, from where we sit building ad-ops tooling.

Reading your agency's ad report: the numbers to check first

Translated from the Japanese original on mureo.jp.

When an agency runs your ads, a report arrives every month. The numbers are lined up, but it is not clear where to look or what to decide. Is that not how plenty of advertisers feel? The money goes out every month, and you cannot verify for yourself whether it is going well. The real source of that unease is not the operations themselves; it is not being able to read the report.

If you assume the reason you cannot read it is your own lack of study, you end up trying to memorize jargon. In most cases, though, it is not a vocabulary problem. The numbers on the page are unreadable because they are not explained in connection with your own business goals. Here we lay out the numbers an advertiser should check first in an agency report, the parts a report tends not to show, and how to make the substance visible while still delegating operations.

The numbers to check first

Report formats differ by agency, but there are not many numbers to look at first. Look at these four, always paired with “how does this stand against the goal?”

Was the amount spent in line with the budget you set? Spend that is too high or too low against budget both need a reason. Not spending it all may signal that delivery is being constrained; going over may mean bidding is running hot. Rather than the amount itself, look at the deviation from the budget you set and whether that deviation has an explanation attached.

How many did you get, and at what cost each? Conversion count, and the cost per conversion (CPA). This is the center of operations. You cannot judge from volume alone or unit cost alone, so always look at the two together. Even if unit cost falls, if volume falls further, the business may have gone backwards.

Is it connecting to revenue and profit downstream? More acquisitions do not grow a business if they are all unprofitable customers. For e-commerce, check ad-driven revenue against cost (ROAS); otherwise, check the quality of inquiries behind the count. When CPA has fallen but revenue has not grown, this is usually what is missing.

How did it move compared with last month? A single month’s numbers do not tell you good from bad. Month over month or year over year, did it go up or down, and is the reason explained? A report where movements have no reasons attached is aggregation, not reporting.

What a report tends not to show

Even with the numbers above laid out, parts remain invisible. This is the substance of the unease of having delegated everything.

Why that allocation? Which campaigns budget was concentrated on, and what was pulled back. The reasoning behind that judgment does not survive in the result numbers. Without the reasoning, you cannot think together about whether next month should follow the same approach, and you are left merely approving the document that arrives.

The substance of search terms and placements Which search terms triggered impressions, and which placements got delivery. Waste accumulates here, yet a summarized report may not show it. Simply asking to see the substance once can turn up spend you could cut.

The change log, and the reasons What changed since last month. The console keeps the fact of a change, but not why it was made. If this is not recorded, the context of operations is severed the moment the operator changes.

Making the substance visible while still delegating

If you cannot read the report, switch agencies, or run it yourself. That is the usual line of thought, but there is a step in between: keep operations delegated, and also pull the same numbers yourself so you can verify from a different angle how they stand against your goals.

Ad platforms let you grant read access to people who are not the operator. Get viewing permission on the console, or pull the numbers from the official API, and you can read the report you receive against your own goals rather than taking it at face value. From there, being able to ask “what is the reason for this allocation?” or “is this search term necessary?” changes the conversation with your agency from a relationship of merely receiving reports.

The mureo tool we build is designed for exactly this “make it visible while still delegating” use. Your agency’s operations stay as they are; mureo pulls the same numbers every day and surfaces how they stand against your goals and where you should ask questions. It works as a way to reach a state where you can talk with evidence, without taking operations back in-house. Delegating operations themselves to AI is covered in Can you automate ad ops with Claude Code?, and designing for consistent quality inside an agency in Why ad ops becomes key-person dependent.

If the fee itself is the burden, there is also the option of revisiting the cost structure. Are ad agency management fees too high? lays out how costs change when you move to a flat rate, in-house, or AI ad ops.

Summary

Not being able to read an agency report is usually caused not by knowledge but by the numbers not being connected to business goals. Amount spent, volume and unit cost, revenue downstream, movement since last month. Look at these four against your goals, and fill in the reasoning and substance the report omits with questions. Keep operations delegated while pulling the numbers yourself, and the unease of having delegated everything turns into something you can verify.