Trust your data
Stop ad blockers losing your data with a proxy
Serve tracking from your own domain so fewer visits go missing.
Updated · 1 min read
Browser extensions and privacy settings often block requests to known analytics domains. When that happens, the visit never reaches your dashboard, and neither does the signup or the sale that followed.
Why this matters
Missing visits skew more than your visitor count. If many of your visitors use blockers, your conversion rates, channel rankings and revenue attribution are all built on a partial picture.
Why most analytics tools can't tell you
Most analytics scripts load from the vendor's own domain, which is exactly what block lists match. You can't fix that from inside the dashboard: the request has to look like it belongs to your site.
How MetricRaven does it
MetricRaven can be served through a same-origin proxy. Your site serves the script and forwards events from paths on your own domain, such as /a/script and /a/event, to MetricRaven. The proxy only exposes the public script and the collection endpoint, never your secret key, and forwards the real visitor IP so locations stay accurate.
Visits arriving right now
Orbit Analytics · synthetic data · right now
How to do it
- Read how the proxy works in Serve tracking from your own domain.
- Pick the recipe for your stack, for example Next.js, Cloudflare Workers, Vercel or Nginx.
- Replace your script tag so the script and its events use your own paths.
- Forward the visitor IP in a header your host sets and overwrites, so countries stay correct.
- In your browser's Network panel, check that requests to your own paths succeed, then confirm new visits show sensible countries.
A proxy helps, but no setup gets past every blocker. For signups and payments, send server events from your backend: they can't be blocked by the browser.