Skip to main content

install

Analytics for Nuxt, 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.

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

  2. Paste the snippet

    Once, in a place every page loads. Replace YOUR_TOKEN with your token.

    Nuxtnuxt.config.ts
    export default defineNuxtConfig({
      app: {
        head: {
          script: [
            { src: 'https://api.getvero.dev/t.js?s=YOUR_TOKEN', defer: true },
          ],
        },
      },
    });

    Register the script in nuxt.config so it is injected on every route.

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

Registering the script in nuxt.config.ts

In Nuxt the tag does not live in a template file. You add an entry with src and defer: true to app.head.script in nuxt.config.ts, and Nuxt injects it on every route. There is no component to import and no plugin to write.

Vue Router changes pages through the History API, so after the first load the document stays put. The SPA module patches pushState and replaceState, listens to popstate, and sends a pageview whenever the path or the query changes. Without it you would only see the page each visit started on. The core also sends a pageview when the browser restores a page from its back/forward cache.

Nuxt is not detected by name when you add a site, and it does not need to be: sites Vero does not recognise get SPA on by default, along with scroll, engagement, outbound and leave. Trim that list per site in Dashboard → Settings → Install without editing nuxt.config.ts again.

Troubleshooting

Visits from a Netlify deploy preview are ignored

Vero only counts beacons sent from the site's domain, its www or apex, and its subdomains. A *.netlify.app deploy preview is another host, so the dashboard names it as a preview and leaves its visits out. Use an install test on the preview to confirm the script runs while your real numbers stay clean.

My data is not showing up

Frequently asked

Do I need a Nuxt module or an npm package?

No. The entry in app.head.script is all it takes; the script itself is served from api.getvero.dev with your site token.

Why defer: true?

It lets the browser keep parsing the page while the script downloads, and runs it once the document is ready. The snippet already sets it.

IntegrationsPricing

After the tag

Hand-picked beta, waitlist open

Ask for a place in the beta.

Anyone can join the list. The accounts we pick get Pro free for the whole beta.

By joining you agree to receive launch updates and accept our Privacy Policy.

See the demo