If you installed the Zenovay tracker and your first visit isn't appearing in the Live View tab after 30-60 seconds, work through this checklist in order.
1. Are you watching the right place?
Open your website's dashboard and select the Live View tab (under Audience in the sidebar). It updates in real time. The main dashboard charts have a 1-2 minute aggregation lag — a brand-new event won't show up there yet. Always verify install on Live View first.
2. Did the script actually load?
Open your site in an incognito window, hit F12 to open DevTools, go to the Network tab, and filter for zenovay.
You should see two requests:
z.js— the tracker script itself, status 200- A request to
api.zenovay.com/e/...(the tracking endpoint) — status 200
If z.js is missing, the script tag never executed. If it returns a 404, the URL is wrong (it should be exactly https://api.zenovay.com/z.js).
3. Is the tracking code correct?
In your dashboard, open the website's Settings → General tab and copy the value from the install snippet. It's a 12-character code like aB3xY9mK2pQz. Compare it character-for-character with the data-tracking-code attribute on your <script> tag.
A common mistake is pasting a placeholder like YOUR_TRACKING_CODE and forgetting to replace it.
4. Is an ad blocker eating the request?
uBlock Origin, AdGuard, Brave Shields, and most major privacy extensions do not block Zenovay by default — but a custom block list might. Test by:
- Disabling extensions for that site, or
- Using a different browser, or
- Loading the site on your phone over mobile data
If the event appears with the blocker disabled, the install is fine — your visitors will just have slightly lower numbers reported. Consider first-party tracking for ad-blocker resistance.
5. Are you testing on localhost?
By default the tracker skips events on localhost and 127.0.0.1. To enable local testing, add data-allow-localhost="true" to the script tag.
6. Does your CSP block the tracker?
If your site uses a Content-Security-Policy header, both directives must allow api.zenovay.com:
script-src ... https://api.zenovay.com;
connect-src ... https://api.zenovay.com;
Look for CSP errors in the browser console — they're explicit about which directive blocked the request.
7. Has your visitor signaled GPC or DNT?
If Global Privacy Control or Do Not Track is enabled in your test browser, the tracker respects it and doesn't send the event. Test in a browser without privacy extensions, or with GPC and DNT turned off.
8. Did your tracking code get rotated?
If you regenerated your tracking code in the dashboard, the old code stops accepting events. Update the script tag and re-deploy.
Still nothing?
- Re-read Verifying your installation.
- Open the Status page to confirm the ingest API is healthy.
- Contact [email protected] with the URL of the page you're testing, your tracking code prefix, and a screenshot of the Network tab.