Company-level identification

Company-level visitor identification.

Company-level visitor identification reveals the organisation behind a visit — not the individual.

  • 50 free / month
  • No credit card
  • GDPR · EU-hosted
  • Cancel anytime
GDPR-friendlyEU · legitimate interest
EU-hostedFrankfurt + Madrid
Company-levelno PII
Pay only for medium+never for noise
One line of codelive in ~10s

What is company-level visitor identification?

It identifies the organisation behind a website visit — 'Acme GmbH' — rather than a named individual. Because it handles no personal data, it can rely on legitimate interest and stays GDPR-friendly. It's the privacy-safe foundation of B2B intent.

Company vs person

Why company-level is the safer default

Person-level identification (naming individuals) raises privacy and consent obligations, especially in the EU. Company-level gives you actionable intent — which accounts are interested — without that exposure.

Company vs person, in detail

Company-level vs person-level: what's the real difference?

The two approaches sound similar but sit on opposite sides of the privacy line. Company-level identification answers the question"which organisation is this?" — it resolves the visit to a business such as Acme GmbH, with its industry, size, location and the pages it looked at. It works from network signals (the ASN that owns the IP range and corporate reverse-DNS) and stores no information about the human at the keyboard.

Person-level identification tries to answer"who is this individual?" — putting a name, and often a work email or LinkedIn profile, against an anonymous session. To do that it has to process personal data, frequently by matching device identifiers against third-party profile databases. That is a fundamentally different activity in data-protection terms. Under GDPR a company name is not personal data, but a named contact and their email plainly are, pulling person-level tracking into consent requirements, data-subject rights, retention rules and the reputational risk of"how did they get my name?" outreach.

For B2B, the account is almost always the unit that matters anyway. Deals are won at the organisation, with multiple stakeholders researching over weeks. Knowing that a target account is reading your pricing page is the actionable signal; knowing the exact junior analyst who opened the tab rarely changes what you do next, and it carries all the compliance weight. Company-level gives you the part that drives revenue and leaves behind the part that creates risk.

Durable & GDPR-safe

Why company-level is the durable, GDPR-safe choice

Choosing company-level is not a compromise you accept to stay compliant — in B2B it is the stronger long-term foundation on every axis that matters.

What you get

What data you get per company

Every medium-or-higher match arrives enriched, so a company name turns into a profile you can act on without leaving the dashboard.

Identity & firmographics

Company name, domain, industry, employee-size band, headquarters location, founded year, LinkedIn profile and tech-stack hints — pulled automatically from public sources so you can qualify fit at a glance.

Visit behaviour

Which pages the company viewed, how often it returned and a confidence score (very_high, high, medium, low, none) on the match — the intent context that tells you whether an account is curious or seriously evaluating.

Where it goes next

Sync identified companies straight into HubSpot, Salesforce or Pipedrive with one-click OAuth, look any company up manually, and review everything in a dashboard built around accounts rather than raw hits.

Who it's for

Who company-level identification is for

Company-level identification fits any business where the buyer is an organisation rather than a consumer, and where purchases involve research before a conversation ever begins.

Related

FAQ

Questions, answered.

Is company-level identification GDPR-friendly?

Generally yes — it processes no personal data and relies on legitimate interest. Person-level identification is treated differently. Not legal advice.

Does Nalloo identify individual people?

No. Nalloo identifies companies, not people. It never stores personally identifiable information.

Is Nalloo GDPR-compliant?

Yes. Nalloo identifies companies (not natural persons), stores no personal data; IP addresses are processed hashed, inside the EU. This page is informational and not legal advice.

How many companies will I see?

Typically 8–18% of B2B traffic depending on industry and market. Corporate networks resolve best; mobile and consumer ISPs less. Start free and see your own rate.

What exactly is the difference between company-level and person-level identification?

Company-level tells you which organisation visited — Acme GmbH, its industry, size and the pages it viewed. Person-level attempts to name the individual human, often by matching against profiles or de-anonymising email identifiers. Company-level handles no personal data; person-level does, which is why the two are treated very differently under GDPR.

What data do I get for each identified company?

For every medium-or-higher match you get the company name and domain plus built-in firmographics from public sources: industry, company size, headquarters, founded year, LinkedIn and tech-stack hints — alongside the pages viewed and a confidence score. No personal contact details are included or stored.

Who is company-level identification best for?

B2B teams with considered, multi-stakeholder sales: SaaS, agencies, industrial and logistics companies whose buyers research anonymously before ever filling a form. If you sell to organisations rather than to consumers, the account is the unit that matters — and that is exactly what company-level resolves.

You're ~10 seconds from your first lead.

50 free identifications. No credit card. No"talk to sales."

EU-hosted · GDPR-friendly · Cancel in one click