Buyer readiness
Programmatic inventory QA checklist
A package can look credible in a media kit and still fail in trafficking if the placement IDs, size maps, labels, reporting keys, and page behavior are not checked before launch.
Use this checklist when a publisher, buyer, or operations team needs to know whether display, native, right-rail, and private marketplace inventory is clean enough to sell, traffic, report, and renew without guessing. The goal is not to promise outcomes. The goal is to make every impression traceable to a reader context, placement contract, creative size, and reporting lane.
Preflight checks
Run preflight before a proposal becomes a live campaign. The review should identify whether the package is ready, needs a trafficking fix, needs a reporting fix, or should stay out of market until the source fields are complete.
| Check | Ready evidence | Hold or fix when |
|---|---|---|
| Placement identity | Every visible unit has a stable placement ID that appears in the media kit, inventory matrix, ad config, and reporting dictionary. | The same unit is described by different names across proposal, page, and report fields. |
| Format and size map | The accepted sizes match the placement contract by desktop, tablet, and mobile viewport. | A creative can be sold into a size the page cannot render cleanly. |
| Plain labeling | Every paid unit is labeled as an advertisement, sponsored module, or sponsor placement in visible page copy. | The label is hidden, ambiguous, or separated from the paid unit. |
| Reader context | The package names the desk, page type, guide set, or case-study group that makes the inventory relevant. | The campaign is sold as a contextual package but trafficked as unclear run-of-publication delivery. |
| Reporting key | Placement, package, creative, device, context, and destination fields can be joined after launch. | The report can only show total impressions, clicks, or leads with no placement-level source trail. |
| Reader experience | Ad load, spacing, mobile behavior, and rail behavior preserve the page's reference value. | Units push content unpredictably, crowd the opening context, or create a layout shift that changes reading flow. |
Page implementation QA
1. Confirm the page contract.Open the live or preview page and record each placement ID, visible label, format, and location. The page should match the media kit and inventory readiness matrix without needing verbal clarification.
2. Test breakpoints before trafficking.Check desktop, tablet, and mobile widths. Rail units should not create empty mobile regions. Inline, leaderboard, native, and post-content units should keep their intended size family and spacing.
3. Keep labels attached.The label should remain close to the paid unit after responsive changes, creative loading, or placeholder rendering. A reader should not have to infer whether a module is editorial or paid.
4. Preserve the reporting grain.Do not collapse package, placement, device, creative size, page context, and destination into one row before the first readout. Aggregation can happen later; missing fields cannot be reconstructed reliably.
5. Note exceptions before launch.If a unit is suppressed on mobile, excluded from a package, held for house inventory, or missing a size, write that exception into the campaign handoff before delivery starts.
Trafficking QA
A clean launch connects the buyer brief, page placement, creative file, tracking values, and report output. Use this table before the campaign goes live.
| Field | What to check | Why it matters |
|---|---|---|
| Campaign and deal name | Buyer, package ID, quarter, objective, and buying path are visible. | Prevents proposal, trafficking, invoice, and report records from drifting apart. |
| Package ID | The package matches the reader job and eligible URL set. | Keeps contextual buying from turning into broad pooled delivery. |
| Placement IDs | Only approved units are included, with device eligibility and size rules preserved. | Stops unavailable or wrong-format inventory from entering the flight. |
| Creative files | Display sizes, native fields, backup mobile assets, click URL, and destination page pass the creative asset acceptance checklist. | Reduces launch delays and keeps creative performance readable. |
| Tracking values | UTM values, placement IDs, creative IDs, destination IDs, and campaign IDs pass the campaign tagging QA checklist. | Preserves the source trail for traffic, lead, and matchback analysis. |
| Destination readiness | The landing page matches the offer, loads cleanly, and can capture lead source fields if needed. | Prevents weak destination execution from being misread as weak inventory. |
| Primary signal | The brief names whether renewal depends on delivery quality, qualified visits, lead quality, brand movement, or a designed lift read. | Stops the readout from choosing the strongest-looking metric after the flight. |
Reportability checks
A campaign is not ready to sell as a clean private marketplace lane unless the readout can separate where delivery happened, what rendered, what a reader did next, and what the evidence can support.
| Report slice | Minimum fields | Do not conclude from this alone |
|---|---|---|
| Delivery | Package ID, placement ID, device class, creative size, rendered impressions, measurable impressions, and viewable impressions when available. | That delivery quality caused downstream outcomes. |
| Context | Desk, page group, article type, URL or URL group, and package inclusion status. | That one strong page represents the whole package. |
| Traffic | Clicks, engaged sessions, return visits, destination actions, invalid-traffic review, and qualified-visit rule. | That traffic volume is the same as incremental demand. |
| Lead quality | Form source, duplicate rule, disqualification reason, qualification status, follow-up status, and stage movement where available. | That form fills created new pipeline. |
| Creative response | Creative ID, message theme, format, destination, active dates, and rotation changes. | That the highest CTR creative is the strongest business choice. |
| Comparison | Prior flight, matched context, reserved holdout, or a clear note that no comparison was designed. | That descriptive performance is causal lift. |
Decision bands
| Status | Use when | Next action |
|---|---|---|
| Ready to traffic | Placement identity, size maps, labels, creative assets, tracking values, and reporting keys are complete. | Launch with the agreed report slices and exception log. |
| Ready after fix | The package is sound, but a size, label, tracking value, or destination field needs correction. | Fix before launch and note the change in the campaign handoff. |
| Report-only flight | Delivery can run, but no comparison or buyer-side outcome will be available. | Use descriptive language and avoid renewal claims stronger than observed response. |
| Hold for rebuild | The package cannot be joined to stable placement, device, creative, context, or report fields. | Rebuild the package contract before selling it as private marketplace inventory. |
Pair with
Use this QA checklist with the media kit for placement specs, the inventory readiness matrix for package contracts, the ad yield and deal-readiness checklist before pricing, the contextual campaign brief template before launch, the private marketplace reporting field dictionary for field names, the private marketplace readout export sample for row-level checks, and the private marketplace renewal scorecard before renewal language is written.
Takeaway
Clean inventory is a chain of small visible facts: a placement ID, an accepted size, a readable label, a reader context, a destination, and a reporting key. If those facts survive launch, the final readout can stay useful without overstating what the campaign proved.