Cookies
Dreamdata Analytics uses cookies to function. This article outlines their names and purpose.
Cookie retention
Below is a summary table of the different cookies we use.
| Name | Persistency | Store | Purpose |
|---|---|---|---|
| dd_anonymous_id | 1 year | Cookie, Local Storage | Used to track the user across multiple visits. |
| dd_group_id | 1 year | Cookie, Local Storage | Used to track the user's organization across multiple visits. |
| dd_group_properties | 1 year | Cookie, Local Storage | Used to track the user's organization across multiple visits. |
| dd_user_id | 1 year | Cookie, Local Storage | Used to track a known user across multiple visits. |
| dd_user_traits | 1 year | Cookie, Local Storage | Used to track a known user across multiple visits. |
| dd_debug_mode | Persistent | Local Storage | Used to see if the script is loaded in debug mode. |
| dd_has_identified | Persistent | Local Storage | Used to track if user has been identified. |
If you are running Dreamdata Analytics in compatibility mode, then the script will use the following cookies:
| Name | Persistency | Store | Purpose |
|---|---|---|---|
| ajs_anonymous_id | 1 year | Cookie, Local Storage | Used to track the user across multiple visits. |
| ajs_group_id | 1 year | Cookie, Local Storage | Used to track the user's organization across multiple visits. |
| ajs_group_properties | 1 year | Cookie, Local Storage | Used to track the user's organization across multiple visits. |
| ajs_user_id | 1 year | Cookie, Local Storage | Used to track a known user across multiple visits. |
| ajs_user_traits | 1 year | Cookie, Local Storage | Used to track a known user across multiple visits. |
| dd_debug_mode | Persistent | Local Storage | Used to see if the script is loaded in debug mode. |
| dd_has_identified | Persistent | Local Storage | Used to track if user has been identified. |
How we use cookies
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 stored as a first-party cookie in the user's browser with an expiration of 1 year. The expiration renews every time the user returns. The cookie is also replicated to local storage with no expiration date. The tracking script tracks across subdomains out of the box.
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, the email will act as the identifier across sessions, browsers, and devices.
If the user clears their cookies or some automated browser cookie-clean cycle has been in effect, that user will be assigned a new anonymous ID and will effectively be a separate anonymous user in our system. Suppose the unique anonymous ID is associated with an email at a later point. The activities will union based on the email associated with the same users and persist across sessions, browsers, and devices.
Dreamdata keeps all anonymous IDs in our database. We experience that most browsers (including Safari) use first-party cookies and only remove them when they expire. However, users can clear cookies, and browsers work differently 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 persist over extended periods. Identifying frequently ensures that cookies are less essential. It also provides that you can track users across devices.
3rd party cookies Dreamdata does not use or benefit from 3rd party cookies. 3rd party cookies have shorter retention in some browsers (e.g., Safari) and will likely, over time, stop working or become even more restricted.
To streamline and enhance the structure of your Cookie Bar information related to Dreamdata integration, I'll organize the additional data points into a markdown table and refine the overall content for clarity and compliance notice:
Cookie bar notice
It is recommended to include Dreamdata within your Cookie Bar information as
part of the Analytics/Statistics cookies category. The use of cookies on our
website allows us to enhance our visitors' experience by understanding their
interactions more effectively.
Please note: This guidance does not constitute legal advice. Implementing cookie policies is the sole responsibility of the company, and it's crucial to consult privacy counsel to comply with applicable laws, as requirements may vary by jurisdiction.
Examples of Cookie Descriptions for Statistics/Analytics:
-
"Statistics cookies by web analytics tools gather information to help us understand visitor interactions, enhancing site usability. They track sessions, page views, and user preferences—aggregated data ensures anonymity."
-
"These cookies enable us to count visits and traffic sources, improving our site's performance. Understanding the popularity of pages and visitor navigation patterns, the collected information is aggregated and anonymous."
-
"Blocking or opting out of these cookies allows website use but limits our ability to enhance visitor experiences. Without these cookies, we can't track visits or analyze site performance."
Dreamdata Service Description:
"Dreamdata provides analytics for clear, actionable insights into B2B revenue drivers. Our cookies analyze user interactions, entry channels, and relevant page visits."
Additional Data Points:
| Information | Details |
|---|---|
| Processing Company | Dreamdata Kalvebod Brygge 39, 1560 Copenhagen, Denmark |
| Data Purposes | Analytics |
| Technologies Used | Cookies |
| Data Collected | IP address, Browser information, Usage data, Date and time of visit, Location information, Cookie Id |
| Location of Processing | European Union |
| Data Recipients | Dreamdata |
| Terms and Privacy Policy | Terms of Service, Privacy Policy |