Glossary

Cookieless tracking: definition and examples

Cookieless tracking measures website activity without using cookies for that measurement. It can still process personal data, so removing cookies does not automatically remove GDPR or consent obligations.

What replaces the cookie?

Some systems count requests without joining them into visitor journeys. Others use temporary identifiers or server-side events. These approaches answer different questions: counting pageviews needs less continuity than recognizing a person who returns next week. A server-side implementation can still use a cookie-derived ID, so moving collection off the browser does not itself make tracking cookieless.

GA4 cookieless tracking

In Google's consent mode documentation, advanced mode can send cookieless pings while analytics storage consent is denied. Basic mode blocks Google tags when consent is not granted. Cookieless pings are still requests to Google and can support modeled reporting; they are not a complete observed history of each nonconsenting visitor. Consent mode communicates choices to tags; it does not supply a banner or decide whether your collection is lawful.

A worked example in AnalyticFast

The standard tracker uses first-party ml_vid and ml_sid cookies. Optional cookieless mode must be configured per site, with the installed snippet set to avoid cookies. The server derives a daily pseudonymous visitor ID from a salt, site ID, IP address and user agent. The IP address is processed transiently for hashing and is not stored with analytics. Latitude and longitude are rounded to two decimal places.

Suppose someone views a guide and a pricing page ten minutes apart on the same UTC day, with the same address and browser. Those visits can join an open session. A visit the next UTC day has a different derived visitor ID. Do not interpret the resulting two daily identities as proof of two people.

Limits and consent

Shared addresses and browsers can merge visitors; changing either can split them. A proxy can make many people appear to share an address. Daily rotation limits automatic continuity across days and devices. Explicit identification or payment metadata can introduce additional links and personal data.

Cookieless describes a collection technique, not legal approval. ePrivacy Article 5(3) concerns device storage and access more broadly than cookies alone. Evaluate the actual implementation and local rules. The consent guide explains how to block collection entirely when required. This is not legal advice.

Related definitions

Install AnalyticFast and connect verified revenue to use these definitions with your own data.

Questions, answered.

Is AnalyticFast cookieless by default?

No. The standard tracker uses first-party visitor and session cookies. Optional cookieless mode requires per-site configuration and an installed snippet that avoids cookies.

Does cookieless mean no consent is needed?

No. Device-access rules can cover other technologies, and GDPR can still apply to pseudonymous data. Assess the collection, purpose and applicable national rules.

Keep exploring