Pageviews tell you where people go; custom events tell you what they do. Vero exposes a single track function so you can record any action that matters to your business.
Conversion goals
The track API
Once the script is loaded, call window.vero.track("signup") from anywhere in your app. The event name is the only required argument and shows up in the dashboard within seconds.
You can attach a small set of properties as a second argument, like window.vero.track("plan_selected", { plan: "pro" }), to segment later. Keep properties non-personal: Vero drops any value that contains an email address, but it stores everything else you send, so never pass a user id or a name.
How should you name custom events?
Use short, lowercase, verb-based names like signup, checkout_start, and invite_sent. Consistent naming keeps your goals and funnels readable months later.
Avoid encoding values into the name (signup_pro, signup_free). Put the variant in a property instead so you can compare them in one place.
From event to insight
Any event can become a goal: mark it in the Goals view and Vero tracks its conversion rate over time. Multi-step funnels chain those events so you see exactly where people drop off.
Cookie-based tools lose traffic to blockers, Safari ITP and consent rejection. Events come from the browser script, which sets no cookies, so ITP and consent rejection take nothing from them. An ad blocker can still stop the script: for an event that has to be counted, send it from your server with POST /api/events, where nothing runs in the browser to block.
Unsure of a term? Read the glossary