Using a proxy
Optimize tracking by proxying data through your own domain.
While not strictly necessary, it’s recommended to proxy the Vemetric script and data through your own domain.
There are two main benefits to this approach:
- Avoiding ad/tracker blockers: By using your domain (e.g.,
hub.yourdomain.com
), Vemetric requests blend in with your site’s traffic and are less likely to be blocked. - No third-party cookies: By proxying the data through your own domain, you avoid using third-party cookies. (By default Vemetric doesn’t use any cookies, but you can enable them if needed)
We recommend avoiding names or paths like
analytics.yourdomain.com
oryourdomain.com/track
, as this might also trigger ad/tracker blockers.Use more generic names like
hub.yourdomain.com
instead.
Guides
We’ve prepared some guides for well-known platforms.
If you need help with a different platform, please let us know!
Optimize tracking by proxying data via Next.js.
Optimize tracking by proxying data via Vercel.
Optimize tracking by proxying data via Nginx.
Optimize tracking by proxying data via Cloudflare.
Welcome to the Vemetric documentation.