A useful agency report tells the client what changed, whether the evidence is reliable, what the business should do next and who will complete that action. Automated charts and fluent summaries help with preparation. They do not establish that a campaign caused a result or that the recommended decision is sensible.
For an agency owner, reporting is part of delivery. It is where the client sees whether the agency understands the business and follows through on its own recommendations. A report that arrives on time but repeats metrics without resolving their implications can still leave the client uncertain about the value of the relationship.
This guide focuses on recurring performance reports for agencies managing marketing and growth work. The operating design applies to other service reports, but the examples use campaigns, qualified enquiries and sales. All financial examples are synthetic. Platform documentation supports specific measurement constraints; the decision framework is an editorial recommendation, not a claim of guaranteed performance.
Start with the decision the client actually needs
Identify the decisions the reporting cadence can support. A weekly report may support fixing a broken form, reviewing creative fatigue or resolving delayed lead assignment. A monthly report may support budget allocation and landing-page priorities. A quarterly report can consider channel strategy after enough sales outcomes have matured.
Write those decisions beside their required evidence. Increasing a budget needs more than a lower cost per click. It may require qualified lead economics, delivery capacity, conversion lag and agreement on acceptable risk. Replacing a landing page may require a clear diagnosis of its role in the journey rather than a disappointing final sales number alone.
Agree the business definitions first. A lead is a recorded enquiry; a qualified lead meets the client's agreed criteria; a sale is a completed commercial event recorded by the appropriate system. A submitted form, attended consultation and paid invoice should not all carry the same conversion label.
The report can still include channel metrics. Their purpose is to explain the decision. If a metric has no bearing on the problem, remove it from the main narrative or place it in a supporting view. A shorter main report can support deeper reasoning when it links to evidence rather than burying the client in screenshots.
Reconcile spend, retained orders and the limits of the evidence.
Identify which decision the evidence supports and what remains uncertain.
Assign the next test, its owner and the date to review the result.
Read the visual explanation
A practical sequence for this decision. Apply your actual records, responsibilities and acceptance criteria.
Establish a metric contract before connecting dashboards
For each important metric, document its definition, source, time basis, owner and known limitations. This is the metric contract. It prevents a month-end discussion from becoming an argument about why advertising-platform revenue differs from the finance system.
| Metric | Definition to agree | Important boundary |
|---|---|---|
| Media spend | Billed or platform-reported spend for the period | State tax, currency and adjustments |
| Enquiries | Unique valid enquiries under agreed deduplication | Separate spam and repeat requests |
| Qualified leads | Enquiries meeting recorded business criteria | Qualification may lag acquisition |
| Attributed revenue | Revenue credited under a named attribution model | Not necessarily causal incremental revenue |
| Collected revenue | Payments recorded in the agreed finance source | Timing differs from orders or invoices |
| Contribution | Revenue less explicitly included variable costs | Missing costs make it provisional |
Time basis is especially important. A report can describe leads created this month and the eventual sales from those leads, or all sales closed this month regardless of acquisition date. Both are useful. Mixing them can produce a conversion rate whose numerator and denominator refer to different groups.
Choose one reporting timezone and normalize currencies before comparisons. Preserve the original values and exchange-rate method. A change caused by timezone boundaries or conversion rates should not be narrated as a marketing improvement.
Evidence
Reconcile definitions, timing and data quality.
Interpretation
Separate the observation from competing explanations.
Action
Specify a bounded test, owner and review point.
Conceptual guide by Looqus Editorial. Read the surrounding analysis for assumptions, exceptions and primary sources.
Check whether the data is ready to support the claim
Show freshness, completeness and reconciliation status before interpretation. Google Analytics notes that processing can take 24–48 hours and some attribution credit can change after the initial event. A report generated early the next morning should therefore label affected figures as provisional. Google Analytics data freshness
Use simple completeness tests tied to the business: all expected ad accounts present, no missing date partitions, CRM qualification coverage known, revenue records refreshed and major totals reconciled within an agreed tolerance. When a check fails, the report should explain the missing evidence and assign resolution rather than silently substituting a value.
Preserve metric lineage. The account lead should be able to open the source view or export supporting a statement. An assistant can produce a plausible explanation from incomplete inputs, so require material claims to identify the data used and the alternative explanations considered.
Fresh data is not automatically comparable data. Google Analytics allows attribution settings to be changed, which affects how credit is assigned in relevant reports. If a setting or conversion definition changes, annotate the comparison and determine whether the historical series can be compared meaningfully. Google Analytics attribution settings
Reconcile discrepancies before writing a confident story
Suppose the ad platform reports 80 leads, the website records 72 submissions and the CRM contains 66 new records. Do not average those numbers or select the most favorable one. Check duplication rules, date boundaries, failed integrations, tracking gaps and whether each tool measures the same event.
A reconciliation note should state the difference, the likely explanations supported by evidence, the owner investigating and the effect on the recommendation. For example, the agency can still recommend repairing a broken CRM handoff while holding a budget increase that depends on an accurate qualified-lead count.
Use a materiality threshold agreed with the client. A small timing discrepancy may not prevent a low-risk operational action. A large missing-revenue segment can invalidate profitability analysis. The threshold should reflect the decision, not a blanket percentage that makes every dashboard appear healthy.
Never turn a missing cost into zero. If product costs, sales commissions, refunds or fulfilment charges are unavailable, state that contribution is incomplete. Revenue can be reported as revenue while the cost owner resolves the gap. This keeps the client informed without presenting a provisional model as accounting profit.
Turn observations into testable recommendations
A strong recommendation has four parts: the observation, the interpretation, the action and the evidence that would change the decision. “Lead volume fell” is an observation. “A broken form caused the fall” is an interpretation requiring evidence. “Repair the form and verify submissions” is an action with a directly observable completion condition.
Do not write a causal story merely because two lines move together. A campaign change, stock shortage, sales-team absence and seasonal demand can overlap. List the plausible competing explanations that matter, then choose an action proportionate to what is known.
| Evidence situation | Reasonable recommendation | Overreach to avoid |
|---|---|---|
| Form errors confirmed in tests | Repair and verify lead delivery | Claiming all lost sales are recoverable |
| Qualified lead rate lower, coverage complete | Review source and offer fit | Increasing spend because raw CPL is lower |
| Revenue immature for recent leads | Wait for cohort maturation; monitor leading signals | Declaring final return immediately |
| Attribution setting changed | Annotate and establish comparable baseline | Treating the discontinuity as growth |
| Sales follow-up overdue | Resolve ownership and contact backlog | Blaming creative without reviewing handoff |
| Capacity fully booked | Review service capacity before acquisition growth | Buying more demand the client cannot serve |
Client reporting becomes more useful when recommendations include a stop rule. A landing-page experiment might continue only while lead quality remains within an agreed range. A spend increase should have an owner, limit and review date. An AI-written recommendation should never execute a budget change without the authority the client has granted.
Fictional USD example. Monetary assumptions in this guide are illustrative US-dollar amounts, not quoted prices, measured results or exchange-rate conversions. The currency does not imply a US tax or legal setting.
Cost per qualified lead in two synthetic campaign cohorts.
A spends USD 12,000 for 24 qualified leads; B spends USD 10,000 for 32. A has lower raw enquiry cost, USD 100 versus USD 125. No causal conclusion from this comparison.
Compare two campaigns using business outcomes
Consider a synthetic month with two campaigns. Campaign A spends USD 12,000, generates 120 valid enquiries and produces 24 qualified leads. Campaign B spends USD 10,000, generates 80 valid enquiries and produces 32 qualified leads. A has a lower cost per enquiry: USD 100 versus USD 125. B has a lower cost per qualified lead: USD 312.50 versus USD 500.
Assume the cohorts have matured, producing three completed sales from A and four from B. If each sale contributes USD 4,000 before media spend under an agreed cost definition, A produces USD 12,000 before media and USD 0 after it. B produces USD 16,000 before media and USD 6,000 after it. Agency fees and other excluded costs still need consideration.
The sample is small. One additional sale would materially change either result. The reasonable conclusion is that B deserves further investigation under a controlled allocation, not that it is permanently superior or can absorb unlimited budget. Check whether the campaigns serve different markets, whether sales follow-up was comparable and whether more qualified demand can be handled.
If the agency's reporting process costs USD 2,000 for the period, do not claim that the USD 6,000 contribution was generated by the report. It describes the campaign cohort under these assumptions. The report's contribution is a better decision process; any incremental financial effect requires a comparison of what changed because of that decision.
Where appropriate and authorized, offline outcome measurement can connect advertising interactions to later lead events. Google describes enhanced conversions for leads as a method using first-party information to improve measurement. Its availability does not remove the need for proper notices, permissions and data handling. Google Ads enhanced conversions
Known
What the measured evidence directly supports.
Assumed
What is plausible but still needs to be tested.
Missing
What blocks a decision and who will resolve it.
Conceptual guide by Looqus Editorial. Read the surrounding analysis for assumptions, exceptions and primary sources.
Design the report as a working decision record
Lead with a concise statement of the business position, confidence and next decision. Then show the relevant comparison, its explanation and the action register. Supporting tables and source links should be available without dominating the first screen.
A useful action record contains the decision, owner, due date, authority needed, completion evidence and next review date. “Improve landing page” is too broad. “Correct the mobile form error and verify that a test enquiry reaches the assigned CRM owner” is inspectable and can be closed.
Use visuals that answer a question. A cohort table can show why recent leads have incomplete sales outcomes. A bar comparison can show the reversal between cheap enquiries and cheaper qualified leads. A freshness strip can show which source is delayed. Avoid decorative charts with invented precision or unlabeled axes.
Accessibility is part of usability. Put the conclusion in text, label series directly where practical and avoid relying only on red and green. Tables should remain readable on a phone, and the report should not force the client to zoom into a dashboard screenshot to understand a recommendation.
Assign responsibility for missing data and unfinished actions
An agency cannot own a trustworthy report while treating every source failure as the client's homework. Establish source owners and a resolution path. If sales outcomes are missing, the reporting owner should identify the records, contact the authorized client counterpart and track the gap to closure within the agreed scope.
At the same time, keep permissions narrow. Reporting access should not automatically grant campaign editing, payment access or unrestricted CRM export. Client information should remain separated across accounts. The ICO's principles provide a useful reference for minimisation and accountability where UK rules apply; the specific obligations depend on the engagement. ICO data protection principles
Carry open actions into the next report with their current status. If a recommendation was not approved, show it as waiting for a decision. If an action failed, explain the blocker and revised plan. Do not delete difficult items simply because a new reporting period has started.
Require approval before client-facing delivery where that is the engagement's rule. Drafting, reviewing, sending and executing recommendations are separate authorities. A reliable workflow respects those boundaries while actively preparing everything needed for the next authorized step.
Pilot with one account and evaluate reporting usefulness
Start with an account that has a clear commercial objective and accessible source owners. Rebuild one recent report using the metric contract, source checks and action register. Compare it with the prior version: which conclusions change, which remain unsupported and which decisions become clearer?
Run the next cycle with assisted preparation and human ownership of interpretation. Record factual corrections, missing inputs, preparation time and unresolved actions. Expand to other accounts only after the process handles a delayed source, a changed metric definition and an unapproved recommendation correctly.
Measure preparation time alongside error rate, action completion and the share of recommendations that receive a clear decision. Faster reporting is not progress if the client receives more confident mistakes. Equally, a report should not wait indefinitely for perfect data when a qualified operational conclusion is already possible.
This is a poor fit for elaborate automation when the account has little recurring data or needs strategic research more than reporting. It is also premature when nobody can agree what success means. Resolve the decision and metric definitions before connecting more dashboards.
Sources
- Google Analytics: Data freshness
- Google Analytics: Attribution settings
- Google Ads: Enhanced conversions
- ICO: Data protection principles
AI does the work.We own the outcome.
Make the next client report useful for a real decision, with checked evidence, clear recommendations and someone responsible for completing the agreed action.
- Agree the result
- Connect the work
- Own the follow-through