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.
UAppLovinMAX::CreateBanner(ad_unit_id, position); UAppLovinMAX::SetBannerPlacement(ad_unit_id, placement);
UAppLovinMAX::CreateMRec(ad_unit_id, position); UAppLovinMAX::SetMRecPlacement(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:
UAppLovinMAX::SetMuted(true); // to mute UAppLovinMAX::SetMuted(false); // to unmute
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.
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.4.2 ⋮ Verbose Logging On: true ⋮
AppLovin SDK tags its logs with the tag /AppLovinSdk: [AppLovinSdk].