Buyer readiness

Private marketplace campaign walkthrough

Organization byline: Measurement Press editorial desk. This page does not list an individual author or reviewer. Read the editorial method and corrections policy.

About 14 min read

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.

Think of the example as a renewal meeting after a campaign has already run. The buyer wants to know whether the contextual package is worth another flight. The publisher needs to answer with the evidence it actually has: package scope, placement delivery, row-level response, lead-status handoff, and a clear warning about what the comparison cannot prove.

The campaign in one record

Simulated Worked Example — not a real campaign report or benchmark. The example uses a contextual package for readers comparing measurement methods. The values below are fictional structure examples used to demonstrate a reproducible readout path.

Identifier boundary: measurement-science-desk and mp-msd-pmp are simulated internal record values. In production, preserve the ad server's canonical Deal ID alongside any publisher package key; do not relabel an internal package name as the platform's Deal ID.

Simulated worked example: roll up the six rows

Roll up the rows before ranking placements. This calculation is deliberately inspectable: every numerator comes from the row-level table above, and the denominators make clear where missing status or mixed formats limits the conclusion.

Assumptions and limits: the six rows are fictional, complete for this example, deduplicated, and aligned to one reporting window; viewability is impression-weighted; qualified visits use one stable rule; qualified and disqualified statuses are resolved while missing status is excluded from the resolved-status denominator. The example contains no spend, revenue, uncertainty interval, randomized holdout, or protected counterfactual. It does not control for audience selection, repeat users, creative rotation, auction competition, or destination friction. Replace every illustrative value with a governed export before using the walkthrough for a real renewal.

Evidence path and claim boundary

A campaign walkthrough is useful only if each stage says what it can support. The same result can justify a renewal action, a mobile fix, or a cleaner test plan. It should not quietly become proof of incremental demand when the comparison was only directional.

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.

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.

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.

Three possible readings

The same rows can produce very different claims. The right readout keeps the evidence useful while leaving the comparison limit visible.

Simulated worked example: calculate the evidence ceiling

This is a simulated worked example, not a real buyer, publisher, or campaign report. The calculation uses the six fictional rows above so a reader can reproduce the renewal discussion from visible denominators instead of accepting a favorable total on trust.

Assumptions and limits: rows are fictional, complete for this example, deduplicated, and measured over one reporting window; viewable rates are treated as row-level rates and weighted by impressions; qualified visits are counted once under an unstated example rule; and missing lead status is excluded from the resolved-status denominator. These calculations are a reproducible method illustration, not a benchmark or forecast. If the package, device mix, destination, status rule, maturity window, or comparison design changes, rerun the calculation.

Preserve the source-field handoff

Before renewal language is written, keep one joinable record across the deal, ad-server export, destination URL, and outcome system. At minimum, retain campaign_id + package_id + deal_id + placement_id + creative_id + destination_url + flight_start + flight_end, and use consistent campaign parameters for the destination. Do not pass email addresses, usernames, or other person-identifying values in ad-request parameters. If any key changes mid-flight, split the analysis or document the change rather than silently combining unlike rows.

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.

Renewal decision

The scorecard should turn evidence into a next action, not a retroactive justification for the most favorable metric.

Buyer-facing close

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 archive follow-up fields 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.