Buyer readiness

Private marketplace readiness index

Published June 2, 2026. Updated June 2, 2026. Status: evergreen buyer reference.

A private marketplace package should leave a clear evidence trail from audience fit to renewal. This index gives buyers, sellers, operations teams, and analysts one compact sequence for checking package proof, activation readiness, reporting fields, and decision language.

Use this page when a contextual package is moving from proposal review into activation, or when a campaign readout needs to be traced back to the package that was actually approved. It is not a rate card or a lift claim. It is a buyer-facing handoff map for deciding what must be ready, what can be revised, and what should hold before money or conclusions move.

The complete readiness sequence

Each stage should produce a named record. If the record is weak, the package may still be useful, but the strongest buyer-facing conclusion should be narrowed.

Stage	Primary decision	Required record	Best starting page
1. Audience fit	Does the buyer's offer match a real reader job?	Reader job, clean-fit category, unsupported uses, and destination depth.	Audience intent map and advertiser source-quality standards.
2. Proposal readiness	Is the proposal narrow enough to price and review?	Objective, package lane, offer evidence, creative concept, destination, floor inputs, and readout boundary.	Proposal review packet and advertiser intake worksheet.
3. Package proof	Can the package be explained without broad audience language?	Package ID, included contexts, excluded contexts, reader job, and primary signal.	Contextual package proof sheet and package proof export template.
4. Inventory contract	Can operations traffic the buy without guessing?	Placement IDs, deal key, ad-unit path, accepted sizes, device rules, refresh status, and reporting key.	Media kit and inventory readiness matrix.
5. Buyer brief	Does the buyer see the scope, fields, and renewal evidence before activation?	Package scope, reader context, creative fit, reporting grain, comparison rule, and renewal threshold.	Private marketplace package brief template.
6. Activation gate	Are proof, identifiers, placement scope, fields, exceptions, and thresholds approved?	Ready, revise, or hold decision with exception owner and launch boundary.	Private marketplace deal review checklist.
7. Launch readiness	Can the campaign launch without losing the evidence trail?	Creative approval, destination QA, URL parameters, change log, trafficking owner, and launch status.	Campaign readiness dashboard, creative acceptance checklist, and landing page QA worksheet.
8. Reporting fields	Will the final report preserve enough detail to interpret results?	Package, placement, context, device, creative, destination, exposure quality, traffic quality, outcome status, and comparison fields.	Reporting field dictionary and campaign data-layer spec.
9. Readout language	Does the report separate delivery, response, quality, and comparison strength?	Row-level export, package performance note, quality flags, and conclusion boundary.	Campaign walkthrough, readout export sample, and package performance readout.
10. Renewal decision	Should the next action be renew, revise, shift, test, pause, or rebrief?	Renewal score, evidence dimension notes, status-window closeout, next-test need, archive record, follow-up tracker, and wording limit.	Private marketplace renewal scorecard, campaign renewal memo template, campaign renewal evidence archive, campaign renewal follow-up tracker, campaign status-window closeout checklist, and incrementality test plan template.

Ready, revise, or hold

This compact decision grid keeps each handoff from becoming a vague approval. A package can be commercially promising and still need a hold if the missing field affects interpretation.

Area	Ready	Revise	Hold
Audience and offer fit	The offer helps the reader with a relevant professional task and the destination has enough substance to inspect.	The fit is plausible, but the offer or destination should be narrowed to one use case.	The package depends on broad reach, thin evidence, or a destination that does not match the reader job.
Package and inventory	Package IDs, eligible contexts, placements, sizes, exclusions, and reporting keys match the public inventory record.	One placement, device rule, or excluded context needs a clearer contract.	The package cannot be trafficked or audited against the sold scope.
Creative and destination	Display or native assets, labels, URLs, UTM values, destination state, and change-log owner are complete.	Creative can launch after a named file, copy, or destination fix.	The creative or destination gap would make response data uninterpretable.
Reporting and comparison	Fields preserve package, context, placement, device, creative, destination, quality, outcome, and comparison status.	Some fields are directional and must be labeled before the readout.	The buyer's expected decision depends on fields or comparisons that will not exist.
Renewal threshold	The renew, revise, shift, test, pause, or rebrief rule is written before results arrive.	The threshold exists but needs a minimum delivery or quality caveat.	The next decision would be chosen after seeing the most favorable metric.

Minimum buyer handoff

If a team needs one portable record, capture the fields below before activation. The values should match the proposal, media kit, ad operations sheet, reporting export, and renewal note.

