Skip to main content
Managed Proxy routes Trfyx analytics through a subdomain you control without requiring you to run proxy code. Trfyx handles the proxy routing and SSL. You only need to choose a subdomain, add the DNS record shown in your Trfyx settings, and update your tracking script.
Managed Proxy is the recommended option for most production websites. Use a self-hosted proxy only when you already need to control the proxy layer yourself.

​
Why use a proxy?

Browsers, extensions, corporate networks, and ad blockers can block requests to known analytics domains. A first-party subdomain makes your collection path look like part of your own website.
Your analytics still go to Trfyx. The proxy only changes how the browser reaches the collection service.

​
Set up Managed Proxy

1

Enable Managed Proxy

In Trfyx, open the website you want to configure and go to its proxy or tracking settings. Enter a dedicated subdomain that belongs to your website, such as a.yourdomain.com or cdn.yourdomain.com.Prefer a short, neutral hostname. Avoid obvious names such as analytics, tracking, or metrics if your goal is to reduce filtering by simplistic blocklists.Enable Managed Proxy. Trfyx will show the DNS record required for your chosen hostname.
2

Add the DNS record

Open your DNS provider and create the record shown in Trfyx.For a typical setup, this is a CNAME:
Do not guess the target value. Copy the exact target displayed in your Trfyx dashboard because it can change between environments or deployments.
If Trfyx asks you to add a TXT verification record, add that record as well. Once the hostname is verified and the proxy becomes active, you can remove a temporary verification record if Trfyx explicitly says it is no longer required.DNS changes can take a few minutes to propagate.
3

Update your tracking script

Change the tracker so both the script and event requests use your managed proxy hostname.
index.html
The important details are:
  • data-domain remains your real website domain.
  • src points to the script on your proxy hostname.
  • data-api-url points to the event endpoint on the same proxy hostname.
  • Use the same proxy hostname for both URLs.
Do not make data-api-url relative when using Managed Proxy. A value such as /api/events resolves against the page’s hostname, not the proxy hostname. Use the complete https://... URL instead.
4

Test locally (optional)

If you need to test tracking locally, enable localhost tracking in your tracker configuration and keep the event URL pointed at the live managed proxy.
index.html
5

Verify installation

  1. Visit your real website. Do not use the proxy hostname as the page you browse.
  2. Open Developer Tools → Network and reload the page. Confirm script.js is loaded from your proxy hostname.
  3. Trigger a pageview or tracked event and confirm the request goes to your proxy hostname’s /api/events endpoint.
  4. Confirm the new visit or event appears in your Trfyx dashboard.

​
Troubleshooting

​
Proxy status stays pending

  • Confirm the CNAME exactly matches the record shown in Trfyx.
  • Make sure you created a DNS record, not a URL redirect or forwarding rule.
  • Check that the DNS record is in the correct zone for your domain.
  • Wait for DNS propagation, then refresh the proxy status.

​
Proxy status shows an error

Re-check the record type, hostname, target, and any TXT verification record shown in Trfyx. Do not add additional DNS records unless Trfyx asks for them.

​
Events are still sent to Trfyx directly

Inspect the tracker in the deployed page source and Network panel. Both src and data-api-url should use your managed proxy hostname.

​
All visitors have the same location

This usually means the original visitor IP is not reaching Trfyx correctly. Managed Proxy is designed to handle visitor IP forwarding automatically. If the problem persists, verify that the request is actually going through the Managed Proxy and contact Trfyx support with the affected hostname.

​
Analytics are still blocked

  • Use a neutral proxy hostname.
  • Confirm the deployed script does not reference app.trfyx.com.
  • Check your Content Security Policy and allow the proxy hostname in script-src and connect-src where required.
  • Test in a clean browser session without extensions to separate implementation problems from browser filtering.

​
Remove Managed Proxy

1

Disable Managed Proxy

Disable or remove Managed Proxy in your Trfyx website settings.
2

Remove DNS records

Remove the DNS records created for the proxy.
3

Switch back to standard tracking

Change the tracker back to the standard Trfyx script:
index.html
Your existing analytics data is not removed just because you stop using the proxy.

​
Next steps

Goals

Define the actions that matter to your business.

Funnels

Understand where users convert or drop off.

Proxy setup

Compare Managed Proxy with self-hosted options.

Troubleshooting

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