Viewability

AppLovin integrates the Open Measurement (OM) SDK. This allows you to measure viewability for ALX creatives. AppLovin supports OM for the following formats:

• Banner HTML/MRAID
• MREC HTML/MRAID
• Interstitial VAST XML and VAST tags
• Interstitial HTML/MRAID
• Native
• Rewarded VAST XML and VAST tags

Configuring viewability tags

To measure viewability for ALX creatives, you must have a direct relationship with a supported viewability vendor. You can find a list of supported viewability vendors under OM SDK Compliance on the Open Measurement Working Group page. Work with your viewability vendor to configure the viewability tags discussed in this section.

Viewability tags are specific to each viewability vendor. However, in general you can configure 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 get 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 to learn the specific way they recommend that you integrate the VAST <Extension> or <AdVerifications> node.

The following instructions show how you implement verification nodes for most verification vendors:

• 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>

Testing your viewability tags

To test your viewability tags, configure your viewability bid responses as described in the test app instructions. Then run test impressions in the test app.

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

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. To collect viewability measurement on your campaigns, include the third-party measurement tags in your creatives and bid responses. To do this, follow 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.