Viewability

Open Measurement (OMID) on CloudX-rendered creatives, and how to configure verification tags

CloudX embeds the IAB Tech Lab Open Measurement SDK (OM SDK) and attempts viewability measurement on creatives it renders itself. CloudX has active Android and iOS entries in the OM SDK compliance register under partner Cloudxai. Certification coverage is version-specific; confirm the shipped SDK version against the current registry entry before relying on certified coverage.

Measurement is driven by the creative. CloudX attempts to open the ad session and run your vendor’s verification script, which you supply in the creative markup. Session creation is best-effort; the creative continues rendering if OMID activation, context, or verification-resource setup fails.

Supported formats

App Open OM SDK measurement is endpoint-dependent and applies when CloudX renders the creative from bid.adm; CloudX confirms support during onboarding.

Native in the publisher-facing ad-format catalog is supplied through mobile SDK network adapters and is outside the public OpenRTB buyer endpoint contract. The Native row therefore makes no CloudX OM SDK promise for buyer-returned Native markup. A partner SDK may provide its own measurement.

The checkmarks above mean the SDK attempts an OMID session for that renderer path; they do not guarantee successful session creation or vendor reporting.

Bid request signal

CloudX advertises OMID support on supported banner and video impressions. The API framework array includes 7 (OMID-1):

No bid response field enables measurement. CloudX does not read bid.apis; the SDK attempts to derive the session from the creative and usable verification resources whether or not you declare the framework on the bid.

Choose a measurement vendor

You need a direct relationship with your viewability vendor. CloudX does not resell or proxy measurement, and does not receive your vendor’s reporting.

Pick a vendor from the IAB Tech Lab compliant companies list under OM SDK Compliance, Mobile App category. Contact the vendor to validate your tags before you launch a campaign — a tag that a vendor has not validated can render correctly and still report nothing.

Configuring viewability tags

HTML and MRAID

Embed your vendor’s OMID JavaScript tag in the HTML you return in bid.adm. Ask the vendor where in the document the tag belongs; placement rules differ by vendor.

CloudX opens an HTML display ad session bound to the creative’s WebView, with verification scripts isolated from the creative’s own JavaScript.

VAST

Return <AdVerifications> as a direct child of <InLine>. CloudX reads it there on every VAST version it renders. Verifications declared on a wrapper in the chain are merged with the inline ad’s own.

<AdVerifications>
  <Verification vendor="vendor-key">
    <JavaScriptResource apiFramework="omid" browserOptional="true">
      <![CDATA[https://vendor.example/omid-verification.js]]>
    </JavaScriptResource>
    <VerificationParameters>
      <![CDATA[vendor-specific-payload]]>
    </VerificationParameters>
  </Verification>
</AdVerifications>

Requirements

What CloudX tracks

• OMID viewability when the HTML or VAST session starts successfully, with the impression event owned by the SDK.
• VAST 4.1 ViewableImpression events, alongside the standard Impression event, when the applicable tracking path is available.

A VAST creative with no <AdVerifications> still renders and still fires CloudX’s own impression tracking, but there is nothing for your vendor to measure — no verification script is loaded and no vendor reporting appears.

CloudX impression thresholds

CloudX’s own publisher-impression trigger is separate from vendor OMID reporting. Android display requires at least 50% visibility for one second. VAST normally requires two seconds of playback while the renderer considers the creative at least 50% visible. On Android, a VAST creative shorter than two seconds also qualifies when it plays through to completion and is at least 50% visible at completion. iOS fullscreen HTML also has a one-second fallback trigger, so do not treat a CloudX impression as proof that a vendor measured the same view.

Testing

1. Enable a test line item with your CloudX account manager and return your instrumented creative on it.
2. Run test impressions on a device.
3. Have your measurement vendor confirm the impressions in their logs and reporting before you scale spend.

Contact your CloudX account manager if measurement is missing after your vendor has validated the tags.