SKAdNetwork (SKAN)

AppLovin SDK fully supports Apple’s SKAdNetwork attribution. It allows DSPs to submit signed clicks to the SKAdNetwork API. Review the bid request/response specification for integration details.

How it works

1. The AppLovin SDK retrieves the SKAdNetworkItems from the source app’s Info.plist.
2. AppLovin Exchange includes the imp.ext.skadn object in the bid request. It sends this request to the demand sources in the source app’s Info.plist.
3. If the winning ad requires SKAdNetwork support, then the bid response includes seatbid.bid.ext.skadn.
4. If the user clicks the ad, Apple considers the source app for install attribution using SKAdNetwork.
5. If SKAdNetwork determines that the click from the DSP’s ad led to the install, Apple sends the postback directly to the DSP.

Creative type specification

The following recommendations show you how to properly handle clicks for each of the AppLovin-supported Creative Types:

VAST

When the SKAdNetwork (skadn object) is in the bid response, the <ClickThrough> node is ignored. Use the <ClickTracking> node if you need click tracking.

HTML

AppLovin accepts click-tracking URLs via the bid response seatbid.bid.ext.clicktrackers array. This is supported on all SDK versions that support SKAN, but not on versions earlier than that. Include this object only when AppLovin includes SKAN parameters in the bid request. When the user clicks an ad, the AppLovin SDK renders the StoreKit, asynchronously hits each URL, and follows redirects (response codes in the 300–399 range).

MRAID

You do not need to do anything special; the AppLovin SDK handles clicks properly.

Considerations

• Custom Product Page ID via ext.skadn.productpage.
• SKOverlay support added. Note: Apple does not provide a callback for when the user clicks the overlay, so AppLovin and DSP click tracking does not work.

SKAdNetwork attribution requires a SKAdNetwork ID. You can get one by registering with Apple.