Ad block detection listening enables you to detect whether or not a customer or visitor is actively using an ad blocking technology to hide advertisements. The result ("yes" or "no") is stored in a profile property for use in a segment. You can also use an event to trigger a dialogue that appears when ad blockers are detected.
Note: The Ad block detection listener does not work on Safari mobile or desktop browsers.
Configure the listener
You can choose where to detect the ad blocker -- on all pages in all channels, or only in some.
Select the profile property where the detection result is stored (or create a new profile property here). The default value is "AdBlock Usage Detected."
To create a new profile property, click the "edit this object" icon and enter a new profile property name.
When an ad blocker is detected, BlueConic throws an event, adblock_detected. You can use this event to trigger a dialogue by adding a "Show on event" rule in the When tab of the dialogue. To prevent the dialogue from showing on every page view, you can add additional rules to the dialogue.
Create a segment of users who are blocking ads
With the Ad Block Listener in place, it will take just a few seconds to use the Segments menu to create a segment for "users blocking ads":
- Choose Segments from the BlueConic navigation menu.
- Select the profile property "AdBlock Usage Detected".
- Select the value "yes".
Interact with your users
As with all data collected and segmentation performed in BlueConic, ad block segmentation is available to be shared out to any number of other systems so you can use this information in campaigns and analyses.
You can also use BlueConic dialogues to take advantage of the otherwise empty ad placements. Prompt users to sign up for newsletters, to subscribe, to share content on social networks, etc.
Here is an example from our example publishing site.
Consider a typical ad placement:
When blocked, you can attempt to recoup lost revenue from this ad space by placing highly relevant messaging in its place:
Listeners can be added to Objectives, allowing for privacy management of the information that is being picked up. The listener will only update a profile if the visitor consented to at least one of the objectives that it is linked to.