Campaign planning
Contextual campaign brief template
A contextual media buy gets easier to measure when the brief names the reader job, eligible inventory, creative promise, primary outcome, and comparison rule before the first impression runs.
Use this template for private marketplace, sponsorship, newsletter, native, or display campaigns where the value of the buy depends on professional context. It is meant to keep media planning, creative handoff, reporting, and claim language aligned.
The one-page brief
The brief should be short enough to read before a kickoff call and specific enough to survive trafficking, analytics exports, and the final report.
| Brief field | Write down before launch | Why it matters later |
|---|---|---|
| Decision owner | The person or team that will use the result, plus the budget, renewal, creative, or testing decision at stake. | Stops the report from optimizing for a metric nobody planned to use. |
| Reader job | The task the reader is performing: choosing a method, evaluating a vendor, checking a source, learning a failure mode, or planning a campaign. | Keeps contextual fit tied to reader intent rather than a broad audience label. |
| Eligible inventory | Topic desk, page set, URL pattern, placement IDs, formats, device classes, and exclusions. | Prevents delivery from drifting into unclear run-of-publication inventory. |
| Creative promise | The offer, message, asset type, destination, and the reader problem the creative claims to help solve. | Separates weak context from weak creative if response is lower than expected. |
| Primary outcome | One main signal selected before launch: qualified delivery, engaged visit, qualified lead, brand survey movement, or designed lift. | Reduces post-flight metric shopping. |
| Comparison rule | Holdout, matched context, prior flight, matched market, business-as-usual baseline, or explicit no-comparison status. | Sets whether the readout can use descriptive, directional, or causal language. |
| Decision threshold | The result that would trigger renewal, creative change, budget shift, deeper test, or stop decision. | Makes the recommendation auditable instead of mood-based. |
Reader context
Contextual buying is strongest when the campaign names the reader's job, not just the page category. A reader evaluating a measurement method is in a different mode from a reader scanning a case study or printing a worksheet.
| Reader job | Good-fit campaign role | Weak readout habit |
|---|---|---|
| Choose a measurement method | Introduce a guide, calculator, research asset, analyst service, or product page that helps compare methods. | Pooling method-selector readers with broad awareness traffic. |
| Evaluate a vendor claim | Offer a review worksheet, benchmark, demo, governance resource, or evidence-quality service. | Treating all source-evaluation traffic as the same intent. |
| Plan a campaign | Promote a practical template, webinar, planning guide, or operational workflow. | Judging the buy only by last-click form fills. |
| Study a failure mode | Pair a case study with a measured next step, such as a checklist or advisory consult. | Assuming deep reading means immediate purchase intent. |
| Check a public or media claim | Support source-quality, research, data, or professional learning offers with careful claim language. | Reading engagement as proof that beliefs changed. |
Inventory and creative handoff
A campaign brief should make trafficking boring. Anyone setting up the flight should be able to map the package, placements, creative, destination, and reporting keys without interpreting a sales paragraph.
1. Name the package and placement IDs.Use the package ID, deal key, placement IDs, accepted sizes, device rules, and page-set exclusions from the media kit or inventory matrix.
2. Version the creative.Record creative ID, size, message angle, offer, brand name, destination URL, active dates, and backup creative for mobile or lower-size placements.
3. Keep destination quality visible.Preserve landing page, form path, page version, UTM values, destination action, and any follow-up rules that affect lead or outcome quality.
4. Log material changes.Creative swaps, page edits, audience changes, paused delivery, tracking fixes, or makegood inventory should appear in the final readout notes.
Measurement plan
The measurement plan should match the decision. A sponsorship flight can be valuable with a descriptive readout, but it should not borrow causal wording from a test it did not run.
| Decision | Minimum evidence | Stronger design | Bounded readout language |
|---|---|---|---|
| Renew a contextual package | Qualified delivery, viewable impressions, frequency, engaged sessions, and destination quality by page set. | Matched prior flight or matched page group with similar creative and destination. | The package delivered the intended context and produced observed response under the stated definitions. |
| Choose a creative route | Delivery and response by creative ID, format, destination, and message angle. | Balanced creative rotation with enough delivery per cell. | The observed response favors this creative in this context; it does not isolate creative effect if rotation was uneven. |
| Judge lead quality | Lead source trail, qualification status, disqualification reason, follow-up status, and duplicate rules. | Matched baseline or holdout for downstream quality under the same sales process. | The campaign generated reported leads with the stated quality mix. |
| Estimate brand movement | Survey sample source, exposed/control balance, question wording, field dates, and uncertainty. | Pre-registered brand lift design with respondent-quality and leakage checks. | The survey suggests movement in the measured sample and window. |
| Claim incremental impact | A protected comparison, assignment or matching method, outcome window, leakage check, and uncertainty statement. | Randomized holdout, clean geo test, or matched-market design selected before results were visible. | The design estimates lift for this population, window, and outcome, with the stated limits. |
Pre-launch QA
| Question | Pass condition | If not |
|---|---|---|
| Can the campaign be reported by context? | Package, page set, placement ID, and device class are captured. | Report at package level and avoid ranking page contexts. |
| Can creative and destination be separated? | Creative ID, message, size, destination, and landing-page version are stable. | Do not call a message or format the winner. |
| Can bad exposure be filtered? | Measurable, viewable, invalid-traffic, and frequency fields are visible where available. | Downgrade to served-delivery language. |
| Can outcomes be joined without guessing? | Lead, sale, survey, or matchback exports carry campaign and source-trail fields. | Report observed outcomes with source-trail caveats. |
| Can the comparison survive launch? | The holdout, matched baseline, prior flight, or no-comparison label is locked before results. | Use descriptive language and plan a deeper test next. |
Report shell
Use the same headings in the final readout. The report should make the planned question, actual delivery, response quality, and evidence level visible before the recommendation.
- Campaign decision and threshold.
- Eligible context, delivered context, and any delivery changes.
- Creative, destination, and device delivery by placement group.
- Exposure quality, frequency, traffic quality, and lead or outcome quality.
- Comparison method and evidence level: descriptive, directional, or causal.
- Recommended action and what would need stronger evidence next.
Pair with
Use this template with the media kit and ad inventory readiness matrix for placement IDs, package IDs, deal keys, and creative sizes. Use the contextual package proof checklist before pricing or trafficking a package, the contextual package proof sheet when the package needs a one-page buyer, operations, and analytics handoff, and the private marketplace package brief template when buyer-facing scope and renewal evidence need to be locked before activation. Use the creative asset acceptance checklist to approve display files, native fields, destination fit, and tracking before launch, then use the landing page launch QA worksheet to check page speed, forms, redirects, source fields, consent state, and routing. Use the campaign data-layer spec to preserve source-trail fields, the private marketplace campaign measurement checklist to set readout boundaries, the private marketplace readout export sample to define row-level delivery and outcome fields, the campaign reporting sample to structure the finished report, and the campaign readout QA checklist before a renewal or budget decision.