Mobwhirlgate: The AdWhirl plus AdMob saga continues

AdWhirl AdMob Saga

AdWhirl AdMob Saga

As an AdWhirl user I got an email from the founders mentioning that AdWhirl is no longer allowed to have any visibility into AdMob’s library for ad cycling and or eCPM optimisation.

The email starts with the reason behind the AdMobgate or Mobwhirlgate scandal.

AdMob additionally required that we prove that AdMob ads in-app are not optimized through our library, so we have added in an unobtrusive branding effect. Since we made ad requests directly from AdMob’s library, it was impossible for them to tell whether traffic was coming through an app using AdWhirl or an app using exclusively AdMob; unfortunately, their new policy was simply to ban indiscriminately unless we could show the difference, so we built in this feature to protect developers.

But then moves to the positive and shares 3 pieces of good news:

1. Legacy support for AdMob will continue.

2. AdWhirl now supports generic notifications that will allow developers to set up ad networks even if they have not exclusively partnered with AdWhirl (Greystripe and Google Adsense)

3. We are now supporting a new ad network MdotM. Plus Jumptap will be on board soon.

What we think?
The plot thickens. This is an honest email from AdWhirl and makes AdMob look even worse for banning them with a half-blood reason.

About Bena Roberts

GoMo News' founder and former managing editor, Bena Roberts has now moved on. She's now spending more time with her family. Tony Dennis has now assumed her mantle as the site's editor.
This article was published in Mobile Ad&Mktg, Mobile Agencies, Mobile Marketing, Mobile Web, Mobile applications, google, iphone and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>