Guide

Visitor Identification and Consent: What the Rules Say

What European and California law say about visitor IDs, cookieless tracking, and identifying the company behind a visit, quoted from the laws and regulators, with our own reading marked as such.

9 min read

This guide sets out what the main rules say about recognizing and identifying website visitors: the visitor ID every analytics tool uses, and the company lookup built on top of it. It quotes the rules where it can. It is general information and not legal advice. Where a statement is our reading, and not the text of a law, a court, or a regulator, it is marked Our reading. For your own situation, ask a lawyer.

In Europe, Two Laws Apply

Most articles on this subject discuss the GDPR and stop. There are two layers, and they ask different questions.

The GDPR defines personal data as "any information relating to an identified or identifiable natural person". Its Recital 30 says people "may be associated with online identifiers" such as "internet protocol addresses", which may be used "to create profiles of the natural persons and identify them".

In the Breyer case in 2016, decided under the data protection directive that came before the GDPR, the EU's Court of Justice held that a dynamic IP address registered by a website operator is personal data for that operator "if it has the legal means enabling it to identify the visitor with the help of additional information which that visitor's internet service provider has".

The company record you end up with is not personal data. The GDPR "does not cover the processing of personal data which concerns legal persons". What is personal is the visitor's IP address and the visit attached to it.

Our reading: looking up the company behind an IP address is a use of that address, so treat the lookup as processing personal data, even though the answer is a company name. Naming the person is the case where the rules bite hardest, because the result itself is personal data.

Processing personal data needs a legal basis. Article 6 lists six. Two matter here:

  • Consent, given "for one or more specific purposes".
  • Legitimate interests, where processing is "necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject".

We read the privacy pages of five identification vendors. Most say company-level identification rests on legitimate interests. One requires customers to run a consent tool before it identifies visitors outside the United States. All five tell customers to name the tool in their privacy notice or cookie policy. Legitimate interests is a balancing test you have to carry out and be able to show. It is not automatic.

Whichever basis you use, Article 13 requires you to tell visitors "the purposes of the processing for which the personal data are intended as well as the legal basis for the processing" and, where you rely on legitimate interests, "the legitimate interests pursued". Under Article 21, a person has "the right to object" to processing based on legitimate interests.

The ePrivacy Directive: Are You Reading From the Visitor's Device?

This is the rule behind cookie banners, and it is separate from the GDPR. As the European Data Protection Board, the body made up of the EU's data protection regulators, summarizes Article 5(3), "the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user" is "only allowed on the basis of consent or necessity for specific purposes set out in that Article". Legitimate interests is not one of the options.

Three points from the board's guidelines on that article, adopted in October 2024, apply to everything below:

  • It is not only about cookies. The article "does not exclusively apply to cookies, but also to 'similar technologies'".
  • Covered does not always mean consent. The applicability of the article "does not systematically mean that consent needs to be collected". Exemptions are assessed case by case, "accounting for the relevant member state transposition(s), and guidance issued by national Competent Authorities".
  • Companies are protected too. "Legal persons are also safeguarded by the ePD." A visitor being at work does not take the visit outside the rule.

These guidelines are the regulators' interpretation. They are not a statute or a court ruling.

Visitor IDs: The Bigger Question

Before any tool can identify a company, it has to tell that two page views came from the same visitor. Every analytics product does this, so it affects far more sites than company identification does. There are two common ways.

An ID stored in the browser. A random ID is saved in a cookie or in browser storage and read back on each page view. That is storing and reading information on the visitor's device, which is what Article 5(3) describes.

An ID computed from the request. Some analytics products avoid cookies by computing a visitor ID on their servers from the visitor's IP address and browser details, and replacing it on a schedule, such as every day. Vendors that work this way say it needs no cookie banner.

Regulators have addressed the second approach directly. The Article 29 Working Party, the group of EU regulators that the board replaced, wrote in its 2014 opinion on device fingerprinting that "a number of online services have proposed device fingerprinting as an alternative to HTTP cookies for the purpose of providing analytics without the need for consent". Its key message was that "Article 5(3) of the ePrivacy Directive is applicable to device fingerprinting", and on analytics it concluded that "first-party website analytics through device fingerprinting do not fall under the exemption" and "consent of the user is required".

The opinion defines a fingerprint broadly, as information "that can be used to single out, link or infer a user, user agent or device over time", and notes that elements become identifying "especially when combined with other identifiers such as the originating IP address". The 2024 guidelines add that relying on request details such as the user agent to collect information, "for example in the context of fingerprinting", "can lead to the application of Article 5(3) ePD".

Two limits on that. The opinion's conclusion is about fingerprints "generated through the gaining of access to, or the storing of, information on the user's terminal device", which is where the argument about data that arrives with every request comes in. And like the guidelines, the opinion is an interpretation, not a ruling.

