How to show clients which companies visited their site, and what to tell them about accuracy and privacy
Short answer: Yes, you can show a client a list of companies that visited their site, but only some visits will be matched, and it is not a list of buyers. A visitor identification tool takes the visitor's IP address (the number that identifies their internet connection) and looks up which company it belongs to. A normal analytics report, such as the one in Google Analytics (Google's free website statistics tool), counts visits and sources but is not built to name companies. Ploy, an AI website and marketing platform, says it identifies new visitors only in the United States and only when they accept cookies. Check local privacy law before you switch any tool on.
You run a client's website and lead generation, and you want to show them which companies are looking at it without overpromising what the data can do or breaking a privacy rule.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Here is the plain answer. Company-level visitor lists are real and useful as a hint about interest. They are not a count of everyone who visited, they are sometimes wrong, and in many countries they need a consent step first. Show them to a client as "companies that looked, and which pages they read", not as "these companies are ready to buy".
This guide is for an agency that runs a client's site and wants to add a "who visited" section to its reporting. It covers what the tools can and cannot do, the privacy checks, the cost of one option, Ploy (a platform from Ploy, Inc. that builds and hosts websites and includes visitor identification), a report layout you can copy, and a test you can run before you promise anything. For the legal side in more depth, read is it legal to identify website visitors. This page is information, not legal advice.
This page may contain affiliate links from which Blur Studio earns commissions.
What visitor identification can and cannot do
There are two levels, and clients mix them up.
| Level | What you get | How it works in plain words |
|---|---|---|
| Company level | The name of an organisation, its size, industry and the pages it viewed | The tool matches the visitor's IP address to a company that owns or rents that connection |
| Person level | A name, job title and sometimes a LinkedIn link | The tool matches the visit to a person using cookies and a data provider's records |
Company level is the easier claim to defend. Person level is where most legal risk sits, and where tools are most likely to be wrong or unavailable outside one country.
What it cannot do, and what you should say to the client before they ask:
- It cannot see everyone. Visitors on a home connection, a phone network or a VPN (a service that hides the real IP address) often do not map to a company. People who refuse cookies are not matched at all by some tools.
- A match is not a buyer. A company name on a list tells you that someone on that network opened a page. It does not say who, or why.
- A match can be wrong. A shared office building, a coworking space or a company's internet provider can produce a company name that is not the real visitor. Treat the list as a lead to check, not a fact.
- No tool publishes a match rate you can rely on. Ploy's pages, for example, give no match rate. Measure it on your client's own traffic (see the test plan below).
I also would not tell a client that Google Analytics will show company names. A standard report is built around sessions, sources and events. If you want to track the things that matter, set up key events (Google's term for an action important to the business, such as a form submit) first. That is a separate job, covered in an agency client reporting template.
What Ploy states about its own visitor identification
Ploy is a good example because it publishes its limits. As of November 2026, its docs and feature pages say:
- It shows, for each identified visitor, the company, and when available the name, job title, LinkedIn (the professional network) link, visit count and pages viewed (docs, last updated October 21, 2026).
- Each identification uses one visitor-enrichment credit. These are separate from AI credits. Starter includes 50 a month, Pro 1,000 a month, and Enterprise a custom amount. The Free plan includes none.
- Only visitors who accept cookies, or visitors on sites that report no choice, are identified. Visitors who refuse through your cookie banner are never matched.
- For net-new anonymous visitors, identification covers the United States only. For visitors in the EU and UK, Ploy says it does not collect or share net-new anonymous visitor data. Do not promise a European client that this works for European traffic.
- You can turn it off for a workspace under Settings, then Enrichments, or for one site in its Visitors tab.
- Ploy does not add a cookie banner. You need your own consent tool and privacy policy, and you are responsible for the rules in your region.
Prices as of November 2026: Starter is $50 a month (or $480 a year), Pro is $300 a month (or $2,880 a year). Check Ploy's pricing page for the current figures. For the full plan comparison, see Ploy pricing explained.
Two limits matter for agencies. First, the visitor lists live inside Ploy's own product, and the docs describe them for sites published on Ploy. Ploy's analytics docs also describe a snippet for sites Ploy does not host, but whether visitor identification works through that snippet is not stated, so ask Ploy before you plan around it. Second, syncing identified visitors to a customer relationship manager (CRM, the system a sales team uses to track leads) such as HubSpot or Attio (two widely used CRM products) needs the Pro plan, per Ploy's integrations page.
Other tools exist. RB2B (a US visitor identification tool) and Leadinfo (a European one) are two that publish their own privacy positions, and each says something different about Europe. Compare vendors on four things: where their identification works, what they need before a match (consent or not), what a match costs, and what the agreement says about who is responsible. Read each vendor's own page, because they change.
Privacy checks before you switch it on
Separate three layers, because clients mix them up. This is information, not legal advice. Check local law.
- Device access (cookies and similar). In the UK and EU, storing or reading information on a visitor's device generally needs consent unless an exception applies. UK rules on this (PECR, the Privacy and Electronic Communications Regulations) were changed in February 2026, so check the current text on the regulator's site.
- Lawful basis for using the data. Under GDPR (the EU's data protection law, copied into UK law), you need a reason to process personal data. An IP address can count as personal data. Some vendors rely on "legitimate interests" for company-level data and say it is lower risk. Others disagree. Record which position your tool takes, and let the client's lawyer decide.
- US notice and opt-out. The California Consumer Privacy Act (CCPA, California's privacy law) is a good example. California's attorney general says people can opt out of the sale or sharing of their personal information, including through a global privacy control (a browser setting that tells every site "do not sell or share my data"). Businesses must respond to an opt-out within 15 business days. The law applies to businesses above set limits, for example $26,625,000 in annual revenue (the inflation-adjusted figure in use since January 2025) or 100,000 California residents or households (page updated August 28, 2026). Many other US states have their own laws. See whether visitor tracking is allowed under privacy law.
Then there is what happens after the match. If the client emails or calls from the list, email rules apply. In the US, the CAN-SPAM Act (the federal law on commercial email) has no exception for business-to-business email, according to the FTC (Federal Trade Commission, the US consumer protection regulator). In the UK and Canada, rules differ by whether the recipient is a company or a sole trader. See cold email and outreach laws. Ploy's own page on this is Ploy visitor identification and outreach.
Copy-ready privacy checklist for each client
- Where do the client's visitors live? If a large share is in the UK or EU, expect company matching to be limited or off there.
- Is there a cookie banner that actually blocks the tool until the visitor accepts?
- Does the banner send the visitor's choice to the tool (for Ploy, a call to
window.ploy.consent)? - Does the privacy policy name the tool, what it collects, why, and how to opt out?
- Do you have the vendor's data processing agreement (DPA, the contract that says how a vendor handles personal data for you)? Ploy's enterprise page says its standard DPA is available on request, and there is no public DPA link, so ask for it.
- Is the global privacy control honoured? Ploy's feature page says Do Not Track and global privacy control are honoured.
- Who owns the account, you or the client? Put it in writing (see contracts between agencies and clients).
- Is there a way to switch it off in one step if the client asks?
- Has someone on the client side, or their lawyer, signed off in writing?
What to put in the client report
Keep it to one page. Sort by interest, not by company size.
| Column | What to show | Why |
|---|---|---|
| Company | Name and industry | The headline |
| Pages viewed | Pricing, services, contact, case studies | Shows what they cared about |
| Visits this month | A number | Repeat visits are a stronger sign than one |
| Already a contact? | Yes or no, from the client's CRM | Stops the client chasing a customer |
| Next step | Call, email, ignore, or watch | Turns a list into an action |
Add two summary lines at the top: how many visits were matched out of all visits, and how many matched companies were new to the client. Those two numbers are what a client will actually use.
Here is wording you can paste into the report: "These are companies whose network visited your site and accepted cookies. A company appearing here does not mean the decision maker visited. Matches are estimates and are limited by location and consent. We check each lead before anyone contacts it."
A worked example (made-up numbers)
Say a client sells software to US accounting firms. In one month their site gets 2,400 visits.
- Of those, 1,700 are from US visitors who accepted cookies. The rest are non-US visitors or people who refused.
- The tool matches 420 of the 1,700 to a company. That is a 25 percent match rate on eligible visits, and 17.5 percent of all visits. (Made-up figures, not typical.)
- Those 420 matches belong to 190 distinct companies.
- You filter to companies that viewed pricing or contact: 38 companies.
- You compare with the client's CRM: 9 are already customers, 6 are open deals, 23 are new.
The report says: "23 new companies looked at pricing or contact this month." That is useful and honest. Now the cost check. If the plan allows 50 identifications a month, you hit the cap at 50 matches, so most of the 420 would not be shown. With a Pro-sized allowance of 1,000 a month, all 420 fit. Count your credits before you promise a list. Credits do not roll over, per Ploy's docs.
Test plan with pass and fail rules
Run this for 30 days on one client before you add it to any contract.
- Week 1. Turn it on for one client with the banner wired up. Record total visits and matched visits. Pass: the banner blocks matching when you click Reject in a test browser. Fail: any match appears for a rejected test visit.
- Week 2. Take 20 matched companies and check them against the client's form fills and CRM. Pass: at least 14 of 20 look plausible (a company in the client's market, a role that fits). Fail: fewer than 14, which means the tool is mostly noise for this client.
- Week 3. Send the first report to the client with the accuracy wording. Pass: the client picks at least 3 companies to follow up.
- Week 4. Count credits used against your plan. Pass: you finished under the cap. Fail: you ran out, so price the next tier into the retainer.
The 14 of 20 line is my own rule of thumb, not a published benchmark. Change it if your client's market makes it too strict.
Who should skip this
- Clients whose traffic is mostly outside the United States, especially the EU and UK, when the tool is US only.
- Consumer businesses with few repeat business visitors, where company names add little.
- Clients with a small number of visits a month. Fifty identifications is plenty for a quiet site, but you will not find many leads in 200 visits.
- Any client whose lawyer is not comfortable. A nice report is not worth a complaint.
- Sensitive sectors such as health or children's services. Do not use visitor identification there without legal advice.
How I'd approach this
I would sell this as a small add-on, not as a headline promise. Pick one client with US B2B traffic, a working cookie banner and a CRM, and run the 30-day test above. Charge for the reporting and the follow-up work, not for the names.
Here is a first-week plan. Day 1: check where the client's visitors live in their analytics. Day 2: read the tool's own privacy and consent pages and your client's cookie banner settings. Day 3: write the privacy checklist answers and get a yes or no from the client. Day 4: switch the tool on for that one site. Day 5: test accept and reject in two browsers. Decision rule: if you cannot prove that rejected visitors are not matched, do not show a single company to the client.
If you want to try the tool the article uses as its example, you can start with Ploy and check its visitor pages against your own client's traffic, and read Ploy for agencies for the multi-client setup. For a wider view of the options, see how to follow up with companies that read your pricing page. If you want a custom version, with AI agents that use your business knowledge, connect to your CRM and calendar, and come with ongoing care, Blur Studio builds that, and you can see what it includes.
For a closer look, see lead scoring and follow-up rules for a small agency.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Can Google Analytics show which companies visit a website?
A standard Google Analytics report is built around sessions, sources and events, not named companies. If you want company names, you need a separate visitor identification tool. For what to track in the report itself, see an agency client reporting template.
Is it legal to identify which companies visit a website?
It depends on where the visitor is, what the tool collects, whether the visitor agreed, and what you do afterwards. There is no blanket yes or no. This page is information, not legal advice. See is it legal to identify website visitors and ask a privacy lawyer.
Does Ploy visitor identification work outside the United States?
Per Ploy's own pages as of November 2026, net-new identification covers the United States only. For visitors in the EU and UK, Ploy says it does not collect or share net-new anonymous visitor data. Do not promise it for European traffic.
How many visitors can be matched to a company?
No vendor figure should be trusted blindly. Ploy's pages give no match rate. Measure it on the client's own traffic with the 30-day test above, and report matched visits as a share of all visits.
How much does Ploy visitor identification cost?
Each identification uses one enrichment credit. As of November 2026 Starter ($50 a month) includes 50 a month and Pro ($300 a month) includes 1,000. Free includes none. Check Ploy's pricing page for current figures.
Can I show a client names of individual people?
Some tools show names and job titles when they can match a person, but this carries more legal risk and is less likely to be available outside the US. Start with company-level data, and only add people when the client's lawyer agrees and the visitor has consented.
What should I tell a client about accuracy?
Say that matches are estimates, that not every visit can be matched, that people who refuse cookies are not matched, and that a company appearing on the list does not mean a buyer visited. Use the wording in the report section above.
Do I need a cookie banner?
In most cases where visitors from the UK or EU are involved, yes, and many US states and clients expect one as well. Ploy does not add a banner for you. You need your own consent tool, wired so that a refusal stops matching. See cookie banners and consent for marketing sites.
More in this topic: Websites: client reporting, leads and ads for agencies (8 guides) →
Sources
- Visitor Identification (Ploy docs)
- Analytics and cookie consent (Ploy docs)
- Ploy pricing (Ploy)
- Ploy for agencies (Ploy docs)
- Integrations (Ploy docs)
- California Consumer Privacy Act (California Attorney General)
- About key events (Google Analytics Help)
- RB2B GDPR page (RB2B)
- Visitor identification on B2B websites and GDPR (Leadinfo)