Buyer readiness
Contextual package proof export template
A contextual package becomes easier to buy, traffic, and renew when the proof can be exported as fields instead of rebuilt from a proposal deck after the campaign ends.
Use this template before a private marketplace or direct contextual campaign launches. It connects the reader job, package contract, eligible inventory, creative handoff, first-party signal readiness, and allowed conclusion language in one exportable record. The point is not to turn context into a performance promise. The point is to preserve enough evidence for a buyer, publisher, and analyst to read the final report the same way.
Where the export fits
The export sits between the package proof sheet and the campaign readout. It should be created before trafficking, then updated only with fields that were truly observed during delivery or supplied by the buyer after launch.
| Workflow moment | Export role | Fields that must be locked | Fields that can mature later |
|---|---|---|---|
| Proposal review | Show why the package fits the reader job. | Package ID, reader job, eligible page set, clean-fit category, and unsupported uses. | Forecast volume, final creative IDs, and landing-page version. |
| Trafficking handoff | Turn the package into operational instructions. | Deal key, reporting key, placement IDs, sizes, device rules, exclusions, and flight window. | Delivery totals, viewability, invalid-traffic status, and makegoods. |
| Signal setup | Preserve context through first-party and buyer-side records. | Source trail, destination ID, event IDs, eligibility rule, missing-value vocabulary, and comparison rule. | Lead status, matchback result, follow-up state, and outcome maturity. |
| Readout meeting | Convert fields into a bounded next decision. | Primary signal, quality flags, comparison status, decision rule, and allowed claim level. | Renewal recommendation after field completeness is reviewed. |
Minimum export schema
These fields are the compact version. A larger report can add cost, pacing, geography, frequency, or order-line details, but these fields should survive into the final interpretation.
| Field | Example value | Source | Readout use |
|---|---|---|---|
| campaign_id | mp-q3-methods-flight | Proposal and trafficking record. | Connects proposal, delivery, analytics, lead, invoice, and renewal records. |
| package_id | measurement-science-desk | Media kit or inventory matrix. | Preserves the contextual package that was sold. |
| pmp_deal_key | mp-msd-pmp | Package contract. | Connects deal route with the agreed package boundary. |
| reporting_key | package.measurement_science_desk | Inventory readiness matrix. | Lets exports join package records without relying on display names. |
| reader_job | Choosing or auditing advertising measurement methods. | Audience intent map and proof sheet. | Keeps the campaign tied to a professional task, not a broad audience label. |
| eligible_context | Measurement guides, method selectors, readout QA pages, and companion templates. | Package proof checklist. | Shows which page groups qualify as on-package delivery. |
| placement_ids | article-inline-1, article-inline-2, article-rail-1, post-content | Placement contract. | Separates inventory, device, and format effects before ranking response. |
| creative_id | guide_offer_v1_728x90 | Creative acceptance record. | Connects message, size, destination, and approval state. |
| destination_id | methods-webinar-landing-v2 | Landing-page QA record. | Separates media response from page speed, form, and routing quality. |
| signal_readiness_level | Quality ready | First-party signal readiness review. | States whether source trails, eligibility, events, and quality status are interpretable. |
| eligibility_denominator | Eligible visits with non-duplicate source trail and complete destination ID. | Data-layer spec and buyer-side status fields. | Prevents match rates or lead rates from hiding excluded records. |
| comparison_rule | Matched prior contextual flight; no protected holdout. | Campaign brief and measurement plan. | Sets the strongest conclusion language the report can use. |
| bounded_conclusion | Observed qualified traffic was strongest in measurement guide contexts. | Readout owner. | Turns the export into language that matches the evidence level. |
Sample package rows
The rows below are examples for structure, not performance benchmarks. Use the real package IDs, eligible contexts, creative IDs, and signal states for the campaign being reviewed.
| package_id | reader_job | placement_ids | signal_readiness_level | comparison_rule | bounded_conclusion |
|---|---|---|---|---|---|
| measurement-science-desk | Choose or audit measurement methods. | article-inline-1, article-inline-2, article-rail-1, post-content | Quality ready | Prior contextual flight; no holdout. | Use directional renewal language and keep qualified visits separate from lift. |
| source-vendor-evaluation-desk | Evaluate vendor evidence before a decision. | archive-leaderboard, article-inline-1, article-rail-1, native-sponsored-card, post-content | Descriptive ready | No comparison available. | Report delivery and observed engagement only; do not rank vendor-evaluation contexts by outcome quality. |
| buyer-readiness | Compare package boundaries and campaign handoff fields. | archive-leaderboard, article-inline-1, native-sponsored-card | Comparison ready | Matched buyer-reference page group. | Compare package response inside the matched context and keep causal wording out of the renewal note. |
| case-study-library | Study measurement failure modes before changing process. | archive-leaderboard, case-inline-1, case-rail-1, post-content | Quality ready | Matched guide-library baseline. | Read return visits and companion-guide movement as learning signals, not business impact. |
First-party signal gate
A package proof export should not mark a campaign as report-ready until the source trail can answer these questions.
1. Can page context survive the export?Package ID, reporting key, placement ID, content group, reader job, and destination ID should appear in the same row or through a stable join.
2. Can eligibility be counted?Eligible, excluded, unmatched, suppressed, filtered, unknown, and not-applicable records should remain separate values.
3. Can events be deduped?Visits, leads, survey responses, and matched outcomes need event IDs, timestamp rules, duplicate rules, and ownership of late-arriving status changes.
4. Can destination quality be separated?Landing-page version, form path, page speed status, routing rule, and follow-up status should remain visible before media quality is judged.
5. Can the comparison support the decision?The export should name no comparison, prior flight, matched context, matched market, protected holdout, or survey design before any conclusion is written.
Allowed claim language
The export should include one conclusion field, but the language should be constrained by the comparison rule and signal readiness level.
| Evidence state | Responsible wording | Language to avoid |
|---|---|---|
| Context and delivery fields only. | The campaign delivered in the planned contextual package and placement set. | The package reached the right buyers and created demand. |
| Delivery plus traffic-quality fields. | Observed traffic quality varied by package, placement, creative, device, and destination. | The best-clicking placement caused the strongest business result. |
| Lead or outcome quality fields with missing status visible. | Lead quality can be reviewed where status is complete; missing status limits the decision. | All attributed leads were qualified pipeline. |
| Matched prior flight or matched context. | The campaign performed stronger or weaker than the chosen comparison, subject to known design limits. | The comparison proves incremental lift. |
| Protected holdout, market test, or survey design. | The design estimates change for the measured population, window, outcome, and method. | The result proves the package will create the same effect in every future flight. |
Pre-launch checklist
- Export grain is chosen before results are visible: package by week, placement by creative, or outcome status by source trail.
- Package ID, deal key, reporting key, placement IDs, creative IDs, and destination IDs are stable.
- First-party signal readiness level is recorded with the field that limits the readout.
- Eligibility denominator, missing-value vocabulary, and matchback status are visible before rates are calculated.
- Comparison rule and allowed conclusion language are written before the campaign can favor one metric.
- Renewal decision rule names whether the next action is renew, revise creative, shift mix, retest, add lift test, or pause.
Pair with
Use this export template after the contextual package proof checklist, contextual package proof sheet, and private marketplace package brief template, alongside the first-party signal readiness checklist, campaign data-layer spec, campaign tagging QA checklist, creative asset acceptance checklist, and landing page launch QA worksheet. Before the readout, compare it with the private marketplace reporting field dictionary, private marketplace readout export sample, campaign reporting sample, campaign reporting worksheet, campaign readout QA checklist, and private marketplace renewal scorecard. For package IDs and placement contracts, use the media kit and inventory readiness matrix.