Skip to main content

Introduction to Cookieless Account Analytics

What is Cookieless Account Analytics?​

Cookieless Account Analytics is a privacy-conscious method for gaining insight into company-level engagement with your website — without relying on traditional cookies. It helps you understand the types of companies visiting your site, how frequently they return, and which content areas draw the most interest.

Designed to support privacy-first web practices, Cookieless Account Analytics avoids persistent tracking and integrates with Consent Management Platforms (CMPs) to ensure user consent preferences are respected. It is built for organizations that want to improve business insights while aligning with data protection obligations.

How does Cookieless Account Analytics work?​

In a privacy-focused digital landscape, traditional cookie-based tracking often requires prior consent under regulations like the ePrivacy Directive and GDPR. Cookieless Account Analytics offers an alternative by avoiding cookies and instead performing a temporary IP-to-Company lookup to infer company-level visits.

IP addresses are processed briefly and solely for the purpose of identifying company-level interactions, and are securely deleted within 14 days. No cookies or persistent device identifiers are used, and no individual users are profiled.

This process is comparable to how Consent Management Platforms use IP addresses to determine regional compliance requirements. Analytics tracking is fully gated behind user consent mechanisms, and the system integrates seamlessly with major CMPs such as CookieBot, CookieScript, and others.

Note

Dreamdata does not provide legal advice and cannot guarantee that your specific data collection practices are fully compliant with applicable laws such as the ePrivacy Directive or GDPR. You should consult with your own legal or privacy team to assess your compliance posture.

Dreamdata’s Cookieless Account Analytics performs a temporary IP-to-Company lookup prior to activating analytics functionality, in order to determine whether analytics processing should occur based on jurisdictional and consent logic. This is conceptually similar to how Consent Management Platforms (CMPs) use IP-based geolocation to determine whether a consent banner needs to be shown.

IP addresses are not retained for profiling, and are securely deleted within 14 days. No cookies or persistent identifiers are used in this step, and all tracking behavior is gated by the user’s consent preferences. The system respects user choice and integrates with most major CMPs to ensure analytics data is collected only when legally permissible. When consent is managed correctly and company policies reflect appropriate legal safeguards, use of Dreamdata as a processor can form part of a compliant analytics strategy.

How to set it up​

To set up Cookieless Account Analytics, use our intuitive wizard by navigating to Data Platform > Sources > Javascript and clicking the configuration button within the Dreamdata application. This guided process will help you easily set it up.

Cookieless Account Analytics works with many popular Consent Management Platforms. If your Consent Management Platform is not listed here, contact us at ag@dreamdata.io to see if we can add support for it.

CookieBot​

Works out of the box.

CookieInformation​

See guide here.

CookieYes​

Works out of the box. We recommend that you turn on Reload page on consent action to get page views when visitors consent.

Affect on MTUs​

Collected page views that are matched to a company with Cookieless Account Analytics will count towards your MTU usage. Page view cannot be associated to a company are disregarded and will not be counted.

Setup for SPAs​

When using a SPA (as described here), our recommend approach is to use our NPM package and creating two Analytics instances, as done below:

import { AnalyticsBrowser } from "@dreamdata/analytics-next";

export const dreamdata = AnalyticsBrowser.load({
  writeKey: "<YOUR_WRITE_KEY>",
});
export const dreamdataCookieless = AnalyticsBrowser.load(
  {
    writeKey: "<YOUR_WRITE_KEY>",
  },
  { anonymous: true },
);

Then tracking can be done as

if (user.hasConsented) {
  dreamdata.track("Clicked button");
} else {
  dreamdataCookieless.track("Clicked button");
}