How to track visitors on Base44.
Base44 builds your app from a chat, so you install tracking by asking the builder to add it. The catch is that the builder can say it has done this when the tag never reaches the published page — so the last step is checking the live HTML yourself.
What you need
- • A Base44 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 the builder to add the tag to the head
In your app's chat, ask for exactly this, with your own key in place of vp_ABC23456: “Add this script tag to the <head> of index.html, unchanged, on every page. Do not load it from a React component or rewrite it.”
Pasting the tag itself, rather than describing it, keeps the builder from inventing its own version.
<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script> - 2
Publish
Changes in the editor preview are not live. Publish the app so the change reaches your domain.
- 3
Confirm the tag is in the live page
Open your published site, 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 site in a private window and move between two pages. Both should appear in Live Radar.
Page changes inside the app are handled
A Base44 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 builder to fire anything on navigation.
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 chat says tracking was added, but nothing arrives
- Check the published page source for cdn.visitorping.com. If it is missing, ask again with the exact tag and the instruction to put it in index.html, then publish.
- 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.
- Visits appear in the preview but not on the live site
- The change was not published. Publish again 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.