You can set a placement name for each ad unit (for example, “Rewarded VideoLevels”, “INTER_levelEnd”, or “RewardedVideoCoinStore”). This can help you aggregate statistics for different placement categories. Below are code snippets that show how you set the placement name for various ad formats:
AppLovinMAX.createBanner(ad_unit_id, position); AppLovinMAX.set_banner_placement(ad_unit_id, placement);
AppLovinMAX.createMRec(ad_unit_id, position); AppLovinMAX.set_mrec_placement(ad_unit_id, placement);
You can mute audio for certain mediated SDK networks when you launch your app. The networks that support this functionality via the AppLovin SDK are Google bidding and Google AdMob, AppLovin, DT Exchange, Google Ad Manager, LINE, Mintegral, Tencent, and Verve. For other networks, consult your network’s account team to learn whether this functionality is available and how to access it. The following code snippet shows how you mute audio on the supported networks:
AppLovinMAX.set_muted(true); // to mute AppLovinMAX.set_muted(false); // to unmute
Enable Verbose Logging
Enable verbose logs with the following call:
To verify that you enabled verbose logs successfully you can check for the line that reads Verbose Logging On: true in the initialization section of the AppLovin SDK logs:
AppLovin SDK Version: 11.11.3 ⋮ Verbose Logging On: true ⋮
AppLovin SDK tags its logs with the tag /AppLovinSdk: [AppLovinSdk].
You can compartmentalize your users into “segments.” This can help you analyze users with particular characteristics, or can be helpful as a part of A/B testing. Each segment has a name of your choice, in the form of a string of 32 or fewer alphanumeric characters. You can set or retrieve the segment name of the current user from the AppLovin SDK by means of the
AppLovinMAX.user_segment.name = "myusersegment";
Creative ID and Network Name
func _on_interstitial_ad_loaded(ad_unit_id: String, ad_info: AppLovinMAX.AdInfo): print("AppLovin Exchange DSP Name: " + ad_info.dsp_name)
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.
You can retrieve the revenue amount in all ad lifecycle callbacks. The following example shows how to do this within the “ad revenue paid” callback:
inter_listener.on_ad_revenue_paid = func(ad_unit_identifier: String, ad_info: AppLovinMAX.AdInfo): print("Interstitial ad revenue paid: " + ad_info.revenue") ⋮ rewarded_listener.on_ad_loaded = func(ad_unit_identifier: String, ad_info: AppLovinMAX.AdInfo): print("Rewarded ad revenue paid: " + ad_info.revenue") ⋮ banner_listener.on_ad_loaded = func(ad_unit_identifier: String, ad_info: AppLovinMAX.AdInfo): print("Banner ad revenue paid: " + ad_info.revenue") ⋮ mrec_listener.on_ad_loaded = func(ad_unit_identifier: String, ad_info: AppLovinMAX.AdInfo): print("MREC ad revenue paid: " + ad_info.revenue") ⋮
Waterfall Information API
This feature allows you to see the information about the current waterfall for an ad that has loaded or failed to load. The network responses provide 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 network response provides error information.
|0||Ad Load Not Attempted|
|2||Ad Failed To Load|