Webflow analytics

StatJolt adds your tracking code to every page of your Webflow site. You paste it into one field in Site settings. Webflow then puts it on every page it publishes, including the ones you build later.

The statistics are cookieless. No cookie banner, no personal data and no second product to bolt on.

Install it in four steps

1. Open your StatJolt account and press the copy button under your code.
2. In Webflow open Site settings, then Custom code. Paste the code into Footer code and save.
3. Publish your site. Custom code reaches your visitors only when you publish.
4. Open your published site in a private window. The status in StatJolt turns green once the first visit arrives.

Paste the whole snippet. There is nothing to configure and nothing to choose.

What you need

Custom code in Site settings is a paid feature. Your site needs a Site plan or a paid Workspace plan that covers it. On a free site the field is not available to edit.

You also need a free StatJolt account, which is where the code comes from.

Where the badge goes

StatJolt shows a small badge on your site. By default it places itself in a corner of the screen and you do not have to touch your layout.

If you want it inside your design instead, drag an Embed element to the spot you want and put this in it:

<div id="statjolt-badge"></div>

Your staging domain counts as its own site

Webflow publishes to yoursite.webflow.io as well as to your custom domain and your footer code runs on both. StatJolt identifies a site by its domain so those are two separate sites in your account.

That is useful before you go live, because you can see the staging site sending data. Once you no longer need that, you can remove this domain any time from your site list in StatJolt.

The Designer canvas does not run custom code at all so the hours you spend inside Webflow are never counted.

Nothing is added to your project

Your Webflow project gains one snippet in one field. No collection, no CMS item, no extra asset and no second script to maintain.

Publishing and caching

Webflow serves your published site from its own CDN and there is nothing for you to purge. Publishing is the step that updates it.

What StatJolt stores

Your visitors stay anonymous. Raw IP addresses never reach disk and the visitor identifier is a hash that is regenerated with a new salt every midnight so yesterday's visitor cannot be matched to today's. The full detail is in the privacy policy.

If you are coming from Google Analytics

You do not need to keep both running. StatJolt replaces the page view, source, page and device reporting you were using GA4 for. It adds Core Web Vitals, funnels and user journeys that GA4 either buries or does not have. There is a fuller comparison in the GA4 alternative guide.

You do not need to ask for consent. StatJolt sets no cookies and collects no personal data so most sites need no consent banner at all. The legal side is in Google Analytics and the GDPR.

Running something outside Webflow too? There is a StatJolt WordPress plugin, a Joomla plugin and a Drupal module as well. The same account and the same snippet cover every site you own.