Buyer readiness
Contextual package proof sheet
Organization byline: Measurement Press editorial desk. This page does not list an individual author or reviewer. Read the editorial method and corrections policy.
About 10 min read
A contextual package is easier to buy, traffic, measure, and renew when the proof fits on one page before the campaign launches.
Use this sheet to turn the media kit, inventory matrix, and package checklist into a shared handoff for buyers, ad operations, and analysts. The sheet should make the package useful without asking a future report to invent the context, comparison, or claim boundary after results arrive.
When to use it
The proof sheet belongs between a package idea and a campaign brief. It is short enough for proposal review but specific enough to become the trafficking and reporting contract.
| Moment | Decision it supports | What must be settled | What stays out |
|---|---|---|---|
| Proposal review | Whether the buyer and package fit the reader job. | Package thesis, eligible contexts, clean-fit category, and destination fit. | Outcome claims that require campaign results or a designed comparison. |
| Trafficking handoff | Whether the campaign can launch without interpretation. | Package ID, deal key, placements, sizes, device rules, creative assets, and exclusions. | Broad audience labels that cannot be mapped to page or placement rules. |
| Analytics setup | Whether the readout can separate delivery, context, creative, and outcome fields. | Reporting grain, UTM structure, source-trail fields, primary signal, and comparison rule. | Post-campaign metric hunting or pooled response totals with no context trail. |
| Renewal meeting | Whether the next action is renewal, creative revision, package change, or stronger testing. | Decision rule, quality flags, claim boundary, and next-test trigger. | Lift language when the campaign only has descriptive response evidence. |
The one-page sheet
Complete the fields before launch. If a field is unknown, mark it as unavailable and state how that limits the readout.
| Field | Write this down | Why it matters |
|---|---|---|
| Package ID and deal key | The stable package ID, deal key, buying path, and reporting key. | Connects proposal, ad operations, delivery, export rows, and invoice records. |
| Package thesis | One sentence naming the reader job and the buyer problem the creative helps address. | Prevents a contextual package from turning into generic reach language. |
| Eligible inventory | Included desks, URL groups, article types, placement IDs, ad sizes, device classes, and exclusions. | Makes delivery auditable against the sold context. |
| Creative and destination fit | Message theme, creative size set, landing-page type, destination promise, and any unsupported creative uses. | Separates context fit from message, format, and landing-page effects. |
| Reporting grain | The row level for readout exports: package by week, placement by device, creative by destination, or outcome status by source trail. | Keeps final reporting detailed enough to explain the result. |
| Primary signal | The signal the campaign is meant to inform: delivery quality, qualified visits, lead quality, survey movement, or designed lift. | Stops a report from choosing the strongest-looking metric after the flight. |
| Comparison rule | No comparison, prior flight, matched context, matched market, holdout, or survey design. | Sets the strongest conclusion language the readout can support. |
| Renewal decision rule | The action criteria for renew, revise creative, shift mix, retest, add lift test, or pause. | Turns the report into a decision rather than a slide deck of favorable metrics. |
Filled sheet example
This example shows format, not a performance benchmark. Replace the sample values with the actual package, creative, and reporting terms for the campaign being reviewed.
| Sheet field | Example value | Claim boundary |
|---|---|---|
| Package | measurement-science-desk, mp-msd-pmp, private marketplace. | Identifies the buying context; it does not prove audience composition. |
| Package thesis | Reach readers choosing measurement methods or auditing campaign readout language. | Supports contextual fit and proposal relevance. |
| Eligible inventory | Measurement desk guides, article-inline-1, article-inline-2, article-rail-1, post-content, desktop and mobile inline sizes. | Delivery outside these contexts should be reported as an exception. |
| Creative fit | Planning guide, webinar, benchmark explainer, or product page that helps analysts choose or review methods. | A helpful destination can improve response quality; it is not proof of media lift. |
| Reporting grain | Package by guide group, placement ID, device class, creative size, destination, and qualified-visit status. | Rows below minimum delivery should be pooled or treated as directional. |
| Primary signal | Qualified visits and lead-quality status, with viewability and invalid-traffic review as exposure-quality checks. | Observed response should not be described as incremental demand. |
| Comparison rule | Prior measurement-desk flight; no protected holdout. | Supports directional renewal language, not causal lift language. |
| Renewal rule | Renew if delivery matched the package, qualified visits concentrated in the agreed contexts, and lead status is complete enough to interpret. | If the next decision needs lift language, plan a holdout or matched baseline before the next flight. |
Evidence trail and a simulated audit gate
The sheet separates contextual fit from delivery and outcome claims. Google Ads contextual-targeting guidance describes matching page content to selected topics or keywords; that match does not prove that every visitor has the intended identity, need, or buying authority. For the operational handoff, Google Ad Manager key-value guidance explains that page or section values can be included in ad tags, while Ad Manager reporting guidance warns that keys need reporting configuration and that overlapping values can complicate interpretation. The MRC Viewable Ad Impression Measurement Guidelines keep served, viewable, non-viewable, and undetermined states distinct. Together, these sources support a traceable package record; they do not establish demand, audience quality, or incremental lift.
| Source boundary | Supports in this sheet | Still requires local evidence |
|---|---|---|
| Contextual targeting guidance | Record the page or topic context that defines package eligibility. | That the context maps to the intended reader job or produces qualified demand. |
| Key-value guidance | Specify the package, page, placement, and reportable values needed for a joinable handoff. | That the values are defined, privacy-safe, reportable, and present after trafficking. |
| Ad Manager reporting guidance | Choose a reporting grain and check undefined values and overlapping keys before interpreting rows. | That the export is complete, comparable, or sufficient for a renewal or lift claim. |
| MRC viewability guidance | Keep served, viewable, non-viewable, invalid, and undetermined states distinct in the sheet. | Actual pixel/time viewability, invalid-traffic filtration, or package effectiveness. |
Simulated worked example — not a real package, campaign result, or forecast: Assume a proof sheet contains 12 planned placement records. Nine include the reader job, included page group, placement ID, creative destination, reporting key, and comparison rule; three are missing at least one of those fields. The package is Revise, not Ready: 9 / 12 = 75% complete and 3 / 12 = 25% incomplete. The missing records must be named before pricing or renewal language is strengthened. These invented values illustrate the method only; they are not evidence about Measurement Press inventory.
| Gate | Simulated calculation | Decision | Limit |
|---|---|---|---|
| Record completeness | 9 complete records ÷ 12 planned records = 75% | Revise the handoff before approval | Completeness is not contextual relevance, viewability, or buyer quality. |
| Missing-record share | 3 incomplete records ÷ 12 planned records = 25% | List the missing fields and hold back stronger claims | Missing records may be systematically different; do not treat them as representative. |
| Conclusion ceiling | No protected comparison in the simulated sheet | Report delivery, context, and field completeness | Clicks, leads, and viewable impressions alone do not establish incremental impact. |
Joinability audit: can the sheet survive the report?
The proof sheet is only useful if the fields written before launch can be joined after launch. Google Ad Manager reporting guidance says a targeting key must be configured for reporting before it can be included, and undefined values will not appear even when the key itself is reportable. That makes field presence a real audit condition, not a formatting preference. MRC guidance also keeps viewable, non-viewable, and undetermined impressions separate; collapsing those states can make a clean-looking package report impossible to interpret.
Simulated joinability audit - not a real package or campaign: Assume 6 field groups are required for each proof-sheet row: package/page ID, placement ID, creative and destination ID, reporting key/value, flight/device grain, and comparison rule. In a 6-row handoff, suppose 5 rows have all 6 groups and 1 row is missing its reporting key/value. Field-group coverage is 35 / 36 = 97.2%, but fully joinable rows are 5 / 6 = 83.3%. If the missing key belongs to the only row for one page group, page-level comparison coverage falls to 4 / 6 = 66.7%. The correct decision is Revise: repair the key/value definition and confirm that it is reportable before ranking contexts or using outcome language.
| Audit step | Reproduction | Pass rule | What changes if it fails |
|---|---|---|---|
| Row-level join | Count rows with all 6 field groups / 6 rows | 6 / 6 = 100% before activation | Hold the package or label the affected rows as unjoinable. |
| Field-group coverage | 35 populated groups / 36 expected groups | Record the missing group by row, not only as an overall percentage. | Do not treat 97.2% coverage as evidence that every context is comparable. |
| Comparison coverage | 4 comparable page-group rows / 6 total rows | Use only the covered rows for descriptive comparison. | Do not call a page group the winner when its join field is missing. |
| Claim ceiling | No protected comparison is created by field completeness alone | Report delivery and data-quality status separately from outcomes. | Plan a holdout, matched market, or other design if the decision needs incrementality. |
To reproduce the audit, export one row per planned placement, mark each required field as present or missing, verify that the reporting key and value are defined and reportable, and calculate both complete-row coverage and field-group coverage. Keep the denominators visible. The example is intentionally small: real packages need a defined grain, exclusions, missingness review, and a documented treatment of undetermined viewability. These checks show data readiness; they do not prove audience quality, demand, or causal effect.
Decision block
Add a short decision block to the bottom of the sheet. This keeps the renewal meeting focused on the action the evidence can support.
Renew as soldUse when delivery matched the package, quality fields are complete, response fits the buyer's stated goal, and the recommendation does not require stronger causal language.
Renew with changesUse when the context is right but creative, destination, device mix, field completeness, or placement allocation needs a tighter second flight.
Retest or add lift testUse when the next budget decision needs incrementality, brand movement, or matched-market evidence that the first campaign was not designed to estimate.
Pause or rebriefUse when the package thesis, eligible inventory, creative fit, or reporting grain was unclear enough that the readout cannot support a confident renewal.
Buyer review questions
- Can the buyer explain why this reader context fits the offer without using generic reach language?
- Can ad operations traffic the package from the sheet without adding their own interpretation?
- Can analytics report package, placement, device, creative, destination, and outcome status separately?
- Does the comparison rule match the conclusion language expected in the readout?
- Is the renewal decision written before the campaign has a chance to favor one convenient metric?
Pair with
Use this sheet with the media kit for package IDs and placement specs, the inventory readiness matrix for deal keys and reporting keys, the audience intent map for reader-job proof, the contextual package proof checklist for package QA, the private marketplace package brief template for buyer-facing scope and renewal evidence, the contextual package proof export template when the handoff needs to become exportable fields, the ad yield and deal-readiness checklist for floor inputs, sell-through state, refresh boundaries, and renewal signals, the contextual campaign brief template for launch planning, the creative asset acceptance checklist before display or native assets are approved, the landing page launch QA worksheet before paid traffic reaches the destination, the private marketplace reporting field dictionary for stable field names, the private marketplace readout export sample for row-level exports, the campaign reporting worksheet for the readout meeting note, and the private marketplace renewal scorecard for final action language.