Media kit
Ad inventory built around careful readers.
Measurement Press offers provider-neutral display, native, and contextual packages for advertisers who want to reach professionals evaluating media framing, attribution, incrementality, MMM, lift tests, and research quality. Packages are organized around reader intent with stable IDs, deal keys, and reporting keys so buying, trafficking, and reporting can stay clear.
Buyer workflow
Use this as the short path from audience fit to a clean campaign readout.
- Confirm audience and package fitMatch the offer to reader jobs, clean-fit categories, and package lanes.
- Check source-quality fitConfirm the source trail, destination depth, native-card fields, and readout limit before pricing.
- Review proposal readinessCheck direct sponsorship and native proposals before they become package or launch records.
- Review creative examplesCompare accepted and revise patterns for native cards, landing pages, and readout language.
- Use the readiness indexSequence audience fit, package proof, activation, launch, reporting, and renewal in one handoff.
- Lock placement contractsUse stable package IDs, deal keys, placement IDs, sizes, and reporting keys before trafficking.
- Translate buying termsDefine package IDs, deal keys, floors, cadence, creative handoff, destination readiness, and readout boundaries.
- Complete advertiser intakeRecord objective, package lane, creative and destination handoff, floor inputs, cadence, and readout boundary.
- Write the package briefTie package IDs, reader context, placement scope, reporting grain, and renewal evidence together.
- Review the deal before activationCheck package proof, deal keys, placement IDs, reporting fields, exceptions, and renewal thresholds.
- Score launch readinessUse one ready, revise, or hold view for package proof, inventory, creative, destination, and reporting fields.
- Write the campaign briefSet context, creative handoff, primary signal, comparison rule, and readout limit before launch.
- Approve creative and destinationCheck display files, native fields, click URLs, UTM values, landing-page fit, and launch fields.
- Track pacing and makegoodsKeep delivery, buyer notices, replacement inventory, and readout notes aligned during the flight.
- Set the experience budgetCheck ad load, layout stability, lazy loading, refresh limits, and script weight before demand expands.
- Check migration readinessConfirm final routes, redirects, ad paths, feeds, seller records, and reporting baselines before cutover.
- Prepare reporting fieldsKeep package, placement, creative, device, traffic quality, outcome status, and conclusion fields aligned.
- Walk through a campaignTrace one contextual package from readiness record to export rows, readout language, and renewal.
- Write package performance languageTurn package delivery, placement response, outcome quality, and comparison limits into buyer-ready language.
- Decide renewal languageTurn delivery, quality, and comparison evidence into a renewal, creative-change, budget-shift, or lift-test decision.
- Track unresolved issuesAssign weak lanes, owners, due dates, retest rules, and claim boundaries before final renewal wording.
- Draft final renewal memoConvert scorecard, issue closeout, and next-test needs into final buyer-facing action language.
- Archive renewal evidencePreserve final decisions, excluded rows, issue IDs, next-test requirements, and follow-up dates.
- Track follow-up readinessCarry archived issues, owners, gate dates, and next-test requirements into the next flight.
- Close status windowsDecide when delayed lead, matchback, attribution, follow-up, or survey rows can support final language.
- Register closeout rowsPreserve closeout IDs, exclusions, allowed claims, and next review dates for later flights.
At a glance
Core audience
Marketing leaders, analysts, founders, researchers, and editors who compare claims against evidence.
Reader mode
Reference reading, planning, vendor evaluation, media buying, analytics QA, and editorial standards work.
Primary formats
Leaderboard, in-article display, right rail, post-content display, and clearly labeled native cards.
Buying paths
Open programmatic, private marketplace packages, and limited direct sponsorships for strong-fit categories.
Placement map
This table is the source of truth for placement IDs, ad-unit paths, accepted creative sizes, and refresh rules. Use the inventory readiness matrix when the same placements need package readiness, campaign handoff fields, and reporting keys.
| Placement ID | Ad-unit path | Context | Creative sizes | Refresh |
|---|---|---|---|---|
| home-leaderboard | /measurement-press/home/leaderboard | Homepage below the opening feature. | 970x250, 970x90, 728x90, 468x60, 320x100, 320x50 | Pageview only |
| home-rail-1 | /measurement-press/home/rail-1 | Desktop rail beside homepage reader-guide modules. | 300x600, 300x250 | Viewability-qualified optional |
| archive-leaderboard | /measurement-press/archive/leaderboard | Article archive, topic pages, case-study index, and buyer pages. | 970x250, 970x90, 728x90, 468x60, 320x100, 320x50 | Pageview only |
| article-inline-1 | /measurement-press/article/inline-1 | Upper body placement inside long-form guides. | 728x90, 336x280, 300x250, 320x100 | Pageview only |
| article-inline-2 | /measurement-press/article/inline-2 | Lower body placement after the second analysis block. | 728x90, 336x280, 300x250, 320x100 | Pageview only |
| article-rail-1 | /measurement-press/article/rail-1 | Desktop rail beside article and guide pages. | 300x600, 300x250, 160x600 | Viewability-qualified optional |
| case-inline-1 | /measurement-press/case-study/inline-1 | Case-study body before the statistical result. | 728x90, 336x280, 300x250, 320x100 | Pageview only |
| case-rail-1 | /measurement-press/case-study/rail-1 | Desktop rail beside worked measurement examples. | 300x600, 300x250 | Viewability-qualified optional |
| post-content | /measurement-press/global/post-content | After primary article, guide, or case-study content. | 970x90, 728x90, 336x280, 300x250, 320x100 | Pageview only |
| native-sponsored-card | /measurement-press/native/sponsored-card | Clearly labeled partner card in relevant article or guide contexts. | Fluid native, 300x250 fallback | Pageview only |
Responsive serving rules
Rails are desktop-first
Right-rail placements are eligible on desktop and tablet layouts only when the configured size set supports the viewport.
Inline units carry mobile
Article, guide, case-study, archive, and post-content units use mobile leaderboard or rectangle sizes when the page narrows.
Reports keep device visible
Campaign readouts should separate desktop, tablet, and mobile delivery before comparing placement or package response.
Experience budgets travel
Ad-load limits, lazy-load behavior, refresh status, and layout exceptions should stay visible from trafficking through reporting.
Private marketplace packages
The topic taxonomy gives buyers and editors a shared map of reader intents, editorial desks, and clean-fit contexts. The audience intent map turns those reader jobs into buyer-ready package proof. The advertiser source-quality standards check whether the offer, evidence trail, destination, native fields, and readout limit are strong enough for the selected context. The direct sponsorship and native proposal review packet decides whether the proposal is ready, needs revision, should be narrowed, or should be held. The native card and landing page example gallery shows accepted and revise patterns before creative approval. The private marketplace readiness index gives the whole audience-fit, activation, launch, reporting, and renewal sequence in one handoff. The private marketplace buying terms guide explains how package IDs, deal keys, floors, cadence, creative handoffs, and destination readiness should appear in a proposal. The advertiser intake worksheet turns those inputs into one proposal record before pricing or trafficking, the private marketplace package brief template turns package scope into buyer-facing context and renewal evidence, the private marketplace deal review checklist checks the approval gate before activation, and the campaign readiness dashboard checks whether the package, creative, destination, inventory, and reporting fields are ready to launch.
| Package ID | Package | Best-fit buyer intent | Core placements | Deal key | Reporting key |
|---|---|---|---|---|---|
| measurement-science-desk | Measurement Science Desk | Reach teams planning, testing, or validating advertising measurement. | archive-leaderboard, article-inline-1, article-inline-2, article-rail-1, post-content | mp-msd-pmp | package.measurement_science_desk |
| media-framing-desk | Media Framing Desk | Reach readers auditing headlines, sourcing, base rates, and claim quality. | archive-leaderboard, article-inline-1, native-sponsored-card, post-content | mp-mfd-pmp | package.media_framing_desk |
| source-vendor-evaluation-desk | Source and Vendor Evaluation Desk | Reach teams comparing source quality, research claims, dashboards, and vendor evidence. | archive-leaderboard, article-inline-1, article-rail-1, native-sponsored-card, post-content | mp-sve-pmp | package.source_vendor_evaluation_desk |
| case-study-library | Case Study Library | Reach readers studying practical measurement failure modes. | archive-leaderboard, case-inline-1, case-rail-1, post-content | mp-csl-pmp | package.case_study_library |
| guide-library | Guide Library | Reach teams looking for reusable planning checklists, glossaries, taxonomy pages, source references, and templates. | archive-leaderboard, article-inline-1, article-inline-2, native-sponsored-card | mp-gdl-pmp | package.guide_library |
| buyer-readiness | Buyer Readiness | Reach buyers comparing placement maps, package boundaries, creative requirements, and campaign handoff fields. | archive-leaderboard, article-inline-1, native-sponsored-card | mp-brf-pmp | package.buyer_readiness |
Package examples
These examples translate the desk map into buyer-ready campaigns. They are not rate cards; they define the context, inventory mix, and reporting lane a buyer should expect before pricing or availability is discussed.
| Example package | Buyer use case | Inventory mix | Recommended readout |
|---|---|---|---|
| Measurement Methods Flight | Analytics, experimentation, MMM, BI, or data-quality brands introducing a planning resource. | Measurement Science Desk guides, article-inline display, article rail, post-content display, and optional clearly labeled native card. | Qualified delivery by guide group, viewable impressions, engaged sessions, return visits, and lead quality. Incrementality requires a separate holdout or matched baseline. |
| Source Quality Native Pairing | Research, survey, panel, governance, or advisory brands helping teams evaluate evidence quality. | Source and Vendor Evaluation Desk pages, source-quality guides, native sponsored card, in-article display, and archive leaderboard. | Report by page context, creative theme, destination, and qualified downstream action. Do not pool source-evaluation traffic with run-of-publication traffic. |
| Case Study Learning Flight | Education, consulting, experimentation, and measurement-service buyers aligned with practical failure-mode learning. | Case-study index, case-study inline display, case-study rail, post-content display, and supporting guide-library inventory. | Separate case-study readers from checklist readers, then compare engagement depth, return visits, and lead quality by context. |
| Buyer Readiness Reference Flight | Brands distributing a report, webinar, template, or product page to readers already planning measurement decisions. | Media kit, advertising overview, audience intent map, inventory readiness matrix, topic taxonomy, and guide-library placements. | Track delivery quality, landing-page engagement, form quality, and follow-up status. Treat attributed conversions as descriptive unless a comparison was set before launch. |
Package-to-readout trace
A strong package should leave a trail from proposal acceptance to renewal language. Use this compact trace when a buyer wants to know how a contextual package becomes a reportable campaign record rather than a loose collection of impressions.
| Trace step | Example record | What the buyer can decide |
|---|---|---|
| Accepted proposal | Measurement Methods Flight for a planning-resource launch; primary package measurement-science-desk; supporting buyer-readiness inventory only when reference pages are part of the brief. | Whether the objective and reader context are specific enough to price, traffic, and later judge. |
| Package contract | Deal key mp-msd-pmp; reporting key package.measurement_science_desk; eligible placements article-inline-1, article-inline-2, article-rail-1, and post-content. | Whether the buy has stable IDs that can survive proposal, trafficking, invoice, and reporting handoffs. |
| Launch handoff | Creative IDs, accepted sizes, destination ID, UTM source trail, device eligibility, flight dates, and the agreed comparison rule are recorded before traffic starts. | Whether the campaign is ready to launch or needs a hold for creative, destination, or measurement gaps. |
| Row-level report | Rows stay at placement by device by creative-size grain, with impressions, viewable rate, clicks, qualified visits, lead status, quality flags, and bounded conclusion. | Whether response came from the intended reader job, a device or destination difference, or a small cell that needs retesting. |
| Renewal decision | Renew the agreed package mix, narrow to upper-body guide inventory, revise creative or landing page, shift budget to a separate lane, or design a lift test. | Whether the evidence supports descriptive optimization, a budget move, or only a stronger next-test design. |
Use the same language chain: start with the readiness index for the full sequence, use the proposal review packet, preserve the package scope in the package brief, approve the activation record with the deal review checklist, export row-level evidence with the readout sample, use the campaign walkthrough to connect readiness, rows, and renewal, write the buyer narrative with the package performance readout, score the next decision with the renewal scorecard, close weak lanes with the campaign issue register, write final action language with the campaign renewal memo template, preserve carry-forward limits with the campaign renewal evidence archive, track next-flight readiness with the campaign renewal follow-up tracker, close delayed outcome windows with the campaign status-window closeout checklist, and preserve closeout rows with the campaign status-window closeout register.
Deal setup
A private marketplace or direct campaign should be trafficked from the same brief that will later be used for the readout. This keeps the package definition, deal key, creative rotation, and measurement language aligned. Use the readiness index when the team needs the whole audience-fit, proof, activation, reporting, and renewal sequence in one place. Use the buying terms guide when a proposal needs buyer-facing definitions before the operational brief is finalized, then use the advertiser intake worksheet to preserve the objective, package lane, floor inputs, creative handoff, destination status, and readout boundary. Use the package brief template before activation so package IDs, reader contexts, reporting grain, and renewal evidence are visible to the buyer. Use the deal review checklist when the package needs a final buyer-facing approval gate for proof, identifiers, placements, fields, exceptions, and renewal thresholds. Use the campaign readiness dashboard before traffic starts so launch approval is tied to a ready, revise, or hold decision.
| Setup field | Specify before launch | Why it matters |
|---|---|---|
| Deal or campaign name | Buyer, package ID, deal key, quarter, primary objective, and buying path. | Connects proposal, trafficking, invoice, and report records without ambiguity. |
| Eligible context | Desk, article set, URL pattern, included placements, device classes, and exclusions. | Prevents a contextual package from becoming unclear run-of-publication delivery. |
| Creative rotation | Sizes, message themes, landing pages, UTM values, backup mobile creative, and active dates. | Allows creative performance to be read without confusing format, message, and destination effects. |
| Primary signal | Delivery quality, qualified visits, lead quality, brand movement, or designed lift. | Stops the report from choosing whichever metric looks strongest after the flight. |
| Comparison rule | Prior flight, matched context, reserved holdout, or no comparison available. | Determines whether the readout can support directional, descriptive, or causal language. |
Yield and deal readiness
Before quoting a floor or renewal package, check that the package has enough context proof, forecastable supply, seller-path evidence, sell-through state, refresh boundaries, creative eligibility, launch QA, reader-experience budget, migration readiness, and renewal signals to support the proposal. The programmatic inventory QA checklist checks whether the placements can be trafficked and reported cleanly; the ad experience and page-speed budget checklist checks whether ad load, layout stability, lazy loading, refresh rules, and script weight preserve the page's reference value; the publication migration readiness checklist checks whether routes, redirects, ad paths, feeds, seller records, and reporting baselines can survive a cutover; the supply path transparency checklist checks whether authorization, seller disclosure, deal keys, and report exceptions are visible; the ad yield and deal-readiness checklist turns those inputs into a practical ready, revise, hold, or rebuild decision.
Floor inputs
Use context scarcity, supply reliability, exposure quality, buyer fit, direct opportunity cost, and renewal evidence. Do not let the floor imply guaranteed business outcomes.
Sell-through fields
Track forecasted, reserved, sold, unsold, makegood, house, and remnant states by package, placement, device, and week.
Refresh limits
Keep pageview-only defaults visible, document any viewability-qualified exceptions, and separate refreshed impressions in reports when they exist.
Creative readiness
Display
Supply JPG, PNG, GIF, or HTML5 display creative in standard IAB sizes. Include click URL, flight dates, and any buyer-side tracking tags.
Native
Provide headline, short body copy, brand name, image asset, destination URL, and disclosure language that clearly identifies the paid placement.
Context
Choose topic, guide, case-study, or run-of-publication targeting. Campaigns can be mapped by content desk and placement group.
Before trafficking, use the native card and landing page example gallery to compare accepted and revise patterns, then use the creative asset acceptance checklist to confirm accepted sizes, native fields, destination fit, tracking values, and the launch handoff record.
Standard reporting handoff
| Reporting slice | Include | Keep the claim bounded |
|---|---|---|
| Placement group | Impressions, measurable impressions, viewable impressions, clicks, CTR, and spend by placement ID. | Placement delivery does not show that the campaign changed demand. |
| Content context | Desk, article group, guide type, case-study group, and page URL where available. | Do not average unlike reader intents into one performance story. |
| Creative and destination | Creative size, message angle, landing page, UTM values, and destination action. | A winning message may be selecting higher-intent readers rather than causing new demand. |
| Traffic quality | Engaged sessions, return visits, content depth, invalid-traffic review, and landing-page completion. | Good traffic is a quality signal, not proof of incremental sales or brand movement. |
| Lead and pipeline quality | Qualified rate, disqualification reason, follow-up status, stage movement, and time to contact. | Lead volume should not be read without qualification and follow-up context. |
| Designed measurement | Holdout, matched baseline, outcome window, leakage check, uncertainty, and limitations. | Use causal wording only when the comparison was designed for that question. |
Reporting structure
Campaign reports should be readable by placement group, content context, device class, creative size, and flight. The most useful readout compares delivery quality and downstream outcomes without treating attributed clicks or matched conversions as proof of incremental value. Use the workflow above for the standard path; pull in specialized lead-quality, matchback, reach/frequency, or lift-test checklists only when those signals are part of the campaign.
Good fit: analytics, research, data infrastructure, professional learning, marketing operations, and evidence-led services. The best creative here helps readers make better decisions from better comparisons. Use the source-quality standards before a strong-fit category becomes a priced package.
Next step
Start with the advertising overview for audience fit, the advertiser source-quality standards for offer and destination fit, the direct sponsorship and native proposal review packet before acceptance, the native card and landing page example gallery for accepted and revise patterns, and the advertiser FAQ for proposal fields. Use the private marketplace readiness index as the full buyer handoff from audience fit through renewal. Use the private marketplace buying terms guide when deal terms need plain buyer-facing definitions, then use the advertiser intake worksheet before pricing, the private marketplace package brief template before activation, the private marketplace deal review checklist before activation approval, and the campaign readiness dashboard before launch approval. For implementation, use the package examples, placement IDs, ad-unit paths, and reporting handoff above with the inventory readiness matrix and the publication migration readiness checklist when routes, domains, templates, or ad paths change.