Windows 10: New App Policy Center for Google AdMob and Ad Manager

Brink · May 2, 2019

Advertising policies help ensure a good user experience while maintaining a healthy advertising environment for app publishers. However, we also understand that without the right tools to streamline and simplify the process, handling policy violations can be frustrating for publishers. That’s why we’re excited to introduce the new App Policy Center for Google AdMob and Ad Manager.

The App Policy Center is part of our effort to protect quality AdMob and Ad Manager publishers while building and maintaining a healthy and trustworthy advertising ecosystem. It is designed to provide publishers with a single centralized hub to review and monitor policy violations and appeals, providing publishers with greater insight into our policy enforcement process. With all the information needed to remain policy compliant in one place, the App Policy Center will help reduce the risk of potential revenue loss resulting from honest mistakes.

The App Policy Center is available now for both Google AdMob and Ad Manager users. You can access it from the homepage dashboard once you sign in to your account.

More about the App Policy Center

The App Policy Center is a single, convenient destination for you to understand everything related to policies and take action as needed. More specifically, you’ll be able to:

View current warnings, violations, and appeals in progress

Appeal policy warnings for certain violations within a 30-day window

Request review after addressing a violation and track the status

App Policy Center for Google AdMob

App Policy Center for Google Ad Manager

In addition to surfacing this information in the App Policy Center, we will continue to notify you of important policy issues through email when any of the following events occur:

When a policy is enforced on an app

App receives policy violation warning

Warning turns into an enforcement

Review request is received

Review request gets accepted and an app is remonetized

Review request is rejected

We are constantly looking for ways to improve the experience on AdMob and Ad Manager, and hope the App Policy Center helps you handle policy issues with more ease and confidence.

To learn more about the App Policy Center and best practices about policies, visit the AdMob Help Center or the Ad Manager Help Center.
Click to expand...

Source: Introducing the Google AdMob App Policy Center

:)

Brink · May 2, 2019

New UWP Ad Monetization policies and updates to Ad unit management UX

Today, we are announcing new policy around ad unit decommissioning, user experience updates to manage active/inactive ad units, default policies around Ad network enablement, and changes to the Ad impression measurement methodology for Windows apps. You may be impacted if you are monetizing using Ads on your Windows app leveraging the Microsoft Advertising SDK (UWP or 8.x apps).

1) Auto enabling new ad networks for Manual ad units on UWP apps

Our team continues to evaluate and onboard new Ad networks to improve yield and offer better variety of demand (formats, market specific demand) for our publishers. Today, when a new ad network is onboarded to our system, UWP ad units that are configured with the ‘Manual configuration’ option do not benefit from these networks as they are not automatically turned on for the Manual ad units. We will be making a change over the next few weeks to turn on any new ad networks by default for all our UWP ad units independent of the Manual or Automatic configuration. For ad units in the Manual configuration, since the ad network waterfall configuration is determined by publisher’s choice, these ad networks will be added to the bottom of the waterfall order. The publisher can then make necessary changes to reorder or opt out of the ad networks as necessary. As always, our recommendation is to choose the ‘Automatic’ ad unit configuration to benefit the most from our platform’s yield maximization capabilities.

2) Policy updates around decommissioning of Ad units

We are implementing an ad unit decommissioning policy wherein an ad unit that hasn’t generated any Ad request over the last 6 months will be subject to deactivation and deletion. We don’t expect active apps to be impacted since we look for a prolonged period (6 months) of ad unit inactivity before we deactivate. However, there may be exceptional circumstances where you may be affected. For instance, if you created an ad unit several months ahead of app deployment time and trying to use this ad unit as your app goes live. Or, you are trying to reuse an existing ad unit from your previous inactive app into your new app. Recommendation in both cases is to use newly created ad units instead of reusing an existing one to avoid potential Ad revenue loss.

Along with this policy announcement, we are making changes in the Windows Dev Center dashboard to make it easy to view active and inactive Ad units. Ad unit state is identified in a separate Status column; in addition, you can choose to view just the Active or Inactive ad units by choosing the appropriate filter on the top of the page.

3) Transitioning to Standards based Ad impression measurement

