Skip to content

Cookies & localStorage

To be able to fully use personalisation via Dropsolid Experience Cloud you need to ensure some first-party cookies are available on your site.
If your site has a way of requesting consent of a visitor (for example with the eu_cookie_compliance Drupal module), you have to make sure:

  • it's clear for the visitors what these cookies are used for
  • they are allowed on your site after consent

Here we describe which cookies are set and which data is stored in localStorage for personalisation via Dropsolid Experience Cloud.

Cookies

The javascript API sets multiple cookies that need to be whitelisted by the site:

dropsolidCapture

This cookie persists for 22 minutes after the cookie has been set, which gets refreshed on every visitor interaction on the site, and is set on the site's domain.

If the cookie is expired, it gets reset with a new uuid on the next visitor interaction on the site.

This cookie contains:

  • uuid
    • the session uuid of the visitor
  • domain
    • the domain of the site this cookie is set for
  • hostName
    • the host name of the site this cookie is set for
  • created
    • the exact time this cookie was created

context-profile-id

This cookie remains for a lifetime, never gets deleted, only updated, and is set on the site's domain.

This cookie only contains an uuid, which is the profile id of the visitor in Unomi.

This cookie is used to make sure the visitors retain the correct profile in Unomi.

This cookie is also used by Unomi by default.

DS_VARY_ML

This cookie remains for a lifetime, never gets deleted, only updated, and is set on the site's domain.

This cookie only contains an uuid, which is the uuid of the segment the visitor gets classified as.

DS_MANUAL_SEGMENT

This cookie is set by the Dropsolid helper extension.

This cookie remains for a lifetime, never gets deleted, only updated, and is set on the site's domain.

When this cookie is set with a value of 1, this means you are testing segments through the helper extension, which means the javascript API will not overwrite the DS_VARY_ML cookie so you can choose which segments to test on the site.

If the segment selection in the helper extension is turned to off, then this cookie will have a value of 0.

localStorage

The javascript API also saves some data in localStorage:

These objects remain in localStorage until the visitor clears it.

dropsolidCapture

It keeps track of the same data as the dropsolidCapture cookie.

The only difference is that here in localStorage the created value does not get updated with every interaction.

myCaptures

It keeps track of the failed captures, so these can be resent when a page gets loaded.

The captures are removed from this object when they are successfully resent.