Handoff field	What to record	Decision it protects
buyer_problem	The planning, evaluation, education, or decision task the campaign supports.	Whether the package is a contextual fit rather than a broad audience buy.
package_id	Stable package ID, label, pmp_deal_key, package_reporting_key, and buying path.	Whether proposal, trafficking, invoice, and report can name the same buy.
eligible_context	Included desks, guide groups, case-study groups, buyer-reference pages, and excluded contexts.	Whether delivery can be judged against the sold reader job.
placement_scope	Placement IDs, sizes, device rules, format, refresh status, and excluded placements.	Whether operations can traffic the package without changing scope.
creative_destination	Creative IDs, message theme, native fields if used, destination ID, URL parameters, and launch state.	Whether response reflects the package, the creative, the destination, or a launch issue.
reporting_grain	Package by context group, placement, device class, creative size, destination, quality flag, and outcome status.	Whether the readout can avoid pooling unlike signals into one claim.
comparison_rule	No comparison, prior flight, matched context, matched market, protected holdout, or randomized split.	Whether the final language can be descriptive, directional, or causal.
renewal_threshold	Minimum delivery, quality condition, outcome state, and next action rule.	Whether the campaign result becomes a clear decision instead of a favorable metric search.
exception_owner	The owner for placement, creative, destination, reporting, comparison, and renewal exceptions.	Whether weak fields are resolved or labeled before the report is written.

Evidence path by buyer question

Different buyer questions require different proof. Start with the question before choosing the metric or report page.

Buyer question	Evidence path	Strongest ordinary conclusion	Upgrade needed for stronger language
Is this the right context for the offer?	Audience intent map, source-quality standards, package proof sheet, and package brief.	The package fits a named reader task and offer type.	Post-launch response by context, creative, and destination.
Can the buy be trafficked cleanly?	Media kit, inventory readiness matrix, programmatic inventory QA, and deal review.	The package has stable IDs, placements, sizes, and reporting keys.	Launch-readiness confirmation and exception log.
Did the package deliver as sold?	Reporting field dictionary, export sample, and package performance readout.	The campaign delivered within or outside the approved package scope.	Device, placement, creative, and context-separated rows.
Did the campaign produce useful response?	Traffic-quality fields, outcome status fields, campaign readout QA, and renewal scorecard.	The campaign produced observed response under the stated quality rules.	A credible comparison if the next question is incremental impact.
Should the package renew?	Package performance readout, renewal scorecard, outcome quality scorecard, and comparison rule.	The evidence supports renewal, revision, mix shift, retest, pause, or rebrief.	A designed holdout, geo test, or randomized split for lift language.

When the path branches

The standard sequence can be shortened or extended depending on the buying path, the format, and the decision the buyer wants to make.

Direct sponsorship

Start with proposal review, source-quality fit, native-card examples, creative acceptance, and the contextual campaign brief before using the same reporting and renewal steps.

Programmatic package

Prioritize inventory QA, supply-path transparency, package IDs, deal keys, size maps, seller-path evidence, reporting keys, and the activation gate.

Native card

Keep display and native results separate. Preserve headline, sponsor label, destination, image, message theme, and placement context before comparing response.

Migration or template change

Use migration readiness before route, ad path, template, feed, or reporting-baseline changes affect package availability or historical comparisons.

Yield decision

Use deal-readiness and yield inputs when the question is floor, scarcity, sell-through, refresh, renewal signal, or package priority rather than campaign response.

Lift decision

Move to incrementality planning when the buyer needs causal language. A clean package readout can justify a better test, but it does not replace the test.

Readiness record example

The sample values below show structure, not performance targets. Replace them with the actual package, creative, destination, and reporting decisions for the campaign being reviewed.

Record item	Example value	Decision note
Readiness decision	Revise before activation.	Package proof and identifiers are ready; destination status and outcome fields need completion.
Package	measurement-science-desk, mp-msd-pmp, package.measurement_science_desk.	Reader job is method selection and campaign measurement review.
Placements	article-inline-1, article-inline-2, article-rail-1, post-content.	Archive leaderboard excluded from this flight because the brief is deep-guide oriented.
Creative and destination	Planning-guide display creative, approved desktop and mobile sizes, destination_id measurement-report-demo.	Click URL and UTM values are ready; form source field still needs QA.
Reporting grain	Package by guide group, placement ID, device, creative size, destination, qualified visit, and lead status.	Small cells will be marked directional before package performance language is written.
Comparison rule	Matched prior contextual flight, no protected holdout.	Supports directional renewal language, not causal lift language.
Next action	Complete landing-page QA, then rerun the deal review before activation.	Activation should wait because destination fields affect the buyer's outcome decision.

Signoff questions

Can the buyer, seller, operations team, and analyst name the same package ID, deal key, placements, and reporting key?
Does the package proof describe a reader job and eligible context rather than a broad audience promise?
Are creative files, native fields, destination state, URL parameters, and change-log ownership ready before traffic starts?
Will the report preserve package, context, placement, device, creative, destination, quality, outcome, and comparison fields?
Is the renewal threshold written before results are visible, and does it match the comparison rule?

Pair with