Campaign measurement

Campaign readout QA checklist

Organization byline: Measurement Press editorial desk. This page does not list an individual author or reviewer. Read the editorial method and corrections policy.

About 10 min read

A campaign readout is not just a report. It is a request to believe that the campaign delivered a certain kind of value and that the next budget decision should follow from it.

Use this checklist when a campaign report arrives, before a renewal meeting, or before an attributed result becomes a board slide. It is written for marketers, publishers, agencies, analysts, and operators who need to separate clean delivery evidence from persuasive but unsupported performance language.

Start with the claim

Read the executive summary as a claim, not as a deck. The first job is to identify what the report wants the reader to believe.

Minimum report packet

A readout is easier to trust when the source materials are visible. Ask for the packet before debating the conclusion.

Decision QA checklist

Simulated Worked Example: cap the decision at observed response

This is a Simulated Worked Example, not a campaign result. The figures are fictional and show a repeatable readout calculation. Replace them with an export that includes the campaign's actual event definition, comparison rule, status window, and exclusions.

The defensible sentence is: “The campaign path had a 6.00% qualified-lead rate versus 5.00% in the selected matched comparison, a 1.00-point observed difference.” Do not turn the 20.00% relative difference into “the campaign drove 20% lift” until the assignment or matching rule, balance checks, leakage controls, outcome maturity, and uncertainty are documented. This example therefore supports a focused measurement follow-up, not automatic budget expansion.

Simulated Worked Example: reconcile the readout packet before renewal

This is a Simulated Worked Example, not a campaign result. Score the packet only after checking the export and its definitions. The score measures documentation readiness; it is not a performance or lift metric.

Reproduction: add the five point values: 1 + 0 + 1 + 1 + 1 = 4. Divide by the five required checks: 4 ÷ 5 = 80% packet readiness. Because the missing lookback setting affects how conversions are assigned to the report, the decision is revise before renewal, not “80% campaign success.” Recalculate after attaching the setting; do not average this score with qualified-lead rate, CTR, or lift.

Assumptions and limits: the example treats each check as equally important, assumes the stated matched comparison has already been defined, and does not estimate uncertainty or causal impact. A failed event definition, comparison, or leakage control should remain a hold even if the arithmetic score is high.

Source trail for the readout boundary

The source links below anchor the platform terms used in this checklist. Google Ads attribution reports distinguish attribution reports from campaign-page totals and expose conversion actions, lookback windows, conversion windows, and path information; the page also notes that attribution reports and the Campaigns page can differ by time of event, network coverage, and conversion source. That is why a readout must name the counting and timing rules. Google Ads Experiment Center guidance distinguishes campaign-setting experiments from lift studies: the former compare settings or assets, while the latter use treatment and control groups to estimate impact. A matched or before-and-after report cannot borrow randomized-lift language. Google Analytics event-parameter guidance describes parameters as key-value context that feeds dimensions and metrics; that is why the packet should preserve event names, parameter values, and their reporting definitions rather than only a rolled-up total. These links define platform concepts; they do not validate a campaign's own export, matching rule, data quality, or causal conclusion.

Reader check: if the platform report and the campaign export disagree, preserve both views and document the time basis, conversion source, event parameters, and reconciliation result. Do not resolve the disagreement by choosing the more favorable total. The source documentation explains reporting objects; the campaign record must still establish which rows are complete enough for a decision.

Causal language ladder

The same result can support different language depending on the comparison. Use the strongest wording the design deserves, not the strongest wording the chart can imply.

Slice audit

Breakouts are useful when they explain a decision. They are dangerous when a small, noisy cell becomes the story.

Meeting script

• What decision was this readout supposed to inform before the campaign started?
• Which metric was primary, and was it selected before results were visible?
• What comparison does the report use, and what better comparison was unavailable?
• Which result would survive if attributed conversions were removed from the summary?
• Which slice is useful enough to act on, and which slice is too small or confounded?
• What should be renewed, changed, tested, or stopped based on the actual evidence level?

Pair with

Use this checklist with the campaign reporting worksheet when the readout needs a compact decision note, the campaign reporting sample when the readout needs a shared table structure, the campaign reporting terms glossary when delivery, traffic, lead, matchback, attribution, or lift language needs boundaries, the campaign KPI dictionary to keep metrics in the right lane, the creative and destination troubleshooting matrix when weak response needs a fix, narrow, hold, or retest decision, the campaign issue log and renewal register when weak lanes need owners, due dates, retest rules, and claim boundaries, the campaign renewal memo template when those rows need final renew, revise, retest, or hold language, the campaign renewal evidence archive when final limits need to carry forward, the campaign status-window closeout checklist before delayed lead, matchback, attribution, or survey rows are treated as final, the campaign status-window closeout register when final and preliminary rows need durable export fields, the outcome quality scorecard before reported visits, leads, pipeline, or matched outcomes become claims, the campaign data-layer spec, campaign tagging QA checklist, and creative asset acceptance checklist to preserve the source trail before launch, the private marketplace campaign measurement checklist to plan the readout before launch, the private marketplace readout export sample when the report needs row-level package, placement, device, creative, traffic-quality, and outcome-status fields, the private marketplace renewal scorecard before turning those fields into renewal, creative-change, budget-shift, or lift-test decisions, the incrementality test plan template when the decision needs causal evidence, and the measurement method selector when the report is using the wrong tool for the question.