Inventory readiness
A placement map buyers can traffic without guessing.
This matrix translates Measurement Press's reader contexts into package IDs, deal keys, placement IDs, package boundaries, creative sizes, and campaign handoff fields. It is written for buyers, publishers, and operations teams who need clean inventory without turning editorial pages into sales copy.
Inventory workflow
Use this sequence when a contextual package moves from proposal to trafficable inventory.
- Confirm format specsReview package examples, placement IDs, ad-unit paths, accepted sizes, and refresh rules.
- Attach package proofConnect the package to reader jobs, eligible contexts, and clean-fit campaign examples.
- Run inventory QACheck placement contracts, labels, size maps, device behavior, and reportable fields.
- Set the experience budgetProtect page speed, layout stability, reading flow, refresh limits, and reportability before adding demand.
- Translate buyer termsLock package IDs, deal keys, floors, creative handoffs, destination readiness, cadence, and readout boundaries.
- Complete advertiser intakeCapture objective, package lane, floor inputs, creative and destination handoff, cadence, and readout boundary.
- Use the readiness indexSequence proof, activation, launch, reporting, and renewal checks in one buyer handoff.
- Write the package briefMake package scope, reader context, reporting grain, and renewal evidence buyer-facing before activation.
- Review the deal gateCheck proof, deal keys, placement IDs, reporting fields, exceptions, and renewal thresholds before activation.
- Check launch readinessScore package proof, inventory contracts, creative approval, destination QA, reporting fields, and readout limits.
- Check migration readinessReview canonical routes, redirects, generated files, ad paths, seller records, and analytics continuity before cutover.
- Check seller-path evidenceKeep seller authorization, seller records, SupplyChain paths, deal keys, and exceptions visible.
- Set deal readinessRecord floor inputs, sell-through state, refresh boundaries, renewal signal, and ready/revise/hold status.
- Track pacing and makegoodsRecord shortfalls, pauses, replacement inventory, buyer approvals, and final exception language.
- Align report fieldsPrepare package, placement, context, delivery, traffic-quality, outcome, and conclusion fields.
- Follow a campaign exampleConnect inventory contracts to export rows, readout language, and renewal decisions.
- Track follow-up readinessCarry archived issue IDs, owner actions, and launch gates into the next inventory handoff.
- Close status windowsCheck whether delayed lead, matchback, attribution, follow-up, or survey rows are ready for final readout wording.
- Register closeout rowsKeep maturity thresholds, excluded rows, allowed claims, and next review dates attached to the readout.
Readiness matrix
Each package should be easy to describe by reader task, eligible placement, and readout standard. That keeps ad operations, editorial judgment, and measurement interpretation in separate lanes.
| Context | Reader task | Eligible placements | Buyer value | Readout boundary |
|---|---|---|---|---|
| Homepage and archive discovery | Find the right desk, guide, or case study. | home-leaderboard, home-rail-1, archive-leaderboard, native-sponsored-card | Broad reach across professional readers entering the publication. | Report delivery, visible placement, device class, and downstream site actions without treating discovery clicks as causal lift. |
| Measurement Science Desk | Choose methods, test designs, and readout language. | archive-leaderboard, article-inline-1, article-inline-2, article-rail-1, post-content | High-context alignment for analytics, experimentation, MMM, survey, and data-quality buyers. | Separate exposure quality and qualified visits from proof of incremental sales. |
| Media Framing Desk | Audit headlines, source balance, base rates, and comparison classes. | archive-leaderboard, article-inline-1, native-sponsored-card, post-content | Contextual adjacency to readers who value source quality and careful interpretation. | Use engagement and qualified traffic as interest signals, not as proof that reader beliefs changed. |
| Source and Vendor Evaluation Desk | Review vendor claims, research reports, dashboards, and budget evidence. | archive-leaderboard, article-inline-1, article-rail-1, native-sponsored-card, post-content | Strong fit for research software, data collaboration, governance, insight, and advisory buyers. | Report by page context and placement group so performance is not pooled across unlike reader intents. |
| Case Study Library | Study practical measurement failure modes before changing spend or process. | archive-leaderboard, case-inline-1, case-rail-1, post-content | Deep-reading context for buyers connected to analytics education, experimentation, and measurement services. | Compare case-study delivery against guide-library delivery before over-reading a small placement sample. |
| Guide Library | Use templates, glossaries, worksheets, source pages, and planning checklists. | archive-leaderboard, article-inline-1, article-inline-2, native-sponsored-card | Evergreen pages with repeat team use and clear professional intent. | Keep report language tied to content context, creative, and reader action rather than broad brand claims. |
Package contracts
These package IDs and deal keys are the stable handoff between a proposal, ad operations, and campaign reporting. They keep contextual packages separate from placement IDs so a flight can be trafficked cleanly without changing the reader-facing page. For the full audience-fit, activation, launch, reporting, and renewal sequence, use the private marketplace readiness index; for buyer-facing definitions of package IDs, deal keys, floors, reporting cadence, creative handoffs, and destination readiness, use the private marketplace buying terms guide; for one proposal record before pricing or trafficking, use the advertiser intake worksheet; for the buyer-facing package scope and renewal evidence, use the private marketplace package brief template; for the final proof, identifier, placement, field, exception, and renewal-threshold gate before activation, use the private marketplace deal review checklist; for a launch-ready, revise, or hold decision, use the campaign readiness dashboard; for floor logic, sell-through fields, refresh boundaries, and package pricing readiness, use the ad yield and deal-readiness checklist; for export definitions and conclusion language, use the private marketplace reporting field dictionary; for a full example, use the private marketplace campaign walkthrough; for sample export rows, use the private marketplace readout export sample; for package performance language, use the private marketplace package performance readout; for readout meeting notes, use the campaign reporting worksheet; for renewal decisions, use the private marketplace renewal scorecard; for unresolved weak lanes, use the campaign issue log and renewal register; for final renew, revise, retest, or hold wording, use the campaign renewal memo template; for carry-forward decision records, use the campaign renewal evidence archive; for next-flight owner actions and gate dates, use the campaign renewal follow-up tracker; for delayed outcome maturity, use the campaign status-window closeout checklist; for exportable closeout rows, use the campaign status-window closeout register.
| Package ID | Deal key | Eligible placements | Reporting key | Readout boundary |
|---|---|---|---|---|
| measurement-science-desk | mp-msd-pmp | archive-leaderboard, article-inline-1, article-inline-2, article-rail-1, post-content | package.measurement_science_desk | Report guide-group response, qualified traffic, and lead quality separately from causal lift. |
| media-framing-desk | mp-mfd-pmp | archive-leaderboard, article-inline-1, native-sponsored-card, post-content | package.media_framing_desk | Read engagement as source-interest and context-fit evidence, not as proof that beliefs changed. |
| source-vendor-evaluation-desk | mp-sve-pmp | archive-leaderboard, article-inline-1, article-rail-1, native-sponsored-card, post-content | package.source_vendor_evaluation_desk | Keep vendor-evaluation delivery separate from broad publication delivery and read lead quality by destination. |
| case-study-library | mp-csl-pmp | archive-leaderboard, case-inline-1, case-rail-1, post-content | package.case_study_library | Compare case-study readers with guide-library readers before judging learning or demand signals. |
| guide-library | mp-gdl-pmp | archive-leaderboard, article-inline-1, article-inline-2, native-sponsored-card | package.guide_library | Separate checklist, glossary, worksheet, and template contexts before pooling performance. |
| buyer-readiness | mp-brf-pmp | archive-leaderboard, article-inline-1, native-sponsored-card | package.buyer_readiness | Read response as buying-process interest, then connect outcomes to the agreed proposal brief. |
Deal-readiness fields
Before a package is priced or renewed, the buyer and publisher should be able to see the evidence that connects reader context, eligible supply, seller authorization, floor logic, page implementation, reader-experience budget, migration state, and reporting fields. The programmatic inventory QA checklist checks placement contracts before launch; the ad experience and page-speed budget checklist checks ad load, layout stability, lazy loading, refresh rules, and script weight; the publication migration readiness checklist checks canonical routes, redirects, ad paths, generated files, and analytics continuity before a cutover changes the reporting baseline; the supply path transparency checklist checks authorized seller rows, seller disclosures, SupplyChain paths, deal keys, and exceptions; the ad yield and deal-readiness checklist is the companion worksheet for floor and renewal readiness.
| Field | Use before pricing | Readout boundary |
|---|---|---|
| Eligible supply | Forecast impressions by package, placement ID, device class, and week. | Do not price from pooled run-of-publication volume. |
| Sell-through state | Separate reserved, sold, unsold, house, remnant, and makegood supply. | High sell-through supports scarcity, not business impact. |
| Floor rationale | Record context scarcity, viewability, buyer fit, direct opportunity cost, and renewal evidence. | A floor protects package quality; it is not a performance guarantee. |
| Refresh rule | Name pageview-only, viewability-qualified optional, or no-refresh status by placement. | Refreshed impressions should be visible if used in delivery reports. |
| Renewal signal | Name the primary renewal evidence before launch: delivery quality, qualified visits, lead quality, or designed lift. | Do not let the report choose the strongest-looking metric after the flight. |
Placement contracts
| Placement ID | Format | Primary context | Accepted sizes | Reporting key |
|---|---|---|---|---|
| home-leaderboard | Leaderboard | Homepage below the opening feature. | 970x250, 970x90, 728x90, 468x60, 320x100, 320x50 | home.discovery.leaderboard |
| home-rail-1 | Homepage rail | Desktop rail beside homepage reader-guide modules. | 300x600, 300x250 | home.discovery.rail_1 |
| archive-leaderboard | Leaderboard | Article archives, topic pages, case-study index, and buyer reference pages. | 970x250, 970x90, 728x90, 468x60, 320x100, 320x50 | archive.discovery.leaderboard |
| article-inline-1 | In-article display | Upper body placement inside long-form guides and source pages. | 728x90, 336x280, 300x250, 320x100 | article.body.inline_1 |
| article-inline-2 | In-article display | Lower body placement after the second analysis block. | 728x90, 336x280, 300x250, 320x100 | article.body.inline_2 |
| article-rail-1 | Right rail | Desktop rail beside articles, guides, and source pages. | 300x600, 300x250, 160x600 | article.rail.primary |
| case-inline-1 | Case-study display | Case-study body before the statistical result. | 728x90, 336x280, 300x250, 320x100 | case.body.inline_1 |
| case-rail-1 | Case-study rail | Desktop rail beside worked measurement examples. | 300x600, 300x250 | case.rail.primary |
| post-content | Post-content display | After primary article, guide, or case-study content. | 970x90, 728x90, 336x280, 300x250, 320x100 | global.after_content |
| native-sponsored-card | Native card | Clearly labeled partner card in relevant article or guide contexts. | Fluid native, 300x250 fallback | native.contextual.card |
Responsive inventory rules
Suppress empty breakpoints
If a placement has no configured size for the current viewport, it should be hidden rather than rendered as an empty or desktop-only unit.
Preserve size mapping
Leaderboard, inline, post-content, and native units keep explicit desktop, tablet, and mobile size sets for trafficking and reporting.
Compare like with like
Readouts should separate placement ID, package ID, device class, and creative size before judging response quality.
Track experience exceptions
Ad-load limits, heavy creative, refresh changes, and layout exceptions should be recorded before they affect campaign interpretation.
Private marketplace checklist
Package definition
Name the content desk, included URLs or URL patterns, eligible placement IDs, device classes, and any page types excluded from the campaign.
Creative handoff
Include creative size, brand name, click URL, destination page, flight dates, UTM structure, backup creative for mobile display, the acceptance status from the creative asset checklist, and the destination decision from the landing page launch QA worksheet.
Readout plan
Agree on delivery, viewability, click, qualified-visit, lead, or survey signals before launch, then state which signals are diagnostic rather than causal.
Campaign handoff fields
| Field | Why it matters | Example value |
|---|---|---|
| Campaign name | Connects creative, placement, invoice, and readout records. | Q3 measurement-desk awareness flight |
| Buying path | Sets whether the campaign runs as open programmatic, private marketplace, or direct sponsorship. | Private marketplace |
| Package | Defines the reader context and content desk. | Measurement Science Desk |
| Placement IDs | Prevents vague trafficking instructions and enables clean reporting. | article-inline-1, article-rail-1, post-content |
| Creative sizes | Confirms the formats that can render without layout surprises. | 728x90, 300x250, 300x600, 320x100 |
| Landing page | Ensures the destination matches the professional reader context. | Product page, research report, webinar, or demo page |
| Readout decision | Names what the campaign is supposed to inform. | Renew package, test creative, qualify lead channel, or compare desk context |
| Comparison | Prevents one placement or creative from being judged without a baseline. | Prior flight, run-of-publication baseline, or matched desk package |
Reader-first boundary
Advertising can help fund a serious publication without changing the job of the page. Measurement Press's ad inventory should remain plainly labeled, contextual, and readable. Campaign reports should be useful about delivery quality and reader response while leaving causal claims to tests designed for that question.
Related references
Use the workflow above for inventory operations, then use the publication migration readiness checklist before a domain, template, or ad-path cutover. Use the advertiser FAQ for proposal fields, the private marketplace readiness index for the full buyer handoff, the private marketplace buying terms guide for deal definitions, the advertiser intake worksheet for the proposal record, the package brief template for buyer-facing scope and renewal evidence, the deal review checklist for the activation approval gate, the campaign readiness dashboard for launch approval, and the contextual campaign brief template before trafficking. After results arrive, use the private marketplace campaign walkthrough, private marketplace readout export sample, package performance readout, campaign reporting worksheet, renewal scorecard, campaign issue register, renewal memo template, renewal evidence archive, renewal follow-up tracker, status-window closeout checklist, and status-window closeout register to keep the readout bounded across flights and ready for the next launch.