Cross-promotion network for Windows 8 and Windows Phone apps

Frequently Asked Questions

Here's a quick overview of all the basics of AdDuplex. Please take a few minutes to watch it if you are new to AdDuplex. It should answer most of your initial questions.

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?

We support text and static image based banner ads. One standard size is supported on Windows Phone and multiple sizes are supported in Windows Store apps.

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, or other ways such as in-app purchases, paid apps, etc.

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 (an updated post coming soon). Alternatively you can use Ad Rotator meta-control to combine and control ads from several ad networks including AdDuplex.

Why would I want to use AdDuplex if I'm already displaying ads from other ad network in my app?

Other than obvious value in promoting your apps for free, the answer is in understanding the concept of "fill rate". Ideally, for every ad request you make to your ad network it would return an ad that you would be compensated for (at least potentially).

Unfortunately, we do not live in the ideal world and that is not the case. Fill rate is a measure of how many ad requests are actually fulfilled with an ad. And it's almost never a 100% (the ideal case). According to various reports fill rates could be as low as 10% on average across the mobile ad networks worldwide. So, unless you are complementing your primary ad network with other ad networks and/or "house ads", you are wasting the valuable ads space quite often. Maybe even 9 times out of 10!

AdDuplex is a great way to complement your commercial ad network(s) as a fallback solution for cases when they don't have an ad to show. Due to its nature AdDuplex has a virtually 100% fill rate (the only case when you aren't getting an ad is if there are some connectivity issues). This way you can combine the best of both worlds: get paid when commercial networks have the ads to show and get free advertising for your apps when they don't.

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

I've added your control to my app, published it and it is showing ads, but the statistics in the client area are not updated and the app is still in "pending activation" state. What's going on?

Normally we activate apps the next day after we start seeing ad impressions coming from them in our logs. If your app is not activated in 3 days after publication of the update with AdDuplex control in it, the most common reasons are these:

  • The AppId property on the ad control is set incorrectly (it should be a 4-6 number that you can see in the client area, not the Store ID you see in the Stores);
  • You have accidentally published the app with IsTest property set true on the ad control. You can verify this by checking your source code or if your app displays your own ads. You'll need to revert IsTest back to false and update the app in the Store;
  • The ad control is fully or partially covered by some other control (even if transparent). You can test for this by temporarily setting IsTest property to true and running the app. It will display a message box in a few seconds after showing the ad, if that's the case. Figure out what is covering the ad control and update the app to resolve the issue.
This blog post covers these issues in more detail.

I can't find an answer to my question/problem in this FAQ.

Contact us at and we will get back to you with an answer or look for a solution together.