How Can You See Who Visits Your Website?
How can you see who visits your website? The honest answer has two halves. You can see a great deal about your visitors as a group: how many came, where they came from, which pages they read, and where they left. You usually can't see a named person, unless that person tells you who they are or a tool you've set up matches them to a record, and even then the match is partial and depends on privacy rules.
This guide explains the difference. It covers the seven things "who visits your website" can mean, what ordinary analytics tools show and don't show, how company identification works and where it breaks down, how to see what visitors do on a page, and how to turn all of that into leads. It also covers the privacy rules that shape what you can collect, and the mistakes that lead people to trust the wrong numbers.
Episode is a platform for building, publishing, and measuring campaign pages. Pages published with Episode come with their own analytics, and Episode's visitor identification matches visitor signals with company data to show which organizations engage with those pages.
What does it mean to see who visits your website?
The search covers more ground than it first appears, because "who visits" can mean a count, a behavior, a source, a company, or a person. Tools that answer one of these questions often can't answer the others, which is why so much advice on this topic feels contradictory. This section separates the seven meanings, so you can tell which one you're after.
a. Aggregate visitor analytics
This is the count and the shape of your traffic: how many people visited, how many pages they viewed, which devices they used, and how the numbers change from week to week. It describes the crowd, not any individual in it. Google Analytics, a site builder's built-in statistics, and most hosting dashboards work at this level.
b. Visitor behavior
Behavior is what people do once they arrive: which pages they open, how far they scroll, what they click, and where they stop. Analytics events, funnel reports, heatmaps, and session recordings all sit here. You learn how visitors act without learning their names.
c. Traffic sources and campaign attribution
This answers "where did they come from?" The answer might be a Google search, an email, a paid ad, or another site. Source, medium, and campaign tags such as UTM parameters connect a visit to the marketing activity behind it, and Search Console adds the searches that led people to your pages.
d. Company-level identification
Some business tools try to associate a visit with an organization, usually by matching network information to a database of companies. The result is a company name and some business details. It is a guess about the organization, and it says nothing about which employee visited.
e. Individual identification
This means learning a visitor's name, email address, or contact details. A website owner doesn't get this from a visit alone. It becomes possible when the visitor volunteers the information, or when a specialist tool matches the visit to a person, which depends on the data that tool holds and the rules that apply where the visitor lives.
f. Known visitors and first-party data
Some visitors identify themselves. They fill in a form, sign in, subscribe, or reply to a campaign. Once that happens, you can connect their later activity to the record you hold, as long as you've told them you'll do so and have a lawful basis for it.
g. Lead generation
Lead generation is the use of everything above to decide who to follow up with and how. A form submission is the clearest signal. Company-level activity and repeat visits can add context, but they're hints and not proof of interest.
h. How the seven meanings compare
The table puts the meanings side by side, so you can match each question to the right kind of tool.
| What you want to know | What it can reveal | Typical tools | Main limit |
|---|---|---|---|
| How many people visit | Counts, trends, devices, locations | Web analytics, site builder statistics | Describes groups, not people |
| What visitors do | Pages, clicks, scrolling, drop-off | Analytics events, heatmaps, recordings | Doesn't say who they are |
| Where they come from | Source, medium, campaign, search queries | Analytics, Search Console, UTM tags | Some visits arrive with no source information |
| Which company visited | A likely organization and its business details | Company-identification tools | A match is a likelihood, not a certainty |
| Which person visited | A name or email in limited cases | Forms, sign-ins, some specialist tools | Partial coverage and strict privacy rules |
| Which leads came from the site | Submissions and their source | Forms, CRM, page analytics | Needs working tracking and follow-up |
Can you see exactly who visits your website?
Usually not, if "exactly who" means names. The practical answer to how can you see who visits your website depends on whether you're asking about the crowd, a company, or a person, and the answers get less certain in that order. This section explains what ordinary tools show, what they leave out, and the circumstances in which you can know more.
a. What ordinary analytics show
Standard web analytics gives you volume, sources, pages, devices, and rough locations, all grouped. Google Analytics, for example, offers a Realtime report that shows activity on your site as it happens, including active users over the last 30 minutes, the sources they came from, and the pages they're viewing. It tells you what is happening, and not who is doing it.
b. What they leave out
Analytics tools measure visits with identifiers that aren't tied to a name. Google Analytics 4 states that it doesn't log or store IP addresses, and Google's policy asks site owners not to send it anything it could recognize as personally identifiable information, such as email addresses, names, or fine-grained location. That policy also warns that URL paths, URL parameters, and page titles can leak personal data by accident.
So if you open Google Analytics hoping to see a list of names, you won't find one, and that is by design.
c. When you can know who someone is
A visitor becomes known when they give you their details. A contact form, a newsletter sign-up, a login, or a link in an email that carries a campaign tag all let you connect activity to a person you already hold a record for.
Google Analytics allows this for signed-in users through User-ID, which lets you attach your own identifier to a person's activity across sessions and devices. The identifier must not contain information that a third party could use to work out who the person is, and you need to disclose its use in your privacy policy.
d. What an IP address does and doesn't tell you
An IP address is the network address a visitor's connection uses. It can point to a region, an internet provider, or sometimes an organization, but it doesn't contain a name. Many people share one address, such as everyone in an office, a household, or behind a VPN, and many addresses belong to internet providers and not to the company where the person works.
That doesn't make IP addresses harmless. The EU's GDPR says in Recital 30 that people can be linked to online identifiers such as IP addresses and cookies, and that these can be combined with other data to profile and identify them. In legal terms, an IP address can count as personal data even when it doesn't tell you a name.
e. Observed, inferred, and unknown
It helps to sort every piece of visitor information into one of three groups.
| Type | Meaning | Example |
|---|---|---|
| Observed | The tool recorded it directly | A page view, a click, a form submission |
| Inferred | The tool estimated it from other data | A company name matched from network information, a rough location |
| Unknown | Nothing in the data establishes it | Who the person is, why they visited, whether they'll buy |
Treat inferred data as a lead to check and not as a fact. Most mistakes in this area come from treating an inference as an observation.
How can you see who visits your website using analytics tools?
Analytics tools can't give you names, but they answer most of the questions that help you improve a site. This section covers the main tools, what each one shows, and how to read the results. So how can you see who visits your website in practice? Most people get what they need from the first three.
1. Google Analytics for visits, sources, and behavior
Install Google Analytics on your site, then use the reports to see how many people visit, which pages they view, and how they arrive. To watch current activity, sign in, select Reports in the left menu, and open Realtime.
For where traffic comes from, Google Analytics groups visits by dimensions such as source, medium, and default channel group, which tell you whether people arrived from search, email, social, paid ads, or a direct visit. Compare these over weeks, and don't draw conclusions from a single day.
2. Search Console for the searches that bring people in
Google Search Console shows how your site performs in Google Search. Its performance report gives you clicks, impressions, click-through rate, and average position, and you can group the data by query, page, country, or device.
This is the closest you'll get to knowing what visitors wanted before they arrived. It's grouped data, so you see the searches and not the people who typed them. Our guide on what AI can and cannot manage in SEO explains how to act on this data.
3. Tags and campaign links for marketing attribution
Add UTM parameters to the links in your emails, ads, and social posts, so each visit carries its campaign, source, and medium. Without them, a lot of traffic lands in a "direct" bucket, which hides what worked.
Keep the tags free of personal data. Don't put an email address or a name in a link, because link parameters end up in your analytics reports, where Google's policy prohibits personal data.
4. Your site builder or hosting statistics
Many website builders and hosts include basic traffic statistics. They're useful for a quick check, but they count things in their own way, so numbers rarely match Google Analytics exactly. Find out what your platform counts as a visit before you compare figures, and treat any "who visited" feature with care. If it shows more than counts and sources, ask how it knows.
5. Consent and configuration
What you can measure depends on your setup and on your visitors' choices. In the UK, the Information Commissioner's Office says that consent for non-essential cookies must be actively and clearly given, and that the cookie rules apply to all cookies, including those used for anonymous data. That page reflects an earlier version of the guidance, and the ICO has been consulting on a revision, so check the current version for your situation.
When visitors decline cookies, your analytics may show fewer of them. This is one reason traffic numbers are estimates and not exact counts.
How to identify companies visiting your website
When the visitors you care about are businesses, how can you see who visits your website at the company level? Company identification tools try to tell you which businesses are visiting. They can help a sales team prioritize, but their output is a likelihood, and treating it as certain causes trouble. This section explains how the tools work in general terms, what they return, and where the results fall short.
a. How company identification works
Most tools match network information, such as the visitor's IP address, against a database of organizations. When the address belongs to a company's network, the tool can return that company's name and business details. Some vendors combine this with other signals.
Vendors describe their methods differently, and the details change, so ask any vendor how its matching works and what data it uses.
b. What you can learn
A match typically gives you a company name and business details such as industry, size, and location. Alongside that, you can see which pages the company's visitors viewed, how often they came back, and how long they stayed. That is useful context when you're deciding which accounts to contact first.
c. Where the results break down
Matching is least reliable in the situations that are now common:
- People working from home reach the internet through a residential provider, which says nothing about their employer.
- Mobile connections often share addresses among many users.
- VPNs and cloud services hide the visitor's real network.
- Large organizations can route many offices through one address.
Vendors' own claims about how many visits they can identify usually come without independent evidence, so ask any provider to show results on your traffic before you decide.
d. A company is not a person
A company match tells you an organization was probably involved. It doesn't tell you who, or whether that person has any buying authority. A company viewing a product page could be a prospect, a competitor, a student, or a recruiter. Use the signal to start a sensible conversation and not to assume interest.
e. Privacy and the legal basis
Company-level and person-level matching raise different privacy questions, and the rules differ by country. An IP address can be personal data under GDPR, so treat anything you collect as something you must be able to justify. Check which rules apply to your visitors, tell them what you collect in your privacy policy, and get advice from someone qualified if you're unsure.
How to find out what visitors do on your website
Behavior data shows you where a page works and where it loses people, without needing to know who anyone is. This section covers the main ways to see it and the care each one needs.
a. Events and key actions
Analytics events record specific actions, such as clicking a button, starting a form, or submitting it. Decide which actions matter, mark the most important ones as conversions, and check that each one records correctly before you rely on it.
b. Funnels and drop-off
A funnel lists the steps toward a goal, such as visiting a page, reaching the form, starting it, and submitting it. The step with the biggest fall shows you where to look first. A big drop between "reached the form" and "started the form" suggests the form is intimidating or the offer isn't clear enough. A big drop after "started" points to the form itself.
c. Heatmaps
A heatmap shows where visitors click and how far they scroll. It helps you see whether people reach your call to action and whether they click things that aren't links. Use enough sessions before you read patterns into one, and check them across different devices.
d. Session recordings
Recordings replay individual visits as a sequence of movements and clicks. They're good for spotting confusion that numbers hide, such as someone repeatedly clicking an image that isn't clickable. They also raise more privacy questions, because they can capture what people type. Mask form fields and sensitive pages, and make sure your privacy notice covers recording.
e. Privacy care for behavior data
Behavior data can include personal data by accident. Page titles, URLs, and form entries sometimes carry names or emails, and Google's policy specifically warns about this. Review what each tool collects, switch off anything you don't need, and record why you collect the rest.
How to use website visitor data to generate leads
Visitor data helps with leads when you use it to improve the path from a visit to a conversation. This section covers six ways to do that, starting with the ones that rely on the firmest evidence.
a. Fix the path from visit to form
Start with the funnel. If many visitors reach a page and few start the form, improve the page, the offer, or the form before you spend more on traffic. Our guide on how to optimize landing pages for lead generation covers the changes that usually matter most.
b. Match content to where visitors came from
Look at the traffic sources that send the most visits and the fewest leads. A page that suits visitors from a search for a specific problem may not suit visitors from a broad social post. Writing a version for each source is often more useful than adjusting one page for everyone.
c. Build pages for the searches you already attract
Search Console shows queries that bring impressions but few clicks, and queries where the wrong page ranks. Each is a prompt to build or improve a page for that search.
d. Follow up on known contacts
When someone submits a form or replies to a campaign, you know who they are and what they asked for. Use that context, such as the page they used and the offer they chose, to make your follow-up relevant. Only contact people in ways your privacy notice and local rules allow.
e. Treat account signals as prompts
If a tool shows that people from a target company viewed several pages, that's a reason to look more closely. It isn't a promise they want to buy. Check the signal against what you know about the account before you contact anyone. Our guide on ABM landing pages explains how to build pages around account-level interest.
f. Measure leads as well as visits
A page with fewer visits and more leads can be doing better than a page with more visits and none. Count form submissions, then check how many of those leads your sales team considers worth pursuing. Our guide on landing page metrics to track covers the measures worth watching.
How Episode helps marketers turn website insights into results
Episode helps with the part of this problem that starts after you've decided what to publish: finding the searches worth targeting, building the pages, measuring how they perform, and seeing which companies engage with them. This section covers each piece, and says clearly where another tool is still needed. For pages built with Episode, how can you see who visits your website is partly answered by Episode itself, and partly by a separate analytics tool for the rest of your site.
1. Finding the searches worth a page
What it does: When you connect Search Console, Episode shows the searches that already earn impressions and clicks, flags queries where you rank but get few clicks, and flags topics where the wrong page ranks. You can turn an opportunity into a brief, a single page, or a connected set of pages.
How it helps: It starts you from the demand your site already attracts, which is firmer evidence than guessing at topics.
What you still need: Your own judgment about which opportunities fit your business. A search opportunity is a starting point and not a promise of traffic.
2. Building and publishing the pages
What it does: You describe a campaign and add your company URL, and Episode builds a page with copy, layout, and design drawn from your brand. You edit it in a no-code Studio, and teammates review it through review links, comments, and approvals before it goes live.
How it helps: The gap between "we should have a page for this" and "it's live" gets shorter. Our guide on how to create a landing page that converts explains what to put on it.
What you still need: Your offer, your proof, and a careful read of anything an AI drafted.
3. Seeing how each page performs
What it does: Analytics start when a page goes live, with no tags to install. Episode shows visitors, sessions, sources, devices, locations, and referring pages, along with scroll depth, clicks, section engagement, and time on page. You define the conversion, such as a form submission or a button click, and Episode reports conversions and conversion rate. It also offers funnels, UTM comparison, form stages (reached, started, and submitted), and heatmaps, which depend on your plan.
How it helps: You see which pages draw the right traffic and which convert, next to the page that earned the result.
What you still need: Analytics for the rest of your website. Episode's analytics cover the pages published with Episode and not your whole site or sales pipeline, so keep Google Analytics or a similar tool for the rest.
4. Seeing which companies engage
What it does: Episode's visitor identification matches available visitor signals with company data to identify the organizations engaging with your pages, including visitors who never fill in a form. For each account, you can see which pages they visited, how often they returned, what held their attention, and whether interest is rising. You can match visits against a target account list, filter by industry or size, and see the campaign and channel that brought them in. Signals can go to HubSpot, Salesforce, Slack, or Zapier, and your team chooses which matches are sent.
How it helps: A sales or marketing team can see which accounts are engaging with a campaign page and follow up with context.
What you still need: Judgment about what a company-level signal means. It is a likelihood, as the earlier section explained.
5. What about individual people?
What it does: Person-level matching is narrower than company matching. It is available for a smaller share of visitors, depending on the data and the visitor's region. Where a match exists, it can show a name, role, work email, and LinkedIn profile.
How it helps: For the visitors it can match, it saves research time before outreach.
What you still need: A careful look at the rules. Many visitors won't be matched at all, and what you're allowed to do with a match depends on where the visitor lives and on your consent and notice practices. Check with your legal adviser and with the Episode team how consent and data handling work for your audience before you use person-level data in outreach.
6. What Episode doesn't do
Episode isn't a replacement for Google Analytics across a whole website, a consent-management tool, or a CRM. It doesn't tell you the identity of every visitor, and it doesn't score leads or run your sales follow-up. For visitors it can't match, the picture stays aggregate, which is how it should be.
7. Which tool answers which question
The table maps common questions to the kind of tool that answers them.
| Question | Where to look |
|---|---|
| How many people visit my whole site? | Web analytics such as Google Analytics |
| What searches bring people to my pages? | Search Console, or Episode's search opportunities |
| How do visitors behave on a campaign page? | Episode's page analytics and heatmaps, or another analytics tool |
| Which companies engage with my campaign pages? | Episode's visitor identification, or a dedicated company-identification tool |
| Who submitted a form? | Your form tool and CRM, including forms connected to Episode pages |
| Which leads turn into customers? | Your CRM |
Common mistakes when tracking website visitors
How can you see who visits your website without fooling yourself? Most mistakes come from asking a tool a question it can't answer, or from trusting a number without checking where it came from. This section covers eight of them, with what to do instead.
a. Assuming analytics reveals every visitor's identity
Standard analytics shows groups. If someone tells you a free tool lists the names of everyone who visits, ask how it could know. Without a form, a sign-in, or a specialist match, it can't.
b. Confusing company identification with personal identification
A company match says an organization was probably involved. It doesn't say which person visited. Keep the two separate in your reports and in how you talk to prospects.
c. Treating inferred data as certain
Locations, company names, and device types are often estimates. Label them as such, and check them before acting on them.
d. Drawing conclusions from incomplete traffic data
Consent choices, browser settings, ad blockers, and tracking gaps mean your numbers undercount. A drop in visitors might be a consent banner change and not a drop in interest. Check your setup before you panic.
e. Collecting personal information without checking the rules
Collecting more than you need creates legal and trust risks. Find out which laws apply to your visitors, and record your legal basis for each type of data.
f. Installing tools without checking configuration
A tag that fires twice doubles your numbers, and a form event that never fires hides your conversions. Test every tag and event, and recheck after site changes.
g. Collecting data without a clear purpose
Every metric should answer a question you intend to act on. If nobody uses a report, stop collecting the data behind it.
h. Focusing on visitor volume instead of outcomes
More visitors don't help if none become leads. Track form submissions and lead quality alongside traffic.
Frequently asked questions about seeing who visits your website
These are questions people often ask about seeing website visitors. Each answer is short and points to the section with more detail.
a. Can website owners see individual visitors?
Not by name, using ordinary analytics. You can see grouped data and, with the right setup, activity from people who have identified themselves through a form or sign-in. Some specialist tools match a minority of visits to people, and the rules for that vary by region.
b. Does Google Analytics show visitor names?
No. Google's policy prohibits sending it data it could recognize as personally identifiable information, and Google Analytics 4 doesn't log or store IP addresses. It reports on groups and on pseudonymous activity.
c. Can an IP address identify a person?
An IP address doesn't contain a name, and many people can share one. Under GDPR, it can still count as personal data because it can be linked to a person when combined with other information.
d. Can businesses identify companies visiting their websites?
Often, but not always. Tools that match network information to company databases can identify some visiting organizations, and they struggle with remote workers, mobile connections, and VPNs.
e. How can you see who visits your website for free?
Google Analytics and Search Console are free to use and show grouped traffic, sources, and search queries. Your website platform may also include basic statistics.
f. Can I see who is on my website right now?
You can see how many people are active and what they're viewing. Google Analytics has a Realtime report under Reports that shows active users over the last 30 minutes, the sources they came from, and the pages they're on. It doesn't show names.
g. Do I need consent to track visitors?
It depends on where your visitors are and what you collect. In the UK, the Information Commissioner's Office says consent for non-essential cookies must be actively and clearly given. Other regions have different rules, so check the ones that apply to your audience.
h. How can I tell which pages produce leads?
Set a conversion for your form or button, then compare conversions by page and by source. Check lead quality in your CRM as well as the count.
Conclusion
How can you see who visits your website? The question has a clear answer once you separate the parts. Analytics can tell you a lot about traffic, sources, and behavior. Company identification can suggest which organizations are engaging, with real limits on accuracy. Identifying a named person is possible only in limited cases, and it depends on what the visitor shares, what the tool holds, and the privacy rules that apply.
A practical next step depends on what you want. To measure traffic, set up Google Analytics and Search Console properly. To understand behavior, add funnels and heatmaps. To see which accounts engage, choose a company-identification tool and check its privacy position. To turn search demand into leads, start from the searches you already attract. Episode helps with that last part: it shows search opportunities, builds and publishes the pages, reports on how they perform, and shows which companies engage with them. To see how it works, take a look at Episode's visitor identification and page analytics.