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:

Banner ad
bannerAd = new MaxAdView( "«ad-unit-ID»" );
bannerAd.setExtraParameter( "content_url", "«value»" );
Interstitial ad
interstitialAd = new MaxInterstitialAd( "«ad-unit-ID»" );
interstitialAd.setExtraParameter( "content_url", "«value»" );
MREC ad
mrecAd = new MaxAdView( "«ad-unit-ID»", MaxAdFormat.MREC );
mrecAd.setExtraParameter( "content_url", "«value»" );
Native ad
nativeAdLoader = new MaxNativeAdLoader( "«ad-unit-ID»" );
nativeAdLoader.setExtraParameter( "content_url", "«value»" );
Rewarded ad
rewardedAd = MaxRewardedAd.getInstance( "«ad-unit-ID»" );
rewardedAd.setExtraParameter( "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:

AppLovinSdkSettings settings = AppLovinSdk.getInstance( context ).getSettings();
settings.setExtraParameter( "uid2_token", "«value»" );
Error handling
Advanced settings
© 2026 AppLovin. All rights reserved.
Policy CenterTerms of UsePublisher PoliciesDemand Partner PoliciesPlatform EnforcementPrivacyYour Privacy ChoicesCPRACookie Settings
search