Radiant Media Player

Ad-blocker detection



Ad-blocker detection documentation sections


Your business model is at risk

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.

Wikipedia https://en.wikipedia.org/wiki/Ad_blocking

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.


Ad-blocker detection strategy

Since Radiant Media Player 4.5.9 the ad-blocker detection logic is built in the player and based on the IAB adblockDetector script.

Radiant Media Player offers 2 options for detecting ad-blocker:

  • Passive strategy: the player will detect the presence of an ad-blocker and will fire API events when required but it will not take any action when an ad-blocker is detected. It is up to you to act upon API events or not. The player will attempt basic counter-measures to allow ad to play by trying to reload the required ad library or switching from Google IMA to rmp-vast but ultimately it is likely the ad-blockder will prevent video ads from playing. If it happens content should play without ads. This is the default.
  • Active strategy: the player will detect the presence of an ad-blocker and will fire API events when required but will also prevent playback of content when an ad-blocker is detected. A customisable message will be shown to the viewer asking to disable the ad-blocker in order to access content.

As discussed in our blog post it is very difficult 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.


Ad-blocker detection player settings

adBlockerDetection: Boolean

Whether or not the player should attempt to detect ad-blocker when init is called. Default: true.

adBlockerDetectedPreventPlayback: Boolean

Whether or not to prevent playback of content when an ad-blocker is detected. When playback is prevented a customisable message is shown to viewer requesting the ad-blocker to be disabled. Default: false.

adBlockerDetectedMessage: String

When playback is prevented the adBlockerDetectedMessage message is shown to the viewer. Default: 'Ad-blocker software detected. To view this content please disable your ad-blocker.'.


Ad-blocker detection player API

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. adBlockerDetection setting must be set to true for this event to fire.

Player API method

  • getAdBlockerDetected: this method will return a Boolean stating if an ad-blocker has been detected or not. null is returned in case this value is not available.

Tested ad-blockers

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:

  • Adblock Plus
  • AdBlock Pro
  • AdBlock
  • uBlock
  • Opera built-in ad-blocker feature (since Opera 37+)

Feel free to contact us with feedback on detecting ad-blockers.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License.