Code Monkey home page Code Monkey logo

Comments (7)

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
Hi Thomas,

Depending on your app and fill rate this is definitely possible. Also, were you 
using the same AdWhirl SDK key in a 3.x app? If you did, the 70% for iAd will 
be ignored, and custom ads will be bumped up to 100%, further skewing the 
statistics.

Is there any more information you can provide?

Original comment by [email protected] on 8 Jul 2010 at 12:09

from adwhirl.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
Hello,

I don´t see how these statistics are possible. AdMob fill rate is almost 100%, 
iAd fill rate is extremely low because most ads are requested outside the US. 
When I assign 70% to AdMob, it works well. When I assign 70% to iAd, AdMob ads 
should be requested instead in most cases.

iAd is not ignored, I do receive some iAd ads. This version of the app ist the 
first version using AdWhirl, so there are no 3.x versions of the app with 
AdWhirl.

Original comment by [email protected] on 8 Jul 2010 at 5:50

from adwhirl.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
Is your app 4.0-only? Did you change the deployment target to anything lower 
than 4.0? If so, 3.X devices are running your app, and those devices are always 
show custom ads.

Original comment by [email protected] on 8 Jul 2010 at 6:11

from adwhirl.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
The app supports 3.0 and above. 3.x devices are running the app but why 
wouldn´t these devices show AdMob ads instead of iAds? According to backfill 
priorities, AdMob should be chosen, not custom ads.
Is it possible at all to have iAds shown whenever possible (-> 100%) and use 
the remaining capacity for other ad networks (-> backfill)? Will 3.x devices 
then show no ads at all?

Original comment by [email protected] on 8 Jul 2010 at 8:50

from adwhirl.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
I think there's a misunderstanding of how backfill works in this situation. 
When a 3.0 device receives your configuration, it drops the iAd portion 
completely. So with your configuration -- iAd 70% and custom 30% , to a 3.0 
devices it is as if the iAd portion does not exist. 3.0 devices will not even 
attempt to fetch iAd ads and so there is no failure, hence there are no 
backfills. Normalizing the percentage, it is equivalent of having 100% custom 
ads.

To achieve what you want, you should create two sites in adwhirl. And in your 
app code, return a different adwhirl id depending on whether iAd is available 
(or the OS version). Than you can configure each adwhirl site differently.

This seems to be a signal for us to write clearer documentation wrt iAd and 
older, pre-4.0 devices.

Original comment by [email protected] on 9 Jul 2010 at 6:13

  • Changed title: Backfill priorities not working as expected for iAd in 3.0 devices (need documentation)

from adwhirl.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
Hey Tom, can you add this to the helpcenter docs somewhere?

Original comment by [email protected] on 13 Jul 2010 at 6:04

from adwhirl.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 16, 2024
Thanks for updating.

Original comment by [email protected] on 14 Jul 2010 at 5:30

  • Changed state: Fixed

from adwhirl.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.