Setting up a proxy (code required)

Around 30% of web visitors use ad-blocking extensions. By routing the Flowsery Analytics script through your own domain, you can avoid being blocked and get more accurate visitor data.

Two pieces: rewrite + real IP header

A complete proxy setup has two parts. Miss either and you lose something:

1. Rewrite — proxy /js/main.js and /api/track through your own server so the tracker looks first-party and survives ad-blockers.
2. Real IP header — when your server forwards /api/track to Flowsery, it must set the header x-flowsery-real-ip to the real visitor's IP. Without this, every visitor appears to come from your server's location, because the server-to-server hop resets cf-connecting-ip to your server's IP.

Your framework-specific guide below covers both steps.

1. What technology does your website use?

Frameworks

Next.js, Astro, Express, Laravel, and more.

• Next.js proxy
• Express.js proxy
• Flask proxy
• FastAPI proxy
• Vue.js proxy
• Astro proxy
• Firebase Hosting proxy
• Laravel proxy
• PHP proxy

Self-hosted servers

Nginx, Caddy, and similar.

• Nginx proxy
• Caddy proxy
• DigitalOcean proxy