> For the complete documentation index, see [llms.txt](https://docs.spindl.xyz/spindl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spindl.xyz/spindl/techncial/javascript-sdk-html-script-guide/setup-a-reverse-proxy.md).

# Setup a Reverse Proxy

Tracking via a Reverse Proxy helps you send events using your own domain. As a result you are less likely to be intercepted by tracking blockers and be able to track more usage data.

Please use at least version **`1.6.0`** of `@spindl-xyz/attribution` or `@spindl-xyz/attribution-lite` for this.

 What happens under the hood that we forward the data to Spindl servers via a Reverse Proxy domain:

<figure><img src="/files/AuojvAeenmlUBwbNaiP9" alt=""><figcaption></figcaption></figure>

Here are several easy ways to implement this. Here are a few simple tutorials:

* [Next.js](/spindl/techncial/javascript-sdk-html-script-guide/setup-a-reverse-proxy/using-next.js.md)
* [Cloudflare](/spindl/techncial/javascript-sdk-html-script-guide/setup-a-reverse-proxy/using-cloudflare-workers.md)
* [Netlify](/spindl/techncial/javascript-sdk-html-script-guide/setup-a-reverse-proxy/netlify.md) (if you're using them as a hosting provider)

You can also use other services that support Reverse Proxies. Here are a a few popular hosting providers and their documentation:

* Amazon Web Services: [API Gateway](https://aws.amazon.com/api-gateway/resources/)
* Microsoft Azure: [API Management](https://docs.microsoft.com/en-us/azure/api-management/api-management-key-concepts)
* Google Cloud: [API Gateway](https://cloud.google.com/api-gateway/docs)