Frequently Asked Questions

Below you can find answers to the most common questions we encounter.
If your question is not listed, please feel free to get in touch. 

Most of ad block users installed one not because of ads on your site, but because they also visit sites where they might feel abused or simply became overwhelmed by the ad density and intrusiveness. That is why we encourage publishers to consider the compliance with the Better Ads Standard. Besides that, they do get exposed to ads on Facebook and Google and other major tech platforms.

From a technical prospective, ANTIADBLOCK (AAB) is suitable for any publisher whether they use a proxy server, load balancer or run in a cloud (e.g. AWS). From the business point of view, it is a matter of the potential amount of regained ad impressions and their monetization opportunities.

There are three instances of implementation: 1. The proxy server has to be configured to handle traffic to users with an ad block via our infrastructure; 2. A piece of inline code has to be implemented on the website (it handles ad block detection and flagging); 3. Prepare you advertising platform for using the recovered ad impressions by tagging them or by creating dedicated advert zones.

No. The entire logic is running on our own infrastructure. It is cloud based and we acquire computing power with the best connectivity to the publisher’s infrastructure to achieve near-zero latency.

Not at all. The traffic to non-blocking users is unchanged and remains direct, as per the publisher’s setup.

We consider it imperative, that the user experience remains unchanged. Our technology does not alter the page design, layout or any content. It only handles advertising.

The publisher continues using their advertising platform already in place. Only minor tweaks in the server’s settings might be necessary to distinguish the ad impressions served to ad block users.

We support the major advertising platforms on our markets and we aim to add more, as per our clients’ needs.

Desktop, video or mobile – the ads are served by the same, or similar technologies at best and represent the same challenge. In video, we support VAST and VPAID tags.

Unless there are significant changes in the page code, especially changes related to page elements handling ads, all maintenance and updates are executed on our side. We do ask to be informed when updates happen in the publisher’s pages, which enables us to react quickly and secure uninterrupted functionality of ad block bypassing.

No. We believe implementing AAB should only have a net positive impact on the publisher’s business right from the start.

We charge per utilization only. In other words, a publisher pays only for the ad impressions sold to the advertiser and successfully delivered to users with an ad block.

AAB is fully CMS independent. The type of CMS in place may play a role in the setup process, but it does not influence the functionality of AAB.

Yes, it is just like any other web page architecture to us.

No. The user is not aware that the ad block has been circumvented. Only highly technically savvy users can identify that their ad blocker is not detecting ads.

Bypassing ad blockers is fully legal. As a matter of fact, the users with an ad block agreed with the site’s terms of use, that normally include the display of advertising.

Yes. We do not store or process any personal data and in case it is required by the publisher, we typically sign a data protection agreement or manifest.