Advanced settings

[COMPONENT: AdPlacements]

[COMPONENT: MuteAudio]

[COMPONENT: MuteCaution]

Enable verbose logging

Enable verbose logs with the following code:

[COMPONENT: VerboseLogging]

[COMPONENT: CreativeIDNetworkName]

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.

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:

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]”.

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.