Ad blocking recovery in AdSense: asking visitors to allow ads
Key takeaways
- Ad blocking recovery is a message type in AdSense Privacy & messaging that is shown to visitors detected as using an ad blocker and asks them to allow ads on your site.
- Unlike consent messages, it needs an explicit ad blocking tag on the page; Google's developer documentation says the regular AdSense tag does not deploy it.
- Google's googlefc JavaScript API reports whether a visitor uses an extension-level or network-level ad blocker, and whether they allowed ads after seeing the message.
- Publishers can suppress the message for chosen visitors, such as subscribers, with googlefc.controlledMessagingFunction and the AD_BLOCKING message type.
- In 2018, when the tool was called Funding Choices, Google reported that on average 16 percent of visitors shown the message allowed ads, with some sites reaching 37 percent.

Ad blocking recovery is a message type in AdSense Privacy & messaging. When Google’s ad blocking tag detects that a visitor blocks ads, the message explains that your site is funded by ads and asks the visitor to allow ads on it. Choices are tracked, and visitors who allow ads start generating impressions again. It needs its own tag, separate from the regular AdSense code.
This guide is based on Google’s help and developer documentation as of November 2026. The AdSense help article on tagging for ad blocking recovery could not be retrieved for this guide, so follow it directly for the current tag code.
What does the ad blocking recovery message do?
Google’s Privacy & messaging overview lists three goals for user messages: gathering consent, handling US opt-outs, and helping you “recover lost revenue from ad blocking users”. The ad blocking recovery message serves the third.
| Visitor situation | What happens |
|---|---|
| No ad blocker | Message is not shown; ads serve normally |
| Extension-level ad blocker (browser add-on) | Message can be shown; visitor may allow ads |
| Network-level ad blocker (DNS, router, VPN filter) | Detected as a separate state; allowing ads may require changes outside the browser |
| Visitor allows ads after the message | Ads can serve on later pageviews |
| Visitor dismisses or ignores the message | No ads; the ad blocker stays on |
The states come from the googlefc API, which defines AdBlockerStatusEnum with four values: UNKNOWN (0), EXTENSION_AD_BLOCKER (1), NETWORK_LEVEL_AD_BLOCKER (2) and NO_AD_BLOCKER (3). A second enum, AllowAdsStatusEnum, records whether the visitor stopped blocking after seeing the message: ADS_ALLOWED (2) means “no longer using an ad blocker after seeing the ad blocking message”.
How do you set it up?
- Create the message in AdSense under Privacy & messaging, choosing the ad blocking recovery message type, and select the sites it applies to.
- Customize the text and style. Explain plainly that ads fund the site. The help center lists the languages supported for this message type, which differ from the consent message list.
- Add the ad blocking tag. The googlefc documentation says user messaging deploys through existing AdSense tags “except for ad blocking recovery messages which require an explicit ad blocking tag”. Copy it from AdSense, following Google’s tagging instructions.
- Publish the message.
- Test it by appending
?fc=alwaysshow&fctype=abto a page URL. Google says this “displays the ad blocking recovery message that is currently published for your site” and “ignores ad block detection”. - Check results in the Privacy & messaging reports after a few days of traffic.
How do you control who sees it?
The googlefc API lets you decide, before any message renders, whether to proceed. Define the function on the window before Google’s scripts load:
<script>
window.googlefc = window.googlefc || {};
googlefc.controlledMessagingFunction = async (message) => {
const isSubscriber = await checkSubscription(); // your own function
if (isSubscriber) {
// Suppress only the ad blocking message; consent messages still run.
message.proceed(false, [googlefc.MessageTypeEnum.AD_BLOCKING]);
} else {
message.proceed(true);
}
};
</script>
Google documents that message-type-specific suppression is supported for the Offerwall and the ad blocking recovery message. It also warns that when this function is defined, “no Privacy & messaging messages display until message.proceed() is called”, which may delay ads, so make sure the call always happens.
Google’s samples page shows other patterns: showing the message to a random 10% of traffic, skipping the home page, waiting until a visitor has viewed a set number of pages, and sending ad blocking states to Google Analytics as events.
One detail in those samples deserves attention. They call message.proceed(false) without a message type list, and the API reference says that a plain proceed(false) prevents any messages from showing. On a site that also runs Google’s European regulations message, a “10% of traffic” sample copied as is would hide the consent message from the other 90% as well. Pass [googlefc.MessageTypeEnum.AD_BLOCKING] as the second argument so only the recovery message is filtered.
The analytics samples on the same page use the legacy analytics.js syntax (ga('send', ...) with a UA- property ID). Google Analytics 4 uses a different tag, so treat them as examples of which states to record, not as code to paste.
| Goal | Control | Where it comes from |
|---|---|---|
| Show the message to a share of ad-blocking visitors | Random check in controlledMessagingFunction |
Samples page |
| Never interrupt subscribers | Subscriber check, then proceed(false, [AD_BLOCKING]) |
API reference |
| Let new visitors read a few pages first | Your own pageview counter, then proceed(true) after the limit |
Samples page |
| Keep the home page clear | URL check before calling proceed |
Samples page |
| Measure blocker types and allow-ads rates | AD_BLOCK_DATA_READY callback, then analytics events |
API reference and samples page |
To read the ad blocker state yourself, push a callback keyed AD_BLOCK_DATA_READY onto googlefc.callbackQueue, then call googlefc.getAdBlockerStatus() or googlefc.getAllowAdsStatus().
How many visitors allow ads?
Google’s most specific public figures are old. In an April 2018 post, when the product was still the Funding Choices beta, Google said that “on average, publishers using Funding Choices are seeing 16 percent of visitors allow ads”, with some seeing “as high as 37 percent”. The same post described three message styles at the time: dismissible, dismissible with a monthly pageview limit, and blocking until the visitor allows ads or pays.
Treat those numbers as historical. Ad blockers, browsers and the product have changed since, and your audience matters more than any average. Measure your own rate with the reports or with AllowAdsStatusEnum events.
What policy and UX limits apply?
| Approach | Policy and UX risk |
|---|---|
| Google’s ad blocking recovery message | Built for the purpose; still keep the text neutral |
| Custom banner asking visitors to disable ad blockers | Allowed in principle, but avoid any wording that asks users to click or view ads |
| Text such as “Support us, click our sponsors” | Prohibited under Google’s ad placement policies |
| Hard wall that blocks all content | Possible business choice; can raise bounce rate and frustrate visitors |
| Message shown on every pageview to everyone | Annoying; use frequency and audience controls |
The ad placement policies prohibit encouraging clicks, including phrases like “Help keep this site running. Check out our sponsors!”. Explaining that ads fund the site and asking visitors to allow ads is a different request, and Google’s message is designed around it.
Ad blocking recovery does not override privacy rules. In the EEA, the UK and Switzerland, a visitor who allows ads still needs a consent choice through your European regulations message, and a visitor who refuses consent may still see only limited ads. Whether running detection itself requires consent under ePrivacy rules is a legal question; this guide does not answer it, and it is not legal advice.
Common mistakes
- Publishing the message without the ad blocking tag. The regular AdSense tag does not deploy it.
- Testing with an ad blocker on and assuming detection failed. Use the
fctype=abpreview first, then test detection separately. - Copying a sample that calls
proceed(false)with no type list. It suppresses consent messages too. - Defining controlledMessagingFunction and never calling proceed. All messages, including consent, stay hidden and ads may be delayed.
- Wording that asks for clicks. That moves the message from recovery to a policy violation.
- Ignoring network-level blockers. Visitors on a filtering DNS or router may not be able to allow ads from the browser alone.
- Quoting 2018 averages as forecasts. Use your own data.
Frequently asked questions
Can I write my own "please disable your ad blocker" banner instead?
You can, but Google's ad placement policies prohibit wording that encourages users to click or view ads, and a homemade banner gives you no data on allow-ads rates. Google's own message is built for this purpose, integrates with Privacy & messaging, and reports whether visitors allowed ads afterward through the googlefc API.
Why does my ad blocking recovery message never appear?
The most common cause is a missing tag. Google's developer documentation states that ad blocking recovery messages require an explicit ad blocking tag, unlike consent messages, which the regular AdSense tag deploys. Check that the message is published for the site, then test with ?fc=alwaysshow&fctype=ab, which shows the message while ignoring ad block detection.
Can I hide the message from paying subscribers?
Yes. Define googlefc.controlledMessagingFunction on the window before Google's scripts load, then call message.proceed(false, [googlefc.MessageTypeEnum.AD_BLOCKING]) for subscribers. That suppresses only the ad blocking message and leaves consent messages working. Calling message.proceed(true) lets messaging continue as usual for everyone else.
Does detecting ad blockers require consent in Europe?
That is a legal question without a single answer. Detection scripts read information from the browser, and the ePrivacy rules on storing or accessing information on devices may apply depending on how detection works and on national guidance. Google's documentation does not settle this, so check with your adviser before showing the message to EEA visitors.
Sources
- About Privacy & messaging · Google AdSense Help
- Privacy & messaging JavaScript API (googlefc) · Google for Developers
- Privacy & messaging samples · Google for Developers
- Helping publishers recover lost revenue from ad blocking · Google
Related guides
- AdSense Privacy & messaging: building the European regulations (GDPR) message
Build the GDPR consent message in AdSense Privacy & messaging: every setting, the two- vs three-button layout, testing, troubleshooting and what it cannot do.
- Personalized, non-personalized and limited ads: the three AdSense serving modes compared
How AdSense picks personalized, non-personalized or limited ads from consent signals, what each mode still collects, the ad code switches and the setting to check.
- Consent mode v2 and AdSense: two consent signals, one site
Google consent mode v2 explained for AdSense sites: why AdSense reads the TCF string, not consent mode, and how to keep Analytics and AdSense signals aligned.
- Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Since 2024 AdSense needs a Google-certified TCF CMP for personalized ads in the EEA, UK and Switzerland. Dates, what happens without one, how to check yours.