Proxy Setup Guide
Proxy setup means the browser loads Affonso through your own domain.
Why teams use it:
- roughly 30% of internet users use ad blockers
- ad blockers and privacy tools commonly block third-party scripts and requests
- using your own domain usually improves tracking accuracy
- the same setup can also make the embedded dashboard more reliable
Important for Tracking
If you proxy /track or /signups, Affonso must still receive a trusted real
client IP header such as CF-Connecting-IP, True-Client-IP, or X-Real-IP.
Otherwise attribution can still work while country analytics are wrong or missing.
What Changes
Without a proxy, the browser talks directly to:
cdn.affonso.iofor the pixel scriptapi.affonso.iofor tracking requestsaffonso.iofor the embedded dashboard
With proxy setup, the browser uses your own domain instead.
Example:
customer.com/r/pixel.jscustomer.com/r/trackcustomer.com/r/signupscustomer.com/r/embed/...
Only the prefix is your choice. The route suffixes should stay as documented in the guides below.
Choose Your Setup
Use the guide that matches your setup:
Do You Need Both?
If you only use the tracking pixel, skip the embed guide.
If you only use the embedded dashboard, skip the pixel guide.
If you use both, you can keep them under the same prefix such as /r.
Before You Start
Make sure you have:
- a domain you control
- a reverse proxy, rewrite layer, or edge function on that domain
- one short path prefix reserved for Affonso, such as
/r - a way to preserve the real visitor IP on proxied tracking requests
A neutral prefix like /r is a good default.
