Overview

Public reports (Backlinko, Statista) indicate up to 50% of web users employ ad blockers, which may block third-party JavaScript tags—including Recurly Engage’s—disabling engagement prompts.

Prerequisites & limitations

• You must have Company, App Administrator, or App Member permissions in Recurly Engage.
• You must be on the Enterprise plan or have purchased the Ad Blocker Mitigation add-on.

Definition

Ad Blocker Mitigation routes the Recurly Engage tag and API traffic through a customer-owned subdomain (e.g., track.yourcompany.com) so that browser extensions no longer block prompt delivery. The change requires only a DNS update and reconfiguration of your tag manager.

Key benefits

• Maximized reach: Ensure prompts reach users even when ad blockers are enabled.
• DNS-only setup: No code changes—just configure a CNAME and update your script tag.
• Seamless updates: Recurly Engage continues to host and update SDK assets on the new subdomain.

Key details

To enable Ad Blocker Mitigation, complete the following steps:

Update DNS

1. Agree upon a subdomain (e.g., track.yourcompany.com).
2. Your Recurly Engage Customer Success Manager will provide the CNAME target (e.g., yourapp.redcurlyengage.com).
3. Your IT team adds a CNAME entry in your DNS: