Managed proxy
Ad blockers block requests to known analytics domains. The managed proxy serves your Statiz script — and its events — from a subdomain of your website, so tracking reads as first-party traffic. No proxy code for you to run: one DNS record and Statiz handles the routing and SSL.
Enable the proxy
- In Settings → General → Managed Proxy, enter a subdomain of your site, e.g.
a.yoursite.com, and click Enable. - Add the DNS record the page shows at your DNS provider — a
CNAMEfrom your subdomain to the target displayed in the table. - Click Check status until the badge reads Active — usually within 1–10 minutes of the DNS change.
- Replace the script tag on your site with the updated snippet: it now loads from
https://a.yoursite.comand sends its events there too.
a., cdn., io. Names like analytics, tracking or stats are on ad-block lists themselves.Set up the DNS record
The record is a plain CNAME at the root of your domain's DNS zone — the settings page shows the exact name and target for your site. Two things to watch:
- It must be a DNS record, not a redirect/forward — the script URL stays
https://a.yoursite.com/…. - Turn your DNS provider's own proxy off for this record (e.g. Cloudflare's orange cloud) so the CNAME resolves directly.
On Vercel deployments with VERCEL_API_TOKEN + VERCEL_PROJECT_ID configured, Statiz attaches the subdomain to the project and Vercel issues the SSL certificate automatically. Without them, add the subdomain once under Project → Settings → Domains yourself.
Self-hosted deployments
Your server needs to answer for the subdomain over HTTPS. With Caddy, on-demand certificates pair with Statiz's approval endpoint (only subdomains you enabled get a certificate):
on_demand_tls { ask https://your-statiz-host/api/proxy/allow } — certificate requests for any other hostname are rejected.Troubleshooting
- Status stays Pending — DNS usually propagates in 1–10 minutes; keep clicking Check status. If it shows a TXT record, Vercel is asking you to prove domain ownership — add it, then check again.
- “reaches a Statiz deployment that doesn't have this proxy enabled” — the CNAME points at a different Statiz instance. Make it point at the target shown in your settings.
- “answered by another server” — another service is on that subdomain, or your DNS proxy is on. Fix the record, then check again.
- Still blocked for some visitors — nothing beats every list; keep the subdomain neutral and avoid the obvious names.
Disabling the proxy in settings removes the routing and restores your original snippet — delete the DNS record whenever you like.