Frequently Asked Questions
This FAQ refers to the Windows Phone version of the SDK. It will be updated to reflect frequently asked Windows 8 questions as we get them.
What's in it for you? What's the catch?
For each 10 ads displayed in your app you get 8 impressions of your ad. The difference is ours to sell. This is how we make money to support the service.
I'm not in the USA. Can I still join?
AdDuplex is open for anyone in the world.
What type of ads do you display?
Currently we display text based ads only. They consist of 4 lines of text displayed in pairs and animated from one pair to the other. The ads can link directly to the marketplace or web URL (for commercial campaigns). Support for graphic ads is coming in the near future.
How much should I expect to make from AdDuplex?
AdDuplex is not a monetization platform. Our goal is to help you gain popularity so you can then monetize your app better using other ad networks targeted on monetization.
I'm already displaying ads from another network in my app. Can I use AdDuplex in conjunction with other networks?
Absolutely. Complementing traditional commercial ad networks is one of intended uses of AdDuplex. We have a blog post on how to do this manually in Silverlight. Alternatively you can use the great Windows Phone 7 Ad Rotator control by Gergely Orosz to combine and control ads from several ad networks including AdDuplex. For XNA apps take a look at ImproviSoft's Ad-Network Manager with House Ads.
I've implemented your control, but I'm only getting the default AdDuplex ad. What am I doing wrong?
Provided that there are no connectivity problems there are a couple of things that can cause that:
- AdDuplex control is obstructed by some other element on your page. Make sure nothing covers (in full or partially) the AdDuplex control when it becomes visible.
- You have a startup animation that renders the control invisible (or obstructed) on launch. Make AdDuplex control collapsed on launch and only set it to be visible when your startup animation is completed.
- You have no ID_CAP_NETWORKING capability specified in your app's manifest. Add <Capability Name="ID_CAP_NETWORKING" /> to your WMAppManifest.xml