Page Summary
-
Long waterfall mediation chains can increase ad request latency for critical first impressions.
-
To reduce first impression latency, you can set an initialization timeout to prevent exceeding a defined time limit.
-
Removing waterfall ad sources from your first request using key-value segmentation can deliver ads without additional latency.
-
Improve performance on less time-sensitive impressions by using ad preloading with an ad request that doesn't target the bidding-only mediation group.
Initializing an app with long waterfall mediation chains and multiple third party adapters can increase ad request latency for critical impressions that show first in the user's session. This increased first impression latency can prevent the ad from showing as the ad request has not yet returned a response.
This guide covers the following to reduce first impression latency in your app sessions:
- Set an initialization timeout
- Remove waterfall ad sources from your first request
- Improve performance on less time-sensitive impressions
Before you begin
Before you continue, set up Google Mobile Ads Unity Plugin.
Set an initialization timeout
To avoid missing an impression opportunity, set an initialization timeout. This approach prevents your app from exceeding the time limit you defined. You can proceed with the ad request after the time limit you set, or after initialization completes.
The following example sets an initialization timeout of five seconds:
private bool _isInitialAdLoaded = false;
void InitializeWithInitialAd()
{
// Load an ad after 5s if SDK initialization is slow.
Invoke("LoadInitialAd", 5);
MobileAds.Initialize((InitializationStatus initstatus) =>
{
LoadInitialAd();
});
}
void LoadInitialAd()
{
if (_isInitialAdLoaded)
{
return;
}
_isInitialAdLoaded = true;
LoadAd();
}
Remove waterfall ad sources on your first request
To deliver ads without any additional latency from waterfall ad sources, implement key-value segmentation to remove waterfall ad sources on your first ad request. Complete the following steps:
- Create a mediation group and add bidding ad sources.
- Add key-value segmentation to
your new bidding-only mediation group using key
latencyand valuelow. - Prioritize your new bidding-only mediation group above your primary mediation group in the UI. To adjust the order, change mediation group priority.
In your first ad request, include the custom targeting key-value pair:
var customTargeting = new Dictionary<string, string> {["latency"] = "low",}; var request = new AdRequest() { CustomTargeting = customTargeting, };Test the key-value segmentation setup to verify you are correctly targeting the new bidding-only mediation group.
Improve performance on less time-sensitive impressions
To improve performance on less time-sensitive impressions, such as ads that don't need to show right at app launch, use ad preloading with an ad request that does not target the bidding-only mediation group.