How to track visitors on Replit.
On Replit you install tracking by asking Replit Agent to add the tag. The catch is that the Agent can say it has done this when the tag never reaches the published app — so the last step is checking the live HTML yourself.
What you need
- • A Replit app you can edit and publish.
- • A VisitorPing site key, in the form vp_ABC23456 — the prefix vp_ and eight characters. The alphabet leaves out I, O, 0 and 1, so there is nothing to misread when copying it.
Install it
- 1
Ask Replit Agent to add the tag to the head
In the Agent chat, ask for exactly this, with your own key in place of vp_ABC23456: “Add this script tag to the <head> of every page the published app serves, unchanged. Do not load it from a React component or rewrite it.”
Pasting the tag itself, rather than describing it, keeps the Agent from inventing its own version.
<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script> - 2
Republish
Click Republish in the upper-right corner — or Publish, if the app has never been published. Changes in the preview are not live until you do.
- 3
Confirm the tag is in the live page
Open your published app, view the page source, and search for cdn.visitorping.com. If it is not there, the install has not happened, whatever the chat said.
Then open the app in a private window and move between two pages. Both should appear in Live Radar.
Page changes inside the app are handled
If your app is a single-page app, moving between screens does not reload the page. The VisitorPing script follows those changes itself, so you do not need to ask the Agent to fire anything on navigation.
If the app serves separate pages from a server instead, each page needs the tag in its head — which is why the request says every page the published app serves rather than one file.
What you will actually see
Per visit: the city and region the network resolves to, where the visitor came from, the page they landed on, their device and browser, and whether they have been before.
You do not get a name, an email address, or an identity. Nobody can give you that from a page view, whatever the marketing says. Geolocation resolves a network rather than a doorstep, so a visitor on a VPN or a mobile network can appear in the wrong city entirely. Treat location as a hint.
You are collecting visitor data, so say so in your privacy notice and check which consent rules apply where your customers are — a question for your own legal advice, not for a setup guide.
If it is not working
- The Agent says tracking was added, but nothing arrives
- Check the published page source for cdn.visitorping.com. If it is missing, ask the Agent again with the exact tag, then republish.
- Some pages have the tag and others do not
- The app serves those pages from different templates. Ask the Agent to add the same tag to the head of each one, then republish.
- The tag is in the source but no visits appear
- Compare the key in the tag with the one on your website's settings page in VisitorPing, and make sure the domain you are visiting is the one registered there. If the tag is present but blocked, ask the Agent whether the app sets a Content-Security-Policy.
- Visits appear in the preview but not on the live app
- The change was not republished. Republish and re-check the live page source.
Find what is costing you search clicks, then watch the fix work.
VisitorPing reads your own Search Console data for the pages losing clicks, then rings your phone the moment someone lands on your website.