I’ve been using AdDuplex to promote Car Dash for awhile now. I’ve always been pleased with my results from AdDuplex campaigns but today I wanted to see if I can improve my conversions with some A/B testing. I’m going to setup the A/B testing today and come back with the results in a few weeks.
A while ago I wrote a post on adding AdDuplex ads to your App Studio App. In that post I added AdDuplex as a fallback option should the PubCenter ad control fail to display an ad. At the end of the post I noted that AdRotator would be a better option for supporting multiple ad providers, but at that time AdRotator did not support Universal Windows Apps. Since then I joined Simon Jackson and worked on adding Universal App support for AdRotator, time for a new tutorial post!
2014 is quickly coming to a close. I really can’t believe how fast this year has gone by, or how much has happened over the past 12 months.
A few weeks ago Microsoft announced Windows Ad Mediation. Their own solution to the problem that the Open Source AdRotator project has helped app developers with since the early Windows Phone 7 days. Since both AdRotator and Windows Ad Mediation are trying to fix the same problem I wanted to look at the different scenarios for Windows and Windows Phone app developers and see which solution made sense for you.
I recently attended a MMADNJ user group session by Nick Landry covering App Studio. Nick created a new app using the App Studio tools and published it by the end of his talk. I followed along creating my own app, Destiny Hub, which was published the day after the user group session.
App Studio gives you the options to add Pubcenter ads to your App Studio creation, but I wanted to have AdDuplex ads as well. Having AdDuplex ads in my app will allow me to advertise my app and get more users for Destiny Hub. So today I’m going to go over the process I went through to add the AdDuplex controls to an App Studio Windows 8.1 and Windows Phone 8.1 app.