"Google optimized" ad refresh... doesn't refresh?

445 views
Skip to first unread message

Marc

unread,
May 1, 2017, 11:43:50 AM5/1/17
to Google Mobile Ads SDK Developers
I've been updating my ad support to add another ad network and to add support for reward videos. While doing this, I also saw the recommendation to enable "Google optimized" for the ad refresh rate for banner ads. Given that it was recommended, I gave it a try.

What I discovered was that after the first banner ad loads, it never refreshes unless I do something to force it (such as changing the device's orientation).

Thinking that perhaps it was related to the updates I had done, I rolled back to the App Store version of my app. I saw that it, too, wasn't refreshing ads.

After I reverted the ad banner to use a custom refresh time of 30 seconds, and then waited a few hours for that change to propagate, I then saw that my app was correctly refreshing ads again.

Is there something I need to do to enable "Google optimized" ad refresh to actually refresh ads in my app?

Deepika Uragayala- MobileAds SDK team

unread,
May 1, 2017, 3:07:31 PM5/1/17
to Google Mobile Ads SDK Developers
Hi Marc,

Thanks for reaching out to us. This is a known issue that our team is working on. I will ping this thread and update you if I have any new information.

Regards,
Deepika Uragayala
Mobile Ads SDK Team

Abdukareem Haruna

unread,
May 19, 2017, 3:42:53 AM5/19/17
to Google Mobile Ads SDK Developers
I noticed that > i earn more with my ad refresh rate =30 than "Google Optimized"..

Marc

unread,
Jul 18, 2017, 9:30:58 AM7/18/17
to Google Mobile Ads SDK Developers
I've noticed the same myself. I've done an experiment over the past few weeks and noted that "Google Optimized" seems to generate about 30-50% less revenue than a 30 second refresh rate.

Deepika Uragayala- MobileAds SDK team

unread,
Jul 18, 2017, 2:58:30 PM7/18/17
to Google Mobile Ads SDK Developers
Hi everyone,

This issue has been fixed by our team. Please let us know if you are still facing this issue.

Regards,
Deepika Uragayala
Mobile Ads SDK Team

Mark B.

unread,
Jul 24, 2017, 9:59:00 AM7/24/17
to Google Mobile Ads SDK Developers
Hey, Deepika:

I'm still seeing issues with mediated SDKs... was this fixed with your comment on 7/18? Google ads still look great and refresh as expected, but when AdMob chooses any ad provider requiring an SDK, ad refreshes seem to stop.

Logcat with Google:

$ adb logcat | grep 'Ads' 
07-21 11:57:35.436 19508 19508 D DynamitePackage: Instantiating com.google.android.gms.ads.ChimeraMobileAdsSettingManagerCreatorImpl
07-21 12:08:31.991 10312 10312 I Ads     : Starting ad request.
07-21 12:08:31.991 10312 10312 I Ads     : Use AdRequest.Builder.addTestDevice("1CE2CD3D434E918C96914180EA4C634B") to get test ads on this device.
07-21 12:08:33.977 10312 10312 I Ads     : Scheduling ad refresh 70000 milliseconds from now.
07-21 12:08:34.027 10312 10312 I Ads     : Ad finished loading.
07-21 12:09:44.018 10312 10312 I Ads     : Starting ad request.
07-21 12:09:44.021 10312 10312 I Ads     : Use AdRequest.Builder.addTestDevice("1CE2CD3D434E918C96914180EA4C634B") to get test ads on this device.
07-21 12:09:45.461 10312 10312 I Ads     : Scheduling ad refresh 70000 milliseconds from now.
07-21 12:09:45.492 10312 10312 I Ads     : Ad finished loading.


Logcat with Millennial Media:


07-21 14:50:46.272 28137 28137 I Ads : Starting ad request. 07-21 14:50:46.273 28137 28137 I Ads : Use AdRequest.Builder.addTestDevice("1CE2CD3D434E918C96914180EA4C634B") to get test ads on this device. 07-21 14:50:46.644 28137 28667 I Ads : Trying mediation network: https://googleads.g.doubleclick.net/aclk?sa=L&ai=CEeWln1tyWZnnB8qRmQSMmYbIB_nJ2qYF0e-FupIBABAIIP6MoiRgyYaFiYikhBCpAgAAAACAhC5BqAMBqgQgT9BypXmp9lrPnGoIkgtjdy9v37fIRxGlvBQ-NQwVEHyQBgHABguAB4H4qTCYBwHSCAcIgGEQARgC&num=1&cid=CAASBORo_qk&sig=AOD64_1qw8SpPY39lJpDgwfZn1XsEnEfkA&adurl=http://example.com 07-21 14:50:46.651 28137 28137 I Ads : Instantiating mediation adapter: com.google.ads.mediation.millennial.MillennialAdapter 07-21 14:50:46.653 28137 28137 W Ads : Server parameters: {"gwhirl_share_location":"1","pubid":"357"} 07-21 14:50:47.130 28137 28137 I Ads : Ad finished loading.

...notice it doesn't schedule the next ad refresh? Any assistance here? Thanks!

--Mark

Deepika Uragayala- MobileAds SDK team

unread,
Jul 24, 2017, 3:05:12 PM7/24/17
to Google Mobile Ads SDK Developers
Hi Mark,

The team recently became aware that this issue has still not been fixed and we are investigating this. We will keep you posted if we have any new updates regarding this.

Regards,
Deepika Uragayala
Mobile Ads SDK Team


Deepika Uragayala- MobileAds SDK team

unread,
Aug 25, 2017, 11:42:01 AM8/25/17
to Google Mobile Ads SDK Developers
Hi Mark,

It looks like the issue is not reproducible anymore. Can you confirm to us whether you are still seeing the issue?

Regards,
Deepika Uragayala
Mobile Ads SDK Team


Mark B.

unread,
Aug 25, 2017, 4:12:24 PM8/25/17
to google-adm...@googlegroups.com
Deepika--

Sorry to say, but I've updated my test project to use 11.2.0, and I'm still seeing the issue... again, only with a mediated SDK downstream from Google.

--Mark

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/AvGXGrAf31k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Deepika Uragayala- MobileAds SDK team

unread,
Aug 28, 2017, 11:36:41 AM8/28/17
to Google Mobile Ads SDK Developers
Hi Mark,

Thanks for confirming. I will share this with the rest of the team and I will update you if I have any new information.

Regards,
Deepika Uragayala
Mobile Ads SDK Team


On Friday, August 25, 2017 at 4:12:24 PM UTC-4, Mark B. wrote:
Deepika--

Sorry to say, but I've updated my test project to use 11.2.0, and I'm still seeing the issue... again, only with a mediated SDK downstream from Google.

--Mark
Reply all
Reply to author
Forward
0 new messages