I built the ad mob example provided straight onto my android phone. Can someone explain to me why no ads are being shown on the mobile??
Also please explain, in your opinion, the best method to add Ad Mob ads to the app.
Finally, what exactly is the App ID?? I keep seeing this term and I cannot find App ID ANYWHERE within adMob… My app isn’t even in the app store or the play store…
Thankyou
Farid
When you create your app on the AdMob portal it will give you something like a PublisherID. This is an ID that is unique to the platform (iOS, Android) and the ad type (Banner, Interstitial), so you could end up with multiple of these PublisherID’s.
In Corona where we ask for the AdMob AppID, that is where you use the publisher ID.
There are may reasons why you would not get ads any where from not having things setup right in the AdMob portal, to no ads being available (Inventory in the ad world jargon), to not setting things up right in your Corona code. It’s hard to know what the cause is without looking in your console log to look for messages about what is going on. If you don’t know how to read your device’s console log, please read this post:
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Rob
Thanks for your reply Rob. It makes more sense to me now.
But still, I built the sample app which is provided by Corona, it says to build for the mobile to be able to see the ads as the simulator does not show them. I built it to my phone exactly how it is in the sample yet I still see no ads on my phone. If I knew why, it would help me to understand the whole advertising thing better.
Unless you can look in the console log of the device and look for errors, then I can only assume that either there isn’t enough inventory of ads to display for your app or you have something not right in the AdMob portal.
Just a thought.
Which Corona Build are you using 2189a?
And which Admob plugin are you using?
If V2 then the API docs say in one place that it’s valid for 2189 but lower down states about only daily builds - 2264 or higher.
I don’t know if the old NEW plugin can be used with legacy admob - i assume Not!
‘’
The AdMob “v2” plugin offers easy integration of AdMob ads using the ads library and ads.init().
This version of the plugin uses the latest version of the AdMob SDK and only works with build 2014.2264 or later.
Type CoronaProvider Library ads.* Revision Current Public Release (2014.2189) Keywords ads, advertising, admob Availability Starter, Basic, Pro, Enterprise Platforms Android, iOS
‘’
I think i am still a legacy Admob user (so i don’t know for certain)- but if you have changed as the deadline is very soon - and are trying to build with 2189a & V2 this could be an answer to your problem.
With these kind of forum posts - it would be wise to get in the habit of declaring your Build & if choices/options are involved (v1/v2) that information as well.
Again - i mention it as a thought because i don’t know. It’s just a potential future bottleneck that is on my radar, but it’s not at the top of my list of things to do (it might break in the future, but at the Mo - it’s not broke).
T.
Thanks ToeKnee for your reply. I am using version 2189 of corona but I have no idea how to see which version of AdMob I am using. In fact, I didn’t even know there were multiple versions.
How do you recommend I get around this problem? Surely there must be thousands of people with the same problem as me and Ads obviously play a large part in monetization.
I will bear that in mind next time I make a post, thankyou.
Farid.
What are you putting in your build.settings?
Rob
-- Supported values for orientation: -- portrait, portraitUpsideDown, landscapeLeft, landscapeRight settings = { orientation = { default = "portrait", supported = { "portrait", } }, plugins = { ["CoronaProvider.ads.admob"] = { publisherId = "com.coronalabs" }, }, iphone = { plist = { UIStatusBarHidden = false, UIPrerenderedIcon = true, -- set to false for "shine" overlay --UIApplicationExitsOnSuspend = true, -- uncomment to quit app on suspend --[[-- iOS app URL schemes: CFBundleURLTypes = { { CFBundleURLSchemes = { "fbXXXXXXXXXXXXXX", -- example scheme for facebook "coronasdkapp", -- example second scheme } } } --]] } }, -- Android permissions android = { usesPermissions = { "android.permission.INTERNET", "android.permission.ACCESS\_NETWORK\_STATE", }, }, }You are using V1 of admob. Here are the docs for V2. You should move to V2 as Google will stop supporting V1 in August.
http://docs.coronalabs.com/plugin/ads-admob-v2/
Rob
Again i stress this was only a possible suggestion to your problem, it could be unrelated.
Based on your build settings - I think you are using the old admob.
However that is from corona’s side - you are the only one who will know your setup with admob - my only suggestion is when you are on your admob site does it ask you to upgrade - if it does perhaps you are on legacy admob - i say perhaps because it’s an assumption on my part.
Rob may be better placed to answer the question of “new admob account but using old plugin {if possible - i assume not}”?
Second point you say 2189 - just to clarify when did you last download Corona and was it 2189a.
There are issues with public build 2189 so corona did a special quick fix public build and created 2189a - hopefully a normal public build is still on the way, and not delayed due to this special fix.
T.
Rob,
But the doc’s say V2 won’t work with 2189 - or will it work with 2189a?
I’ll have to ask and see.
Rob
So where is this sample “admob” app - i just check the sample code and only see iAds/ Inmobi / & interactive.
If it’s not too long it might be an idea to post the code - esp the code concerning how the ads API works - check docs.
Obviously replace your ID’s with XXXXX’s of better “faridXXXX” just to let us know that you have replaced with something.
Just to cover all possibilities - you checked internet/wifi connection - i.e. you could see ads in another app but then switch to yours and none.
I’m far from an ad expert - but just some things to check.
Also my admob site has a screen wide banner at the top “On August 31, 2014, legacy AdMob will no longer be available. All legacy ad serving will stop soon.” with a blue box “upgrade to new admob” on the right.
T.
AdMob V2 says it only works with 2264 or higher? My Corona build just says 2189, not 2189a. So either way I’m gonna need to upgrade my Corona build somehow?
Also, I’m assuming my AdMob account is updated because I pressed on the “Help” tab and it took me to a webpage with the address "https://support.google.com/admob/v2/"??
well if you are on the new admob account - afaik it requires you to use the V2 admob plugin - which as you know requires 2264 or higher - which as a basic user you don’t have access to. So you have limited choices, upgrade to Pro or wait.
If you decide to wait then my advice is to use the time to fine tune other aspects of your app to make it the best you can ( remember there are people out there who teach people to not “copy” but “model and improve”- which to the normal person they attract means copy - so improving your app and making it as perfect as you can will help combat cloners), or start that new project.
T.
When you create your app on the AdMob portal it will give you something like a PublisherID. This is an ID that is unique to the platform (iOS, Android) and the ad type (Banner, Interstitial), so you could end up with multiple of these PublisherID’s.
In Corona where we ask for the AdMob AppID, that is where you use the publisher ID.
There are may reasons why you would not get ads any where from not having things setup right in the AdMob portal, to no ads being available (Inventory in the ad world jargon), to not setting things up right in your Corona code. It’s hard to know what the cause is without looking in your console log to look for messages about what is going on. If you don’t know how to read your device’s console log, please read this post:
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Rob
Thanks for your reply Rob. It makes more sense to me now.
But still, I built the sample app which is provided by Corona, it says to build for the mobile to be able to see the ads as the simulator does not show them. I built it to my phone exactly how it is in the sample yet I still see no ads on my phone. If I knew why, it would help me to understand the whole advertising thing better.
Unless you can look in the console log of the device and look for errors, then I can only assume that either there isn’t enough inventory of ads to display for your app or you have something not right in the AdMob portal.
Just a thought.
Which Corona Build are you using 2189a?
And which Admob plugin are you using?
If V2 then the API docs say in one place that it’s valid for 2189 but lower down states about only daily builds - 2264 or higher.
I don’t know if the old NEW plugin can be used with legacy admob - i assume Not!
‘’
The AdMob “v2” plugin offers easy integration of AdMob ads using the ads library and ads.init().
This version of the plugin uses the latest version of the AdMob SDK and only works with build 2014.2264 or later.
Type CoronaProvider Library ads.* Revision Current Public Release (2014.2189) Keywords ads, advertising, admob Availability Starter, Basic, Pro, Enterprise Platforms Android, iOS
‘’
I think i am still a legacy Admob user (so i don’t know for certain)- but if you have changed as the deadline is very soon - and are trying to build with 2189a & V2 this could be an answer to your problem.
With these kind of forum posts - it would be wise to get in the habit of declaring your Build & if choices/options are involved (v1/v2) that information as well.
Again - i mention it as a thought because i don’t know. It’s just a potential future bottleneck that is on my radar, but it’s not at the top of my list of things to do (it might break in the future, but at the Mo - it’s not broke).
T.