# Can I See Who Visited My Website? What You Can Know > Can you see who visited your website? Analytics shows counts, sources and countries, not names. Here is what you can see, what you can't, and how to learn more. Canonical: https://indiehacker.studio/blog/can-i-see-who-visited-my-website [Analytics](https://indiehacker.studio/blog/category/analytics) Nemo · October 30, 2026 · 6 min read Can you see who visited your website? Partly. Any analytics tool shows how many people came, which pages they read, where they came from and roughly which country and device they used. It does not show names or emails. You learn who a visitor is only when they tell you: by signing in, filling a form or starting a chat. That gap is where most founders get stuck, so this guide covers what each method can show, what it can’t, what the law allows, and a short setup for a small app. A note on bias: we make Indiehacker Studio, a tool for this; the method works with any tool. Nothing here is legal advice. ## Why can’t you just see who visited? Say you open your dashboard after a launch and see 300 visitors and 4 signups. The other 296 are just a number. You can’t email them, you don’t know what they wanted, and you can’t tell whether they left because of the price, a bug or a missing feature. The web was built that way. A browser sends a page request with an IP address, a user agent and a referrer. None of these names a person. An IP address points to a network, often a phone carrier or an office that many people share. Unless the visitor gives you something more, the request stays anonymous. The cost of guessing is real for a small app. With no idea who left or why, you tend to change the wrong thing: rewrite the landing page when the problem was a broken signup form, or cut the price when people just didn’t understand the product. ## What can you see about website visitors? Here is what common methods show. The left column is what a typical analytics script collects; the rest needs the visitor to act. | Method | What you see | Names or emails? | |---|---|---| | Analytics script | Visitors, pageviews, top pages, referrers, UTM campaigns, countries, devices, browsers | No | | Server logs | Every request with IP, path and user agent, plus lots of bots | No | | Signed-in users (identify) | Which account viewed which page | Yes, your own users | | Forms and signups | The email the visitor typed | Yes, if they submit | | Live chat | The question, the page they were on, the email they leave | Yes, if they write | | B2B IP lookup tools | A company name guessed from the network | Company only, and often wrong | So the honest answer has two parts. For anonymous visitors you see patterns, not people. For visitors who sign in or write to you, you can see exactly who they are. ## How do you see which pages people visited? Install an analytics script. It sends a small record on each page load, and the dashboard turns those into reports. For a small app, a few reports answer most questions: - **Live visitors:** who is on the site right now, useful on launch day. - **Top pages:** where people land and what they read. - **Referrers and UTM campaigns:** which post, directory or ad sent them. - **Countries and devices:** who your audience is and what to test on. - **Custom events:** how many reached a signup or a checkout. Our [website visitor tracking](https://indiehacker.studio/blog/website-visitor-tracking) guide covers which numbers matter, and [what is web analytics](https://indiehacker.studio/blog/what-is-web-analytics) explains how the reports are built. ## How do you find out who a visitor is? Give them a reason to tell you. Three ways work for small apps: 1. **Identify signed-in users.** When someone logs in, your app already knows their account. Pass that id to your analytics so their visits show up under their name. With Indiehacker Studio it is one line: `window.ihs?.identify({ id: "user_123", email: "a@b.com", name: "Ana" })`. 2. **Offer a chat bubble.** A visitor who is confused or curious will often ask. You see the question, the page they were on, their country and device, and the email they leave so you can reply later. 3. **Ask at the right moment.** A feedback or bug report button on the page where people get stuck gets more answers than a survey sent a week later. None of these track anyone in secret. The visitor chooses to sign in or to write, which is also why the data is useful: it comes with context. ## Is it legal to see who visits your website? Counting visits is legal almost everywhere. What you store is where the rules start. - **Cookies and device storage** in the EU and UK fall under ePrivacy rules, which often require consent. - **Personal data** such as IP addresses, emails and account ids falls under GDPR and similar laws. Collect what you need, keep it for as long as you need it, and say what you collect in your [privacy policy](https://indiehacker.studio/privacy). - **Fingerprinting** a visitor to identify them without asking is the method to avoid. EU guidance treats it like cookies, and visitors don’t expect it. A tool that sets no cookies and stores no IP reduces what you have to cover. It does not remove the duty to describe what you collect. See [Google Analytics and GDPR](https://indiehacker.studio/blog/google-analytics-gdpr) for the common cases and [what is cookieless tracking](https://indiehacker.studio/blog/what-is-cookieless-tracking) for how cookieless counting works. ## How do you set this up on a small app? With Indiehacker Studio, analytics, the chat bubble, feedback and bug reports come from the same script: 1. [Create a free account](https://indiehacker.studio/signup) and add a project with your domain. 2. Paste one line before `` on every page: ``` ``` 1. Verify the domain from the dashboard (a link, a meta tag or a DNS record). 2. Call `identify` after sign-in so signed-in visits and chats carry the user’s name. The script sets no cookies and stores no IP address. It keeps a random id in the browser’s local storage to count unique visitors, and it tracks route changes in single-page apps. It has no heatmaps and no session replay. When a visitor writes in the bubble, the inbox shows their current page, country, device, first and last seen, and past threads next to the message. ## Frequently asked questions ### Can I see the names of people who visit my website? Not from analytics alone. You see a name when the visitor signs in and your app identifies them, fills a form, or leaves their email in a chat. ### Can I see who visited my website for free? Yes, as counts and sources. Several tools have free tiers. Indiehacker Studio Free covers 1 project, 10,000 pageviews and 50 conversations a month. ### Can I see a visitor’s IP address? Your server logs record it. Many privacy-friendly analytics tools drop it on purpose. An IP rarely names a person anyway, since many people share one network. ### Do IP lookup tools tell me which company visited? Some B2B tools match IP addresses to company names. Results are often wrong for home and mobile networks, and they never give you the person. ### Can I see who visited a specific page? You can see how many visited it and where they came from. For signed-in users you identified, you can see which of them opened it. ## Try Indiehacker Studio See your visitors on every app you run, and talk to the ones who want to talk, from one dashboard. Free covers one project; Pro is $12 a month for up to 50 projects, with a 7-day trial. See [pricing](https://indiehacker.studio/#pricing). Your next step: add the script to one site, call `identify` after sign-in, and open the inbox the next time someone writes. [Start for free](https://indiehacker.studio/signup) **About this article.** Written by Nemo, who builds Indiehacker Studio: analytics, support chat, feedback and Stripe revenue for every app you run, from one script. Spotted something wrong or out of date? Write to [support@indiehacker.studio](mailto:support@indiehacker.studio). ## One script. Every project. [Start free](https://indiehacker.studio/signup) More in Analytics [ANALYTICS](https://indiehacker.studio/blog/category/analytics) Nov 3, 2026 · 6 min ## [PostHog Alternative for Indie Founders: 4 Lighter Options](https://indiehacker.studio/blog/posthog-alternative) A PostHog alternative for indie founders who only need traffic, support and MRR: Indiehacker Studio, Plausible, Umami and Mixpanel compared on price and scope. [ANALYTICS](https://indiehacker.studio/blog/category/analytics) Oct 26, 2026 · 6 min ## [Fathom Analytics Alternative: 4 Options for Indie Apps](https://indiehacker.studio/blog/fathom-analytics-alternative) A Fathom Analytics alternative for indie founders: Plausible, Umami, Cloudflare and Indiehacker Studio compared on price, limits and what each adds. [ANALYTICS](https://indiehacker.studio/blog/category/analytics) Oct 23, 2026 · 6 min ## [Web Analytics: What It Is and What to Measure](https://indiehacker.studio/blog/what-is-web-analytics) Web analytics explained for founders of small sites: what it measures, how tracking works, which metrics matter and how to pick a tool without a data team.