Ad Serving Limits: Why They Happen and What to Do
What an AdSense or AdMob serving limit means, the usual causes and how to respond while one is in place.
5 min read · Updated
Few messages worry a publisher more than a notice saying ad serving on the account has been limited. Earnings drop, the explanation is short, and there is rarely a button to make it go away.
A limit is not a ban. It is a network deciding to serve fewer ads to you while it learns more about your traffic or works through a concern. This guide explains what a limit means on Google AdSense and AdMob, the usual causes, what to do and what to avoid while one is in place, and how it differs from a policy violation or a disabled account. The rules and the wording in your account change over time, so confirm the details in your own account and the official help centres.
What an ad serving limit means
When an account is limited, the network restricts how many ads it will show on your site or app. Some requests still return an ad, others do not. The account stays open, you can still log in and read your reports, and you are still paid for valid earnings.
In practice a limit behaves like a sharp drop in fill rate. Our benchmark tables assume AdMob fills about 88% of requests in normal conditions. If a limit means only half of those ads are served, your impressions fall by half and so does revenue, even if the price per impression does not change at all. Our guide to fill rate explains how that number feeds into earnings, and our guide to reading the AdMob report shows where to watch it.
The notice in your account usually gives a reason, at least in broad terms. At the time of writing, Google's common reasons fall into the groups below.
Common causes
New account assessment
When an account is new, or has been inactive for a while, Google may limit ad serving while it assesses the quality of the traffic. This is routine and not a judgement on you. The system needs time and real visitors to build a picture.
Invalid traffic concerns
If the system sees activity that looks invalid, it may limit serving to protect advertisers while it keeps watching. The trigger can be self-clicks, accidental clicks from placement, bought traffic or bots you never invited. Our guide to invalid traffic covers each one and how to reduce it.
Account or policy issues
Problems such as incomplete account details, or content and behaviour that breach program policies, can also restrict serving. These usually come with a more specific message, and often a separate entry in the policy centre.
Limits, policy violations and disabled accounts
These three are easy to confuse, and they follow different paths.
| Situation | What happens | What you can do |
|---|---|---|
| Ad serving limit | Fewer ads are served across the account | Fix any likely cause and wait for the automatic review |
| Policy violation | Ads are restricted or stopped on specific pages, apps or the whole account | Fix the issue, then request a review in the policy centre |
| Disabled account | The account stops serving ads altogether | Use the appeal route the network offers |
In general, ad serving limits are reviewed automatically and lifted when the system is satisfied, without a request from you. Policy violations work differently: once you have fixed the content or behaviour, you can usually request a review of that specific issue. Check the policy centre in your account for anything listed there, because a limit and a violation can exist at the same time. The AdSense help centre and AdMob help centre describe the current process for each.
How long a limit lasts
There is no fixed length, and it varies a great deal. A new account assessment can clear within days for some publishers and take several weeks for others. Limits linked to invalid traffic depend on what the system sees after the limit begins, so they can last longer if the pattern continues. Google does not publish a timetable you can plan around, and nobody outside the network can tell you exactly when yours will lift.
What you can influence is the quality of the traffic the system sees in the meantime. A steady flow of ordinary visitors or players gives the assessment something to work with.
What to do while you are limited
- Read the exact notice. Note the reason given, the date it appeared and whether anything is listed in the policy centre.
- Leave your ad code in place. Taking ads down can leave the system with nothing to assess. Keep serving to your normal audience.
- Audit your placements. Move ads away from buttons, controls and navigation. Fix layout shifts that cause mis-taps. Make sure ads are labelled and clearly separated from content.
- Check your traffic sources. Pause any paid campaign, traffic package or partnership you cannot vouch for, and look for unusual referrers or countries in your analytics.
- Use test ads for development. Make sure no test build uses live ad units, and that nobody on your team taps live ads.
- Report suspicious activity. If you find traffic you did not cause, report it through the invalid activity route in the help centre.
- Keep a log. Write down what you changed and when. It helps you judge what worked, and it helps if you ever need to explain your setup.
If you use mediation, the other networks in your stack keep making their own decisions under their own policies. That is normal, but it is not a fix. If the underlying cause is invalid traffic, it will reach those networks too. Our guide to mediation explains how a stack shares requests.
What not to do
- Do not click your own ads to check whether serving is back.
- Do not buy traffic to raise volume or to prove your audience is real. Low-quality traffic is one of the surest ways to make a limit worse.
- Do not open a second account, or run ads through someone else's account, to replace the limited one. Networks generally treat this as a serious breach of their terms.
- Do not ask readers or players to click or view ads to make up the shortfall.
- Do not make lots of large changes at once. You will not be able to tell which one mattered.
If any term here is unfamiliar, such as match rate or invalid activity, the glossary has short definitions.
Planning for the revenue gap
A limit hits your income directly, so it helps to know the size of the hole. Take a hypothetical app with 10,000 daily users, each triggering two interstitial requests a day, all in Tier 1 on AdMob. At our benchmark eCPM of $8.00 and 88% fill, that is 20,000 requests x 0.88 = 17,600 impressions, worth about $140.80 a day. If a limit halves the ads served, the same day earns about $70.40.
For a smaller account, the gap also delays reaching the $100 payment threshold, as our AdMob payment guide explains. Run your normal figures through the AdMob revenue calculator or the AdSense revenue calculator to see what a full month should look like, then treat anything earned during a limit as a shortfall against that line rather than your new normal.
If you are about to launch a new site, our AdSense approval checklist covers the groundwork that makes a smooth start more likely. For anything not covered here, read Google's publisher policies and our answers to common ad income questions.