iOS v6.10.0 is launching all click-through ads in Safari instead of modally inside the app

247 views
Skip to first unread message

Tracy Keeling

unread,
Jul 22, 2014, 12:33:23 PM7/22/14
to google-adm...@googlegroups.com
We would like to upgrade the iOS SDK in our app to resolve a crash we were getting from v6.9.2.

We created a build with v6.10.0 of the SDK, but now all of the banner ads open externally on click-through.  This is easy to reproduce with the test ad, which claims:
- clicking on the main part of the ad will launch externally in Safari
- clicking on the info icon will launch inside the app

Both actions are launching externally in Safari with v6.10.0.  With v6.9.2 the test ad works as advertised.

We really don't want to have our users leave the app every time they click on an ad, so we don't want to use v6.10.0.

Is there anywhere we can download v6.9.3 which will supposedly fix the crash but hopefully not have this other issue?

Can you confirm the issue with v6.10.0?

Thanks,
Tracy


Eric Leichtenschlag

unread,
Jul 22, 2014, 7:35:55 PM7/22/14
to google-adm...@googlegroups.com
Hmm, I've confirmed that the Ads By Google button on v6.10.0 now goes to Safari, but my main concern about that change is there isn't a way to test the in-app browser case on iOS. As far as the ads themselves, most ad templates already click through to Safari. This is actually preferred from the SDK perspective since it allows the SDK to better track conversions. So even if the test ad is fixed, it likely won't affect the percentage of live traffic that opens in Safari vs in-app browser.

I'll follow up internally though why the test ad behavior changed on 6.10.0.

Thanks,
Eric

Tracy Keeling

unread,
Jul 22, 2014, 7:43:58 PM7/22/14
to google-adm...@googlegroups.com
To be clear, this is affecting live ads as well.  Ads that are supposed to open in an in-app browser are opening in Safari instead.

I do not understand your statement that "there isn't a way to test the in-app browser case on iOS".  What exactly are you unable to test?

Eric Leichtenschlag

unread,
Jul 23, 2014, 5:49:48 PM7/23/14
to google-adm...@googlegroups.com
After following up on this, opening up in Safari was an intentional change starting in 6.10. As mentioned before, this is done for better tracking conversions which in the long term should increase RPM for publishers.

j.sa...@gmail.com

unread,
Sep 17, 2014, 10:26:38 PM9/17/14
to google-adm...@googlegroups.com
The release note states: 
  • Ads now default to opening in Safari instead of the in-app browser.

Since it mentions this is default behavior, this indicates that this is overridable.  I don't see documentation on how to override this behavior.  While you state that publishers will prefer this long term due to conversion tracking, our preference is that we leave the user in the app and to not see them get kick out of our app if they click an ad.

Can you please on how we can override this.  The only documentation I could find online was for the IMA library, not the standard iOS admob library.

Thanks,
Jay

Eric Leichtenschlag

unread,
Sep 18, 2014, 3:11:12 PM9/18/14
to google-adm...@googlegroups.com
The app can't override this, but the creative owner can either use mraid.expand if they're using mraid, or admob.opener.openOverlay if they're using the AdMob API for Ads to make the ad open in-app.

Shana Weitzen

unread,
Nov 6, 2014, 8:51:50 PM11/6/14
to google-adm...@googlegroups.com
Is there not a way to override this behavior solely through DFP and not using AdMob API or mraid? 

Thank you,

Shana 

Eric Leichtenschlag

unread,
Nov 6, 2014, 10:53:05 PM11/6/14
to google-adm...@googlegroups.com
Unfortunately there is not right now. DFP might be working on adding such an option, but I'll have to verify.

Thanks,
Eric

Shana Weitzen

unread,
Nov 7, 2014, 12:19:58 PM11/7/14
to google-adm...@googlegroups.com
Okay, Thank you for getting back to me so quickly.

-Shana 

--

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

Eric Leichtenschlag

unread,
Nov 11, 2014, 2:44:31 PM11/11/14
to google-adm...@googlegroups.com
So the update I have on DFP providing a workaround is essentially no update. We do realize this has been a pain point for several DFP publishers, and that there needs to be some easier way to override the default behavior, but I don't know what that change will look like or what the timeline is for pushing it out.

Thanks,
Eric
To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

Shana Weitzen

unread,
Nov 12, 2014, 2:47:35 AM11/12/14
to google-adm...@googlegroups.com
Hi Eric, thank you for the update. So we can expect a solution we just don't know when?

Thank you,

Shana 

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

Shana Weitzen

unread,
Nov 12, 2014, 2:06:26 PM11/12/14
to google-adm...@googlegroups.com
You mentioned that it is a pain point for DFP publishers, does this suggest that developers have found a workaround?

Eric Leichtenschlag

unread,
Nov 13, 2014, 11:45:45 AM11/13/14
to google-adm...@googlegroups.com
Right now there's still no workaround other than running your own custom creative that opens an overlay.

I can't promise there will be an easier solution. But given the pushback, I think it's likely something will be done.
Reply all
Reply to author
Forward
0 new messages