Live Visitors for Agencies and Client Sites
Updated
TL;DR
For an agency, whoisbrowsing is one script tag per client site: each site gets its own live view, so you can show a client their visitors moving on their real pages during a call, with no recordings stored. It is free, and nothing about the client's visitors is kept on our servers.
Why a live view helps on client calls
A launch call or a monthly check-in is easier when the client can see something happening. Reports describe last month. A live view shows a visitor from Google on the pricing page right now, and a phone user scrolling the landing page. In those few minutes, the client sees what their site does for real people.
Typical agency moments:
- Handover. After you ship a new site, install the script and show the first real visitors arriving.
- A campaign goes live. Show where visitors from the campaign land and what they do next.
- A bug report. "It breaks on phones": open the live view and watch a phone visitor's band instead of guessing.
- A pitch. Install on a prospect's staging site and show it working with a test visit from a private window.
One tag per site
Each website is separate. A client with a marketing site and a shop uses two site entries. Localhost and production never mix, and www. is the same website as the bare domain.
<script src="https://live.whoisbrowsing.com/s.js" data-site="YOUR_SITE_ID" defer></script>
Use each client site's own ID in place of YOUR_SITE_ID.
The script is under 4 KB gzipped, loads after the page and never changes how the page looks, so it is easy to explain to a client's developer. Platform-specific steps are in install: the exact placement depends on the CMS or framework, and some platforms restrict custom code by plan, so check the client's plan.
If you manage many sites, an AI coding agent can install it for each one. The prompt is Add whoisbrowsing (live visitor view) to this project. Follow https://whoisbrowsing.com/SKILL.md exactly. See install with an AI agent.
What the client sees
| Element | Meaning |
|---|---|
| Coloured cursor and fading trail | A desktop visitor's movement |
| Click ripples | Where visitors click |
| See-through band | Where a phone or tablet visitor is looking |
| Side panel | Live counts per page, busiest first, and one line per person |
| Per-visitor details | Source, approximate city, device, browser, operating system, time on site and pages this visit |
Source includes Google, Bing, ChatGPT, Perplexity, Gemini, Copilot, Claude, another site's link or direct, which opens a useful conversation about AI visits.
Privacy you can tell the client
Agencies carry the privacy conversation with the client. These are the facts, word for word:
- Your visitors' browsers send the page, pointer position, clicks, scroll, device type, source, browser and operating system, and time on site. Never keystrokes, form values or page text.
- Nothing about your visitors is stored on our servers.
- No cookies on your visitors.
- Visitors from the EU/EEA, UK and Switzerland, and browsers with Global Privacy Control, are never shown.
This is a description of what the tool does, not legal advice and not a guarantee of any legal status. Whether a given site needs a notice or a consent mechanism is a question for the client and their adviser. Read Is live visitor tracking GDPR-safe? and the privacy page before you present it.
A launch call, step by step
- The day before, add the tag to the client's site and confirm it with a private-window visit.
- On the call, share your screen and open the client's site after clicking Watch.
- Walk through the side panel first: the busiest pages, and where each visitor came from.
- Then scroll to the page the campaign links to and let the client watch cursors and phone bands move on it.
- End with what is not there: no recordings, no history and no names. Then hand over the privacy facts below.
Testing before the call
Open the client's site in a Chrome Incognito or Safari private window while watching, and you appear as a visitor. The owner's own regular browser is never counted. Because EU/EEA, UK and Switzerland visitors are not shown, do the test from elsewhere, or you will see nothing.
When whoisbrowsing is NOT the right tool
It does not produce monthly reports, history or heatmaps, and it does not store sessions. For client reporting use an analytics tool, and for session replay use Microsoft Clarity or Contentsquare (which Hotjar is now part of). Treat whoisbrowsing as the live view next to them. Compare options on the compare page.
It is free, with no credit card and no usage limits for now. Try it without an account and claim the site later.