Migration Completed

I’m happy to report that server migration went smoothly and everything should be operational by now in full capacity. In case you notice any irregularities and/or bugs in the new setup, please, don’t hesitate to let us know at info@adduplex.com.

One thing to notice is that the new servers are operating on UTC timezone settings and old ones were on CST. So, even though there was no interruption in service, you will probably notice a drop in your stats for March 2 since the “server day” was 6 hours shorter than the real one.

Planned Migration, Client Area Downtime

Thanks to all the app authors participating in AdDuplex network for making it a success and driving traffic up! In order to provide best possible service going forward we decided to move our servers to Windows Azure.

Tomorrow, March 2nd, 2011, we will be performing a planned migration to a new hosting environment. The core ad serving engine should stay operational throughout the process, but we will close the client area on the old server to maintain consistency. We plan to start the process around 7:00 AM GMT. Please, make any planned changes to your ads before that time. You will be able to access Client Area on a new server once DNS records are updated (usually within a day).

Thank you for your cooperation!

Incoming Clicks Statistics

Up until now our app statistics page reported on the clicks originating from your app. That was probably not the most interesting metric for you. Way more interesting is how many clicks did you get on your ads displayed in other apps. Now you can learn just that.


Keep in mind that we track Marketplace clicks in unobtrusive way. Meaning that the click is only tracked when user returns to the app where he/she clicked on the ad. If the user never returns to the app, the click is not registered in the system. So, the actual number of clicks (both incoming and outgoing) is most definitely higher than reported.

Announcing AdDuplex XNA SDK


I’m happy to announce that we have completed initial development and internal testing of AdDuplex library for XNA. We would like to test it with a couple of XNA apps before making it available for the general public and we need your help.

We Need Your Help

We would like to make a test run of the SDK with 2-3 apps and we are looking for developers willing to participate in this closed beta. We are looking for XNA games that are already in the marketplace and can/wish to push out an update with AdDuplex SDK within a week or so.

What We Offer in Return?

If you participate in the beta we will give you a permanent exchange ratio of 0.9 (normally – 0.8) or 10,000 free ad impressions on the network. It’s up to you to choose what you prefer.

How to Participate?

In case you want to participate please send an email to info@adduplex.com with the name of your game/app and approximate timeframe for the next update (with AdDuplex code).

Thank you!

Use Your WP7 App Popularity to Promote Your Other Apps

Our terms and conditions contained a clause that prohibited apps participating in Ad Exchange to use their credits to promote anything else than themselves. After some consideration we decided that this clause is too strict for no particular reason. We’ve rewritten that clause and now it looks like this:

4.1. Apps participating in the Ad Exchange Program can only have ads advertising official Windows Phone 7 Marketplace apps. Advertising of other apps or services is prohibited.

This means that now you can leverage popularity of one or several of your apps to promote your newer or less popular apps. A great way to boost exposure of that great app that went under the radar for some reason.

Can’t Commit 100% to AdDuplex? You Don’t Have To!

There’s a lot of developer interest in AdDuplex. Thank you! That said one repeating theme I hear is that it’s hard for developers to decide not to earn any money from their apps at start. I thought it goes without saying that you are not required to be exclusive neither to AdDuplex, nor, as far as I know (but you should check the terms), to any of the other, traditional ad networks.

So, to set the record straight I’ve decided to post several implementation samples for scenarios mixing AdDuplex with other ad networks.

Scenario 1. Different pages – different ad networks

Not much to add here. Just implement some ad network on some pages of your app and AdDuplex on other pages.

Scenario 2. Distribute impressions by some ratio

You can just dedicate some percentage of your app usage to showing ads from some ad network and the rest to AdDuplex. A 50:50 split could be implemented like this:

var rnd = new Random();
if (rnd.NextDouble() > 0.5)
    AdNetworkAd.Visibility = Visibility.Visible;
    AdDuplexAd.Visibility = Visibility.Collapsed;
    AdNetworkAd.Visibility = Visibility.Collapsed;
    AdDuplexAd.Visibility = Visibility.Visible;


Scenario 3. Show AdDuplex in regions not supported by the other ad network

The best known example is Microsoft’s pubCenter. It shows ads to US customers only. So you can safely show AdDuplex to non-US users without loosing a single cent of your ad revenue. A code like this would do it:

if (CultureInfo.CurrentCulture.Name == "en-US")
    AdNetworkAd.Visibility = Visibility.Visible;
    AdDuplexAd.Visibility = Visibility.Collapsed;
    AdNetworkAd.Visibility = Visibility.Collapsed;
    AdDuplexAd.Visibility = Visibility.Visible;


These are just some of the most obvious scenarios. You can implement more advanced scenarios yourself. One that would make a lot of sense is if your commercial ad network collapses the ad space when it can’t serve the ad for it. You can hook up to this event and display AdDuplex when the network fails.

As you can see there’s no reason not to maximize ROI of ad space in your apps. It’s easy and straightforward to implement, and AdDuplex ad control is on 27kb (uncompressed) so there’s basically no tax for doing so.

Makes sense? Join AdDuplex now!

Worry About Popularity First, Monetization – Second

I’ve published a post in a personal blog about my position on current state of affairs in WP7 marketplace in regard of monetizing your applications. I think it makes the case for AdDuplex and is the basic reasoning why AdDuplex was born.

The post is called Don’t “monetize” your WP7 apps on Day 1.

And the main point is that gaining popularity for your app is much more important at this early stage of Windows Phone Marketplace, than getting a few extra bucks.

AdDuplex is Now Open for Registration + Bonus

banner_square_freeAdDuplex – a new innovative way to promote your Windows Phone 7 apps for free – no longer requires invitations to join.

AdDuplex helps you promote your WP7 app by helping other developers/publishers to promote their. You just add AdDuplex AdControl to your WP7 Silverlight application (XNA support coming later) and start showing ads for other apps on the network. They, in turn, show ads for your app. It’s that simple.

The exchange ratio is currently set to 8:10. This means that for each 10 ads you show for other apps you’ll get 8 impressions for your app’s ad. The remaining 2 will be sold to support the service.

Join now!

Go Live in February and Get 1000 Impression Bonus!

Register your app on AdDuplex network, implement AdControl and go live in Windows Phone 7 marketplace by the end of February, 2011 and get 1000 extra impressions for your ad absolutely free.

AdDuplex Control Version 1.1 Released

A new version of AdDuplex Silverlight AdControl is now available. It ads click tracking for Marketplace ads (all exchange ads). You can download it from the client area of the AdDuplex site.

In order to facilitate the best possible user experience we didn’t track clicks on WP7 Marketplace targeted ads in the first release. Now we found a way to overcome this limitation without sacrificing the quality of user experience.

Applications running earlier version of AdControl don’t need to update, but we encourage you to use the latest AdDuplex version when you submit a planned update to your app.