AppLovin integrates the Open Measurement (OM) SDK. This allows you to measure viewability for ALX creatives. AppLovin supports OM for the following formats:
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:
<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:
<AdVerification> node nested inside, as shown here:[COMPONENT: Extension]
[COMPONENT: AdVerifications]
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.
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.
Before you run viewability campaigns through AppLovin, contact your third party viewability vendor (including IAS & Moat) to validate your viewability tags.
OMSDK tags and postback calls must use secure (HTTPS) URLs.