Plausible Analytics Not Working? Common Errors & Fixes

If Plausible shows no visits, the snippet is usually missing from the <head>, an old cached page is still served, or a consent banner, CSP or ad blocker stops the script. Confirm the snippet in the page source and a 200 request to plausible.io in the Network tab.

The verification tool can fail even when tracking works: it only visits the exact URL you added and can't see scripts loaded after consent or through an outdated proxy. If real visits appear in the dashboard, you can ignore the error.

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.

Plausible only displays custom events that have a matching goal in Site settings > Goals with the exact same name. Events sent before the goal existed are never backfilled, and CMS tools may break the plausible-event-name class.

next-plausible usually fails because the proxy config doesn't match the provider, the site is statically exported (rewrites don't run), or events are sent from a server component. Match src in PlausibleProvider and withPlausibleProxy and call usePlausible from a client component.

The official plugin excludes logged-in administrators by default, and its proxy breaks after caching, migrations or cloning. Enable admin tracking to test, then disable, clear caches and re-enable the proxy.

Plausible and GA4 count visitors differently, so a 10-20% gap is normal. Plausible often shows more visitors (no consent needed, blocked less), while lower numbers usually mean ad blockers, bot filtering or a missing proxy.

Plausible only records UTM tags and referrers on the first pageview of a new session (sessions last 30 minutes after the last pageview), and redirects that drop the query string turn campaigns into Direct / None.

Exceeding your tier once is ignored, but two consecutive months over the limit triggers an upgrade notice, and the dashboard locks if you don't upgrade within a week. Stats keep being collected and unlock when you upgrade or usage drops.

GA4 imports only cover dates before your first native Plausible visit and only what Google still retains (up to 14 months). If an import failed partway, delete it and re-run; goals, revenue and UTMs are never imported.

Use Site settings > Shields to block your IP addresses (both IPv4 and IPv6), or set the browser localStorage flag if your IP changes. WordPress users can exclude roles in the plugin.

After a Community Edition upgrade, pageviews can stop because ClickHouse migrations or settings didn't apply. Check the plausible and ClickHouse container logs, back up, and follow each major version's upgrade notes; rolling back restores logging while you fix it.

Sudden visitor spikes in Plausible are often bots. Cloud filters about 32,000 data-center IP ranges and uses behavioural detection; the self-hosted CE only filters by user agent and referrer spam, so use Shields (country, page, hostname) or block bots at your CDN.