SuprAnalytics

Ad-blocker proxy

Count the visitors ad blockers hide.

Ad blockers and privacy browsers block requests to known analytics hosts. Serve the script from a subdomain of your own website instead, set up for you with one DNS record, or forward it through your own reverse proxy.

Start free trial How it works

14-day free trial · No card required · From $9/month

The managed proxy.

Type a subdomain such as a.yourdomain.com in Settings → General → Managed Proxy and add the CNAME record it shows. SuprAnalytics sees to the HTTPS certificate. The card shows where it stands:

Waiting for DNS
The record isn't there yet, or points elsewhere. The card checks again every 20 seconds, and Check now checks straight away.
Verify the domain
Add the TXT record shown too, to prove the domain is yours.
Issuing certificate
DNS is right; the HTTPS certificate is on its way.
Active
The subdomain answers over HTTPS, and the snippet in Settings → General loads from it.

What goes through it.

The subdomain serves the tracking script and the events it sends back.

  • Visitors' browsers still reach SuprAnalytics directly behind the subdomain, so their own address gives the location and rate limits, and is never stored
  • The dashboard and sign-in stay on SuprAnalytics' own address
  • Session recordings don't go through it: the recorder and its uploads always use SuprAnalytics' own address
  • One subdomain per website, of its domain or one of its additional domains. Keep the name neutral, like a. or cdn.: blockers also look for words like analytics, stats or track

Or your own reverse proxy.

Forward /js/script.js and /api/event from your website to SuprAnalytics with nginx, Caddy, Next.js rewrites or Express, and load the script from your own domain. The script sends events to the host it came from; if /api/event is taken, point it elsewhere with supr-api.

The trade-off: SuprAnalytics then sees your proxy's address for every visitor, so locations can't come from the visitor's address, the limit of 120 hits a minute per address applies to all your traffic together, and cookieless mode can't tell visitors apart. The own proxy guide has the snippets.

Set it up.

  1. Pick a subdomain

    In Settings → General → Managed Proxy, type a subdomain of your website and click Enable.

  2. Add the DNS record

    Add the CNAME record shown where your domain's DNS is managed. On Cloudflare, set it to DNS only (the grey cloud).

  3. Wait for Active

    DNS usually takes minutes, sometimes a few hours.

  4. Update your snippet

    Paste the snippet from Settings → General, which now loads from your subdomain. The old one keeps working meanwhile.

How it works, in detail.

The docs page “Serve the script from your own subdomain” goes through it step by step.

How it works

Limits worth knowing

  • A proxy gets the script past lists of analytics hosts; visitors with JavaScript turned off still aren't counted
  • Session recordings don't go through the proxy, so a blocker can still stop the recorder
  • Removing the subdomain stops counting from any snippet that still loads from it: put your snippet back first
  • One subdomain per website, and a subdomain can belong to only one website

Questions, answered.

Why do ad blockers hide visits?

They keep lists of analytics hosts and block scripts and requests going to them, so visitors using one are never counted. Served from your own subdomain, the script looks like part of your website.

What do I need to set it up?

Access to your domain's DNS. You add one CNAME record, and sometimes a TXT record to prove the domain is yours. No code changes beyond pasting the new snippet.

Which subdomain should I use?

Something short and neutral, like a. or cdn.. Blockers also look for words like analytics, stats or track in host names.

Does it work with Cloudflare?

Yes. Add the CNAME record with the proxy off, as DNS only (the grey cloud).

Are visitors' IP addresses stored through the proxy?

No. They're used for the location and rate limits, as without the proxy, and never saved.

Should I use my own reverse proxy instead?

The managed proxy is less work and keeps each visitor's own address. Your own proxy works too, with the trade-offs above: shared rate limits and no locations from visitors' addresses.

More features

All features

See it on your own website.

Every feature is on every plan, with a free trial and no card.

Start free trial

14-day free trial · No card requiredPricingHow it worksAll features