Advanced settings

DSP name

To retrieve the name of the DSP for a MAX ad served from AppLovin Exchange, call the ad’s getDspName() method:

Impression-level user revenue API

You can access impression-level user revenue data on the client side. You can use this data to compare different sources and campaigns. You can also access this data by using the MAX user revenue API. MMPs who want to access this data should review the impression-level user revenue API for MMPs documentation.

[COMPONENT: AdRevenueAttribution]

You can retrieve the revenue amount in all ad lifecycle callbacks. Do this by creating a MaxAdRevenueListener, implementing its onAdRevenuePaid() method, and passing that listener to setRevenueListener(). The following example shows how to implement such an “ad revenue paid” callback:

You can also retrieve a precision evaluation for the revenue value, as shown in the following example:

[COMPONENT: PrecisionValues]

Establishing ad request callbacks

To listen for an ad request, set a MaxAdRequestListener, implement its onAdRequestStarted() method, and pass that listener to setRequestListener(). The following example shows how to implement such an “ad request started” callback:

Selective init

You can initialize the SDK with specific ad units by specifying your ad units in the AppLovinSdkInitializationConfiguration. If you do so, the SDK only initializes those networks that you configured for the ad units you specify. If you do not specify any ad units, the SDK assumes the current session needs all your ad units. In such a case it initializes all networks that you configured for those ad units. The following example shows how you implement this feature:

[COMPONENT: SdkKey]

[COMPONENT: WaterfallInformationAPI]

AdLoadState values

[COMPONENT: AdLoadStateValues]

Example

Customize banner / MREC ad refresh

You can customize banner and MREC ad refresh intervals via the API, just as you can configure them in the Ad Unit UI. The minimum and maximum refresh intervals allowed are 10 seconds and 120 seconds, respectively. MAX ignores values outside these limits. The following code samples show you how to customize these refresh intervals:

Ad placements

You can set a placement name for each ad unit (for example, “Rewarded VideoLevels”, “INTER_levelEnd”, or “RewardedVideoCoinStore”). This can help you gather statistics for different placement categories. The following snippets show you how to set the placement name for different ad formats.

You can share impression-level ad revenue data with your mobile measurement partner of choice, such as Adjust for all supported networks.

Creative ID and network name

You can retrieve the creative ID and the network name of displayed ads from mediated networks. Refer to the Creative Debugger documentation for more information.

Mute audio

You can mute audio for some mediated SDK networks when you launch your app. The networks that support this feature via the AppLovin SDK are:

{props.iosNetworksIncluded ?? true ?

• AppLovin
• Bigo (native only)
• DT Exchange
• Google Ad Manager
• Google bidding and Google AdMob
• LINE
• Mintegral

• AppLovin
• Bigo (native only)
• DT Exchange
• Google Ad Manager
• Google bidding and Google AdMob
• LINE
• Mintegral

For other networks, consult your network’s account team to learn whether this feature is available and how to access it.

The following code snippets show how you mute audio on those networks that support this feature:

This precision takes one of the following values:

"publisher_defined" : the revenue amount is the price assigned by the publisher

"exact" : the revenue amount is the result of a real-time auction

"estimated" : the revenue amount is based on Auto-CPM or FB Bidding estimates

"undefined" : no revenue amount is defined and there is not enough data to estimate

"" : revenue and precision are not valid (for example, in test mode)

You can find your SDK key in the Account > General > Keys section of the AppLovin dashboard.

To verify that you enabled verbose logs, check for the line that reads Verbose Logging On: true in the initialization section of the AppLovin SDK logs:

AppLovin SDK tags its logs with the tag “/AppLovinSdk: [AppLovinSdk]”.

Waterfall information API

The Waterfall Information API tells you about the current waterfall for an ad (one that has loaded or failed to load). The API returns the ad load state, latency, credentials, and mediated network information for each ad in the waterfall. If an ad in the waterfall fails to load, the API provides error information.

The value of ad.getRevenue()/ad.revenue may be -1in the case of an error.

When you use selective init, MAX excludes any ad units that you do not explicitly specify from serving ads for the current session.

Selective init has no effect when you enable test mode.

If the waterfall is empty, MaxError.getWaterfall() returns null. If so, you cannot interrogate the waterfall properties. However, you can retrieve the ad load latency for an empty waterfall by calling the getRequestLatencyMillis() method:

“Take Ad-Revenue Attribution to the Next Level With MAX” from AppLovin’s Blog

Set the mute state before you load ads. Some networks (like Google bidding and Google AdMob) return muted or unmuted videos depending on what the mute state is before ad load.

Note: if you mute ads, this may result in lower ad revenue.