Proper way of pre-loading multiple rewarded video ads

138 views
Skip to first unread message

Krzysztof Poprawa

unread,
Jan 11, 2022, 5:30:44 PM1/11/22
to Google Mobile Ads SDK Developers
Hello,

I've tried searching for this but wasn't able to find any definitive answer, so here goes.

In my game, I'm using Rewarded Video format in quite a couple of places (6 to be exact) for different kind of rewards. And I've been wondering, what's the proper approach/architecture to achieve this:

1. Should I have a single Rewarded Video ad pre-loaded for all of the scenarios and just share it between them while loading next one after using it? - single shared RewardedAd object
2. Or can I safely pre-load the same ad placement for each and every scenario so that each one has it's own distinct Rewarded video ad loaded when needed? - multiple RewardedAd objects for the same AdUnitId

Approach #1 seems okay at first but it gives off a 'meh' vibe to the user since after watching one ad he needs to wait few seconds to be able to watch another since I need to block all 'Watch ad' buttons until another ad is loaded. Here's an example: say I have 2 distinct rewards in the game for 2 different types of currencies. A user can watch ad for reward #1, then reward #2 is blocked until another an ad is loaded, only once a new ad is loaded he can claim - it which might be off-putting to the user as its breaking the flow even if for a few seconds only.

Approach #2 seems to easily rectify that, each distinct reward will have its own Rewarded Video ad instance pre-loaded on app start and he can watch them in any order with no delays in-between if he wishes to. 

Are there any downsides to approach #2 that I should be concerned with? I have a strange feeling that this architecture might mess up my analytics/fill rates but am not too sure. Any insights on that?

Regards,
Krzysztof Poprawa 

Mobile Ads SDK Forum Advisor

unread,
Jan 12, 2022, 3:42:47 AM1/12/22
to krzy...@poprawa.eu, google-adm...@googlegroups.com
Hi Krzysztof,

Thank you for reaching out to us.

With regard to your concern, both of your implementation is permissible and is fine. Just to take note to keep a reference to the ad that's showing until it closes to ensure you receive important event callbacks like userDidEarnReward(). If you drop the reference to the rewarded ad, you rely on the SDK to keep the reference to the ad and your callback, and you may see unexpected behavior or race conditions if the SDK drops the reference too and garbage collection happens.

Regards,
Google Logo
Teejay Wennie Pimentel
Mobile Ads SDK Team
 


ref:_00D1U1174p._5004Q2Uj3l3:ref
Reply all
Reply to author
Forward
0 new messages