If you're managing cookie consent, the Engage (Redfast) tag can get blocked before a visitor ever consents — and that can quietly stop critical functions like cancel-save from firing. Here's why it happens and how to configure consent categorization and opt-out syncing so Engage keeps working for every visitor.
Available on all Recurly Engage plans
By default, the Engage tag loads with your site's default consent configuration. If that configuration categorizes the tag under Performance or Targeting, cookie managers block it until the visitor consents to that category. Because Engage deploys as a single script rather than per-prompt, this classification applies at the tag level, not to individual prompts.
WarningIf the Engage tag is categorized under Performance or Targeting, it won't load for any visitor who hasn't consented to that category — including visitors who need to reach critical functions like cancel-save or the on-hold state.
Set the Engage tag's cookie category to Strictly Necessary. This ensures critical functions fire reliably for every visitor, regardless of consent status.
1
Set this at the tag level in your cookie manager. Since Engage deploys as a single script, the category applies to the tag as a whole rather than to individual prompts.
2
Engage can read the cookie consent directly using live user trait ingest, recording that value as a user trait.
3
Use the synced trait to create a separate segment for visitors who've opted out of targeting.
For this segment, you have two options:
- Exclude the segment fully from the experience
- Show a "blackbox" version — opted-out users still receive the experience, but you won't see the performance data for that flow
TipEither option keeps opted-out users on core functions like the paywall and the on-hold state — they just won't receive personalized experiences.
By default, Recurly Engage collects only session timestamps. No personally identifiable information (PII) is collected unless you explicitly configure it, and IP addresses are never stored. Location targeting uses a one-way hash against a locally hosted GeoIP database. Cookies aren't used in platform operations unless you explicitly enable first-party cookies for your use case.
