Search

Viewability

  • Updated

AppLovin integrates the Open Measurement (OM) SDK and thereby allows you to measure Viewability for ALX creatives. AppLovin supports OM for VAST on SDK versions 11.0+, and for additional formats on SDK versions 11.3.0+.

The formats supported on SDK 11.3.0+ are:

Please reach out to your third party viewability vendor (including IAS & Moat) to validate your viewability tags before running viewability campaigns through AppLovin.

Setting Up Viewability Tags

In order to measure viewability for ALX creatives, you must have a direct relationship with one of the supported viewability vendors. You can find a list of supported viewability vendors under Member Companies on the Open Measurement Working Group page. Work with your third party viewability vendor to set up the viewability tags discussed in this section.

Viewability tags are specific to each viewability vendor. However, in general you can set up viewability tags in the ways described below, depending on the ad format:

  • For HTML tags, include your viewability vendors’ OMID/JavaScript tag in the HTML code. Work with your viewability vendor to obtain the tag and for guidance on where to insert it in your HTML.
  • You can implement VAST XML video measurement tags in-app by adding either an <Extension> or <AdVerifications> node to your VAST tag. For each third-party viewability vendor, work directly with your viewability vendor account representative on the specific way they recommend that you integrate the VAST <Extension> or <AdVerifications> node. For most verification vendors, the following instructions indicate how to implement the verification nodes:
    • For VAST versions pre-4.1, include an extension node below the VAST XML, with the <AdVerification> node nested inside, as shown here: 
      <Extension type="AdVerifications">
  <AdVerifications>
    <Verification vendor="vendor name">
      <JavaScriptResource apiFramework="omid" browserOptional="true">
        <![CDATA[]]>
      </JavaScriptResource>
      <TrackingEvents>
        <Tracking event="verificationNotExecuted">
          <![CDATA[]]>
        </Tracking>
      </TrackingEvents>
      <VerificationParameters>
        <![CDATA[“Vendor name”]>
      </VerificationParameters>
    </Verification>
  </AdVerifications>
</Extension>
    • For VAST 4.1, include the <AdVerifications> node directly below the VAST XML, as shown here: 
      <AdVerifications>
  <Verification vendor="vendor name">
    <JavaScriptResource apiFramework="omid" browserOptional="true">
      <![CDATA[]]>
    </JavaScriptResource>
    <TrackingEvents>
      <Tracking event="verificationNotExecuted">
        <![CDATA[]]>
      </Tracking>
    </TrackingEvents>
    <VerificationParameters>
      <![CDATA[“Vendor name”]>
    </VerificationParameters>
  </Verification>
</AdVerifications>undefined</Extension>

Testing Your Viewability Tags

To test your viewability tags, set up your viewability bid responses as per the test app instructions, and run test impressions in the test app.

From there, you can work with your viewability vendor to confirm tracking is correct. They will instruct you to collect charles logs and track certain calls made by their tags, and/or review reporting in their own viewability platform.

OMSDK tags and postback calls must use secure (HTTPS) URLs.

Bid Responses

To help your viewability partner communicate with the AppLovin SDK properly, you can include the OMID-1 API (value = “7”) in the API array of your bid response (bidresponse.bid.apis). Refer to the AppLovin OpenRTB 2.5 spec for details.

Reporting

You can receive viewability reporting on your ads if you have a direct relationship with a third-party viewability vendor. In order to collect viewability measurement on your campaigns, include the third-party measurement tags in your creatives and bid responses by following the instructions above and those from your vendor.

All apps on supported SDK versions automatically integrate with and opt into OMSDK. You can receive viewability reporting for your integrated ads on apps that run a supported SDK version.