Plausible Blocked by Ad Blockers (How to Set Up a Proxy)

Workaround available Web Updated October 21, 2026

Quick answer

Some blocklists block plausible.io, hiding roughly 5-25% of visitors depending on the audience. Serving the script and event endpoint through a proxy on your own domain fixes most of it.

Most likely fix: WordPress: enable the plugin proxy.

Symptoms

Visitor counts look low for a technical audience, uBlock/Brave block the request (ERR_BLOCKED_BY_CLIENT), or your own visits never appear.

Why it happens

  • Script loaded from the third-party plausible.io domain
  • Blocklists that include Plausible
  • Proxy not forwarding the visitor IP, so events are dropped as bots

How to fix it

Try these in order — the most common fix is first.

  1. 1. WordPress: enable the plugin proxy

    1. Install the official Plausible Analytics plugin
    2. Open its settings and enable the proxy toggle
    3. Clear all caches (WordPress, host, Cloudflare)
  2. 2. Set up a proxy on your platform

    1. Follow Plausible's proxy guide for Cloudflare Workers, Vercel, Netlify, Nginx, Apache, Caddy or Laravel
    2. Serve the script and the /api/event endpoint from your own domain
    3. Update the snippet to point to the proxied paths
  3. 3. Forward the real visitor IP

    1. Make sure the proxy passes X-Forwarded-For with the visitor's IP
    2. Check /api/event responses in DevTools for the header x-plausible-dropped: 1 (dropped even with a 202 status)
    3. Send X-Debug-Request: true to see which IP Plausible uses
  4. 4. Use the managed proxy (Enterprise)

    1. On Enterprise, add the CNAME record Plausible gives you
    2. Update the snippet to the managed proxy domain

This guide also covers

  • plausible ad blocker
  • plausible proxy
  • plausible blocked by ublock
  • plausible cloudflare proxy

Still not working?

If Plausible Analytics keeps failing, you're not alone. See every Plausible Analytics problem users report or the alternatives people switch to.

Other Plausible Analytics errors