AdWhirl enables you to monetize your app inventory by allowing you to use multiple ad networks from within one client SDK. AdWhirl makes it easy to allocate a percentage of your inventory to the various ad networks and update your allocations in real time. By utilizing multiple ad networks, you can select the ad networks that perform best for your app and also make sure you have a high fill rate on your inventory.

Yes. Simply click on the "Custom Ad" tab in the AdWhirl website after you are signed in. You will be able to create and manage your custom ads and allocate any percentage of your available inventory to them.

AdWhirl allows you to serve ads from any ad network. Detailed instructions on how to include AdMob, JumpTap, Millennial, Quattro Wireless, and VideoEgg are included in the instruction manual. You can include additional ad networks in the AdWhirl Client SDK by using the Generic Notifications feature, or, by modifying the SDK source to include direct support for the desired network. The AdWhirl open source team is actively working on support for additional networks and is always happy to review patches that ad support for new networks.

Yes. You can turn ads on or off by using the switch on the top right of the My AdWhirl page, which affects all ads for the app that is currently being viewed.

Ad networks are sometimes unable to fill all ad requests. If your app requests an ad from a network that is unable to return an ad, AdWhirl will request an ad from the next prioritized ad network in the AdWhirl Client SDK until the request is filled. This ensures you nearly always have an ad to show and maximizes your fill rate.

No. Both the AdWhirl Client SDK and Server code are free to download and use.

No. AdWhirl is a free service to the mobile community and we believe that it is a necessary component of a healthy mobile ecosystem.

Yes, all features of the ad network libraries are enabled within the AdWhirl Client SDK.

You will receive payments directly from the ad networks you work with. AdWhirl does not have any insight into your business relationships with ad networks and does not have access to your eCPMs or earnings on the ad networks you use.

AdWhirl was acquired by AdMob in 2009. We decided to release it to the open source community so that ad mediation can be transparent and open. Developers can review the code and then decide which ad networks to include in their own custom build. AdMob has dedicated resources focused on improving the AdWhirl product and looks forward to working with the developer community at large to improve the product.



Most developers can setup AdWhirl in less than an hour. We have created a step-by-step guide that you can review before getting started, which you can download here.

Yes. You will need to retrieve the SDKs from each ad network you would like to include in the AdWhirl Open Source Client SDK. We have tested and verified that the SDK libraries for all supported ad networks are compatible with the AdWhirl SDK and have included detailed instructions to make integration easy for these ad networks.



Yes. You will need to register and create accounts with all of the ad networks you want to run within the AdWhirl SDK. You will receive your payment checks and reporting of revenue metrics directly from the individual ad networks. 



If you didn't receive a sign-up verification message in your email inbox, please check your junk/spam boxes, especially if you've applied very strict spam filtering options. If you still don't see a verification email, please contact us at support@adwhirl.com.

You can "turn on" an ad network after the application is already in the App Store for any ad network whose library you included in your AdWhirl build. That means you don't have to go through the hurdles of updating the application to the App Store. All you have to provide is your application key that you obtained from the new ad network, log into AdWhirl, and reconfigure your traffic allocation percentages.

You only have to return the AdWhirl application key. You can optionally implement methods to know when ads are received, when the in-app webview is visible when users tap on a banner ad (so you can pause games, for example), any many others, including the ability to pass in information so we can provide target ads with better CPMs - the methods are there for your benefit.



You can include additional ad networks in the AdWhirl Client SDK by using the Generic Notifications feature. You can learn more about how to use that feature by downloading the AdWhirl Client SDK Configuration Guide on the Instructions page.

You may also modify the AdWhirl Client SDK source to directly support the desired ad network, and, if you so chose, submit your patches to the AdWhirl open source team for possible inclusion in the AdWhirl Client SDK open source distribution.

Yes. You can change the origin of the rectangle frame to any spot you wish. You have full control over that frame and its size, but all of the ad content fits nicely in a 320x50 px frame size.



Yes. The client SDK checks to see if network connectivity is available before allowing any ad requests to run. If no network connectivity is available, no ad requests are made. Therefore, note that since no ad requests are made, no callbacks will be made.

When a refresh kicks in, a getNextAd call is made automatically. The call will choose an ad network based on the traffic allocation percentages you've applied. An ad request is then triggered. If the ad request fails, the backup ad network sources will then be used. If all of the backup sources are used and all ad requests still fail, the roller will stop fetching ads. As a result, you will not see an ad refresh. If you feel this isn't the case, please let us know about this issue right away.



The AdMob SDK includes compiled TouchJSON (and Quattro Wireless compiled TouchXML). Therefore TouchJSON (and TouchXML) are also included in the AdWhirl SDK. Version 1.0 is being used, so the way around this is to just include the TouchJSON headers (or TouchXML headers) without the class files so that you don't produce object files that will cause a linker error when the linker detects that TouchJSON (TouchXML) components are already defined. You can find the TouchJSON headers that they provided here.



If you're having issues with Pinch Media, it may be because TouchJSON is already included in the library (see question above). In that case, you can simply just include Pinch Media's Analytics headers (which can be downloaded here) and make analytics calls through the Pinch Media ad library that we've included. Otherwise, the other option is for us to give you a custom AdWhirl SDK client library with Pinch Media's ad library removed. Please let us know if you prefer to have this option instead.

Pretty simple. First, click on Info.plist and change the "Bundle Identifier" value to something that your provisioning profile supports (e.g. com.yourcompany.sampleapp). Then, go to the build tab after double-clicking on your application's target and choose a provisioning file + development certificate combo. Lastly, change your Active SDK platform on the upper-left section on XCode to Device - iPhone [2.0/2.1/2.2/2.2.1]. You may have to reopen XCode if you're still having issues during the code-sign process or application load process.



Yes. AdWhirl was built to handle massive amounts of traffic, and many apps that use AdWhirl generate millions of impressions per day, so you shouldn't worry about scalability issues with AdWhirl.

Yes. You can refactor the class names of your version of TouchJSON, TouchXML or FMDB and make calls to your refactored classes. In that case, for example, you would no longer run calls to CJSON or CXML, but you'd make calls to your own classes instead (e.g. ARJSON or ARXML). In the meantime, we're providing this feedback to ad networks and urging them to refactor these classes.



AdWhirl currently supports iPhone OS versions 2.2.1 and above. You can download instructions on how to configure AdWhirl for specific iPhone OS versions by visiting the instructions page.

You have full control over the roller's view frame. You will also notice that if you adjust the frame's size to any CGSize (such as 480x50), the roller's frame will adjust accordingly. However, the ad content will still stay at 320x50. Therefore, we recommend that you simply center the roller view in landscape mode. To do so, adjust the roller's view resizing mask to pad the left and right margins of the roller view (rollerView.autoresizingMask = UIViewAutoresizingFlexibleLeftMargin | UIViewAutoresizingFlexibleRightMargin). Also, don't forget to set the clipsToBounds property to YES so that the animation happens within the 320x50 frame and doesn't leak out of that frame. 



That is because Pinch Media's advertising library contains FBConnect. The workaround is to either refactor your version of the FBConnect classes, or make calls directly into the FBConnect object code that's been compiled into their library. Please refer to the AdWhirl Client SDK Configuration Guide on the Instructions page for more detail on how to do that.



AdWhirl supports both the x86 (simulator via intel platform) and ARM (iPhone/iPod device) processors, which is why there are two static libraries available. The warning is not an issue, and is the result of the linker's complaint that it can't link to a library that is supported for a different platform. But the linker will automatically link with the correct library before deploying the app onto your phone. There are thousands of free apps running AdWhirl as of today, so please rest assured that this warning is not an issue.