In Web SDK 19.4+, there is an option for a micro-cookie instead of the traditional cookie. In this configuration, a small (under 50 bytes), first-party cookie assigns a unique ID to each visitor, while the state is kept in the cloud. With the micro-cookie option, the cookie size is consistently smaller compared to a floating size used for traditional tracking options.
While this is an attractive option when the cookie-budget is at a premium, it does involve more asynchronous network traffic to synchronize the state between the browser and the state server. The precise amount of network traffic depends on how many CPPs are set, and how often, along with how many tabs the user has open. The average payload size tends to be under 1KB and occurs whenever the state changes. (Note: network requests occur every heartbeat once the tracker window is opened. This is the same as with the traditional cookie option and is the check to determine if the user continues to browse on your site. The survey is presented once the end of the website session is detected.)
Once micro-cookie is enabled in your Web SDK configuration, the local, traditional cookie data is read and securely copied to Verint's cloud storage. Then, this cookie is deleted from the user's local storage and replaced with the micro-cookie, resulting in reclaimed browser storage for end users.
Updated 5 months ago