我可以添加一个新的AdWhirl广告网络为现有的应用程序？ [英] Can I add a new AdWhirl ad network for an existing app?
问题描述
我现在有AdMob和iAd的在AdWhirl中设置配置为我的iOS应用程序，这是目前在App Store上。我想补充的InMobi为好。很显然，我需要将SDK的InMobi添加到我的应用程序，做一个更新的应用程序。我担心什么虽然是，一旦我启用的InMobi会发生什么旧版本我的应用程序。他们将获得他们不能处理的InMobi的请求？基本上，这将是一个问题？
I currently have AdMob and iAd configured in the AdWhirl settings for my iOS app, which is currently on the app store. I'm thinking of adding InMobi as well. Obviously I'll need to add the InMobi SDK to my app and do an update for the app. What I'm worried about though is, what happens to old versions of my app once I've enabled InMobi. Will they get InMobi requests they can't handle? Basically, will it be a problem?
推荐答案
这其实是一个非常好的问题。如果您更新了UI的AdWhirl配置添加的InMobi，运行老版本的应用程序的用户将获得新的配置。最重要的是怎样的AdWhirl处理配置。该行为是iOS和Android不同，但我认为无论是相关的。
This is actually a very good question. If you update your configurations in the AdWhirl UI to add InMobi, users running the old version of your app will get the new config. What is important is how AdWhirl handles the config. The behavior is different for iOS and Android, but I think both are relevant.
的简短的回答：的
的iOS ：百分比是标准化的有效网络
iOS: Percentages are normalized for valid networks.
的Android ：顶在有效回填优先网络消费前填写百分比无效的网络
Android: Top valid network in back fill priority consumes front fill percentages for invalid networks.
说明：的
的iOS：：当iOS的尝试<一个href=\"http://$c$c.google.com/p/adwhirl/source/browse/iphone/AdWhirl/internal/AdWhirlConfig.m?repo=sdk-iphone#460\"相对=nofollow>解析一个新的配置，那就只能设置为符合一定条件的广告网络，包括<一个配置href=\"http://$c$c.google.com/p/adwhirl/source/browse/iphone/AdWhirl/internal/AdWhirlAdNetworkConfig.m?repo=sdk-iphone#121\"相对=nofollow>具有相应的适配器。否则，该网络的配置返回零，并且只有有效的网络中包含的中介。那么你的的百分比将归。如果你有20％的AdMob，20％的iAd和60％的InMobi，旧的应用程序，只有AdMob和iAd的会出20/40 AdMob，并为20/40的iAd，或者为每个网络50％的百分比。回填重点将是相同的预期，但exluding无效的网络，如的InMobi。
iOS: When iOS tries to parse a new config, it will only set up configurations for ad networks that meet certain conditions, including having the corresponding adapter. Otherwise, the config for that network returns nil, and only the valid networks are included in the mediation. Then your percentages will be normalized. If you had 20% AdMob, 20% iAd, and 60% inMobi, the percentages for old apps with only AdMob and iAd will be out of 20/40 for AdMob and 20/40 for iAd, or 50% for each network. Backfill priority will be the same as expected, but exluding invalid networks like inMobi.
Android的：：当Android的尝试<一个href=\"http://$c$c.google.com/p/adwhirl/source/browse/src/com/adwhirl/AdWhirlManager.java?repo=sdk-android#339\"相对=nofollow>解析一个新的配置，你的老的应用程序会盲目添加的InMobi作为配置。该SDK通常包括作为一个罐子其中包括广告网络适配器的所有.class文件，因此在该检查是不是对Android侧进行。不同于iOS版，Android版的会尽量让即使是在旧的应用程序向InMobi的请求。该请求将正常失败，但随后的AdWhirl会滚动到你的回填优先即可。这意味着，如果你有20％的AdMob，20％的iAd和60％的InMobi和iAd的是你的首要优先回填，你会得到本质上80％的iAd和20％的AdMob旧的应用程序，只有AdMob和iAd的软件开发工具包包括在内。在Android上做这样的更新时，因为结果可能不是你预期什么要小心。
Android: When Android tries to parse a new config, your old apps would blindly add inMobi as a configuration. The SDK is generally included as a jar which includes all .class files for the ad network adapters, so this check isn't made on the Android side. Unlike iOS, Android will try to make a request with inMobi even on old apps. The request will fail gracefully, but then AdWhirl will roll over to your backfill priority. This means if you had 20% AdMob, 20% iAd, and 60% inMobi, and iAd was your top backfill priority, you would essentially get 80% iAd and 20% AdMob for old apps with only AdMob and iAd SDKs included. Be careful when making such updates on Android as the result may not be what you anticipated.
这篇关于我可以添加一个新的AdWhirl广告网络为现有的应用程序？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
