1. Add your website in Settings
In your WhoVisited workspace, open Settings and add your website name and main HTTPS address, such as https://example.com. The www version is included automatically. Add other subdomains, such as https://app.example.com, on separate lines if you want them to send events to this site.
Each workspace supports up to two websites. Each website has its own site ID and installation snippet. Use the snippet from the website you want to measure, and save changes before testing.
2. Put the script in your website
Copy the Installation snippet from Settings into your shared page layout, inside the HTML <head>. It should load on every page you want to measure. Replace the placeholder below with the site ID from your own snippet.
<script async src="https://whovisited.net/tracker.js"
data-site-id="YOUR_SITE_ID"></script>If you use Google Tag Manager, paste your snippet into a Custom HTML tag and configure its firing and consent conditions for the pages you want to track. Publish the container when you are ready. Install through one method to avoid loading the same tracker twice.
The tracker handles page changes in single-page apps. For a Next.js site, place it in the shared root layout rather than adding a separate copy to every page. Deploy your changes so they are present on the public website.
3. Connect your collection controls
To make the tracker wait for your consent manager, add data-consent="required" to the script. After the script has loaded, call window.whovisited.consent(true) when the visitor grants consent. Call window.whovisited.consent(false) when they withdraw it.
WhoVisited respects Do Not Track and Global Privacy Control signals. It uses browser storage for random visitor and session identifiers. The privacy policy describes the data and controls; choose your consent setup for your website and audience.
4. Visit your website, then verify installation
Open a tracked page on your deployed website. In WhoVisited, expand that website in Settings and click Verify installation. A successful check displays Integrated when a matching tracking event has been received.
This confirms event receipt for that website. It does not prove that every page has the snippet or that future visits will always be recorded. Check another page and a client-side navigation if your website uses one, then look for the activity in Visitors.
Saved domain → Published snippet → Real website visit → Integrated
A tracker test page can help diagnose collection, but visiting your own deployed website is the check that matters for installation.What if no visits appear?
- Check that the deployed page contains the correct snippet and site ID.
- Check that collection is enabled for the site and the workspace has an active subscription and available event quota.
- Check the actual address in the browser. A separate subdomain needs to be saved in your allowed origins.
- Check whether your consent manager has granted collection and whether browser privacy signals or extensions are preventing it.
- In the browser Network panel, inspect the request for
tracker.jsand the subsequent bootstrap and event requests. A loaded script alone does not confirm accepted events.
Once visits appear, set up a goal so you can measure outcomes as well as traffic.