Buyer readiness
Private marketplace campaign walkthrough
This walkthrough follows one anonymous contextual package from pre-launch readiness through row-level reporting, buyer-facing readout language, and the renewal decision. It shows how a private marketplace campaign can be useful without pretending that observed response is the same as causal lift.
Use it when the checklist pages feel too separate: the readiness index says what should exist, the export sample shows the row fields, the package readout shows the narrative, and the renewal scorecard turns the result into a next action. This page connects those pieces in one campaign path.
The campaign in one record
The example uses a contextual package for readers comparing measurement methods. The values below are structure examples, not performance benchmarks or promises.
| Record field | Example value | Why it matters |
|---|---|---|
| Campaign decision | Should the buyer renew a contextual package, narrow the placement mix, or plan a stronger incrementality test? | Names the decision before the report searches for a favorable metric. |
| Package ID | measurement-science-desk | Keeps proposal, deal review, trafficking, export, and readout tied to the same package. |
| Deal key | mp-msd-pmp | Connects the private marketplace transaction route to the package definition. |
| Reader job | Compare measurement methods before using a campaign report for budget or renewal decisions. | Prevents the package from being sold or judged as a broad audience buy. |
| Eligible contexts | Measurement-method guides, campaign reporting guides, and buyer-readiness references. | Defines where delivery is expected before impressions arrive. |
| Primary creative lane | Display creative that points to a measurement planning resource. | Separates media context from offer, message, and destination effects. |
| Primary outcome | Qualified visits with lead-status handoff where available. | Keeps raw clicks and raw forms from becoming the success claim. |
| Comparison rule | Prior contextual flight and matched guide group; no protected holdout. | Supports directional language, not lift language. |
| Renewal threshold | Renew only if delivery stays in scope, qualified visits concentrate in the intended contexts, and lead status is complete enough to interpret. | Sets the next action before results are visible. |
Pre-launch readiness path
The campaign should not move from proposal to activation until each handoff can name the same package, placements, fields, and decision limits.
| Step | Record to check | Ready signal | If weak |
|---|---|---|---|
| Audience fit | Audience intent map and source-quality review. | The offer helps a reader with measurement planning and the destination has enough substance to inspect. | Narrow the offer or hold the package until the destination can support the reader job. |
| Package proof | Contextual package proof sheet. | Included and excluded contexts are named, and the reader job matches the buyer problem. | Revise the package scope before pricing or trafficking. |
| Buyer brief | Private marketplace package brief. | The buyer sees package ID, deal key, placements, reporting grain, comparison rule, and renewal threshold. | Do not let the readout expectation be negotiated after launch. |
| Activation gate | Deal review checklist. | Proof, identifiers, creative files, destination, field names, exceptions, and thresholds are approved. | Launch only the ready portion or hold the campaign. |
| Launch state | Campaign readiness dashboard. | Creative, destination, URL parameters, source fields, and owners are green or explicitly excepted. | Label the exception before it can distort the readout. |
What launched
The campaign launched with one primary package and one supporting lane. Reporting kept placements, device class, creative size, destination, and outcome status separate.
| Package | Placement | Format | Destination | Readout note |
|---|---|---|---|---|
| measurement-science-desk | article-inline-1 | Display, desktop and mobile sizes. | Measurement planning resource. | Primary in-context body placement. |
| measurement-science-desk | article-inline-2 | Display, desktop and mobile sizes. | Measurement planning resource. | Secondary body placement with separate device read. |
| measurement-science-desk | article-rail-1 | Rail display, desktop. | Measurement planning resource. | Desktop-only support; do not compare directly with mobile body units. |
| buyer-readiness | archive-leaderboard | Leaderboard display. | Measurement planning resource. | Discovery lane; keep separate from deep-guide contexts. |
| buyer-readiness | native-sponsored-card | Native card. | Measurement planning resource. | Separate format lane because copy and reader action differ from display. |
Row-level readout
The row-level export preserves enough detail to explain the result. Totals still matter, but the decision should be made after checking context, placement, device, creative, and outcome quality.
| Package | Placement | Device | Impressions | Viewable rate | Qualified visits | Lead status | Fair read |
|---|---|---|---|---|---|---|---|
| measurement-science-desk | article-inline-1 | desktop | 46,800 | 75% | 91 | 13 qualified, 5 disqualified, 2 missing | Strong observed response in the intended context; preserve placement and creative fields before scaling. |
| measurement-science-desk | article-inline-1 | mobile | 33,400 | 67% | 43 | 4 qualified, 7 disqualified, 1 missing | Mobile response needs destination and form-friction review before judging media fit. |
| measurement-science-desk | article-inline-2 | desktop | 28,900 | 71% | 38 | 6 qualified, 3 disqualified, 1 missing | Useful supporting response, but smaller than the first body placement. |
| measurement-science-desk | article-rail-1 | desktop | 22,600 | 69% | 17 | 3 qualified, 2 disqualified, 0 missing | Rail delivery helped reach, but the cell should not carry the renewal argument alone. |
| buyer-readiness | archive-leaderboard | desktop | 19,200 | 63% | 13 | 2 qualified, 1 disqualified, 2 missing | Discovery inventory created some response; interpret as awareness support, not lower-funnel proof. |
| buyer-readiness | native-sponsored-card | mobile | 10,400 | 72% | 29 | 5 qualified, 3 disqualified, 0 missing | Native card response is promising but must stay separate from display placement rankings. |
Three possible readings
The same rows can produce very different claims. The right readout keeps the evidence useful while leaving the comparison limit visible.
| Reading | Example sentence | Problem or use | Better next action |
|---|---|---|---|
| Overstated | The package drove incremental demand and proved the buyer should scale spend. | The comparison was not protected, so the report cannot separate media effect from prior intent, context selection, or destination behavior. | Remove lift language and plan a holdout if causal proof is needed. |
| Too vague | The campaign performed well and should renew. | The sentence hides which package, placement, device, and outcome fields support the recommendation. | Name the rows, quality flags, and comparison limit. |
| Supportable | The measurement-science package delivered in scope and produced the strongest observed qualified traffic in upper-body guide placements; renew a narrower package while testing mobile destination friction. | The sentence names delivery fit, observed response, placement concentration, and a bounded next action. | Use this language for renewal and reserve lift language for a designed test. |
Quality flags that changed the readout
Quality flags make the report more valuable because they stop a strong-looking total from becoming a stronger claim than the campaign can support.
Device mix
Desktop body inventory carried most qualified visits. Mobile results need destination review before package fit is judged.
Native separation
Native card response stayed outside the display placement ranking because the format, copy, and reader action were different.
Lead status
Most rows had lead status, but missing status stayed visible in the renewal note instead of being ignored.
Comparison limit
The prior-flight comparison helped directionally, but it did not create a protected counterfactual.
Small cells
Rail and archive cells helped diagnose reach and discovery but did not drive the main recommendation.
Destination friction
Mobile response was treated as a media, creative, and landing-page question rather than a simple package failure.
Renewal decision
The scorecard should turn evidence into a next action, not a retroactive justification for the most favorable metric.
| Dimension | Score | Reason | Decision effect |
|---|---|---|---|
| Package delivery | Strong | Most delivery stayed inside approved measurement-science and buyer-readiness contexts. | Supports renewal of the core contextual package. |
| Placement evidence | Strong but uneven | article-inline-1 carried the clearest response; rail and archive cells were smaller support lanes. | Narrow the package mix and protect row-level reporting. |
| Outcome quality | Moderate | Lead status was present for most rows, but mobile quality and missing status need review. | Renew with destination QA and status-completion requirements. |
| Comparison strength | Directional | The readout used a prior contextual flight and matched guide group, not a protected holdout. | Do not claim lift; plan a stronger comparison if the next budget decision requires it. |
| Next test need | Clear | The buyer now knows which package, placement, and device questions deserve a cleaner test. | Renew a narrower flight and reserve a comparison cell for the next round. |
Buyer-facing close
Recommended wordingThe campaign delivered primarily inside the approved measurement-science package and produced the clearest observed qualified traffic in upper-body guide placements. The readout supports renewing a narrower contextual package, keeping native response separate, and fixing mobile destination friction. Because the comparison was directional rather than protected, the result should not be described as incremental lift unless a future flight uses a designed counterfactual.
Walkthrough checklist
- Can every row trace back to the same package ID, deal key, placement ID, creative, destination, and reporting key used before launch?
- Did the strongest response occur in the reader context that justified the package?
- Are device, format, native, and destination differences separated before placement rankings are written?
- Is lead status complete enough to support the renewal decision, and are missing fields visible?
- Does the final sentence say delivery, observed response, directional evidence, or lift with the right level of confidence?
Pair with
Use this walkthrough with the private marketplace readiness index for the full pre-launch sequence, the contextual package proof sheet and private marketplace package brief template for buyer-facing scope, the private marketplace deal review checklist for activation approval, the campaign readiness dashboard before launch, the private marketplace reporting field dictionary for field names, the private marketplace readout export sample for row structure, the private marketplace package performance readout for buyer-ready narrative, the creative and destination troubleshooting matrix when uneven response needs a fix, narrow, hold, or retest decision, the campaign issue log and renewal register when weak lanes need owner actions and claim boundaries, the private marketplace renewal scorecard for the next decision, the campaign renewal memo template for final action language, the campaign renewal evidence archive for preserving the decision before the next flight, the campaign renewal follow-up tracker for next-flight owners and launch gates, the campaign status-window closeout checklist when package outcomes need delayed status review, the campaign status-window closeout register when the example needs exportable closeout rows, the outcome quality scorecard for lead status, and the incrementality test plan template when the next flight needs lift evidence.