Consent and cookies

Default mode

Without data-require-consent="true", the tracking script can use its first-party identifiers as it collects activity. This supports recognizing returning visitors and joining activity across tabs or separate visits.

Your privacy notice and consent implementation must accurately describe the behavior you enable.

Require consent for cookies

Add data-require-consent="true" when first-party cookies must not be used until the visitor grants consent. The setup screen can generate this version for you.

Before consent is granted, the tracker creates no analytics identifier, writes no browser storage, and sends no analytics event. This means page activity, visitor counts, session continuity, and visitor-level attribution are unavailable for non-consenting visits.

Attribution consequences

Revenue attribution needs a RevenueUI visitor or session identifier to be attached to the relevant payment object. If consent has not supplied a persistent identifier, RevenueUI may still import the payment as revenue but cannot reliably connect it to a visitor journey.

This is expected: attributed revenue and total imported revenue answer different questions.

Integration checklist

• Decide whether cookies require prior consent for your audience and jurisdiction.
• Use the generated embed option that matches that decision.
• Keep the consent state consistent between your consent manager and RevenueUI integration.
• Explain the enabled collection accurately in your privacy notice.
• Test that the not-accepted path creates no storage or network request, and that the accepted path starts collection.