Buyer readiness

Private marketplace buying terms guide

Published July 3, 2026. Updated July 9, 2026. Status: evergreen buyer reference.

A private marketplace buy is easier to price, traffic, and read when the buyer and publisher use the same terms before the campaign starts. Use this guide to translate package language into a clean proposal brief.

The terms below are written for buyers who need a practical handoff, not a platform-specific integration manual. They keep package scope, deal setup, creative assets, destination readiness, reporting cadence, and performance language in separate lanes.

Imagine the proposal review is happening two days before launch. Sales has promised a premium measurement package, operations has a deal key, the buyer has sent two creative files and a landing page, and analytics is asking which fields will survive into the final report. The page can still launch, but only if those pieces become one shared record instead of four loose conversations.

Private marketplace buying terms review desk with package, deal, creative, destination, and reporting checks before launch. — The buying-terms review should put the package, deal setup, creative handoff, destination state, and reporting cadence in one visible record before pricing or launch work hardens.

Term sheet

Use the term sheet before pricing or trafficking. Every field should be specific enough that an operations team can implement the buy and a reporting team can interpret it later.

In plain language, a term is buyer-ready when it tells the next person what to do without a meeting. A package ID should tell traffickers which context is eligible. A deal key should identify the exact commercial lane. A floor should explain the price guardrail without promising lift. A readout boundary should say how strong the final campaign sentence is allowed to be.

Private marketplace buying terms stack flowing from package scope, deal setup, creative handoff, and reporting fields into one approved campaign record. — A trafficable campaign record is a stack, not a slogan. Package scope, deal setup, creative and destination fields, and reporting boundaries each need their own lane before they converge into a launch packet.

Term	Buyer-ready meaning	What to lock before launch
Package ID	The stable name for the reader context being bought.	Desk, guide group, case-study group, included URL patterns, excluded contexts, and package reporting key.
Deal key	The private marketplace identifier used to connect buying, trafficking, and reporting records.	One deal key per package lane, with the buyer name, quarter, campaign objective, and package ID preserved in the campaign name.
Placement ID	The specific ad slot or sponsored module eligible for the package.	Placement list, accepted sizes, device eligibility, refresh status, and whether native is included.
Floor	The minimum price needed to preserve package quality and opportunity cost.	Context scarcity, forecastable supply, exposure quality, buyer fit, sell-through state, and whether the floor is test, renewal, or always-on.
Flight window	The active campaign dates and delivery pacing plan.	Start date, end date, pacing target, blackout dates, makegood rule, and report cadence.
Creative handoff	The final assets and click instructions that can be approved for traffic.	Creative IDs, sizes, file type, brand name, message theme, click URL, UTM values, backup mobile asset, and acceptance status.
Destination readiness	The landing page state that makes downstream response interpretable.	Landing page URL, page speed, message match, form fields, source capture, consent state, redirects, and lead-routing owner.
Reporting cadence	The schedule for delivery checks and final readout.	Launch QA date, mid-flight delivery check, post-flight data close, buyer-side status deadline, and final readout date.
Readout boundary	The strongest claim the report can support.	Descriptive delivery, directional comparison, matched-baseline estimate, or designed lift result.

Terms readiness score

Score the proposal before the package is sold as ready. The point is not to make the terms bureaucratic. The point is to find which missing field will create the first trafficking, billing, or readout problem.

Score	Condition	Buyer-facing decision
4 - ready	Package ID, deal key, placements, creative fields, destination fields, cadence, and readout boundary are complete and internally consistent.	Proceed to pricing or activation with the term record attached to the proposal.
3 - fixable before launch	The package and buyer fit are sound, but one owner must close a named gap such as missing backup mobile creative or an unresolved UTM value.	Proceed only after the owner updates the record and the launch note names the fix.
2 - risky readout	The campaign can be trafficked, but the reporting cadence, source fields, or buyer-side status path is incomplete.	Keep performance language descriptive until the missing reporting fields are supplied.
1 - hold	The deal key, package scope, placement set, or destination state cannot be tied to the proposal promise.	Hold the package out of market or rewrite the proposal around the narrower record that can be supported.

Buying path by question

Buyer question	Use this page	Decision it supports
Does this audience fit the offer?	Audience intent map	Choose a reader job and package lane before asking for availability.
Which units and sizes can run?	Media kit	Confirm placement IDs, ad-unit paths, creative sizes, and native availability.
Can the package be trafficked cleanly?	Inventory readiness matrix	Check package contracts, placement maps, reporting keys, and handoff fields.
What must the buyer send?	Creative asset acceptance checklist	Approve display, native, click URL, source trail, and launch fields.
Is the landing page ready for paid traffic?	Landing page launch QA worksheet	Check page speed, message match, forms, redirects, source fields, and lead routing.
How should results be interpreted?	Reporting field dictionary	Keep package, placement, delivery, quality, outcome, and conclusion fields aligned.