Standards based Ad impression measurement requires that the ‘Ad must be loaded and at minimum begin to render’ to be counted as a valid impression. For Ad networks that are relying on other methods such as server based Ad impression counting, we are making changes to gradually migrate all our Windows app ad units over the next few months closer to Standards based measurement. More specifically, the impression counting will rely on techniques such as firing an ad network impression beacon upon starting to render the Ad on the client. This is done to better adhere to the IAB standards around Ad impression counting and to be fair to the advertisers. This will also benefit apps that are striving to do right by making sure that Ads are rendered on the client and are viewable.

If you are following standard guidelines put forth in our documentation and recommendations from earlier blogs on how to design the Ad placements in your app, you should not see adverse impact on your Ad monetization. However, if your app is designed in a way that interferes with the rendering of the Ad, you may see a negative impact on your App Ad revenues. For instance, if you are placing an Ad in a UI dialog box that can be easily dismissed by the user before the Ad gets a chance to render or your app is pulling Ads on a background thread, these Ads that previously were possibly counted as valid impressions will not be counted in the new standard. We strongly recommend you to evaluate your app for such practices and actively fix these issues to minimize impact to your Ad revenues.

Please reach out to L: aiacare@microsoft.com for questions or comments!
Click to expand...

Source: Announcing new Ad Monetization policies and updates to Ad unit management UX - Windows Developer Blog

Roohi_Taj · May 2, 2019

Google Chrome Crahses and suspended in task manager

Hi GSsswuw8,

Thank you for writing to Microsoft Community Forums.

Could you please help me with the below information:

Do you have any antivirus installed on the computer?

Are you aware of making any changes to the computer or browser prior to the issue?

This issue is because of profile data corruption on google chrome or because of cookies, extensions, plugins and History. I would suggest you to follow the steps mentioned below to resolve this issue.

Method 1: Rename Google chrome file.

Before proceeding I would suggest you end all the task related to Google Chrome from task manager.

Step 1: Rename Chrome User Data file.

Press Windows and
E key together on your Keyboard.

Navigate to %LOCALAPPDATA%\Google\Chrome.

Search for User data folder. Rename this folder to UserData.old

Open the chrome now and check if it is working.

Note:
The new user data folder will be created automatically, but
new profile will not have any of your previous data in it. To access the data back, try signing out and signing in back to the application. Or you have to manually copy the data from old profile.

Step 2: Copy the previous data to New Profile.

I would suggest you end all the task related to Google Chrome from task manager.
Then follow the steps mentioned below:

Press Windows and
E key together on your Keyboard.

Navigate to %LOCALAPPDATA%\Google\Chrome\UserData.old\Default.

Open a new tab and navigate to: %LOCALAPPDATA%\Google\Chrome\User Data\Default. (Make sure this is the new user data folder)

Now copy the file one by one, once the copy is done. In-between Reopen Chrome browser and check if there is issue same issue.

If the issue reoccurs, then the culprit is one of the file copied above.

Method 2:
Troubleshoot on google chrome.

Note: The Uninstall and Reinstall option might reset security settings or privacy settings that you added, this will also clear the history, favorites, cookies and password. We recommend
that you note these sites and settings before you use the Reset on chrome.

I would suggest you to follow the steps mentioned in the article on
Fix Chrome if it crashes or won't open.

Hope it helps.

Let us know if you got the help you needed by clicking Yes or No.

Roohi Taj S

Microsoft Community - Moderator

K Douglas · May 2, 2019

Adding Google Apps account: No calendar!

I have my email on a private domain with a Google Apps account. Adding this account to my WP7 device yields only email -- no calendar. Any options for this?

Windows 10: New App Policy Center for Google AdMob and Ad Manager

New App Policy Center for Google AdMob and Ad Manager

New App Policy Center for Google AdMob and Ad Manager

New App Policy Center for Google AdMob and Ad Manager

New App Policy Center for Google AdMob and Ad Manager - Similar Threads - App Policy Center

Group Policy Management Secondary AD Inaccessible

Group Policy Management Secondary AD Inaccessible

Google introduces new Google Podcasts Manager tool

New policies for Google Chrome extensions and Google Drive API

google chrome://policy-ERR_BLOCKED_BY_ADMINISTRATOR"

Adding Internet Download Manager by Tonec extension to Google Chrome

Google Chrome new policy to block unwanted autoplays

Managing apps and visibility of in-app purchases in Dev Center

New UWP Ad Monetization policies and updates to Ad unit management UX