AdBlock Detection
Detect if a visitor is using an ad blocker and set up targeting rules accordingly.
AdBlock Detection is an OptiMonk targeting condition that identifies whether a visitor is using a browser ad-blocking extension and lets you use that information as a campaign targeting rule. AdBlock extensions are installed by a significant portion of web users, and while most OptiMonk campaigns load independently of ad blockers, there is one important exception: if OptiMonk is installed via Google Tag Manager, ad blockers will prevent the script from loading entirely — because they block GTM itself, not just individual ad units. AdBlock Detection allows you to respond to this segment in two complementary ways: you can show a targeted campaign to ad block users asking them to disable it (so they regain access to your full site functionality and your campaigns load for them), or you can exclude ad block users from campaigns that you know will not display correctly for them. The detection is built into OptiMonk's targeting condition system and works like any other condition. It can be combined with URL rules, cart rules, visitor history rules, and any other targeting logic.
Key benefits
- Turn ad block users into a targetable segment instead of an invisible blind spot. Without AdBlock Detection, you have no way of knowing how many visitors are silently missing your campaigns due to an ad blocker. With this condition active, you can quantify that segment, serve them a specific message — such as a politely worded request to disable their blocker — and potentially recover the leads and conversions that would otherwise be lost entirely.
- Protect ad revenue and site functionality with a dedicated message. Ad-blocking visitors who are unaware that their extension is breaking parts of your site can be shown a targeted notification explaining the situation. Rather than leaving them to experience a broken layout or missing content without context, you can proactively communicate why disabling their ad blocker benefits them — preserving both your revenue and their experience.
- Exclude ad block users from campaigns they cannot see. If OptiMonk is installed via Google Tag Manager and ad blockers prevent the script from loading, you can use AdBlock Detection in the inverse direction: exclude ad block users from campaigns that depend on GTM delivery. This prevents incorrect impression counts and allows you to direct your non-ad-block campaign budget toward visitors who will actually see the messages.
How it works
In your OptiMonk dashboard, select the campaign you want to configure and click Edit settings. Under "Select who should see the popup," click Add new condition and choose AdBlock detection from the condition list.
The condition has two states: "use AdBlock" targets visitors who have an active ad-blocking extension detected, and "don't use AdBlock" targets visitors without one. Select whichever matches your campaign's purpose — showing a disable-your-adblocker message to the first group, or restricting another campaign to the second group only.
Click Save and proceed through the campaign settings. The AdBlock Detection condition works with AND logic alongside any other targeting rules you have set — for example, you can show the ad block message only to visitors on your homepage, or only to returning visitors, by combining conditions. Publish the campaign and it will fire selectively based on whether ad block is detected at display time.
Frequently asked questions
What is AdBlock Detection in OptiMonk?+
AdBlock Detection is an OptiMonk targeting condition that identifies whether a visitor's browser has an active ad-blocking extension installed. It can be used to show specific campaigns to ad block users — such as a request to disable their blocker — or to exclude ad block users from campaigns that rely on Google Tag Manager for delivery, where ad blockers would prevent the OptiMonk script from loading at all.
Does AdBlock always prevent OptiMonk campaigns from displaying?+
Not always. If OptiMonk is installed directly via a JavaScript snippet in your site's code, most ad blockers will not prevent OptiMonk campaigns from displaying, since OptiMonk is not classified as an ad network. However, if OptiMonk is installed through Google Tag Manager, ad blockers typically block GTM itself, which in turn prevents OptiMonk from loading. In that case, those visitors will never see any OptiMonk campaign regardless of its targeting settings.
What should I show to visitors with an ad blocker?+
The most common approach is a polite, informational popup explaining that your site relies on ad revenue or that certain features may not work correctly with an ad blocker active, with a call to action asking the visitor to disable it for your domain. Because the visitor's ad blocker has not blocked the OptiMonk script itself (in non-GTM installs), this message will still reach them. Keep the tone friendly rather than restrictive, as aggressive ad-block gates often increase bounce rates.
Can I use AdBlock Detection to exclude ad block users from all campaigns?+
Yes. By setting the condition to "don't use AdBlock" on a campaign, you restrict it to visitors without an ad blocker. You can apply this condition across any campaign where ad block interference is a concern. This is especially relevant for GTM-installed OptiMonk, where ad block users would never see the campaign anyway — filtering them out keeps your impression and conversion rate data accurate.
Can AdBlock Detection be combined with other targeting conditions?+
Yes. Like all OptiMonk targeting conditions, AdBlock Detection works with AND logic alongside other rules. For example, you can show an ad block notification only to first-time visitors (by combining with the New visitor condition), only on specific pages (by combining with the Current Page / URL rule), or only to visitors with a certain cart value. This lets you tailor the tone and timing of the message rather than showing a blanket notification to every ad block user on every page.
Try OptiMonk for free
Launch your first campaign, learn what works, then scale what converts.