Floor language

A floor is a pricing guardrail, not a promise of business outcomes. It should be explained from inventory quality and package constraints rather than from unsupported performance claims.

Use

The measurement-science-desk floor reflects limited guide-library supply, high contextual fit, stable pageview-only delivery, and the opportunity cost of reserving upper-body placements.

Avoid

This floor guarantees better leads or incremental demand.

Reporting cadence

Cadence matters because late buyer-side status or unclear source fields can weaken the readout. Set dates before launch so the final report is not forced to use incomplete outcome data.

Moment	What to check	Useful output
Pre-launch QA	Package ID, deal key, placement IDs, creative IDs, click URLs, UTMs, destination status, and reporting owner.	Ready, revise, or hold decision before the flight starts.
Launch check	Eligible placements render, labels are visible, click URLs resolve, and device behavior matches the size map.	Launch note with any exceptions that should appear in reporting.
Mid-flight check	Pacing, measurable impressions, viewability, creative rotation, destination errors, and early quality flags.	Keep running, revise creative, fix destination, or adjust pacing.
Data close	Final delivery, invalid-traffic review, qualified visits, buyer-side lead status, missing status, and comparison rule.	Clean export for the final package readout.
Readout meeting	Package response, placement response, creative and destination differences, outcome quality, and evidence limit.	Renew, narrow, retest, pause, or design a stronger lift test.

Creative and destination handoff

A buyer should send one clean record rather than scattered assets and notes. The minimum handoff is final creative, click destination, source values, dates, and owner names.

Private marketplace buying terms handoff workflow turning scattered creative, click, landing page, source, and owner records into one launch packet. — Scattered assets create avoidable launch risk. The useful handoff gathers display files, native copy, click destinations, source fields, dates, and owners into one packet the ad operations and reporting teams can both use.

Display creative: creative ID, size, file type, landing URL, UTM structure, active dates, backup mobile asset, and any buyer-side tracking tags.
Native creative: brand name, headline, short body copy, image asset, destination URL, disclosure language, and fallback display size.
Destination: final URL, message match, primary action, form fields, source capture, consent state, redirect chain, page-speed status, and lead-routing owner.
Report fields: campaign name, package ID, deal key, placement IDs, creative IDs, device classes, primary signal, comparison rule, and readout boundary.

Clean proposal language

Proposal language should be specific enough to set expectations and careful enough to avoid turning contextual fit into a guaranteed outcome.

Private marketplace buying terms decision board showing delivery, directional comparison, matched baseline, and designed test evidence lanes before readout wording. — The readout boundary is the terms guide's final guardrail. Delivery-only evidence, directional comparisons, matched baselines, and designed tests can all be useful, but they do not earn the same campaign language.

Proposal area	Buyer-ready wording	Why it works
Context	This package reaches readers using measurement guides and campaign reporting references.	Names reader task rather than implying broad audience intent.
Inventory	Eligible delivery is limited to the named package, placement IDs, device classes, and approved creative sizes.	Keeps run-of-publication delivery separate from contextual delivery.
Floor	The floor reflects package scarcity, exposure quality, clean trafficking fields, and direct opportunity cost.	Explains price without claiming lift.
Measurement	The standard readout will report delivery quality, qualified traffic, creative response, destination response, and buyer-side status when supplied.	Sets the reporting surface before results arrive.
Comparison	Causal language requires a separately designed holdout, matched baseline, or other agreed comparison method.	Prevents a descriptive campaign report from becoming a lift claim.

Final pre-launch check

Can the buyer name the package ID, deal key, placement IDs, device classes, and excluded contexts?
Is the floor tied to supply and package quality rather than promised outcomes?
Are final display, native, click URL, UTM, backup mobile, and destination fields approved?
Does the reporting cadence include launch QA, mid-flight check, data close, buyer-side status deadline, and readout date?
Does the proposal state the strongest allowed readout language before the campaign begins?

Pair with

Use this terms guide with the advertiser FAQ for proposal fields, the media kit for package and placement specs, the inventory readiness matrix for package contracts, the private marketplace package brief template before buyer-facing scope is finalized, the private marketplace deal review checklist before activation approval, the ad yield and deal-readiness checklist before pricing, the private marketplace reporting field dictionary before final reporting, and the package performance readout after campaign exports are complete.

Keep reading

Choose the next buyer-readiness step

Move from this page into package proof, activation gates, and buyer-facing readout fields without losing the evidence trail.

Buyer deskStart the readiness pathUse the buyer-readiness desk to connect audience fit, launch QA, reporting, and renewal evidence. Readiness indexSequence the handoffTrace audience fit, package proof, activation, launch, reporting, and renewal checks in order. Package proofName the reader jobKeep package scope, eligible context, creative fit, reporting grain, and renewal evidence visible.