Overview

Required plan

This feature or setting is available to all customers on any Recurly Engage subscription plan.

Prerequisites & limitations

You must have Company, App Administrator, or App Member permissions in Recurly Engage.

You need access to modify your site’s HTML or tag manager container.

If using a tag manager, ensure you have publish permissions.

Definition

The Recurly Engage tag is a lightweight JavaScript snippet that initializes Engage on your site. It enables tracking of user interactions and powers secure, branded checkout flows within your application.

Key benefits

Easy integration: Deploy via popular tag managers without editing page code.
Optimal performance: Load asynchronously or deferred to avoid delaying page rendering.
Flexible deployment: Choose from multiple tag managers or embed the script directly.

Key details

The following tag managers are supported for convenience. You can also add the JS directly to your site if you prefer.

In most cases, we recommend using the defer or async script element attribute to ensure minimal impact on page rendering performance. The Recurly Engage tag will execute once the page has rendered. Please reach out to your customer success manager if you have questions on specific requirements.

Important: Content Security Policy (CSP) Requirements

If your website uses a Content Security Policy (CSP), you must allow Redfast domains to ensure the tag loads and communicates correctly.

Please add the following to your configuration:

Script Source (script-src): Add your unique company-specific JS tag domain.
Connect Source (connect-src): Add conduit.redfast.com to allow necessary network traffic.

Why is this necessary?

Without these entries, your browser may block the Redfast tag from executing or prevent it from sending data to our API.

Technical Note: This is a client-side configuration. While Redfast manages CORS on our end, the CSP must be updated within your own site’s headers or meta tags.