Campaign reporting
Campaign renewal memo template
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 renewal memo is the bridge between a campaign readout and the next media decision. It should say what worked, what is unresolved, what changes before the next flight, and which claims the evidence can support.
Use this template after the campaign readout QA pass, renewal scorecard, and issue register. It is built for contextual display, sponsorship, and private marketplace packages where the next step may be renewal, narrower scope, creative or destination repair, a designed test, or a hold decision.
Memo or archive?
These records work together but answer different questions. Write the memo while the next action is being decided; write the archive after the decision is closed so a later team can see what was included, excluded, and still unresolved.
| Record | Reader question | Minimum useful output | Failure if skipped |
|---|---|---|---|
| Renewal memo | What should we do next? | Action, scope, evidence basis, allowed claim, owner, and due date. | A report becomes a vague continue or scale recommendation. |
| Evidence archive | What must the next team preserve? | Final decision, included and excluded rows, issue states, claim boundary, and next-test gate. | A later brief silently reuses excluded or immature rows. |
| Issue register | What remains open? | Issue ID, owner, closeout state, proof source, review date, and decision effect. | Conditions become caveats with no closeout path. |
Page boundaryUse this page when a decision owner needs an actionable renew, revise, retest, or hold recommendation. Move the accepted decision, excluded rows, unresolved issue states, and next-test gate into the evidence archive after approval; do not use the memo as the durable row-level record.
Choose the record by decision stage
The memo is the action document, not a second archive or a replacement for row-level closeout. Keeping the stages separate prevents a polished recommendation from losing the exclusions and maturity rules that limit what the evidence means.
| If the reader needs to... | Use this record | Carry forward |
|---|---|---|
| Approve, narrow, repair, retest, or hold the next flight | Renewal memo | Decision scope, evidence rows, allowed and unavailable claims, owner, and due date. |
| Reopen the decision after the flight or hand it to another team | Evidence archive | Included and excluded rows, issue states, comparison limits, and the gate for stronger evidence. |
| Decide whether delayed, missing, or unresolved rows are ready for final wording | Closeout register | Window definition, maturity threshold, exclusions, closeout state, and the final allowed sentence. |
Memo decision header
The first block should make the decision visible before charts, anecdotes, or caveats pull the reader into a weaker interpretation.
| Field | What to write | Do not write |
|---|---|---|
| Decision requested | Renew same package, renew narrower package, revise creative, repair destination, retest, add lift test, or hold. | A vague recommendation such as continue, scale, or optimize without scope. |
| Evidence basis | The package, placement, creative, device, date, traffic-quality, outcome-status, and comparison rows used for the decision. | A total campaign result when important rows were pooled, missing, or unresolved. |
| Decision boundary | The strongest action the evidence can support now and the action that requires stronger evidence later. | A broad causal claim based on descriptive delivery or attributed response. |
| Owner and due date | The person or team responsible for each condition before launch, readout, or retest. | A passive caveat with no owner, date, or closeout rule. |
One-page memo structure
Keep the memo short enough to read before a renewal meeting. The goal is not to repeat the report; it is to convert the report into a bounded next action.
1. Recommendation
Name the action, scope, timing, and condition. Example: renew the verified placement set for one flight after mobile destination repairs are complete.
2. Evidence used
List the rows that support the decision: package ID, placement IDs, creative IDs, device scope, date range, quality flags, and outcome status.
3. Evidence excluded
Name pooled, incomplete, off-scope, low-volume, or unresolved rows that should not define the renewal claim.
4. Issue closeout
Summarize the open issue register rows, owners, due dates, retest rules, and whether each row is fixed, excluded, conditional, or still blocking.
5. Claim language
Write the exact sentence allowed in the renewal, and the stronger sentence that remains unavailable until a better comparison exists.
6. Next evidence
Define what the next flight must preserve: fields, thresholds, baseline, holdout, outcome status, page state, and readout date.
Decision language matrix
The memo should use different language for renewal, repair, retest, and hold decisions. A useful campaign can still need cautious wording.
| Memo decision | Use when | Supportable wording | Next evidence |
|---|---|---|---|
| Renew same scope | Delivery matched the package, quality fields are complete, the response supports the stated goal, and unresolved issues are low risk. | The package produced strong observed response under the reported scope and quality controls. | Preserve field completeness and add a designed comparison if lift language is needed. |
| Renew narrower scope | Some placements, devices, dates, or creative rows are decision-grade while others are pooled, weak, or incomplete. | The verified scope supports renewal; excluded rows should not define the package claim. | Separate rows before launch and report scoped results independently. |
| Revise before scale | Context fit was plausible, but creative promise, destination speed, form behavior, or routing limited response quality. | The result supports a repair-and-retest decision, not a broad media-context conclusion. | Document creative, page, form, and routing fixes before the next flight. |
| Retest before renewal | Response is directional but small, uneven, confounded, or missing outcome status. | The result is a hypothesis for a cleaner next test. | Name minimum cells, status coverage, baseline choice, and retest window. |
| Add causal test | The business decision needs lift, but the current readout is descriptive, attributed, or prior-period only. | The campaign produced observed response; incremental impact remains unproven. | Reserve a holdout, matched market, or preplanned comparison before lift wording. |
| Hold or rebrief | The package missed scope, fields are missing, destination fit is broken, or the recommendation would outrun the evidence. | The readout does not support renewal beyond operational learning. | Rebuild the brief, package proof, field contract, or destination before buying again. |
Fill-in memo template
Replace the bracketed values with the campaign record. Keep the verbs modest unless the comparison design supports stronger language.
Renewal memoDecision: [renew same scope / renew narrower scope / revise / retest / add causal test / hold]. Scope: [package ID, placement IDs, creative IDs, devices, dates, and excluded rows]. Evidence basis: [delivery quality, exposure quality, traffic quality, outcome status, and comparison rule]. Open conditions: [issue IDs, owners, due dates, retest rules, and closeout states]. Allowed claim: [observed response sentence that matches the evidence]. Unavailable claim: [lift, broad scale, winner, or audience-quality sentence that needs stronger evidence]. Next step: [renew, fix, retest, holdout, matched comparison, or rebrief action with date].
Worked memo excerpt
This example uses anonymous package language and example structure only. It does not describe a real advertiser, publisher, platform, or campaign.
Example wordingDecision: renew a narrower contextual package for one flight. Scope: keep the verified measurement-desk placements and desktop and tablet rows; exclude pooled lower-volume placements and mobile rows until page fixes are complete. Evidence basis: delivery matched the scoped package, exposure quality was complete for verified placements, qualified visits were strongest in the verified rows, and lead status was complete enough for directional outcome language. Open conditions: mobile destination speed and lead-routing status remain conditions for the next launch. Allowed claim: the verified package produced useful observed response for readers in the intended context. Unavailable claim: the campaign proved incremental lift or that all placements should scale. Next step: repair the mobile destination, keep row-level package reporting, and reserve a matched baseline before stronger impact language.
Simulated worked example: keep the claim tied to the rows
This is a simulated worked example, not a report from a real advertiser or campaign. It shows why a memo can support a bounded renewal decision while still rejecting lift language.
| Metric | Verified package | Prior-period comparison | Calculation and reading |
|---|---|---|---|
| Impressions | 80,000 | 80,000 | Equal volume in this illustration; that alone does not make the periods comparable. |
| Qualified visits | 1,600 | 2,000 | Visit rate = visits ÷ impressions: 1,600 ÷ 80,000 = 2.0%; 2,000 ÷ 80,000 = 2.5%. |
| Qualified leads | 48 | 40 | Lead rate = leads ÷ qualified visits: 48 ÷ 1,600 = 3.0%; 40 ÷ 2,000 = 2.0%. |
| Raw lead difference | 48 | 40 | 48 → 40 = 8 additional observed leads, or 20% more raw leads; no holdout means this is not incremental lift. |
Bounded memo conclusionAllowed: the verified package produced 48 observed qualified leads in the reported scope, with a 3.0% qualified-visit-to-lead rate. Unavailable: the package caused 8 incremental leads or improved performance by 20%. Limitation: the prior-period rows are descriptive and may differ in audience, context, timing, destination, status maturity, or mix. A matched baseline or holdout is required before causal wording.
Source-to-decision handoff
The memo fields below are grounded in platform guidance re-read for this source trail, but the guidance does not validate any particular campaign result. Google's experiment guidance calls for a stated hypothesis, a controlled test variable, and preselected success metrics; its conversion-lag reporting is available only for eligible campaign types and warns that query-date reporting can make recent CPA or ROAS look temporarily worse; and its attribution-model guidance describes credit allocation rather than incrementality. Check the actual system, campaign eligibility, observation cutoff, and export definition before applying any of those labels. Use the definitions to decide what the memo must preserve and where the claim ceiling stays low.
| Verified source | Memo decision it informs | Record to preserve |
|---|---|---|
| Google Ads: Test with confidence with the Experiments page | If the next decision needs impact or uplift language, require a stated hypothesis, a defined test variable, and preselected success metrics instead of treating a prior-period change as proof. | Hypothesis, control/test scope, one-variable change, metric definition, start/end dates, and any base-campaign changes. |
| Google Ads: About conversion lag reporting | Do not close a renewal memo while recent outcome rows may still mature; conversion delay can make current CPA or ROAS look worse before later conversions arrive. | Conversion window, query-date cutoff, last refresh, maturity status, and the rows excluded until the window closes. |
| Google Ads: About attribution models | Label attribution credit as model-dependent and keep it separate from incremental impact; a model comparison can change reported credit without changing the underlying delivery. | Conversion action, primary/secondary status, attribution model, model-comparison view, and the exact sentence allowed in the memo. |
Reproduction packetTo reproduce this handoff, save the three source URLs, the exported campaign rows, the scope and exclusion rule, the conversion-window cutoff, the conversion action and attribution model, the test hypothesis if applicable, and the memo's final allowed/unavailable claim. Recalculate every rate from raw counts; if a denominator, scope, maturity status, or attribution setting changes, mark the memo as revised rather than silently updating the conclusion.
Pre-meeting checks
- Does the memo name the exact action instead of using a broad continue or scale recommendation?
- Are included and excluded rows visible enough for a buyer, analyst, or seller to challenge the scope?
- Does each unresolved issue have an owner, due date, retest rule, and closeout state?
- Is the allowed claim weaker than or equal to the evidence, comparison, and outcome-status record?
- Does the memo say what evidence would be needed before lift, winner, or budget-shift language appears?
Pair with
Use this memo after the campaign readout QA checklist, the private marketplace renewal scorecard, and the campaign issue log and renewal register. Pair it with the private marketplace package performance readout when the buyer-facing narrative needs package-level wording, the campaign reporting worksheet when the team needs a compact evidence note, the creative and destination troubleshooting matrix when a weak response lane needs repair, the outcome quality scorecard when lead or matchback status shapes the recommendation, the campaign status-window closeout checklist when delayed outcome rows need maturity review before final wording, the campaign status-window closeout register when final wording needs closeout IDs and exclusions, the campaign baseline comparison checklist when current language depends on a prior-period or matched baseline, the private marketplace readout export sample when row fields need cleanup, the campaign renewal evidence archive when final decisions, owners, and next-test requirements need to carry forward, and the incrementality test plan template when the next action requires causal evidence.