Learn what domain verification is, why you might see a 403 error from the Zenovay tracking script, and how to fix it.
What Is Domain Verification?
Zenovay verifies that tracking scripts only send data from authorized domains. When a visitor loads a page with your tracking script, Zenovay checks the request's Origin header against the list of allowed domains registered for your website.
This prevents unauthorized websites from sending fake analytics data to your account and keeps your reports accurate.
Why Am I Seeing a 403 Error?
A 403 Forbidden response from the Zenovay tracking API means your tracking code is sending data from a domain that is not authorized in your website's allowed domains list.
This typically happens when:
- You added your tracking script to a new domain or subdomain without updating your allowed domains
- Your website moved to a different domain
- You are testing on a staging or preview domain (e.g.,
staging.example.com) - The www and non-www versions of your domain are not both covered
Example console errors:
POST https://api.zenovay.com/track 403 (Forbidden)
The API returns one of these messages:
"Domain not authorized for this tracking code"-- the domain is not in your allowed list"Missing request origin"-- the browser did not send an Origin or Referer header
How to Fix It
Step 1: Log In to Zenovay
Go to app.zenovay.com and sign in to your account.
Step 2: Open Your Domain Settings
- Go to Domains from the sidebar navigation
- Click on the website that is showing the error
- You will land on the General tab of your domain settings
Step 3: Add Your Domain
- Find the Allowed Domains section
- Click Add Domain
- Enter the domain where your tracking script is installed
- Click Save
Step 4: Add Both www and non-www Versions
Make sure to add both versions of your domain:
example.comwww.example.com
Subdomain matching: If you add example.com, subdomains like blog.example.com are automatically allowed. However, adding both explicitly is recommended for clarity.
Wildcard support: You can use *.example.com to allow all subdomains at once.
Troubleshooting Tips
Check Domain Spelling
A small typo can cause verification to fail. Double-check that the domain in your allowed list matches the actual domain exactly.
Correct: example.com
Wrong: exmple.com
Wrong: example.co
Check www vs non-www
While subdomains of an allowed domain are automatically permitted, it is best practice to add both www.example.com and example.com explicitly to avoid confusion.
Proxy or Ad-Blocker Bypass Domains
If you are using a custom proxy domain to bypass ad blockers (e.g., analytics.yourdomain.com), make sure the proxy domain is also added to your allowed domains list.
Staging and Preview Domains
If you use deployment previews or staging environments, add those domains as well:
staging.example.compreview.example.com*.vercel.app(use wildcard for deployment preview URLs)
Still Having Issues?
If you have verified your domain settings and still see 403 errors:
- Wait a few minutes -- Domain changes can take up to 2 minutes to propagate
- Clear your browser cache and reload the page
- Check your browser console for additional error details
- Contact support at support@zenovay.com with:
- Your website URL
- The domain showing the error
- A screenshot of your allowed domains settings