RevSure Cookieless Tracking

Overview

Cookie-less Visitor Tracking refers to the process of identifying a Visitor across different pages and browser sessions over a period of time, without using cookies to track the user information.  RevSure supports Cookie-less Visitor Tracking through a combination of settings in the First party JavaScript Pixel and its Multi-level Fingerprinting technology.  

Cookie-less Visitor Tracking is useful for mapping out the journey of the visitor while complying with the privacy regulations.  

Default Cookie Management

RevSure uses Rudderstack’s JavaScript SDK for its website tracking pixel.  The pixel is typically installed under the control of a Cookie Consent Management tool like OneTrust.  

By default, RevSure’s First Party Pixel uses Cookies to store and track user information.   All the cookies used by the pixel along with their purpose and persistence rules can be found here:  RevSure Website Tracking - Cookie Data Persistence

When the pixel is linked to a tool like OneTrust, it is not fired without explicit consent provided by the visitors.  In this scenario, no data is collected and sent to RevSure

Cookie-less Tracking

In scenarios where the customers do not want to use cookies at all, RevSure can customize the First Party Pixel in such a way that the visitor's information is not stored and tracked in any form in the User’s browser.  

This is achieved by setting the storage type as “none” in the Rudderstack SDK’s load function.  In this scenario, Rudderstack’s anonymous_id (cookie id) is not stored and tracked across sessions in cookies or using any other storage methods.   The data collected for each page visit is still sent to RevSure.

Fingerprinting

With the basic data collected through the pixel, RevSure applies 3 levels of fingerprinting to identify a Visitor across pages and sessions to build the complete journey of the profile.

The following are the 3 levels of fingerprinting supported by RevSure

  • Level 0: IP Address, Location, Time Zone, ISP (Cross-device fingerprint)
  • Level 1: Level 0 + Device details + OS details (Cross-browser fingerprint)
  • Level 2: Level 1 + Browser details (browser level fingerprint)

For each visitor record collected, RevSure creates these 3 fingerprint hashes and provides a configurable option to use one of them to merge duplicate visitors.  

While Level 0 provides the broadest set of attributes to identify a visitor, Level 2 fingerprint provides the most granular level of identification that minimizes errors and identifies the same user based on most number of attributes collected by the pixel.

Conclusion

With its robust fingerprinting technology, RevSure provides a way to connect the buyer journeys from when they were anonymous and improves attribution even in a cookie-less world.

See a DemoPricingWhy RevSureFuture of AttributionSecurity Center
Read RevSure reviews on G2