Measurement support has a commercial role before an ad is served. A buyer can require signals that an otherwise playable placement cannot provide. A published partnership case from PubMatic and ironSource illustrates why an inventory team should treat measurement readiness as part of its demand strategy, while keeping the result of a partnership separate from the effect of any individual standard.
This is an original analysis of a published case, with links to the source. It does not reprint the publisher's article or graphics. The financial and campaign results are the publisher's reported figures, rather than measurements performed by VASTLint.
The source describes a demand connection and reports monetization figures.
PubMatic's ironSource partnership case says DSPs required OM SDK signals and that ironSource's iSX supported them. It reports a 600% increase in video revenue, a doubling of eCPM, an 83% video completion rate and 95% viewability. The page attributes the figures to PubMatic internal data and identifies a comparison from the second half of 2020 to the first half of 2021. It also describes connecting premium brand demand to the inventory.
These are historical partnership results, not an estimate of what installing OM SDK would earn today. The published material does not provide a controlled comparison that isolates the SDK from changes in demand, inventory or campaign mix. Its commercial relevance is the explicit connection between measurement requirements and access to a buyer population.
Buyer requirements belong in the inventory eligibility model.
A publisher planning an integration should identify which buyers require a capability and where the current implementation can supply it. That creates a testable question: what inventory is eligible for those buyers under their actual requirements? The answer needs the deployed app or player configuration and the buyer's acceptance criteria, rather than a broad claim that the publisher supports video measurement.
An inventory planning record can distinguish technically available placements from placements that satisfy a particular campaign's conditions. This helps sales teams propose a supported offer and helps engineering prioritize work with a known commercial owner. A capability that no relevant buyer currently requires may still have value, but it should not receive a revenue forecast based on unidentified demand.
The IAB Tech Lab Open Measurement overview describes shared measurement infrastructure and its supported integrations. The standard supplies a technical route to measurement signals. A campaign agreement still determines what a buyer needs to receive, which environments it accepts and how the relevant reporting will be assessed.
A business case needs the alternative use of the same opportunity.
When evaluating expanded buyer eligibility, estimate what would happen to the inventory without the change. It might remain unfilled, serve a different paid campaign or be unavailable for another reason. The distinction affects the value of new demand. Counting all newly eligible delivery as additional revenue can substantially overstate the benefit if another buyer would have filled those opportunities.
Use observed billable delivery and net commercial terms when they are available. Keep the forecast separate when they are not. An engineering project can be supported by a specific buyer commitment or a measured eligibility gap without inventing the final revenue outcome. The forecast should identify its assumptions and be revisited after the integration is deployed.
Operating costs also belong in the comparison. Include integration work, provider onboarding, testing and continuing maintenance. If a shared implementation reduces repeated work, measure that benefit separately. A reduction in engineering effort and a change in realized yield answer different questions, even when both are relevant to deciding whether the project should proceed.
Measurement acceptance requires evidence from the receiving system.
Start with a controlled test population and an agreed expected event. Retain the relevant creative and campaign identifiers, environment and test settings. Confirm which signals the implementation emits and what the receiving provider actually records. This makes it possible to identify the stage where a reporting requirement stops being satisfied.
Then test the production path that transforms or forwards the ad document. A declaration can exist at submission and be missing by the time the destination consumes the response. Keep the relevant versions of the document with the integration record. The purpose is to verify the handoff the campaign will use, rather than relying on a successful test of a different path.
These checks should remain distinct from agreement about methodology or settlement. A provider can receive signals correctly while two campaign reports still describe different populations or definitions. Establish those scopes before interpreting a discrepancy as a broken integration. The business team needs an explanation of which requirement was tested and which questions remain commercial or methodological.
VASTLint helps check the document side of that workflow.
VASTLint's OMID documentation explains verification declarations in VAST. The validator can help identify document issues before runtime session testing. Preserve the input and findings when a supplier needs to change a declaration, and confirm the correction in the same delivery configuration that the campaign intends to use.
Those results do not certify an OM SDK integration or establish that a buyer accepted an impression. Combine them with platform testing and provider-side records. Our measurement readiness guide explains how to connect these technical checks with buyer eligibility and reconciliation work.
A published business case is useful when it identifies a commercial dependency worth investigating in your own workflow. The next step is a measured eligibility and delivery comparison for that workflow. That produces a stronger investment decision than borrowing another partnership's headline growth figure as a forecast.
Alex Sekowski creates VASTLint. The cited partnership is not presented as a VASTLint customer or endorsement. This analysis was prepared with AI assistance; reported results remain attributed to PubMatic's published case.
Top comments (0)