Microsoft Universal Ad Client SDK for Windows 10

The Microsoft Universal Ad Client SDK is now available for Windows 10 devices. The ad SDK also supports Windows and Windows Phone 8.1 apps. The new ad SDK is built using native code and does not require .NET runtime, reducing the memory used and increasing performance. In addition, the new Ad SDK integrates several bug fixes and reduces the minimum refresh time to 30 seconds (previously it was 60 seconds when the app was running in metered networks).

Support for video interstitials

Today we are releasing the capability to display video interstitials through the Microsoft Universal Ad Client SDK. Video ads are a highly popular way of monetizing apps and games, and can offer higher eCPM than banner ads. Video Ads are supported in Windows 10, Windows 8.1 and Windows Phone 8.1 through the Microsoft Universal Ad Client SDK released today.

Read the instructions on how to use video interstitials to get started.

Dev Center has supported ad mediation for Windows Phone apps for some time now, allowing you to manage multiple ad SDKs from different providers to achieve up to a 99% fill rate, thus increasing the ad revenue in your apps. Enabling ad mediation is easy, just add the Windows ad mediation SDK to an app and submit it to the Store. You can then managing multiple ad networks without having to modify the app code or resubmit the app for certification.

With the new release, you have the same capabilities and reports provided previously for Windows Phone ad mediation, such as tracking fill rate for each ad network and users by configuration. Ad mediation is supported by both Visual Studio 2015 and Visual Studio 2013, and supports Windows 8.1, Windows Phone 8.x, and Windows 10 UWP apps.

As we continue to roll out new features and tools for Dev Center, please let us know if there are any issues (through support) or new features you’d like to see included in future releases (through user voice).

Error 1 To ensure the correct metadata resolution, the type ‘Microsoft.Advertising.WinRT.UI.__IExpandPropertiesFactory’ contained in .winmd file ‘Microsoft.Advertising.winmd’ should be located in ‘Microsoft.Advertising.WinRT.UI.winmd’. TestInetstitalApp.Windows

Now both Windows 8.1 and Windows Phone 8.1 has same error
Interstitial ad doesn’t work with the appid and appunitid created in dev center, it works with appid and adunitid provided in Test mode values in below link.

With ad reports moved to dev center (and no longer requiring pubCenter)m when we build a new UWP app, are we still required to use two different adunits, or is one sufficient and the ads filling/reporting will be handled in the background with respect to platform?