Hi Corona;
Please add me to the list of people willing to pay a reasonable for an admob plugin. With that being said please, please, please don’t make it a part of Corona Ads!!
I’m going to touch on a couple of issues not raised above – but issues which I believe to be pertinent to this overall discussion. My points are based on my experience these last 6 months.
#1 – We have apps for which the #1 source of Ad Revenue has been Chartboost Interstitials and #2 has been AdMob Interstitials. We were pushed into using Chartboost “through” Corona Ads this autumn when the older 3rd party plugin was removed. I certainly did not mind having 5% of the revenue go to Corona. But we saw an immediate drop in Chartboost revenue of 50% on the same app displaying Chartboost ads in the same places with the same frequencies. This was true when we compare succeeding months (Sept. & Oct.) where the app’s play sessions, DAU, etc. were actually going up a bit. The Chartboost eCPM through Corona wasn’t that bad but the fill rate must have dropped significantly (we can’t actually see that stat in the Corona Dashboard). I’d be happy to share specifics (confidentially) with somebody at Corona if they are interested. Here is a note of speculation on what might have occurred to cause this drop – we have some excellent game apps with good demographics and I feel like Chartboost used to give us some of the “cream” advertising because we were an excellent performer for them. Now, Chartboost can’t (or doesn’t) pick us out and reward us – we are now simply a part of a pool of Corona apps. Why is Chartboost relevent to this AdMob discussion?? I fear that our high levels of AdMob revenue might drop in the same manner once we are simply a part of the Corona pool. It is worrisome.
#2 – Have any other Devs out there picked up on a problem that rises out of the “fine location” permissions (and other Android permissions) required by Corona Ads? When you use Corona Ads, you end up publishing to fewer devices. I’ll try to keep this brief but here is what we found:
A ) We “inadvertently” left the Corona Ads plugin in our Google/Android build.settings file for our Just Jumble app when we did an update last June. We weren’t going to use the plugin; we had simply been testing it out. Over the following 3-4 months, we received a number of e-mails EVERY WEEK from disappointed Android users complaining that they could no longer update the app as their device was not supported. Many of these user had recently purchased tablets (i.e. not old clunkers) running fairly new Android OS versions. We were puzzled by the numerous reports and complaints.
B ) The Corona staff really do listen and we encouraged Corona to add support for Amazon Devices in Corona Ads (and, by extension, Chartboost). Bless them, they did this in September. Hurray, we appreciated what they did! But when we tried to publish an Amazon update in October using the Corona Ads plugin on Amazon devices, fewer than half of the Fire Devices would be “supported” if we used Corona Ads. This drop in device support on Amazon made us go back and look at device support on Google Play (“a” above).
By trying a few different builds and submitting them to Google and Amazon, you can see in the attached screenshots (#1 and #2) how many Amazon Devices are NOT supported when you include Corona Ads (probably over half of the installed base of Kindles). And you can also see that removing the “inadvertent” inclusion of the plugin on Google Play devices resulted in an INCREASE in supported devices of roughly 10% (1,200+ additional supported devices).
So back to my first sentence. Please DO come up with an AdMob solution that allows us to keep using it in the flexible, direct-with-Google way we have had – even if it involves a fee. And, for heaven’s sake, please don’t make us include the Corona Ads plugin because it has a fair number of serious issues of its own! Thanks;
Steve Bullock