Skip to content

Data & Keyword Passing

Segment Targeting

AppLovin MAX SDK version 12.6.0 introduces a privacy-safe way to target waterfalls and Direct Sold campaigns. The APIs introduced in this version use a generic key-value numeric pairing method.

You decide the meaning of each key and each value.

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:

MaxSegmentCollection collection = new MaxSegmentCollection();
collection.AddSegment(new MaxSegment(849, new List<int> { 1, 3 }));
MaxSdk.SetSegmentCollection(collection);
MaxSdk.InitializeSdk();

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.

The following code snippets show how you pass your app content URL when you make an ad request:

MaxSdk.SetBannerExtraParameter("«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:

MaxSdk.SetAppOpenAdExtraParameter("«ad-unit-ID»", "uid2_token", "«value»");