When data does not appear, the cause is almost always one of five things. Work down this list in order and you will find it fast.
Check the token and script
Confirm the s= token in the script URL matches the one in Settings exactly. A single wrong character routes events nowhere. Make sure the tag is in the page head and loads on every route, not just the homepage.
View source on your live site and confirm the script tag is actually present; build steps and content security policies sometimes strip it.
Is an ad blocker or localhost hiding your data?
An ad blocker or privacy extension can block the script, as it can any analytics script. Test in a clean browser profile with no extensions before assuming a bug. To count visitors who run a blocker, measure from the edge or your server (docs, Edge / no-script).
Localhost is not counted. Once your site has a registered domain, Vero only accepts events whose origin is that domain or a subdomain of it, with or without www. A page on localhost, or on a hosting preview URL under another domain, sends events that are dropped. To test before going live, deploy to a subdomain of your domain, such as staging.yourdomain.com.
Bots and origins
Vero filters known bots by default, so automated hits will not show. That includes headless browsers and test tools such as Playwright, Puppeteer, Selenium, Cypress and Lighthouse, and any browser driven by automation. The tracker also stays off when the browser sends Do Not Track or Global Privacy Control, so turn both off in the browser you test from.
Finally, check the origin. Each site has one registered domain, set when you create it and shown read-only in Settings. Events are accepted from that domain, its www version and any subdomain of it, and from nowhere else. If the page you test lives on another host, the API rejects its events for security: load it on the registered domain or a subdomain of it and reload.
Unsure of a term? Read the glossary