Our reading: avoiding cookies does not take a tool outside this rule. Whether an ID that is rebuilt every day from the IP address and browser details needs consent is contested. The regulators' texts point toward yes. The vendors that use it disagree, and we did not find a regulator's decision or a court ruling on that specific design. A daily ID also cannot connect a visit this week to a signup next month, which limits what the analytics can tell you.

Company Lookups by IP Address

The same guidelines cover tracking that uses the IP address alone. Gaining access to an IP address triggers Article 5(3) "in cases where this information originates from the terminal equipment of a subscriber or user". That is "not systematically the case". But "unless the entity can ensure that the IP address does not originate from the terminal equipment of a user or subscriber, it has to take all the steps pursuant to the Article 5(3) ePD".

Our reading: for company lookups on European visitors, the cautious position is to ask for consent first, because you usually cannot show where an IP address originates. We did not find a regulator's decision or a court ruling that deals specifically with identifying companies from website visits, so this has not been tested.

  • Consent covers what the visitor was told. The GDPR defines consent as a "freely given, specific, informed and unambiguous indication of the data subject's wishes". Our reading: if consent is the basis you rely on for identifying companies, your banner and privacy notice need to say that it is one of the purposes, because a general "analytics" choice may not cover it. If you rely on legitimate interests, the requirement is the notice and the right to object described above, not a banner purpose.
  • Consent can be taken back. Under Article 7, a person can withdraw consent "at any time", and "it shall be as easy to withdraw as to give consent".
  • Naming a person is the harder case. Our reading: tools that name an individual depend on recognizing the visitor's browser or device, which is the kind of access Article 5(3) is about. Plan on needing consent in Europe.

In California

The California Consumer Privacy Act works differently. It is built on notice and the right to opt out. The following comes from the state attorney general's guidance.

Who it applies to. For-profit businesses that do business in California and meet any of three tests: gross annual revenue of over $25 million; buying, selling, or sharing the personal information of 100,000 or more California residents or households; or deriving 50% or more of annual revenue from selling California residents' personal information.

What it covers. Personal information is information that "identifies, relates to, or could reasonably be linked with you or your household". The attorney general's examples include internet browsing history.

What people can do.

  • They can ask a business to stop selling or sharing their personal information, "including via a user-enabled global privacy control".
  • Sharing refers to cross-context behavioral advertising, "the targeting of advertising to a consumer based on the consumer's personal information obtained from the consumer's online activity across numerous websites".
  • A business that sells or shares personal information has to offer a "Do Not Sell or Share My Personal Information" link.

Business contacts are covered. The exemptions for employment-related personal information and for personal information reflecting business-to-business transactions "expired on December 31, 2022".

Our reading: if an identification vendor keeps your visitors' data for its own database, ask whether that makes you a business that sells or shares personal information.

This section covers the CCPA only. Other US states have their own privacy laws, and other California laws can apply to website tracking. Ask a lawyer about those.

Resolving a Visit and Acting on It Are Different Steps

Knowing that a company visited is one decision. Emailing a person at that company is another. The GDPR's purpose limitation principle says personal data must be "collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes". Our reading: permission for analytics is not permission for outreach. Marketing messages also have their own rules, which vary by country.

A Practical Checklist

These are our suggestions, not legal requirements.

  1. Know what the tool reads. The IP address only, or cookies and device details as well?
  2. Know where your visitors are. Apply the stricter rule where it applies.
  3. Ask for consent where it is needed, say what it is for, and record it. A consent choice you cannot show later does not help you.
  4. Honor opt-outs and global privacy control. Automatically, not by ticket.
  5. Say what you do in your privacy notice. Including the name of the vendor.
  6. Ask the vendor what it keeps. Does it add your visitors to its own database? For how long?
  7. Do not guess on home and mobile networks. Those addresses belong to households, not companies.

How Leapio Fits

Leapio's own visitor ID is a random ID stored in a first-party cookie. It is not derived from the IP address or browser details. Because it is stored on the visitor's device, Article 5(3) applies to it.

Leapio checks consent before it resolves an anonymous visit. A visitor with explicit analytics consent, recorded by your consent banner, the API, or a stored choice, is resolved wherever they are. Without it, a region policy decides by the visitor's location. The default resolves visitors in the United States only. Visits from home internet providers and from hosting or VPN networks are not resolved. Whether you may use a resolved company for outreach is checked at the point you act, not at the point it is resolved. Leapio records the consent it is given. What your banner and privacy notice tell visitors is yours to get right. See Visitor Identification and Consent Settings.

Get Started

See Your First Events in Minutes

Free to start, no credit card. Add signals and actions when you are ready.

AI-Native Go-to-Market Analytics That Drives Revenue and Action