How to track visitors on Webflow.

Webflow keeps site-wide scripts in project settings. Paste once, publish, done — with one wrinkle around which domains you publish to.

What you need

• A Webflow project on a paid site plan — custom code requires one.
• Access to Project Settings.
• 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
Open custom code
From your Webflow dashboard open the project, then Project Settings — the gear icon — and choose Custom Code.
2
Paste into Head Code
Put the tag in the Head Code section with your own key in place of vp_ABC23456, then Save Changes.
```
<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script>
```
3
Publish to every domain
Click Publish and tick all domains, not just the webflow.io staging one. Custom code only reaches a domain you publish to.

Staging and live can disagree

Webflow publishes per domain. It is easy to publish to the webflow.io staging address, see the tracking working, and leave the customer-facing domain without it.

If visits appear from your staging domain but not your real one, that is what happened — publish again with every domain selected.

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

Custom Code is greyed out: It needs a paid site plan. An account plan alone does not unlock it.
Changes are saved but not live: Saving custom code does not publish it. Publish the site afterwards.

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.

Start Free Trial See how it works

Install it

Open custom code

From your Webflow dashboard open the project, then Project Settings — the gear icon — and choose Custom Code.

Paste into Head Code

Put the tag in the Head Code section with your own key in place of vp_ABC23456, then Save Changes.

<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script>

Publish to every domain

Click Publish and tick all domains, not just the webflow.io staging one. Custom code only reaches a domain you publish to.

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 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.