When you see the Tracker not detected banner in your Zenovay dashboard, it means our automated detection probe could not find a working tracker on your homepage. The probe runs every few hours and looks for two things — the script tag and at least one successful event in the last 24 hours.
What the probe actually does
- Fetches your website's homepage with a regular browser User-Agent (not a bot fingerprint).
- Parses the HTML looking for
<script src="...zenovay.com/z.js">or a known first-party proxy URL. - Checks the database for at least one successful event from your tracking code in the last 24 hours.
If either step fails, the banner appears.
Common causes
1. Tracker is on a sub-page but not the homepage
The probe only fetches your homepage URL (the URL you registered in Settings → Website). If you only added the script to specific pages, the probe will say "not detected" — even if tracking works fine on the pages where it's installed.
Fix: add the tracker to the site's shared layout / header so it loads everywhere, not just on a few pages. Or update the registered URL in Settings → Website to a page that does have the tracker.
2. Server-side rendering removes the tag
Some templating systems strip <script> tags they consider non-essential, especially in production builds. If you can see the script in your local development build but not in view-source: on the live site, the build is stripping it.
Fix: check your build configuration (Webflow custom code panel, Next.js Script component, WordPress theme cache).
3. CDN cache is serving an old version
If you recently added the tracker but your CDN (Cloudflare, Fastly, Vercel Edge) is caching a stale version of the page, the probe sees the cached HTML.
Fix: purge the cache for the homepage URL. Wait 5 minutes, then click Re-check in the banner.
4. The tracker is loaded but cannot reach api.zenovay.com
Sometimes the script loads but is blocked from posting events. Common reasons:
- CSP
connect-srcdirective doesn't includeapi.zenovay.com - Corporate firewall blocks the domain
- Network outage in your visitors' region
Open DevTools → Network tab on a real visit and look for failed requests to api.zenovay.com. The error message will tell you which.
5. Tracking code mismatch
The probe expects the registered tracking code. If you regenerated it but didn't update the script tag, the tracker is loading but events are being rejected for the wrong code.
Fix: in Settings → Tracking Code, copy the current code and confirm it matches the data-tracking-code on your live site.
6. Localhost development
If your registered URL is localhost:3000 or similar, the probe can't reach it from the public internet. This is expected — register your real production URL instead.
Re-running the detection check
After fixing the issue:
- In your dashboard, click the Re-check button on the banner (or wait — the probe re-runs every few hours).
- The banner clears once the probe sees a working tracker AND at least one successful event in the last 24 hours.
Still stuck?
If you've worked through the list and the banner persists:
- Open the Status page to confirm the detection probe itself is healthy.
- Email support@zenovay.com with your homepage URL, the value of
data-tracking-codeon your live page, and a screenshot of the dashboard banner.