Public reports (Backlinko, Statista) indicate that up to 50% of web users employ ad blockers. Ad blockers may block third-party JavaScript tags, including the Recurly Engage tag, which disables your engagement prompts.

Available on the Enterprise plan or with the Ad Blocker Mitigation add-on

1Definition 2Key benefits 3Key details

Prerequisites

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 (for example, track.yourcompany.com) so that browser extensions no longer block prompt delivery. The change requires only a Domain Name System (DNS) update and reconfiguration of your tag manager.

Key benefits

Maximized reach Make sure prompts reach users even when ad blockers are enabled.

DNS-only setup No code changes. Configure a canonical name (CNAME) record and update your script tag.

Automatic updates Recurly Engage continues to host and update software development kit (SDK) assets on the new subdomain.

Key details

To enable Ad Blocker Mitigation, complete the following steps.

Update DNS

Agree on a subdomain

Agree upon a subdomain (for example, track.yourcompany.com).

Get the CNAME target

Your Recurly Engage Customer Success Manager provides the CNAME target (for example, yourapp.recurlyengage.com).

Add a CNAME entry

Your IT team adds a CNAME entry in your DNS.