install
Analytics for Webflow, in one tag
A 1.2 KB core, no cookies and no stored IP. Replace YOUR_TOKEN with your site token to measure visits and sources, and connect Stripe, Lemon Squeezy, Paddle, or the revenue API to see the revenue behind them.
Copy your site token
It is in Dashboard → Settings → Install, inside the snippet. Before launch, you get a dashboard once we pick your account for the beta.
Paste the snippet
Once, in a place every page loads. Replace YOUR_TOKEN with your token.
<!-- Site settings → Custom code → Head code --> <script defer src="https://api.getvero.dev/ t.js ?s=YOUR_TOKEN"></script> Paste it into Site settings → Custom code → Head code, then publish the site. Vero does not read Webflow Ecommerce orders: revenue comes from Stripe, Lemon Squeezy, Paddle or the revenue API.
Deploy and open your site
Vero counts visits to your domain and its subdomains, so a localhost test never shows up. With the snippet live, open your site in another tab: your dashboard notices the first visit by itself.
Webflow custom code, staging and your domain
The tag goes in Site settings → Custom code → Head code, the site-wide slot Webflow adds to every page. Saving there changes nothing for visitors until you publish the site again. Once it is live, Check my site in the dashboard confirms the snippet is on your custom domain, that its token belongs to this site and that your Content-Security-Policy lets it run.
Webflow gives each site a staging address on webflow.io, and that is a different host from your custom domain. If the Vero site is your custom domain, visits to the webflow.io address are ignored, and the dashboard tells you visits are arriving from another host. To check the tag on staging without counting it, run an install test. If people really do visit the webflow.io address, add it as a site of its own.
To count a form or a button as a conversion, call window.vero.track with an event name from an Embed element's script, then create a goal on that event to see its conversion rate.
Troubleshooting
Head code is saved, but Check my site finds no snippet
Check my site opens your custom domain's home page as visitors get it. Custom code saved in Site settings is not on the live site until you publish, and publishing only to the webflow.io staging address leaves the custom domain on the old version. Publish to your custom domain and run the check again.
Frequently asked
Does Vero see my Webflow Ecommerce sales?
No. Revenue reaches Vero from Stripe, Lemon Squeezy, Paddle or the revenue API. Stripe Payment Links buttons carry the visit through the checkout module, so those sales are tied to the visit that clicked.
Should I add the webflow.io address as a separate site?
Only if real visitors use it. To check the tag before launch, the install test is enough and keeps those visits out of your numbers.
After the tag
- Connect your revenuePaste one webhook URL into Stripe, Lemon Squeezy or Paddle and each sale arrives with its visit.
- Send your own eventsA signup, a click on a plan: point a goal at the event and get its conversion rate.
- Pick your modules9 optional modules, such as SPA routes, scroll or Web Vitals, turned on per site.
Ask for a place in the beta.
Anyone can join the list. The accounts we pick get Pro free for the whole beta.