Data & Keyword Passing
Segment Targeting
AppLovin MAX SDK version 12.6.0 introduces a privacy-safe way to target waterfalls. The APIs introduced in this version target by means of a generic key-value numeric pairing method. You are responsible for mapping the segment key and the applicable value(s) that represent the users you are targeting
For example, you could establish segments that represent the genres that a user is interested in.
You could represent these segments with the key number 849.
Genre values might include “horror”, “thriller”, and “romance”.
You could represent these by the the values of 1, 2, and 3 respectively.
The following code shows how you would add a user to the horror and romance genre segments, if you defined your keys and values in that way:
AppLovinMAX.addSegment( 849, [1, 3] );
AppLovinMAX.initialize( «SDK-key» ).then( ( conf: Configuration ) => {})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:
BannerAd.setExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );InterstitialAd.setExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );MRecAd.setExtraParameter( '«ad-unit-ID»', 'content_url', '«value»' );<NativeAdView adUnitId={adUnitId} extraParameters={{ 'content_url' : '«value»' }} ⋮/><AdView adUnitId={adUnitId} extraParameters={{ 'content_url' : '«value»' }} ⋮/>RewardedAd.setExtraParameter( '«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:
AppOpenAd.setExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );BannerAd.setExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );InterstitialAd.setExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );MRecAd.setExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );<NativeAdView adUnitId={adUnitId} extraParameters={{ 'uid2_token' : '«value»' }} ⋮/><AdView adUnitId={adUnitId} extraParameters={{ 'uid2_token' : '«value»' }} ⋮/>RewardedAd.setExtraParameter( '«ad-unit-ID»', 'uid2_token', '«value»' );