Campaign diagnosis
Campaign evidence triage tree
A campaign readout usually creates pressure to pick an action quickly: renew, revise, shift budget, request more data, or claim lift. The safer sequence is to triage the evidence lane before choosing the action.
Use this page after the first readout pass and before the renewal note is written. It turns the main evidence questions into a decision tree so teams can distinguish operational fixes, creative or destination changes, descriptive renewals, and true incrementality-test needs.
Five-minute triage
Start at the top. Do not move to stronger decision language until the previous branch is clean enough for the decision at hand.
| Branch | Gate question | If the answer is yes | If the answer is no |
|---|---|---|---|
| 1. Eligibility | Did the campaign run in the agreed package, placement, device, geography, date, and creative scope? | Move to source-field completeness. | Treat the readout as an operational exception. Fix trafficking, package definition, or delivery evidence before judging response. |
| 2. Source fields | Are placement IDs, creative IDs, destination IDs, dates, device class, audience rule, and primary outcome visible at the row level? | Move to exposure and traffic quality. | Request the missing fields and log an issue. Do not let a pooled summary become the decision record. |
| 3. Exposure and traffic | Are measurability, viewability, invalid-traffic review, frequency, qualified visits, and destination behavior good enough to interpret the response? | Move to outcome status. | Diagnose exposure quality, creative, destination, or routing before treating weak response as a media-context failure. |
| 4. Outcome status | Are reported leads, conversions, matches, sales steps, survey responses, or pipeline rows defined and separated by quality status? | Move to comparison strength. | Hold final action language until outcome maturity, lead quality, matchback, or survey status is clear enough. |
| 5. Comparison strength | Is there a prior-period, matched, holdout, geo, model, or survey-control comparison that was defined before the conclusion? | Read the uncertainty and decide the action boundary. | Keep the conclusion descriptive. Renew, revise, or retest only within the observed-response evidence. |
| 6. Uncertainty | Does the result show a range, threshold, minimum cell size, or sensitivity check that could change the recommendation? | Use the evidence-to-action matrix below. | Reduce the strength of the claim and request a cleaner readout before scaling the decision. |
Evidence-to-action matrix
The right next action depends on which lane is weak. A campaign can be worth renewing without supporting lift language, and a strong-looking response can still be too messy to renew.
| Evidence pattern | Best next action | Allowed language | Pair with |
|---|---|---|---|
| Clean delivery, complete fields, weak qualified response. | Diagnose creative, destination, offer, lead routing, and context fit before changing the media plan. | The campaign delivered cleanly, but response quality needs diagnosis before renewal. | Creative and destination troubleshooting matrix |
| Clean delivery, strong observed response, no credible comparison. | Renew carefully or repeat with a planned baseline, but do not claim incremental impact. | The campaign produced strong observed response under the reported context and quality controls. | Campaign baseline comparison checklist |
| High exposure quality, weak outcome status. | Check landing-page quality, form quality, sales follow-up, matchback rules, or delayed status windows. | The campaign met exposure-quality thresholds, but downstream outcome evidence is not final. | Outcome quality scorecard |
| Strong total result, noisy or contradictory slices. | Use issue rows and minimum cell thresholds before naming placement, creative, device, or audience winners. | The total result is useful, but slice-level conclusions are not stable enough for winner language. | Campaign issue log and renewal register |
| Incomplete lead, matchback, attribution, or survey status window. | Publish a provisional decision only if the incomplete fields cannot change the action. | The readout is preliminary until delayed status rows mature. | Campaign status-window closeout checklist |
| Credible comparison with visible uncertainty and stable quality controls. | Act within the design limit, then preserve the assumptions for the next flight or model calibration. | The campaign supports a bounded lift or budget-direction claim for this design, audience, and window. | Evidence-to-claim language matrix |
Decision tree by next action
Renew the package
Use when delivery matched the agreed context, response quality met the stated goal, and the recommendation stays descriptive or uses a clearly bounded comparison.
Revise creative or destination
Use when the media context was eligible but response quality points to message mismatch, format friction, page speed, form quality, or lead-routing issues.
Shift mix carefully
Use only when placement, creative, device, or audience slices have enough comparable delivery and quality controls to support a mix change.
Request missing evidence
Use when row-level fields, outcome status, exclusions, denominator, or comparison rules are missing from the packet.
Run a lift test
Use when the next budget decision requires causal language and the current readout is descriptive, confounded, or based on attribution.
Pause or rebrief
Use when package definition, delivery eligibility, creative acceptance, destination readiness, or measurement handoff broke before the report arrived.
Triage worksheet fields
Use these fields as the compact record that travels into the renewal memo, issue register, or next-test plan.
| Field | What to record | Why it matters |
|---|---|---|
| Primary decision | Renew, revise, shift mix, request evidence, pause, or test. | Prevents a general readout from pretending to answer every possible decision. |
| Weakest evidence lane | Eligibility, source fields, exposure quality, traffic quality, outcome status, comparison, or uncertainty. | Shows where the conclusion should be bounded. |
| Cleanest evidence lane | The strongest supported finding after exclusions and quality checks. | Keeps useful learning from being discarded when one lane is weak. |
| Claim ceiling | Delivery, observed response, directional comparison, bounded lift, or unsupported. | Sets the strongest sentence the readout can support. |
| Owner and due date | The person or team responsible for missing fields, issue closeout, creative revision, or test planning. | Turns critique into an operational next step. |
| Carry-forward rule | What must change before the next flight can use stronger language. | Protects the next campaign from recycling the same evidence weakness. |
Meeting script
- Which branch of the tree is the first weak branch?
- What action can the cleanest evidence support today?
- What action would require a stronger comparison or more mature status window?
- Which result would change if attributed outcomes, small slices, or incomplete statuses were removed?
- What must be fixed before this evidence can be reused in a renewal or next-flight brief?
Pair with
Use this triage tree after the campaign readout QA checklist, before the campaign renewal memo template, and alongside the private marketplace renewal scorecard when a contextual package needs a final action. Use the campaign status-window closeout register when delayed rows need durable closeout fields, the campaign renewal evidence archive when final limits need to carry forward, the campaign renewal follow-up tracker when the next flight needs owner actions, and the incrementality test plan template when the next decision requires a stronger causal design.