Data & keyword passing

Content URL passing

AppLovin recommends that you pass your app content URL when you make ad requests. It allows for buy-side contextualization or review. Some DSP buyers may require it. You pass this URL in the bid request.

You can pass your app content URL when you make an ad request. The following code snippets show how to do this:

AppLovinMAX.setBannerExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );

AppLovinMAX.setInterstitialExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );

AppLovinMAX.setMRecExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );

MaxNativeAdView(
  adUnitId: '«ad-unit-ID»',
  extraParameters: { 'content_url' : '«value»' }
  ⋮
)

MaxAdView(
  adUnitId: '«ad-unit-ID»',
  extraParameters: { 'content_url' : '«value»' }
  ⋮
)

AppLovinMAX.setRewardedAdExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );

Unified identifiers

You can pass UID2 tokens in the bid stream. Buyers use these tokens to target and accurately bid on app inventory. You are responsible for tokenizing and for passing the token to AppLovin. The code examples below show how you pass the tokens:

AppLovinMAX.setAppOpenAdExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );

AppLovinMAX.setBannerExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );

AppLovinMAX.setInterstitialExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );

AppLovinMAX.setMRecExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );

MaxNativeAdView(
  adUnitId: '«ad-unit-ID»',
  extraParameters: { 'uid2_token' : '«value»' }
  ⋮
)

MaxAdView(
  adUnitId: '«ad-unit-ID»',
  extraParameters: { 'uid2_token' : '«value»' }
  ⋮
)

AppLovinMAX.setRewardedAdExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );

SKAdNetwork

Advanced settings

Policy Center Terms of Use Publisher Policies Demand Partner Policies Platform Enforcement Privacy Your Privacy Choices

Cookie Settings