- Published
- Oct 30, 2026
- Reading time
- 11 min read
OMID Script Loads but Measurement Is Missing: What to Check
Trace OMID results from verification resources and session events to provider receipts and reports. Separate local validation from production measurement.

In this guide (11 sections)
A loaded OMID verification script does not prove that a measurement provider received usable events or included them in the report you opened. Trace the actual verification resource, session, event flow, provider receipt and reporting scope. Keep a successful local integration test as evidence of that test, rather than treating it as a production reporting guarantee.
An older archived web-video question describes exactly this gap: the integration's test script appeared to work, video events were signaled, and the vendor script ran, yet the expected measurement requests and report data were missing. A later reply asks whether anyone resolved it. Neither the original post nor the replies establish one confirmed root cause.
A separate archived ad-network question asks how to receive signals from publishers that already advertise OM SDK support. Together, these questions expose a practical distinction: installing the framework, executing a particular verification resource and obtaining a usable provider report are different responsibilities.
First identify which measurement mechanism is missing#
Write down the exact outcome you expected: an OMID event visible to a verification client, a request to a provider, an eligible or measurable impression, or a report row. They are not interchangeable symptoms.
Also separate OMID verification from ordinary video tracking and publisher-determined VAST viewability callbacks. If your missing event is the VAST ViewableImpression outcome URL, use the callback-specific diagnostic. Adding a verification script does not establish that a player implements that separate callback.
Keep the expected mechanism, responsible component and recipient in the incident record. “Viewability is broken” is too broad to assign a useful next action.
| Checkpoint | Evidence to retain | Limit of that evidence |
|---|---|---|
| Resource was supplied | Actual resolved VAST verification entry | Does not establish execution |
| Resource loaded and ran | Runtime observations for that exact resource | Does not establish a usable session |
| Session received expected events | Session-correlated validation or supported diagnostics | Does not establish provider receipt |
| Provider accepted relevant data | Provider-confirmed receipt and interpretation | Does not establish inclusion in every report |
| Intended report includes the result | Matching metric, IDs, dates and eligibility | Does not establish all other inventory was measured |
This is a diagnostic worksheet, not a claim that every provider exposes a receipt API or that every integration has every field.
Trace verification through to reporting
Record the resource, session events, provider receipt and report scope.
Use the tracking QA checklistOpens a practical guide. No email required.
Treat local validation as a specific test result#
IAB's Web Video validation guide describes a Validation Verification Client that logs event messages through local HTTP requests. It also distinguishes performing those checks from obtaining independent certification guidance.
Use the validation client to observe the tested session's start, impression, playback or viewability-related events as applicable. Record the environment, versions, fixture, timestamps and actual observed messages. Save missing or contradictory events as findings instead of selecting only the successful console output.
Then run a separate provider-approved production-like test. The local client is not the provider's reporting integration. Replacing the vendor resource with a test resource can help isolate the publisher-side path, but it also changes the component under investigation.
Do not say the production resource is validated merely because the local one receives events. Conversely, a failed local fixture does not prove every production placement is unmeasurable. Preserve the scope of each observation.
Inspect the delivered verification entry without rewriting it#
Capture the resolved response and relevant wrappers for one affected ad. Identify the vendor key, resource URL, declared framework, resource environment and associated parameters. Keep the exact response privately, with sensitive identifiers removed from shared excerpts.
VAST 4.3, section 3.17.5, makes the VerificationParameters format vendor-defined and requires it to be passed verbatim. It is bootstrapping metadata for the verification code, not a generic list of URLs the publisher should call manually.
Do not invent a parser for another provider's opaque payload, remove unfamiliar fields or execute every URL-looking value. Ask the resource owner what diagnostics it supports and whether the resource and parameter version belong together. A repair that changes the payload to resemble a forum example can destroy the evidence needed to locate the real issue.
Compare generated, delivered and runtime versions. A correct entry in the ad server does not establish that an intermediary preserved it or that the released player consumed it. A URL hosted on a familiar domain is not evidence of compatibility, vendor approval or the intended reporting account.
If the contract is unclear, obtain a supported test tag from the provider and compare it with the affected one under controlled conditions.
Check the session's actual environment and lifecycle#
For web video, IAB's integration guide separates the Service Script from the JS Session Client. It also calls for a new AdSession for each ad when multiple ads run on a page. Check the implementation path appropriate to the released integration, not just whether a dependency exists in the build.
Ask the integrator to identify the measured video element, session identity, event owners and expected event sequence. Compare the resource's execution with that session. A script can run while the intended ad's measurement context remains incomplete.
Use supported diagnostics to observe an ordinary playback, pause/resume and end-of-session case. Keep the resource constant while testing lifecycle behavior. Do not manufacture impression or progress events just to populate a report.
Cleanup matters too. The Web Video guide requires at least three seconds after the last adSession.finish() before unloading the Service Script's iframe, allowing final verification requests. That is a scoped lifecycle instruction, not a universal reporting-delay SLA. Check whether the actual release destroys the context prematurely.
Audit iframe boundaries as separate components#
An iframe setup needs more than a successful script download. IAB's Web Video iframe guidance requires the Service Script and creative element to share a non-null origin. The Session Client has different placement rules; cross-origin communication with the Service Script requires the documented setup, including the applicable version behavior.
Draw the top window, creative element, Service Script, Session Client and relevant frames. Record their actual origins and which window owns each object. A screenshot of the page cannot establish that relationship.
Have the implementation owner compare the deployed arrangement with the supported topology. An arbitrary cross-origin frame or a null-origin container is not repaired by changing the report filter. Keep any resulting change inside the integrator's supported implementation and repeat the validation fixture afterward.
Do not apply this web-video guide as a universal recipe for native apps, hybrid renderers or CTV. For a hybrid app, use the renderer and measurement-session review. Environment support and session ownership must be verified for that path.
Use non-execution evidence without treating silence as success#
The verification resource can be absent, rejected, unsupported or unable to load. VAST 4.3 section 3.17.4 defines verificationNotExecuted and its reason codes: 1 for rejection, 2 for unsupported verification and 3 for a detectable load error. The specification also notes that some script parsing or runtime errors may not be detectable by the player. VAST verification tracking reference
Preserve a received non-execution notification with its session and resource scope. It is evidence about verification execution, not an automatic conclusion about whether the video played, was viewable or was invalid traffic.
Absence of that notification is not proof that verification succeeded. The notification path itself can be unobserved, and some failures do not produce a detectable signal. Match runtime evidence, request attempts and recipient records instead of turning a silent row green.
If the environment rejects a resource, obtain the receiving platform's supported process from the responsible team. Do not adopt old forum claims about automatic bans, universal whitelists or approval timelines as current policy. Do not bypass a rejection or substitute another provider's identity.
Confirm capability declarations and reporting entitlement separately#
A declared capability tells the receiving platform what the integration claims to support. It is not a receipt that the measurement executed successfully for this ad.
For a concrete scoped example, Google's current DV360 OpenRTB specification requires the relevant API framework declaration to enable OMID Active View measurement and recommends supplying the integration partner name and version. It also documents how certification status affects the reporting population. Those are DV360 exchange-integration instructions; they do not guarantee a matching metric in Campaign Manager or another product.
Ask the provider which report should receive the tested result, what the metric counts, which integration/version it recognizes and what account configuration is required. Record the answer for the actual environment. A metric being selectable in a report does not establish that the tested path supplies it.
Keep partner identity accurate. Do not copy a certified partner name into an unrelated integration or change capability declarations solely to obtain a populated result. Correct the declared implementation and validate the supported path.
Follow provider receipt into the correct report#
Where authorized evidence is available, follow one test from the session to the provider's accepted record. Distinguish an outgoing request, its transport response and the provider accepting it as eligible measurement. A successful transport response alone cannot establish the final classification.
Then align campaign and placement references, report product, metric, date range, timezone, filters, extraction time and documented processing window. Ask whether the data is expected in the chosen population, such as eligible, measurable or viewable impressions. Preserve unknown eligibility rather than forcing it into a non-viewable count.
Do not promise a universal reporting delay. Use the provider's actual guidance and a dated receipt. If processing is still pending, label it pending; if the report scope is wrong, correct the comparison without claiming to have recovered missing exposure.
The platform-versus-independent measurement workflow helps preserve these population and reporting distinctions when several systems disagree.
A hypothetical review of twelve test sessions#
Hypothetical example only: an integrator reviews twelve distinct, authorized test sessions with the same expected reporting destination. Each receives one initial evidence status:
| Initial evidence status | Sessions |
|---|---|
| Intended provider receipt and matching report result confirmed | 5 |
| Local validation observed, provider path not established | 3 |
| Verification resource execution failed | 2 |
| Insufficient evidence to locate the gap | 2 |
| Total reviewed | 12 |
Five of twelve, about 41.7%, have the complete evidence required by this test. This is an evidence-completeness ratio, not a campaign viewability rate or a market benchmark. The three local-validation successes cannot be added to the five provider/report confirmations.
The team next compares a supported provider fixture for the three local-only sessions, investigates the two execution failures and obtains missing traces for the remaining two. A common symptom does not establish a common cause.
Retain the initial classification after repairs. Later passes establish the retested versions and conditions, not retroactive proof that historical campaign data was complete. Do not calculate savings, refunds or incremental outcomes from these test counts.
Send a support packet that identifies the missing boundary#
Include the authorized fixture, exact versions and environment, relevant delivered verification entry, session chronology, local validation result, non-execution evidence if present, permitted network observations and intended provider/report scope. State what is confirmed and which checkpoint remains unproven.
For supported campaigns sending relevant events to AdProof, prepare a campaign/date/timezone-scoped export of available delivery and video-stage records. Compare it alongside the integration and provider evidence. AdProof's received campaign events do not replace an OMID certification, vendor receipt or provider-specific report. The anonymous streaming-publisher case provides review context. Request an AdProof measurement review to establish which existing signals can support the investigation.
Frequently asked questions#
Does a passing OM SDK validation test prove vendor reporting works?
It establishes the observed validation behavior for that fixture. Test the actual supported provider resource and reporting destination separately, preserving the evidence for each checkpoint.
Should my player call URLs found inside VerificationParameters?
Follow the provider's supported integration and preserve its payload. Do not reinterpret opaque bootstrapping metadata as a generic tracker list or manually generate measurement events.
Does a missing verificationNotExecuted notification prove success?
No. Use the actual runtime and receiver evidence. An unobserved notification or an undetected failure cannot establish that the intended measurement reached the report.
Can this web-video procedure be applied unchanged to every CTV app?
No. Confirm the platform, renderer, supported integration and event owners first. The specific web-video checks here do not establish equivalent capabilities in another environment.
Trace verification through to reporting
Record the resource, session events, provider receipt and report scope.
Use the tracking QA checklistOpens a practical guide. No email required.
