In this article, we’ll review what types of issues affect ad serving and what the ad serving statuses mean in the Policy center.
Issues that affect ad serving
If your app has an issue that affects ad serving, it means that your app either violates our Program policies, is affected by a regulatory requirement, or is receiving less advertising due to an advertiser preference.
There are three types of issues identified in the Policy center: policy issues, regulatory issues, and advertiser preferences. You will not receive advertising where there are policy issues. Repeated policy violations may lead to an account suspension. You don’t have to fix regulatory issues or advertiser preferences, but you'll likely receive less advertising, which may impact your revenue.
You may also receive a warning before action is taken on your ad serving.
Review the tables below for more information about these issue types and their associated ad serving statuses.
Policy issues
Policy issues are caused if you fail to follow the Program policies when displaying ads on your apps. When this occurs, you need to make changes in order to receive advertising. Violations of the Program policies may result in ad serving restrictions, disabled ad serving, account suspensions, or account termination.
Here are some examples of policy issues:
| Example | What's happened | Ad serving status |
|---|---|---|
| Sexually explicit content | Your app is not currently in compliance with the Google Publisher Policy for Sexually explicit content. | This policy issue is enforced with Disabled ad serving. |
| Google-served ads on screens without publisher-content | Your app is not currently in compliance with the Google Publisher Policy for Google-served ads on screens without publisher-content. | This policy issue is enforced with Restricted ad serving. |
Regulatory issues
Regulatory issues are caused when ads on your app are affected by a country or regional regulatory requirement. Examples of such regulations include the General Data Protection Regulation (GDPR), US states privacy laws, etc.
Regulatory issues can affect the type of ads users see on your app, such as personalized or non-personalized, or ad serving restrictions in some geographical regions.
Here's an example of a regulatory issue:
| Example | What's happened | Ad serving status |
|---|---|---|
|
Consent requirement: No CMP |
You're not currently using a certified Consent Management Platform (CMP) registered with the IAB's Transparency and Consent Framework (TCF) when serving ads to users in the EEA, the UK, and Switzerland. |
Apps with consent requirement issues receive Restricted ad personalization |
Advertiser preferences
Advertiser preferences means that some advertisers choose not to bid for ads on labeled content because these advertisers don't find certain content (e.g., alcohol, tobacco or sexually suggestive images) appealing or a good fit with their brand. Advertiser preferences could also apply as a result of how you place ads on your apps.
Advertiser preferences include issues that fall under the Google Publisher Restrictions, as well as treatments such as Confirmed Click. Issues labeled as advertiser preferences will likely receive less advertising. Fixing an advertiser preference is recommended as it can affect your revenue.
Here are some examples of advertiser preferences:
| Example | What's happened | Ad serving status |
|---|---|---|
|
Sexual content |
Your app falls under the Google Publisher Restriction for Sexual content. |
Apps with publisher restrictions receive Restricted ad serving. |
|
Confirmed Click |
Google Ads has determined that certain ads on your app are generating unintended clicks. This creates a poor user experience because the user ends up on advertiser landing pages instead of their intended content. Google Ads has added Confirmed Click on its affected ads. Confirmed Click adds a second click that improves the user experience by letting the user confirm their intent to visit the advertised page. |
Apps with Confirmed Click added receive Confirmed Click on. |
Warning
Some policy issues, regulatory issues, and advertiser preferences have a warning period before action is taken on your ad serving. If you receive a warning, it means that your app is not currently in compliance with the Program policies or contains content that falls under the Google Publisher Restrictions. If you don't make changes, further actions may be taken on your app or account.
Here's an example of a warning:
| Example | What's happened | Ad serving status |
|---|---|---|
|
Ads & Content Overlap |
You've received a warning that your app is not in compliance with the Ads & Content Overlap Program policy. You need to make changes to your app to bring it into compliance. Check your Policy center for the "fix by" date. |
Apps with warnings receive Ad serving at risk. |
Ad serving status
The status of your ad serving lets you know how your apps with issues are impacted. The table below explains the statuses and what they mean.
| Status | What it means | What you can do |
|---|---|---|
| Disabled ad serving | All advertising is blocked on your app. Your app isn’t serving ads due to a policy violation. |
Review the issue description in the Policy center to determine the changes you need to make. After you address the policy violations on your app, you may request a review to enable ad serving. |
| Restricted ad serving |
There are restrictions on the advertisers that can bid on your inventory. Your app is likely to have little or no buyer demand because not all ad sources can bid. |
Review the issue description in the Policy center to determine the changes you need to make, if any. |
| Ad serving at risk |
Ad serving isn’t affected yet, but you’ll need to make changes to your app to ensure ad serving continues. This is due to a warning on your app. Warnings typically include enforcement dates, when further action is taken and ad serving is affected. |
Fix the issues before the enforcement date to prevent ad serving from being restricted or disabled. Review the issue description in the Policy center to determine the changes you need to make. |
|
Limited ad serving |
This affects your AdMob account. Limited ad serving means Google has placed a limit on the number of ads your AdMob account can show. Learn more about ad serving limits. |
Make sure you understand your ad traffic and users. Never click on your own ads, and avoid partnering with untrusted or low-quality parties. Learn more about preventing invalid activity. |
| Confirmed Click on | Some ads on your inventory are creating unintended clicks so Google has added Confirmed Click on these ads. |
Review your ad implementations. Learn how can you prevent accidental clicks. Our system automatically applies Confirmed Click when it detects accidental clicks. Similarly, the system automatically lifts Confirmed Click when it no longer detects accidental clicks. |
| Restricted ad personalization |
Some apps are not using a certified CMP to ask for user consent. Apps that do not adopt a Google certified CMP will not be eligible for personalized ads. Apps using a certified CMP are eligible for personalized ads, non-personalized ads (NPA), and limited ads. |
No CMP Some ad requests on your inventory from the EEA, the UK, and Switzerland are missing a TCF string.
Learn more about certified CMP options. CMP not certified Some ad requests on your inventory from the EEA, the UK, and Switzerland are missing a TCF string from a certified CMP.
Note: If you recently adopted a certified CMP, it may take up to 48 hours for this issue to be resolved and removed from the Policy center.
Low coverage A majority of ad requests on your inventory from the EEA, the UK, and Switzerland are missing a TCF string.
|