I got an email from admob about account upgrading. Here is the fragment:
Legacy admob will be shutting down on 31 august 2014. this means that on 31 august, you will no longer be able to use legacy admob to promote and monetise your apps. specifically, please be aware of the following:
Ads will stop serving to legacy ad units that are not migrated.
House ad campaigns will stop serving.
You will not be able to access the legacy admob ui after 31 august 2014.
Further details available in our Help Center.
This is very important sentence:
“Ads will stop serving to legacy ad units that are not migrated”
As I understand ads will be served to old units but you have to upgrade the admob account. It makes sense (I think…), because in the new admob old ad units are mapped to the new ones. So I guess that when there is an ad request with the old ad unit it is mapped to the new ad unit (from new admob servers) and that new mapped ad id is used for the ads. If old ad unit is not mapped on the server then ad request will fail. So yeah… there is no choice and we all have to upgrade admob (I did it yesterday).
I’ve read a whole lot now and there are some facts:
old admob (legacy) will stop to get ads at 31st august. Everyone not upgraded the sdk will be without ad revenue - and it seems, they will turn off legacy admob at all so you will not be able to login to legacy and lose all your data - you will not be able to import any data after 31 august (from what they say)
google play services are NOT required on the target device. ad serving is built into the sdk you link in your apk. when there is a newer version of the gplay services on the phone, your app will use this but fall back to its own thing when not available (true for amazon i.e). if you use ANY other services from gplay services, you will have to rely on installed gplay - just for the ads it’s sufficient to include the lib in your apk. that’s confusing because admob is not stating that clearly because this assumption is only true for the ad serving but NOT for the other gplay services.
But you have to update and you have to resubmtr your aps whereever you have uploaded them. You will lose the option for paypal payout.
Personally, I use this work to update all backends I use in my games and integrate interstitials in my apps. But I still don’t like this step … but it had to happen some day (unfortunately)
No, no e-mails. And during the talk I had with adMob representative not a word about the need to get rid of legacy ids in my apps (fortunately most important of them use mopub which allows me to easily switch the ad id).
Guys it clearly states on the sdk integration help pages of admob that admob sdk will no longer be compliant. And you know what compliance means to Google (banning).
So as of result, Iam updating all my apps to use Google play services and removing the sdk
still updating … many apps … eclipse regulary killing itself when removing libraries … still a lot to do to update multiple stores … oh man … headache. need beer
after migrating to new admob, and after signing adsense and adwords accounts upon sign in, can i change them in the future. for example now when i’m in the new admob, i want to change my adwords account to another (with another e-mail). can i do that or i’m forced to use these accounts?
this is so i can use account with currency set to EURO, because i make a mistake when i input currency type into my account…
According to this Google AdMob Help, it seems that we still need to update the mediation ID to the new Ad Unit ID.
Apps you previously monetized in legacy AdMob used legacy Publisher IDs to identify the ad units and legacy Mediation IDs for mediation. Both of these IDs have been replaced by a single new ad unit ID. To benefit from all of AdMob’s mediation features, you need to update the legacy IDs in each of the ad units in your apps to their corresponding new ad unit IDs, then republish your apps.