---
title: "Using a proxy | Documentation - Vemetric"
description: "Optimize tracking by proxying data through your own domain."
url: https://vemetric.com/docs/advanced-guides/using-a-proxy
---

# 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](https://vemetric.com/docs/advanced-guides/using-cookies) if needed)

> We recommend avoiding names or paths like `analytics.yourdomain.com` or `yourdomain.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!

[Next.js](https://vemetric.com/docs/advanced-guides/using-a-proxy/nextjs)

Optimize tracking by proxying data via Next.js.

[Vercel](https://vemetric.com/docs/advanced-guides/using-a-proxy/vercel)

Optimize tracking by proxying data via Vercel.

[Nginx](https://vemetric.com/docs/advanced-guides/using-a-proxy/nginx)

Optimize tracking by proxying data via Nginx.

[Cloudflare](https://vemetric.com/docs/advanced-guides/using-a-proxy/cloudflare)

Optimize tracking by proxying data via Cloudflare.