Vendors & measurement
Use of non-allowlisted OMID verification script
- Ad Manager API value
- USE_OF_NON_ALLOWLISTED_OMID_VERIFICATION_SCRIPT
What Google's rule says
The Ad Manager API records this as a non-allowlisted OMID verification script. Google's Open Measurement guidance is that creatives using OMID scripts may only use allowlisted domains, so that third-party code running in the measurement path has been validated first.
What actually causes it
- A verification vendor whose OMID domain is not on Google's allowlist.
- A vendor key written with the wrong domain, or with no use case suffix.
- A vendor that belongs to the Open Measurement Working Group but whose domain has not been raised with Google.
- A verification script inherited from a creative built for a different platform.
How to fix it
Read the vendor key in the creative's verification node and check the domain in it. Allowlist membership attaches to that domain — if it is not the one the vendor was validated under, the script is not allowlisted no matter which vendor supplied it.
The part that is not obvious
OMID vendor keys follow the shape [domain]-[usecase] — moat.com-omid, integralads.com-omid, comscore.com-omid, doubleverify.com-omid — so the string in the creative carries the identity being checked, and you can diagnose this one by reading the tag rather than by testing it. There is also a route that no amount of tag editing will find: Google documents that domains belonging to Open Measurement Working Group members are eligible beyond the published allowlist, and that the way in is to raise the domain with your account manager. If your vendor is a Working Group member, the fix is a conversation, not a code change.
Related reasons
Reason name and API value verified against Open Measurement SDK — Authorized Buyers Help on 30 July 2026 (Ad Manager SOAP API v202602). The causes and fix above are practitioner guidance, not Google policy text.