Export (0) Print
Expand All

Known Issues - AdControl for Windows 8.1

Microsoft Advertising Services

Updated: April 28, 2014

Published: April 28, 2014

Known Issues

No Ads

There are many reasons you may see no ads, including network errors. Other reasons might include:

  • Selecting an ad unit in pubCenter with a size that is greater than the size of the AdControl in your app's code.

  • Using test ad ids in a live app.

  • If you created a new AdUnitID in the past half-hour, you might see no ad until the back-end servers propagate new data through the system. Existing IDs that have shown ads before should show ads immediately.

  • For apps built using HTML 5: If you are investigating a no ads scenario, you can try the following workaround. Include the attribute position:relative in the div that defines the AdControl. This will override the default position setting of the iFrame used by the AdControl.

If you can see test ads in the app, your code is working and is able to display ads. For no ad issues, contact product support. On that page you will find the product support link under "App development", and then click the "Advertising SDK" link. To post a question in the support forum go to http://social.msdn.microsoft.com/forums/en-us/home?forum=aiaforwin8.


Reserved variables: The AdControl exposes variables that are reserved for its own use. These are:

  • window._msAdsGlobalEventManager

  • window._msAdEngaged

Do not use these variables.

Use only one Application ID in an AdControl: ApplicationId must be the same for all ad placements in an app, and cannot be changed during runtime. AdUnitId cannot be changed for a given AdControl during runtime. If you do assign a new value, the property value will change without throwing an exception. However, on the next ad refresh the errorOccurred event will fire.


Z-Order: HTML5 apps must NOT place elements into the reserved MAX-10 range of z-order, with the sole exception of interrupt overlays. For example, an inbound call notification for a Skype app. You can test your app with click-to-full-screen experiences by implementing the test AdUnitID value 10043107 and clicking on it in the emulator.

Memory Leak: You might observe a memory leak when running the app using the debugger. During runtime, when an ad is refreshed, the AdControl might create a new iframe for the ad, and the old iframe is queued for garbage collection. However, this may not happen under the debugger. This is a known issue with iframe use in the debugger. If you observe what appears to be a memory leak in your app after an ad refresh, try running the app without debugging.


Do Not Use Borders: Setting border related properties inherited by the AdControl from its parent class will cause the ad placement to be wrong. The modern Windows 8 interface discourages the use of borders. Consistent layout and the use of margins are the modern Windows 8 style. For more information see Developing Windows 8 style apps.


No Native Support: The current Ad SDK does support .NET C++ (managed C++ using the CLR). The AdControl loads the CLR and uses managed C++. Fully native support is planned for a future release -- there is no release ETA.

Important Notice

Be sure to read the end user license agreement (EULA) in its entirety. See the topic Important Notice – End Users License Agreement.

Age Rating: Your Windows 8.1 apps must have an Age rating of at least 12+ in the Windows Application Marketplace to receive Ads. See the Additional Agreements section.

AdSettingsFlyout Issues

There are known issues with AdSettingsFlyout.

See the topic Known Issues - AdSettingsFlyout for more information.

More Information

For more information about the latest known issues and post questions related to the Windows 8.1 Advertising SDK, go to the support forum.


Contact product support. For product support, under "App development" click the "Advertising SDK" link. To post a question in the support forum, scroll down to "Find answers online" and click "Ads-in-Apps for Windows 8 forum".

Support and Feedback

Get product support or report a bug in the advertising SDK by visiting the Windows Store Apps developer support page support page. For product support, under "App development" click the "Advertising SDK" link. To post a question in the support forum, scroll down to "Find answers online" and click "Ads-in-Apps for Windows 8 forum".

Send feedback about this documentation to adsfdbk@microsoft.com. There is no product support through this alias. Documentation feedback only.

Community Additions

© 2014 Microsoft