Skip to main content
A proxy routes Trfyx tracking requests through a domain you control instead of sending them directly to app.trfyx.com. This can improve collection reliability when browser extensions, network filters, or ad blockers block known analytics domains.
A proxy is optional. Install the standard Trfyx tracker first, then add a proxy when you are ready for production traffic or want a first-party collection path.

​
Choose your setup

​
Managed Proxy

Use Managed Proxy when you want the simplest setup. Trfyx provides the proxy routing and SSL; you configure a subdomain and one DNS record, then point your tracker at that hostname.
Managed Proxy is recommended for most sites.

Set up Managed Proxy

Route Trfyx through your own subdomain without running proxy code.

​
Self-hosted proxy

Use a self-hosted proxy when your application already has a reverse proxy, server middleware, or edge configuration that can forward Trfyx requests. Choose the guide that matches your stack:

Next.js

Express

PHP

FastAPI

Flask

Vue.js

Astro

Laravel

Nginx

Caddy

Firebase Hosting

DigitalOcean

​
What should be proxied?

A working proxy needs to forward both:
  1. The Trfyx browser script.
  2. The event collection endpoint.
For self-hosted setups, preserve the visitor’s original IP information when forwarding requests. If every visitor appears to come from your server or proxy location, the proxy is not forwarding the client IP correctly.

​
Verify installation

1

Open your production website

Load a live page on your site.
2

Check the network panel

Open Developer Tools → Network and reload the page.
3

Confirm the script loads through your domain

Check that script.js is requested from your domain rather than app.trfyx.com.
4

Trigger and confirm an event

Fire a pageview or tracked event and confirm the request also goes through your proxy.
5

Check Trfyx for the activity

Verify the new visit or event appears in your Trfyx dashboard.
Do not use a proxy just because you can. A broken proxy is worse than no proxy: it can silently drop events or replace every visitor’s IP with the server’s IP. Verify collection and visitor location after deployment.

​
Next steps

Goals

Define the actions that matter to your business.

Troubleshooting

Diagnose missing or unexpected data.
Last modified on October 12, 2026