install
Analytics for SvelteKit, 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.
<head> %sveltekit.head% <script defer src="https://api.getvero.dev/ t.js ?s=YOUR_TOKEN"></script> </head> Add it to app.html. Enable the SPA module to track client-side route changes.
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.
Why app.html is the right file in SvelteKit
Every page in a SvelteKit app renders through src/app.html, the template that holds %sveltekit.head%. Put the tag on the line right after it and the tracker is present on every route, without touching a single layout or page component.
After the first load, the SvelteKit router moves between pages in the browser, and the core only ever sees that first load. Enable the SPA module and each client-side route change that alters the path or the query through the History API becomes a pageview. Hash-only changes stay out, so a table of contents link does not inflate the count.
SvelteKit is not one of the stacks onboarding detects by name, but a site it does not recognise gets SPA on by default, with scroll, engagement, outbound and leave. Open Dashboard → Settings → Install to confirm the modules before you deploy. Changing them later never means editing app.html: the tag only carries your site token.
Troubleshooting
Only the first page of each visit shows up
That is the core counting the initial load while client-side navigation goes unseen. Turn the SPA module on for the site in Dashboard → Settings → Install. The tag in app.html stays exactly as it is, since the modules come from your site settings and not from the snippet.
Frequently asked
Do I need to change app.html when I switch modules?
No. The tag only identifies your site; which modules load is set per site in Dashboard → Settings → Install.
Can I try it against the Vite dev server first?
Yes. Start a test in the dashboard, then load your localhost page. Vero tells you the snippet works on that host and does not count that visit.
What happens with visitors who send Global Privacy Control?
The tracker does not run for them, and the same goes for Do Not Track. Nothing is sent from those browsers.
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.