Buyer FAQ
A clearer brief before a campaign is priced.
Use this page to decide whether Measurement Press is a fit, what a proposal should include, how availability is scoped, and which reporting claims can be made after a flight. It is the compact handoff between the advertising overview, audience intent map, media kit, inventory readiness matrix, launch checklists, and reporting references.
At a glance
Best-fit buyers
Analytics, research, experimentation, data infrastructure, governance, professional learning, and evidence-led services with a clear source trail.
Reader context
Professionals comparing measurement methods, media claims, source quality, vendors, reports, and budget evidence.
Usual formats
Leaderboard, in-article display, right rail, post-content display, and clearly labeled native cards.
Readout standard
Delivery and response signals stay separate from causal claims unless the campaign includes a designed comparison.
Proposal one-sheet
A proposal should define the reader task, inventory lane, and measurement language before launch. That makes the campaign easier to traffic and harder to over-read after results arrive.
| Field | What to specify | Clean example |
|---|---|---|
| Buyer category | Business category, product type, and reader problem the campaign helps solve. | Measurement platform for teams planning incrementality tests. |
| Campaign objective | The decision the flight should inform. | Introduce a guide, qualify a webinar audience, test a message, or compare desk fit. |
| Package ID or deal key | The stable package contract used for proposal, trafficking, and reporting. Use the private marketplace readiness index when the buyer needs the full audience-fit, activation, reporting, and renewal sequence. Use the buying terms guide when the proposal needs plain definitions for package IDs, deal keys, floors, cadence, and readout boundaries. Use the advertiser intake worksheet when those fields need to become one proposal record, the deal review checklist before activation approval, then the campaign readiness dashboard before launch approval. | measurement-science-desk or mp-msd-pmp. |
| Eligible context | Desk, guide group, case-study group, article set, URL pattern, or run of publication. | Measurement Science Desk plus private marketplace checklist pages. |
| Placement mix | Placement IDs, formats, device classes, and whether native is included. | article-inline-1, article-rail-1, post-content, and optional native-sponsored-card. |
| Deal readiness | Eligible supply, sell-through state, floor logic, refresh boundary, and renewal signal. | Ready to price after context, supply, creative, and reporting fields are complete. |
| Creative handoff | Creative sizes, brand name, destination URL, UTM structure, flight dates, backup mobile assets, and acceptance status. | 728x90, 300x250, 300x600, 320x100, report landing page, final click URLs, and approved creative IDs. |
| Primary signal | The metric lane that should lead the readout. | Qualified visits, lead quality, engaged sessions, survey result, or delivery quality. |
| Comparison rule | Whether results are compared with a prior flight, matched context, holdout, or no baseline. | Matched guide-library context from the prior quarter. |
| Readout limit | The strongest claim the report is expected to support. | Descriptive performance, directional comparison, or designed lift estimate. |
Campaign fit FAQ
What campaigns fit best?
Campaigns that help readers make better professional judgments: measurement explainers, research reports, analytics tools, data-quality resources, planning templates, events, and services tied to evidence quality. Use the source-quality standards and example gallery before pricing a native or private marketplace package.
What campaigns are weak fit?
Creative built around exaggerated claims, hidden sponsorship, broad consumer impulse, unclear lead capture, or claims that would conflict with the reader's need for careful evidence.
Can buyers choose specific contexts?
Yes. Packages can be scoped by desk, guide type, case-study library, URL pattern, placement group, device class, or run of publication. The package should name included and excluded contexts before launch.
Are native units available?
Yes, in limited contexts. Native placements should be clearly identified, contextually useful, and separate from editorial judgment. Display units remain available across more page types.
Operations FAQ
| Question | Answer |
|---|---|
| What is needed before launch? | Final creative, destination URLs, flight dates, UTM values, buyer contact, placement scope, primary signal, and the comparison rule for the readout. The private marketplace deal review checklist checks proof, identifiers, placement IDs, reporting fields, exceptions, and renewal thresholds before activation. The campaign readiness dashboard puts package proof, inventory contracts, creative approval, destination QA, reporting fields, and readout limits into one ready, revise, or hold view. |
| How is availability scoped? | Availability is tied to reader context, placement mix, device class, and page type. Direct sponsorships should stay limited enough that the page remains useful as an editorial reference. |
| What terms should be locked before a private marketplace buy? | Package ID, deal key, placement IDs, floor rationale, flight window, creative handoff, destination readiness, reporting cadence, primary signal, comparison rule, and readout boundary. The private marketplace buying terms guide defines each field in buyer-facing language. |
| What reporting slices are useful? | Placement group, page context, creative size, message theme, destination, device class, qualified visit, lead status where available, and designed comparison when present. Use the contextual package proof checklist before the package is priced, the contextual package proof sheet before the launch handoff, the private marketplace reporting field dictionary when package and placement field names need to line up, the campaign reporting sample when the readout needs a shared table structure, and the campaign reporting terms glossary when terms need clearer boundaries. |
| Can a campaign prove incremental lift? | Only when a holdout, matched baseline, geo design, or other comparison method is set before launch. Without that design, the readout should stay descriptive. |
| How should buyer-side data be used? | Buyer-side lead status, CRM stage, or landing-page completion can improve the readout when definitions are agreed before launch and matched back to the correct package and creative. Use the landing page launch QA worksheet before the destination receives paid traffic, then use the landing page and lead quality checklist for form fills, lead filters, and sales follow-up. Use the identity matchback checklist when the report relies on matched conversions or offline outcomes. |
| Where do creative specs live? | The media kit lists package IDs, deal keys, placement IDs, ad-unit paths, accepted sizes, contextual package examples, and standard reporting handoff expectations. The creative asset acceptance checklist defines what display, native, destination, and source-trail fields should be approved before trafficking. The landing page launch QA worksheet checks the destination page, forms, redirects, source fields, and routing before paid traffic goes live. The private marketplace reporting field dictionary defines the package, placement, context, delivery, and conclusion fields that should travel with those specs. The audience intent map explains which reader jobs support each package lane. |
Clean handoff path
1. Confirm fit
Match the buyer, offer, and destination to a reader task rather than a broad audience label.
2. Lock context
Name the desks, page types, placement IDs, device classes, and exclusions that define the package.
3. Traffic cleanly
Approve final assets, click URLs, UTM values, dates, backup mobile assets, and creative IDs in one handoff.
4. Read results carefully
Separate delivery quality, reader response, lead quality, and designed lift so the report stays useful.
Best next step: Start with the audience intent map for package fit, then use the source-quality standards for offer, destination, native-card, and readout fit, the example gallery for accepted and revise patterns, the media kit for specs, this page for the proposal brief, the readiness index for the full private marketplace handoff, the buying terms guide for package and deal definitions, the advertiser intake worksheet for the proposal record, the deal review checklist before activation approval, the campaign readiness dashboard for launch approval, the inventory readiness matrix for trafficking contracts, and the reporting field dictionary before readout language is finalized.
Related buyer references
Use the advertising overview for audience fit, the audience intent map for package proof, the advertiser source-quality standards for offer and destination fit, the native card and landing page example gallery for accepted and revise patterns, the media kit for package examples and creative specs, the private marketplace readiness index for the full package handoff, the private marketplace buying terms guide for deal definitions, the advertiser intake worksheet for one proposal record, the private marketplace deal review checklist before activation approval, the campaign readiness dashboard for a ready, revise, or hold launch decision, and the inventory readiness matrix for placement contracts. Use specialized launch or measurement checklists when the campaign depends on native creative, a landing page, lead quality, matchbacks, or designed lift.