As of Q2 2015, 45 million Americans were using ad blockers. In a survey research study released Q2 2016, MetaFacts reported 72 million Americans, 12.8 million adults in the UK, and 13.2 million adults in France were using ad blockers on their PCs, Smartphones, or Tablets.
The 2017 PageFair report shows that 11% of the global Internet population is blocking ads on the web (as of December 2016). In some countries like Germany, Sweden, India or Indonesia this figure is well above 25%.
Stop revenue loss today! You have the right to counter ad-blocking software to keep your business going.
An ad-blocker detection strategy should be in any project serious about making legitimate revenue with video ads.
Our ad-blocker detection engine will survey both contextual blocking and HTTP requests blocking. This allows us to support detection for ad-blockers on mobile devices and browser built-in content blockers on top of classic ad-blockers available as desktop browser extensions. Our ad-blocker detection engine is turn off by default as some users may want to have an ad-blocker detection policy at the site/app level rather then at the player level.
Assuming you are turning on ad-blocker detection within Radiant Media Player (see adBlockerDetection setting below), 2 options for detecting ad-blocker are available:
As discussed in our blog post it can prove challenging to by-pass ad-blockers. Several initiatives in the ad-tech industry are emerging to address the issue and browser vendors are also starting to work on the subject so the game is likely to change in the years to come.
adBlockerDetection: Boolean
Whether or not the player should attempt to detect ad-blocker when
init is called. Default: false.
adBlockerDetectedPreventPlayback: Boolean
Whether or not to prevent playback of content when an ad-blocker is detected. When playback is prevented a message is shown to viewer requesting the ad-blocker to be disabled. Default: false.
The message displayed by the player when an ad-blocker is detected can be customized with player labels.
Note that the ad-blocker detection player API is only available when
adBlockerDetection is set to true.
Player API event
adblockerdetected: this event fires when an ad-blocker is detected after
init is called on player. Note that this event will fire just after
ready event if an ad-blocker is detected.Player API method
getAdBlockerDetected: this method will return a Boolean stating if an ad-blocker has been detected or not.<script src="https://cdn.radiantmediatechs.com/rmp/5.6.1/js/rmp.min.js"></script>
<div id="rmpPlayer"></div>
<script>
var src = {
hls: 'https://your-hls-url.m3u8'
};
var settings = {
licenseKey: 'your-license-key',
src: src,
width: 640,
height: 360,
contentMetadata: {
poster: [
'https://your-poster-url.jpg'
]
},
ads: true,
adTagUrl: 'https://www.radiantmediaplayer.com/vast/tags/inline-linear.xml',
// ad-blocker detection settings
adBlockerDetection: true,
adBlockerDetectedPreventPlayback: true
};
var elementID = 'rmpPlayer';
var rmp = new RadiantMP(elementID);
var container = document.getElementById(elementID);
container.addEventListener('adblockerdetected', function () {
console.log('adblockerdetected');
});
container.addEventListener('ready', function () {
console.log(rmp.getAdBlockerDetected());
});
rmp.init(settings);
</script>
Over the past few years we have seen many ad-blocker solutions coming to the market. Most common ad-blockers are browser extensions generally "free" to install. It is also to be noted that browser vendors are starting to implement (or are showing interest into implementing) their own ad-control strategy. We have tested our ad-blocker detection approach against:
Feel free to contact us with feedback on detecting ad-blockers.