Bypass adblockers with a proxy
Some visitors use adblockers or privacy tools that block analytics scripts. avasda is blocked far less than Google Analytics. Firefox and Safari do not block it by default, but some blocklist maintainers block all analytics regardless of privacy practices.
A proxy routes the avasda script through your own domain as a first-party request, making it indistinguishable from your own files. This bypasses most blockers and lets you count visits that would otherwise be missed.
Which option fits you
No proxy (default)
Run the default script from www.avasda.com. This is the simplest setup and works well for most sites. Expect some visitors with strict blockers to be missed, typically between 5% and 25% depending on your audience.
Use this when: accuracy gaps from adblockers are acceptable for your use case.
WordPress one-click proxy
The official WordPress plugin includes a built-in proxy you can enable with a single toggle in your plugin settings. No CNAME records, no server configuration, no maintenance.
Use this when: your site runs on WordPress.
Self-setup proxy
Route requests through your own infrastructure using a Cloudflare Worker, Vercel rewrite, Netlify redirect or reverse proxy. Requires developer access but is free and gives you full control.
Use this when: you are not on WordPress, have developer access, and want to manage the proxy yourself.
Guides: Cloudflare · Vercel · Netlify · Nginx · Apache · Caddy · Laravel
Managed proxy (Enterprise)
We handle the proxy for you. You set up a CNAME record pointing to our infrastructure, update the snippet on your site, and we take care of everything else. No ongoing maintenance on your end.
Use this when: you are not on WordPress and want the proxy without managing it yourself, or your infrastructure makes self-setup impractical.
Available on Enterprise plans. Contact us to discuss →
A note on IP forwarding
When your proxy forwards requests to avasda, the real visitor IP must be passed in the X-Forwarded-For header. If this header is missing or contains your server's IP instead of the visitor's, avasda's bot filter will drop the event silently. The API returns HTTP 202 either way.
Most CDN-level proxies such as Cloudflare Workers or Vercel rewrites handle this automatically. If you are writing a custom proxy function, set the header explicitly. See the Events API reference for how to verify which IP avasda is receiving.