Cookie-less and Consent-Aware Tracking with RevSure

Prev Next

Overview

RevSure supports cookie-less and consent-aware website tracking, allowing organizations to collect website engagement data while respecting visitors' consent preferences.

With RevSure's updated First-Party Tracking SDK, websites can capture anonymous engagement events without setting tracking cookies before consent. Once a visitor grants consent, the SDK transitions to standard first-party tracking with persistent visitor identification.

The integration works with existing Consent Management Platforms (CMPs), including OneTrust, Osano, CookieYes, and other solutions that support JavaScript-based consent notifications.

How It Works

RevSure operates in two tracking modes based on the visitor's consent status.

Pre-Consent Tracking

Post-Consent Tracking

Tracking mode

Cookie-less

First-party cookie-based

Cookies

No tracking cookies

First-party tracking cookies

Visitor identification

New anonymous identifier for each event

Persistent anonymous visitor identifier

Page views and events

Captured anonymously

Captured with persistent visitor identification

Consent status

Not granted

Granted

Data destination

RevSure First-Party Tracking data source

RevSure First-Party Tracking data source

Pre-Consent Mode

When a visitor accesses the website without granting analytics consent, RevSure operates in cookie-less mode.

  • No persistent visitor identifier is created.

  • Tracking cookies are not stored in the visitor's browser.

  • Page views and supported events can still be captured.

  • Each event receives a temporary, non-persistent identifier.

  • Events are sent to the RevSure data collection endpoint configured in the script.

Post-Consent Mode

When a visitor grants analytics consent, RevSure automatically switches to first-party cookie-based tracking.

  • First-party cookies are enabled.

  • A persistent anonymous visitor identifier is created.

  • A new identifier is generated at the moment of consent, so events captured before consent are not linked to this identifier.

  • Subsequent website interactions can be associated with the same visitor.

  • Standard event tracking and visitor identification become available.

Consent Withdrawal

If a visitor withdraws consent, RevSure switches back to cookie-less tracking.

The consent handler removes RevSure tracking cookies and clears associated queued event data from browser storage.

Prerequisites

Before configuring cookie-less tracking, ensure that:

  1. A RevSure First-Party Tracking data source is already configured.

  2. You have access to the RevSure tracking snippet and corresponding write key.

  3. You can update your website's HTML or Google Tag Manager configuration.

  4. Your Consent Management Platform can execute JavaScript when a visitor grants or withdraws consent.

  5. RevSure's required domains are permitted by your website's Content Security Policy.

Setup Instructions

Step 1: Update the RevSure Tracking Script

Replace your existing RevSure First-Party Tracking snippet with the updated consent-aware snippet provided by your RevSure customer success team.

The updated implementation uses the RevSure-hosted JavaScript SDK:

https://assets.revsure.cloud/static/global/js/v2/modern/rsa.min.js.gz

This hosted file uses the JavaScript SDK version 3.24.0.

Install the snippet on all relevant website pages, preferably within the HTML <head> section.

If using Google Tag Manager, configure the tracking snippet as a Custom HTML tag with the appropriate page-load trigger.

Important: The RevSure snippet must be permitted to load before analytics consent if you intend to capture cookie-less, pre-consent events. The snippet manages the transition between tracking modes. If your CMP blocks scripts until consent (for example, Osano script blocking), add assets.revsure.cloud to its allowed list. Otherwise the SDK will not load before consent.

Step 2: Enable Pre-Consent Tracking

The SDK uses the preConsent configuration to enable cookie-less tracking.

preConsent: {
  enabled: true,
  storage: {
    strategy: "none"
  },
  events: {
    delivery: "immediate"
  }
}

 

This configuration enables anonymous event collection without persistent visitor storage.

RevSure also uses the following consent management configuration:

consentManagement: {
  enabled: true,
  provider: "custom"
}

The custom provider allows the SDK to receive consent decisions from your existing Consent Management Platform.

If consent has already been granted, the initialization configuration should reflect that stored consent state.

Your RevSure-provided snippet should include these settings as part of the complete SDK initialization.

Configure your Consent Management Platform to notify RevSure whenever a visitor grants or withdraws consent.

The RevSure integration snippet exposes the following functions.

When consent is granted:

window.revsureConsent.grant();

This switches tracking to first-party cookie-based mode.

When consent is denied or withdrawn:

window.revsureConsent.deny();

This switches tracking back to cookie-less mode and clears RevSure's persistent browser identifiers.

Configure your CMP to invoke the appropriate function:

  • When the visitor initially accepts or declines analytics consent.

  • When the website loads and the CMP retrieves an existing consent preference.

  • Whenever the visitor updates or withdraws consent.

The exact implementation depends on your Consent Management Platform.

Note: The snippet's method list already includes "consent", so consent updates are queued even before the SDK finishes loading. Do not remove methods from this list.

