Buyer readiness
Private marketplace package performance readout
A private marketplace readout should help a buyer see whether the package delivered the promised context, which placements carried the response, whether outcomes were qualified, and what the evidence can fairly support.
Use this sample after the row-level export is complete. The values below are example values for report structure, not performance benchmarks. The goal is to show how a package performance narrative can stay useful without turning observed response into an unsupported lift claim.
Imagine the renewal meeting is two days away. The buyer wants to know whether the measurement-science package should be renewed, narrowed, retested, or turned into a formal lift design. The readout has to put package delivery, placement behavior, lead quality, and comparison limits on the same table before anyone writes the recommendation.
Readout frame
Open the report by naming the package, the decision, and the comparison limit. This keeps the strongest table cell from becoming the whole story.
| Readout field | Example value | Why it belongs first |
|---|---|---|
| Campaign objective | Drive qualified visits to a measurement planning resource. | Connects delivery and response to the buyer's stated job. |
| Primary package | measurement-science-desk | Shows the contextual package being judged. |
| Supporting package | buyer-readiness | Separates buyer-reference inventory from measurement-method inventory. |
| Eligible placements | article-inline-1, article-inline-2, article-rail-1, archive-leaderboard, native-sponsored-card | Keeps placement-level delivery visible before totals are averaged. |
| Primary signal | Qualified visits with lead-status handoff. | Prevents raw click volume from becoming the success metric. |
| Comparison rule | Prior contextual flight and matched guide group; no reserved holdout. | Sets directional language and blocks causal overstatement. |
| Decision this report can support | Renew, narrow package mix, revise creative, or plan a lift test. | Keeps the recommendation within the evidence level. |
Executive narrative
Package deliveryThe flight delivered primarily inside the measurement-science-desk package, with a smaller buyer-readiness component. The report can say the campaign reached the intended reader contexts because package IDs, placement IDs, and device classes were preserved.
Observed responseQualified visits were strongest in upper-body guide inventory, especially article-inline-1 within measurement planning and reporting contexts. That is useful directional evidence, not proof that the placement caused incremental demand.
Outcome qualityLead status was available for most reported form starts, which makes the readout stronger than a click or form-fill report. Missing and disqualified status still need to appear beside qualified outcomes.
Next decisionRenew a narrower measurement-science package, keep buyer-readiness inventory as a separate test lane, and add a protected comparison if the next budget decision needs lift language.
Those four statements are easier to defend when each evidence layer stays separate. Delivery proves the campaign reached the promised context. Exposure quality says whether the unit had a fair chance to be seen. Traffic and lead status describe observed response. The comparison rule decides whether the final language can be descriptive, directional, or causal.
Package and placement read
Read package performance at the placement and outcome level before ranking packages. Totals can hide a device, creative, or destination difference that changes the decision.
| Package ID | Placement ID | Device | Impressions | Viewable rate | Qualified visits | Lead-quality read | Fair conclusion |
|---|---|---|---|---|---|---|---|
| measurement-science-desk | article-inline-1 | desktop | 48,600 | 74% | 94 | 14 qualified, 6 disqualified, 2 missing | Strong observed response in upper-body guide context; preserve the placement and review creative mix before scaling. |
| measurement-science-desk | article-inline-2 | mobile | 32,400 | 66% | 47 | 5 qualified, 8 disqualified, 1 missing | Mobile traffic produced weaker qualification; inspect destination friction before calling the context weak. |
| measurement-science-desk | article-rail-1 | desktop | 26,900 | 68% | 22 | 4 qualified, 2 disqualified, 0 missing | Rail delivery supported desktop reach, but the smaller cell should not drive a budget shift alone. |
| buyer-readiness | archive-leaderboard | desktop | 21,800 | 62% | 18 | 3 qualified, 2 disqualified, 2 missing | Buyer-reference discovery created some response; read as package awareness, not lower-funnel impact. |
| buyer-readiness | native-sponsored-card | mobile | 12,300 | 70% | 33 | 6 qualified, 4 disqualified, 0 missing | Native response should be reported separately because format, copy, and reader intent differ from display. |
The package table should be read like a workflow, not a leaderboard. Clean the export, split package and placement rows, separate device and format behavior, check outcome quality, then write the comparison rule before the final recommendation. If any stage fails, fix the row or qualify the language before the memo is approved.
Outcome quality ladder
The narrative should climb only as far as the evidence allows. A report can have strong delivery evidence and still have weak outcome evidence.
| Evidence layer | What the report has | Useful statement | Limit to keep visible |
|---|---|---|---|
| Qualified delivery | Package IDs, placement IDs, sizes, device classes, and context groups. | The flight delivered within the agreed inventory and reader contexts. | Delivery quality does not prove downstream demand. |
| Exposure quality | Measurable and viewable rates by placement and device. | Measured exposure quality was stronger in upper-body guide inventory. | Viewability is an exposure condition, not a causal outcome. |
| Traffic quality | Qualified visits defined by engaged session, geography, and duplicate rules. | Observed visit quality differed by package, placement, device, and destination. | Qualified visits can still reflect selected high-intent readers. |
| Lead status | Qualified, disqualified, follow-up, and missing status fields. | The campaign produced a mixed lead-quality profile that should guide creative and destination decisions. | Incomplete status can change the interpretation. |
| Comparison strength | Prior contextual flight and matched guide group, but no protected holdout. | The result is directional and useful for a renewal or retest decision. | Do not call the difference lift without a stronger counterfactual. |
Decision language
Use wording that makes the evidence useful to a buyer without making it sound stronger than it is.
| Decision | Write this | Do not write this |
|---|---|---|
| Renew package | Renew the measurement-science-desk package for guide-context delivery and observed qualified traffic, with the same reporting fields preserved. | The package proved incremental demand. |
| Narrow placement mix | Keep article-inline-1 as a primary placement and retest lower-body and rail placements with comparable creative and device controls. | Article-inline-1 is always the best placement. |
| Revise creative or destination | Mobile response needs destination and form-friction review before media fit is judged. | Mobile readers rejected the offer. |
| Use native separately | Report native-sponsored-card response as a separate format lane because copy, layout, and reader intent differ from display units. | Native and display performance can be pooled into one placement ranking. |
| Add lift test | The next flight should reserve a holdout or matched-market design if the renewal question is incremental impact. | The descriptive readout is enough to justify lift language. |
Decision map for the sample readout
The final readout should sort each possible action by the evidence it actually has. This prevents one strong observed response cell from swallowing unresolved delivery, destination, or comparison limits.
| Candidate action | Evidence that supports it | Boundary to keep visible | Buyer-facing handoff |
|---|---|---|---|
| Renew a narrower measurement-science package. | Package and placement IDs are preserved, article-inline-1 shows the strongest qualified visit pattern, and lead status is mostly available. | The report still uses a prior flight and matched guide group, not a protected holdout. | Renew the stronger package lane while preserving the same reporting fields and comparison rule. |
| Review mobile destination and form friction. | Mobile article-inline-2 has lower qualification even though delivery and viewability are measurable. | The readout cannot tell whether the issue is context, creative, page speed, form design, or audience intent without a destination review. | Retest mobile after destination fixes instead of dropping the package only because the first mobile row looked weaker. |
| Report native response separately. | The native-sponsored-card row has a different format, copy environment, and reader intent than display units. | Pooling native and display rows would make the package ranking easier to read but less true. | Use native as its own format lane with separate creative and destination notes. |
| Plan a protected lift test for the next budget decision. | The descriptive readout is useful, but the renewal question is moving toward incremental impact language. | Observed qualified traffic is not the same as lift. | Reserve a holdout, matched market, or stronger baseline before the next report uses causal wording. |
| Hold unresolved rows from the headline conclusion. | Missing lead status and unresolved delivery questions remain visible in the table. | Incomplete rows can change the interpretation after closeout. | Keep unresolved rows in the appendix or issue register until an owner confirms the field. |
Buyer questions before renewal
- Which package IDs and placement IDs explain the recommendation?
- Did the strongest response come from the same reader context that justified the buy?
- Which result changes after separating device, creative size, and destination?
- How much lead status is missing, and would it change the renewal decision?
- Does the next decision require descriptive optimization, a matched baseline, or a designed lift test?
Readout close
Recommended buyer-facing closeThe campaign delivered the intended measurement-science context and produced useful observed response, especially in upper-body guide inventory. Because the comparison was directional rather than protected, the readout supports a narrower renewal and a stronger next-test design rather than a causal lift claim.
Pair with
Use this package readout with the private marketplace reporting field dictionary for package and placement fields, the private marketplace readout export sample for row-level exports, the private marketplace campaign walkthrough for the full readiness-to-renewal example, the campaign reporting sample for the full report structure, the private marketplace renewal scorecard for renewal decisions, the campaign issue log and renewal register when unresolved rows need owner actions before final wording, the campaign renewal memo template when the package narrative needs final renew, revise, retest, or hold language, the campaign renewal evidence archive when package limits must carry into the next flight, the outcome quality scorecard for lead-status interpretation, the minimum detectable effect planning checklist before a lift test, the contextual package proof sheet, private marketplace package brief template, and private marketplace deal review checklist for pre-launch package evidence, the media kit for package and placement definitions, and the inventory readiness matrix for placement contracts.