Cookie Retention

Ole Dallerup Updated by Ole Dallerup

A user lands on a page you own (for the first time) with a Dreamdata tracking script. The user is then assigned an anonymous ID, that is stored as a first party cookie in the user’s browser with a expiration of 1 year. The expiration renew every time the user returns. The cookie is also replicated to localstorage that does not have any expiration date.

When that user arrives on another page later, we will re-use that locally stored anonymous ID if it is present, and those sessions will be visible as a single user inside Dreamdata. If the user is identified using an email in the browser, then the email will act as the identifier across session, browser and device.

If the user clears his/her cookies, or some automated browser cookie-clean cycle has been in affect, that user will be assigned a new anonymous ID and will effectively be separate anonymous users in our system. If the new anonymous ID is associated with an email at a later point, then the activities will union based on the email associated into the same users and thereby persists across session, browser and device.

Dreamdata keep all anonymous IDs in our database. We experience that most browsers (including Safari) keep first party cookies and only remove them when they expire, though users can clear cookies and browsers does work different also depending on user settings.

Browser behavior might change in the future. Therefore it's recommended to ensure users are identified with email as often as possible or when it makes sense as that removes the need for cookies to persists over longer periods. Identifying frequent ensuring not only that cookie are less important it also ensures that you can track users across device.

3th party cookies

Dreamdata does not use or benefit from 3th party cookies. 3th party cookies have shorter retention in some browsers amongst other Safari and will likely over time stop working or be even more restricted.

How did we do?

Cookie Bar

Dreamdata Cookies

Contact