--- updatedAt: 2026-09-18T18:48:44.000Z agentTools: siteIndex: https://docs.recurly.com/llms.txt projectIndex: https://docs.recurly.com/recurly-engage/llms.txt --- # Recurly Engage javascript tag Implementation details for adding the Recurly Engage tag to your site, via tag managers or direct script injection.
Add the Recurly Engage tag to your site to initialize Engage, track user interactions, and power secure, branded checkout flows. Install it directly or through the tag manager you already use.
Available to all customers on any Recurly Engage subscription plan
1Definition 2Key benefits 3Key details
### Prerequisites ### Limitations # 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 through a popular tag manager 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 JavaScript directly to your site if you'd rather skip the tag manager. In most cases, we recommend the `defer` or `async` script attribute to keep the tag from delaying page rendering — the Recurly Engage tag runs once the page has rendered. Reach out to your customer success manager if you have questions about specific requirements.
## Content Security Policy (CSP) requirements If your site uses a Content Security Policy, you'll need to allowlist Recurly Engage's domains so the tag can load and communicate correctly. Add the following to your configuration: ### Why this is necessary Without these entries, your browser may block the tag from executing or prevent it from sending data to our API. Common failures caused by a missing or misconfigured CSP include: If you add a custom background image to a prompt, it may still fail to load even with the CSP entries above in place. This usually happens when your security settings require all image sources to be self-hosted — in that case, host the image on your own infrastructure rather than Recurly's, since Recurly's domain won't be an allowed source under those stricter policies.
NoteThis is a client-side configuration. Recurly Engage manages CORS on our end, but the CSP itself must be updated in your own site's headers or meta tags.
# Sub pages * [Google tag manager](https://docs.recurly.com/recurly-engage/docs/google-tag-manager.md) * [Adobe dynamic tag manager](https://docs.recurly.com/recurly-engage/docs/adobe-dynamic-tag-manager.md) * [Tealium iQ tag manager](https://docs.recurly.com/recurly-engage/docs/tealium-iq-tag-manager.md) * [Direct tag management](https://docs.recurly.com/recurly-engage/docs/rengage-direct-tag.md) # Sibling pages * [Overview: Recurly Engage](https://docs.recurly.com/recurly-engage/docs/overview-recurly-engage.md) * [Recurly Engage setup](https://docs.recurly.com/recurly-engage/docs/setup-your-app.md) * [Invite users](https://docs.recurly.com/recurly-engage/docs/invite-users.md) * [Sync user traits](https://docs.recurly.com/recurly-engage/docs/sync-user-traits.md) * [Activate prompts](https://docs.recurly.com/recurly-engage/docs/activate-prompts.md) * [Create a pop-up](https://docs.recurly.com/recurly-engage/docs/create-a-pop-up-recurly-engage.md) * [Create an experiment](https://docs.recurly.com/recurly-engage/docs/create-an-experiment.md)