Skip to main content

install

Install Vero with Google Tag Manager

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.

    Google Tag ManagerCustom HTML tag
    <script defer src="https://api.getvero.dev/t.js?s=YOUR_TOKEN"></script>

    Create a Custom HTML tag with this snippet, fire it on All Pages, then publish the container.

  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.

Running Vero inside a GTM container

In your container, create a Custom HTML tag, paste the snippet, and give it the All Pages trigger. Then publish the container. A tag that is saved in the workspace but never published stays off the live site, and Vero never hears from it.

From the outside, a GTM container is a closed box. Check my site can see that GTM is on your home page but not what it loads, so when it finds no Vero tag in the HTML it says so and asks you to publish the container if you added Vero there. The first visit in your dashboard is the confirmation.

Single-page apps behind GTM do not need a history trigger for Vero. All Pages loads the script once, and route changes are the SPA module's job, switched on per site in Dashboard → Settings → Install.

The tracker sets no cookies and writes nothing to the visitor's device. It does not run at all when the browser sends Do Not Track or Global Privacy Control.

Troubleshooting

The tag fires in GTM, but no visits arrive

Loading through GTM does not get around your Content-Security-Policy. If the site sends one, script-src has to allow api.getvero.dev so the script loads, and connect-src has to allow it too, or the script runs and its events are blocked. Add the host to both and publish.

My data is not showing up

Frequently asked

Should I fire the tag on a history change trigger as well?

No. Load it once, on All Pages. The SPA module, switched on per site, turns History API route changes into pageviews.

Can other GTM tags send custom events to Vero?

Yes. Any tag that runs after Vero has loaded can call window.vero.track with an event name and properties, and a goal on that event gives you its conversion rate.

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