Step 4: Allow RevSure Domains

Ensure the following domains are allowed in your website's Content Security Policy.

Domain

Purpose

https://assets.revsure.cloud

Loads the RevSure tracking SDK

https://analytics.revsure.cloud

Receives website tracking events

Your CMP must also permit the SDK to load in pre-consent mode if anonymous tracking is required.

Step 5: Validate the Implementation

After updating the tracking script, validate the integration in a test environment before deploying it to production.

Test Scenario

Expected Behavior

Visitor opens website without consent

RevSure SDK loads in cookie-less mode

Visitor has not granted consent

No RevSure tracking cookies are created

Visitor accepts analytics consent

First-party tracking cookies are enabled

Visitor reloads the page after accepting

Persistent anonymous visitor ID remains available

Visitor withdraws consent

RevSure tracking cookies are removed

Visitor declines consent

Anonymous events can continue without persistent identifiers

Visitor submits a test form

Configured tracking events are delivered successfully

Recommended validation steps:

  1. Open the website in a private browser window.

  2. Open Developer Tools and navigate to Network.

  3. Confirm the RevSure SDK loads successfully.

  4. Check browser cookies before granting consent.

  5. Grant analytics consent and confirm that tracking cookies are created.

  6. Withdraw consent and verify that RevSure tracking cookies are removed.

  7. Confirm that events are successfully sent to the data collection endpoint in the script.

For further validation, contact your RevSure customer success team to confirm that test events have been received.

IP Address Handling

RevSure supports an optional server-side IP anonymization configuration for events collected without analytics consent.

When enabled, this configuration can:

  • Truncate IPv4 addresses by removing the final octet.

  • Truncate IPv6 addresses to the first 48 bits.

  • Preserve the standard IP handling configuration for consented events.

IP anonymization is performed within RevSure's data processing pipeline before events are stored in the data warehouse.

Important: IP anonymization requires configuration by the RevSure team and is not automatically enabled for every implementation. Contact your RevSure customer success team to request activation and confirm the applicable IP-handling policy.

The data collection endpoint still receives the originating IP address to process incoming requests.

Frequently Asked Questions

1. Does RevSure support tracking without cookies?

Yes. RevSure supports pre-consent tracking without setting persistent visitor tracking cookies. Each pre-consent event uses a temporary identifier instead of a persistent visitor identifier.

Yes. RevSure supports integration with CMPs that can communicate consent changes through JavaScript.

The consent functions can be connected to your existing CMP events.

3. Do we need to create a new RevSure data source?

In most cases, no. The updated script sends events to your existing RevSure First-Party Tracking data source. Your RevSure team will confirm this during setup.

There is no requirement to create another pixel or data source.

RevSure switches back to cookie-less mode, removes its tracking cookies, and clears associated queued event data from browser storage.

Subsequent events can continue to be captured anonymously.

5. Will existing reports and dashboards continue to work?

The updated SDK supports existing event names and the same RevSure data source.

However, attribution and journey analysis may behave differently for visitors who have not granted consent because their events cannot be reliably connected through a persistent browser identifier. Events captured before consent are also not linked to the visitor identifier created after consent.

6. Does RevSure support IP anonymization?

Yes. IP anonymization can be configured within RevSure's data processing pipeline.

Please contact your RevSure customer success team to request this configuration and confirm when it is active.

7. Will the SDK update automatically?

The SDK is served from a fixed RevSure-hosted URL (currently SDK version 3.24.0). RevSure manages updates to this file, your RevSure team will confirm this during setup.

8. Does cookie-less tracking store any data in the browser?

The SDK does not set persistent visitor tracking cookies or a persistent visitor identifier in pre-consent mode. However, it may temporarily use browser local storage for event delivery queues.

Cookie-less tracking should therefore not be interpreted as a guarantee that no browser storage is used.

9. Can existing form tracking and custom events continue working?

Yes. Existing tracking methods, including track() and identify(), remain available.

For visitors without consent, events should contain the information required for the individual event, since a persistent anonymous identifier is not available to link separate events.

10. Is cookie-less tracking automatically compliant with privacy regulations?

Cookie-less tracking provides privacy-supporting controls, but compliance depends on your organization's legal requirements, consent policies, data collection configuration, and applicable regulations.

Your organization should determine whether pre-consent event collection is permitted under its privacy requirements.

Note that pre-consent events can still include data you send explicitly, such as form fields passed through identify() or track(). The SDK does not automatically honour Global Privacy Control (GPC) or Do Not Track signals. These should be handled through your CMP if required.


Support

For help with implementation, consent management integration, IP anonymization, or validation, contact your RevSure Customer Success Team.

RevSure can assist with configuring the updated tracking script, connecting consent signals, and verifying successful data collection.