Data & keyword passing
© 2025 AppLovin. All rights reserved.
AppLovin MAX SDK version 12.6.0 introduces a privacy-safe way to target waterfalls. The APIs introduced in this version target a generic key-value numeric pairing. You are responsible for mapping the segment key and the applicable value(s) that represent the users you target
For example, you could establish segments that represent the genres that interest a user.
You could represent these segments with the key number 849.
Genre values might include “horror”, “thriller”, and “romance”.
You could represent these by 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:
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.
The following code snippets show how you pass your app content URL when you make an ad request:
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:
