Vendors & measurement
Misuse of OMID API
- Ad Manager API value
- MISUSE_OF_OMID_API
What Google's rule says
The Ad Manager API defines MISUSE_OF_OMID_API with the line "OMID sdk injected by creative." The objection is to the creative bringing its own Open Measurement SDK rather than using the one the host environment provides.
What actually causes it
- A creative bundling a copy of the OM SDK so that measurement works regardless of the app.
- A creative that starts its own OMID session instead of the ad session the SDK opened.
- A tag ported from an environment where the creative was responsible for loading measurement.
- A vendor wrapper that injects the SDK as a defensive fallback when it cannot detect one.
How to fix it
Take the SDK out of the creative and let the app or player provide it. The verification script belongs in the creative; the SDK that runs it does not.
The part that is not obvious
The value is named for API misuse but its documented definition is narrower and more useful: an injected SDK. That points at a specific, well-meant mistake — a creative that carries its own OM SDK so measurement works everywhere. It defeats the design, because Open Measurement exists so that one SDK owned by the app or player observes the ad from outside it. A creative measuring itself with a library it supplied is exactly the arrangement the standard was created to replace, which is why this is a policy violation rather than a duplicate-code warning.
Related reasons
Reason name and API value verified against Ad Manager API — CreativePolicyViolation (v202602) on 30 July 2026 (Ad Manager SOAP API v202602). The causes and fix above are practitioner guidance, not Google policy text.