Campaign diagnosis

Campaign issue log and renewal register

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

About 12 min read

The renewal meeting is two days away. The report shows useful response, but the strongest slide also depends on pooled placements, a mid-flight creative change, missing lead-status rows, and a comparison that cannot support lift language.

A register is the shared issue log that prevents those caveats from disappearing. It says which rows can support renewal, which rows need repair, which rows are excluded, and which claims must wait for a stronger test.

Use this page after the readout QA pass and before the renewal meeting. It is designed for publishers, advertisers, agencies, and analysts who need one shared record for weak evidence lanes, owner actions, fix deadlines, retest requirements, and final supportable claim language.

When to open a register

Open a register whenever the next decision is stronger than the current evidence. A register is most useful when the team is tempted to solve every issue in the final slide instead of assigning each weak lane to a concrete next action.

Minimum register fields

The register should be short enough to use in a meeting and specific enough to survive handoff. These fields keep the decision tied to evidence instead of opinion.

Register template

The values below show structure, not benchmarks. Replace the example IDs with the campaign's actual package, placement, creative, destination, and outcome records.

Simulated worked example: scope the renewal before calculating the claim

This is a simulated worked example, not a report from a real advertiser or campaign. The numbers are intentionally small and reproducible so the register logic can be checked by hand.

Assumptions: the verified package contains 10,000 in-scope impressions, 220 visits, 22 submitted leads, and 11 qualified leads. A separate pooled slice contains 4,000 impressions and 100 visits, but its lead-status rows are incomplete. The prior-flight comparison has 9,000 impressions and 180 visits, but the offer and season are different, so it is descriptive context rather than a protected control.

Limitations: these calculations do not estimate uncertainty, account for user overlap, or prove that media caused the visits or leads. They show how a register separates a valid descriptive denominator from an unsupported causal conclusion. If the missing statuses change the qualified-lead conclusion, the outcome row remains a blocker rather than an optimization note.

Primary source trail for the register rules

The register’s boundaries are anchored to first-party measurement guidance, not a generic checklist convention. Google Ads’ conversion-status troubleshooting guidance says to verify tag firing and account for reporting latency and attribution differences; that is why this page separates delivery, submitted outcomes, qualified outcomes, and status-window closeout. Google Ads’ experiment guidance recommends a clear hypothesis, testing one variable at a time, preselecting success metrics, and keeping experiment records; that is why unresolved rows receive an owner, due date, retest rule, and claim boundary. For incrementality, Google’s Experiment Center guidance distinguishes ordinary experiments from controlled lift studies that compare randomized or geographically split treatment and control groups.

Source boundary: these Google Ads documents help diagnose platform implementation, reporting delay, and experiment structure. They do not certify a CRM status, deduplicate a lead export, establish buyer quality, or turn an unresolved register row into incremental evidence. Those claims still require the campaign’s own definitions, row-level reconciliation, and an appropriate comparison design.

Severity bands

Severity should describe decision risk, not how embarrassing the issue feels. A small operational defect can be high severity if it changes the renewal claim.

Renewal decision map

The register is useful only if it changes the meeting outcome. Read each row against the decision being requested, then use the lowest supportable action instead of averaging good and weak evidence into one broad yes.

Closeout rules

Every row should end in one of five states. The closeout state should be visible in the renewal note so the final recommendation does not outrun the record.

Simulated action-permission check

This simulated check turns the five register rows above into a meeting-ready boundary. It counts requested actions that the current record can permit; it is not a campaign-quality score, a benchmark, or a substitute for the source fields and status rules recorded in each row.

Reproduce the boundary: permitted requested actions ÷ requested actions = 1 ÷ 5 = 20%. The correct meeting decision is therefore a focused renewal of the verified scope, not a broad renewal, mobile scale, qualified-lead claim, lift statement, or budget shift. If status coverage is repaired, comparison design is changed, or the small cell reaches its minimum delivery rule, recalculate the count; the denominator also changes when the meeting requests a different set of actions.

Renewal note pattern

A useful renewal note names the clean evidence, the unresolved rows, and the next test without making the reader infer which caveats matter.

Meeting script

• Which unresolved row could change the renewal, creative, destination, budget, or test decision?
• Which issue is a blocker, which is a decision limit, and which is only an optimization note?
• Does every weak lane have an owner, due date, retest rule, and claim boundary?
• Which rows are excluded from the final recommendation, and which are conditions for the next flight?
• What exact sentence is allowed until the fix, status update, or comparison test is complete?

Pair with

Use this register after the campaign readout QA checklist and the creative and destination troubleshooting matrix. Pair it with the campaign reporting worksheet when the renewal meeting needs a one-page note, the private marketplace renewal scorecard when the decision needs scoring, the campaign renewal memo template when scored issues need final renew, revise, retest, or hold language, the campaign renewal evidence archive when closeout states must carry forward, the campaign renewal archive follow-up fields when archived issues need owners, due dates, and next-launch gates, the campaign status-window closeout checklist when unresolved rows depend on delayed lead, matchback, attribution, or survey status, the campaign status-window closeout register when those delayed rows need IDs, exclusions, and next-review dates, the private marketplace readout export sample when rows need a consistent field structure, the package performance readout when the buyer-facing narrative needs tighter language, the campaign baseline comparison checklist when the comparison is weak, the outcome quality scorecard when lead or matchback status is incomplete, and the incrementality test plan template when the next decision needs causal evidence.