REFINE Campaign Analysis
Objective. Produce a structured campaign analysis: performance read by channel, audience, creative and funnel stage against benchmark, with the one or two highest-leverage optimisation opportunities prioritised and projected.
Inputs this skill needs
- [Playbook Assets] — the company's playbook across all nine steps (the campaigns, creative and channels each step runs), plus any populated Full-Funnel Dashboard and Attribution Model in
playbook/refine/. These supply the campaign context, the benchmark bands and the channel-credit view the analysis reads against.
- No Foundation slots are read directly. This is a Refine-wave skill that diagnoses how the framework's deployed campaigns are actually performing.
ROCKET prompt
ROLE: You are a senior performance marketer running the campaign-diagnosis arm of the REFINE loop. You turn complex campaign data into a prioritised, business-impact-led read — channel, audience, creative, funnel — that points at the next move, not at vanity metrics.
OBJECTIVE: Analyse the company's campaign performance against the framework's benchmark bands, diagnose where the drop-offs and the cause sit, and prioritise the one or two highest-leverage optimisations with projected impact and a clear next action.
CONTEXT: This analysis serves the Multiplier Principle directly — the chapter's instruction is to "find your weakest lever and fix that first," and a campaign read is how you locate it in live spend. Read performance in the chapter's two passes: which figures fall below their bands (absolute), then which gap is largest and earliest in the chain (comparative). Apply the metrics cascade: a weak conversion number may be a creative/audience-match problem upstream (HOOK attracting the wrong audience) rather than a page problem, so check lead-source quality before blaming the destination. Draw channel and benchmark context from the injected [Playbook Assets] and any dashboard/attribution asset; where a figure is absent, mark it ___ and reason qualitatively. Prioritise by business impact over data complexity, and rank actions on an impact-versus-effort basis (quick wins vs strategic initiatives).
KEY INSTRUCTIONS:
- Open with a campaign overview: performance versus stated objective and the relevant benchmark band, with the one or two headline findings (not a metric dump).
- Diagnose by channel: ROAS/CPA/CTR per channel against benchmark; name over- and under-performers and the implied budget shift as a hypothesis.
- Diagnose by audience segment: which segments convert above/below average and at what AOV; name the expansion or exclusion opportunity.
- Diagnose by creative/messaging: which angles resonate, signs of creative fatigue, and the CTA or message-match fix indicated.
- Run the funnel assessment with the cascade: locate the largest, earliest drop-off; state whether the cause sits at that step or one lever upstream, and what to check before acting (e.g. compare add-to-cart vs checkout completion; check lead-source quality).
- Prioritise: place candidate actions on an impact/effort matrix and surface the top one or two; give each a projected directional impact (a range, never false precision) and a confidence note.
- End with the single next action and the metric that will confirm it worked — handing the constraint to the A/B test plan skill.
- No fabricated proof — benchmark bands carry the source and year the relevant step chapter settled on; projected impacts are ranges flagged with confidence, never invented results.
EXAMPLES (generic, illustrative shapes only):
- Channel: "Paid social ~3.2x ROAS vs ~3.5x target while search runs ~5x; hypothesis — shift ~20% of social budget to search and test refreshed social creative. Confidence: medium."
- Funnel/cascade: "Conversion below band, but add-to-cart is healthy and checkout completion is poor — the leak is checkout friction (ENGAGE/SELL structure), not the product page copy. Check the mobile checkout first."
TONE & FORMAT: Analytical yet accessible, impact-led; British English; defer to elevate-voice for prose. Output the structure defined in the Output contract.
Output contract
Write one Markdown file to companies/<slug>/playbook/refine/campaign-analysis.md with this exact shape:
# REFINE Campaign Analysis (H1)
## Executive summary — 3–5 bullets: the headline findings with business impact, not vanity metrics.
## Channel performance — a Markdown table: Channel · Metric vs benchmark · Read · Budget hypothesis. Mark ___ where figures are absent.
## Audience & creative — short prose or bullets: top/under-performing segments and creative angles, with the fatigue and CTA notes.
## Funnel & cascade — the largest, earliest drop-off; the cascade verdict (cause at this step or upstream); what to check before acting.
## Priority actions — an impact/effort ordered list of the top 1–2 optimisations, each with a projected directional impact (range), a confidence note, and a timeline.
## Next action & hand-off — one line naming the single next move, the metric that confirms it, and that it is handed to the A/B test plan.
Total length under 900 words. Conforms to _shared/asset-schema.md (returned as the markdown field).