# Plausible Analytics Problems & Issues 2026 - Not Tracking, Ad Blockers

Source: https://www.tryorbye.com/products/plausible
Last analyzed: 2026-10-21
Try or Bye score: 72/100

## Verdict: Try

Plausible Analytics is worth trying for most users (score 72/100). Most reported issues: Plausible not tracking visitors after installation; Ad blockers still block Plausible unless you set up a proxy; Why is Plausible so expensive for high-traffic sites?. Not a good fit for: Self-hosters wanting the full feature set; Product teams needing user-level analytics; Performance marketers. Users most often switch to Umami, Fathom Analytics, PostHog.

## What it is

Plausible Analytics is an open-source (AGPL) web analytics tool that shows pageviews, sources, pages, countries, devices, goals and funnels on a single dashboard without cookies or personal data. It targets bloggers, indie makers, agencies and businesses that want simple GDPR-friendly stats instead of Google Analytics. It is sold as a paid cloud service billed by monthly pageviews, and there is a free self-hosted Community Edition with fewer features.

## Common errors & fixes

### Plausible Not Tracking Visitors (No Stats Showing)

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.

1. **Check the snippet is in the page** — Open your site and view the page source (Ctrl+U, or Option+Command+U on Mac) Search for plausible.init or your plausible.io script Make sure it is inside <head> and matches the snippet from site settings exactly Remove any second copy of the snippet
2. **Purge every cache** — Clear your CMS/plugin cache (WP Rocket, LiteSpeed, etc.) Purge your host and Cloudflare/CDN cache Reload the page in a private window
3. **Check the network request** — Open DevTools > Network and reload Look for the plausible.io script request (starting with pa-) returning 200 Check the Console for Plausible or CSP errors If blocked by CSP, add plausible.io to your allowed script and connect sources
4. **Test without blockers** — Disable ad blockers, privacy extensions and VPN, or use another browser Visit the live domain, not localhost or a staging URL Check the realtime view in the dashboard
5. **Check Shields rules** — Go to Site settings > Shields Make sure your IP, country, page or hostname isn't excluded If using hostname allowlist, add the domain you're testing

Full guide: https://www.tryorbye.com/products/plausible/issues/not-tracking

### Plausible Verification Failed (Couldn't Verify Installation)

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.

1. **Verify manually** — View page source and search for plausible.init Open DevTools > Network, reload and confirm a request to plausible.io (pa-...) with status 200 Visit the site from another device and check the realtime dashboard
2. **Update the proxied script** — If you proxy the script, update your proxied copy to the latest snippet version Purge cache and re-run verification
3. **Load the script outside the consent gate** — Plausible is cookieless; after checking with your legal team, load it without waiting for consent Otherwise rely on manual verification instead of the tool

Full guide: https://www.tryorbye.com/products/plausible/issues/verification-failed

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

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.

1. **WordPress: enable the plugin proxy** — Install the official Plausible Analytics plugin Open its settings and enable the proxy toggle Clear all caches (WordPress, host, Cloudflare)
2. **Set up a proxy on your platform** — Follow Plausible's proxy guide for Cloudflare Workers, Vercel, Netlify, Nginx, Apache, Caddy or Laravel Serve the script and the /api/event endpoint from your own domain Update the snippet to point to the proxied paths
3. **Forward the real visitor IP** — Make sure the proxy passes X-Forwarded-For with the visitor's IP Check /api/event responses in DevTools for the header x-plausible-dropped: 1 (dropped even with a 202 status) Send X-Debug-Request: true to see which IP Plausible uses
4. **Use the managed proxy (Enterprise)** — On Enterprise, add the CNAME record Plausible gives you Update the snippet to the managed proxy domain

Full guide: https://www.tryorbye.com/products/plausible/issues/blocked-by-ad-blockers

### Plausible Custom Events and Goals Not Showing

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.

1. **Create the goal with the exact name** — Go to Site settings > Goals > + Add goal Choose Custom event Enter the event name exactly, with spaces instead of + (e.g. 'Button Click' for plausible-event-name=Button+Click) Trigger the event again; older events won't appear
2. **Fix the CSS class** — Inspect the element in the browser and check the class is plausible-event-name=Event+Name If your CMS turned '=' into '-', use '--' instead (plausible-event-name--Signup) In WordPress add it under Block > Advanced > Additional CSS class(es)
3. **Check the event request** — Open DevTools > Network and click the element Look for a request to /api/event If the response has x-plausible-dropped: 1, test on the live domain instead of localhost/staging If no request appears, the class or script isn't on that page
4. **Debug Google Tag Manager** — Use the official Plausible GTM template Open GTM Preview mode and confirm the trigger fires Publish the container (drafts don't run)

Full guide: https://www.tryorbye.com/products/plausible/issues/custom-events-not-showing

### Plausible Not Working in Next.js (next-plausible)

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.

1. **Match the proxy and provider config** — Wrap next.config with withPlausibleProxy In next-plausible v4, pass the same script src to withPlausibleProxy as to PlausibleProvider Rebuild and check that /js/script.js and /api/event load from your domain
2. **Don't rely on rewrites with static export** — If you use output: 'export', load the script directly from plausible.io or set up a proxy at your CDN (Cloudflare, Netlify, Vercel) Otherwise deploy with next start or Vercel so rewrites run
3. **Fix custom events in the App Router** — Move usePlausible calls into a component marked 'use client' Make sure PlausibleProvider wraps the layout Create a matching goal in Site settings > Goals
4. **Self-hosted instance** — Set customDomain to your Plausible CE URL Check the Network tab that requests go to your instance

Full guide: https://www.tryorbye.com/products/plausible/issues/nextjs-not-working

### Plausible WordPress Plugin Not Tracking

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.

1. **Track admins while testing** — Open the plugin settings Under 'Track analytics for user roles' enable Administrator Or test while logged out in a private window
2. **Reset the proxy** — Disable the proxy in plugin settings Clear all caches (WordPress, host, Cloudflare) Re-enable the proxy Clear all caches again
3. **Exclude the script from caching plugins** — Add the Plausible script URL to WP Rocket's (or your plugin's) JS exclusion list Purge cache
4. **Fix the plugin token** — Open https://plausible.io/YOURDOMAIN/settings/integrations?new_token=WordPress Create a token (it starts with plausible-plugin-) Paste it into the plugin's Plugin Token field
5. **Speed up a slow proxy** — Copy plausible-proxy-speed-module.php from the plugin's mu-plugin folder Paste it into wp-content/mu-plugins (create the folder if needed)

Full guide: https://www.tryorbye.com/products/plausible/issues/wordpress-plugin-not-tracking

### Plausible Numbers Different From Google Analytics

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.

1. **Compare like with like** — Run both tools in parallel for 2-4 weeks Compare unique visitors and pageviews, not sessions or engagement metrics Expect a 10-20% difference
2. **Recover blocked visits** — Set up a proxy so the script loads from your own domain Re-compare after a week
3. **Separate imported data** — Open the chart's options menu Turn off 'Include imported data' when comparing periods

Full guide: https://www.tryorbye.com/products/plausible/issues/numbers-lower-than-google-analytics

### Plausible UTM Parameters and Referrers Not Showing

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.

1. **Test in a fresh session** — Wait 30 minutes since your last pageview, or use another device, browser or network Click the tagged link and check the realtime dashboard
2. **Preserve query strings in redirects** — Check every redirect in the chain keeps ?utm_... parameters Link directly to the final URL in campaigns

Full guide: https://www.tryorbye.com/products/plausible/issues/utm-referrer-not-showing

### Plausible Pageview Limit Exceeded (Dashboard Locked)

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.

1. **Check what counts** — Open Account Settings > Subscription Review billable pageviews for the last 30 days Remember custom events count; pageview goals do not
2. **Block junk traffic** — Go to Site settings > Shields Block offending countries, IPs (max 30 entries, no ranges) or pages Use the Hostnames allowlist so only your real domains are recorded; blocked visits don't count toward usage
3. **Upgrade or wait** — Upgrade from the plan page (prorated) to unlock immediately Or wait for the next billing cycle; dashboards unlock automatically if usage is back within limits

Full guide: https://www.tryorbye.com/products/plausible/issues/pageview-limit-exceeded

### Plausible Google Analytics Import Failed or Missing Data

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.

1. **Re-run a failed import** — Go to Site settings > Imports & Exports Delete the failed import with the bin icon Click Google Analytics, pick the property, Continue, then Confirm import Wait for the completion email (large histories can take a couple of hours)
2. **Fix gaps or overlaps** — Check the import's date range in site settings Confirm when Plausible started recording Use CSV import to fill gaps if needed
3. **Recreate goals** — Add your goals in Site settings > Goals Accept that historical goal data stays in GA

Full guide: https://www.tryorbye.com/products/plausible/issues/google-analytics-import-failed

### How to Exclude Your Own Visits in Plausible

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.

1. **Block your IPs** — Go to Site settings > Shields > IP Addresses Click Add IP Address and use the button to add your current one Repeat for your IPv6 address Changes take effect within a few minutes
2. **Use the localStorage exclusion** — Follow Plausible's 'exclude your own visits' guide to set the ignore flag in each browser you use Repeat on every device and browser
3. **WordPress role exclusion** — In the Plausible plugin, choose which user roles are tracked Leave Administrator unticked

Full guide: https://www.tryorbye.com/products/plausible/issues/exclude-own-visits

### Self-Hosted Plausible CE Not Recording Pageviews

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.

1. **Read the logs** — Run docker compose logs plausible Check the ClickHouse container logs with docker compose logs Look for migration or missing-column errors
2. **Upgrade in stages with backups** — Back up Postgres and ClickHouse volumes Upgrade one major version at a time following the release notes Use the community-edition compose file for the target version Check health after each step
3. **Roll back if needed** — Restore the previous image tag and your backups Confirm pageviews log again Retry the upgrade after fixing the config

Full guide: https://www.tryorbye.com/products/plausible/issues/self-hosted-not-recording

### Plausible Bot Traffic Spike (Fake Visitors)

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.

1. **Use Shields** — Go to Site settings > Shields Add Countries or Pages that only bots hit Add your real domains to the Hostnames allowlist so other hosts are ignored
2. **Block at the edge** — Add WAF / bot-fight rules at Cloudflare or your CDN for the offending traffic
3. **Move to Cloud for advanced filtering** — If on CE, consider Plausible Cloud, whose bot filtering excludes data-center IP ranges and uses behavioural detection

Full guide: https://www.tryorbye.com/products/plausible/issues/bot-traffic-spike

## Common problems

- **Plausible not tracking visitors after installation** (reliability): The most common support topic: the dashboard stays on the blinking 'waiting for first pageview' screen. Plausible's own troubleshooting guide lists the usual causes: snippet not in the <head>, a stale page cache, a consent banner or plugin altering the script, a Content Security Policy that blocks plausible.io, duplicate snippets, or testing on localhost where the script disables itself.
- **Ad blockers still block Plausible unless you set up a proxy** (reliability): Plausible is blocked less often than Google Analytics, but some blocklists still block plausible.io. Plausible itself estimates roughly 5-25% of visitors can be hidden depending on the audience. Fixing it means a self-built proxy (Cloudflare, Vercel, Netlify, Nginx and others) or the WordPress plugin proxy; the managed proxy is Enterprise-only.
- **Why is Plausible so expensive for high-traffic sites?** (pricing): Entry pricing is $9/month for 10k pageviews, but every tier counts pageviews plus custom events across all sites in a team. Starter reaches $69/month at 1M and $169/month at 10M; Business costs $139 at 1M and $339 at 10M. Users comparing with free GA4 or Umami's free tier call it hard to justify for hobby sites.
- **Self-hosted Plausible CE is overrun by bot traffic** (reliability): The free Community Edition only filters bots by user agent and referrer spam. Cloud adds behavioural detection and excludes about 32,000 data-center IP ranges. One self-hoster reports a site with about 200 daily visitors showing over 5,000 on CE, making stats meaningless.
- **Plausible raised prices and grandfathered older subscribers** (pricing): One long-time customer reports the 100k pageview plan rose from $96 to $190 per year in July 2022, with existing subscribers kept on the old price. In November 2023 Plausible added a separate Business plan for funnels and ecommerce revenue; existing subscribers could stay on their plan but had to move to the newer, higher price list to unlock those features.
- **No free plan for Plausible Cloud** (pricing): There is only a 30-day free trial (no card needed). After that every cloud site needs a paid plan, which pushes small hobby sites toward self-hosting the Community Edition or switching to tools with free tiers.
- **Funnels, revenue and custom properties locked to the Business plan** (customization): Funnels, user journeys, ecommerce revenue attribution, custom properties, the Stats API and Looker Studio connector all require Business (from $19/month vs $9 Starter). Shared segments also moved to Business in 2025. Users who outgrow simple pageview stats find the jump to Business is where the real cost starts.
- **Plausible custom events and goals not showing** (usability): Events only appear once a matching goal exists in Site settings > Goals, names must match exactly including capitalisation, and events sent before the goal was created are not backfilled. Some CMSs (Webflow) rewrite the '=' in plausible-event-name class names, which silently breaks tracking.
- **Plausible too basic for product and marketing analytics** (usability): Reviewers note there are no individual visitor sessions, no retention or cohort reports, no ad-platform data connections and only device categories rather than screen sizes. Teams that need product analytics, attribution or A/B testing end up adding a second tool.
- **Plausible open source edition missing features** (customization): Funnels, user journeys, ecommerce revenue goals, SSO and the Sites API are Cloud-only. CE ships about twice a year while Cloud updates several times a week, and CE gets community support only. Self-hosters criticise Plausible for marketing open source while keeping core features out of it.
- **Self-hosted Plausible upgrades break pageview logging** (integrations): Upgrading CE between major versions involves ClickHouse version changes and new environment settings. A GitHub discussion describes a v1.4 to v2.1 upgrade where no pageviews were logged due to ClickHouse column errors until rolling back, and guides for v3 stress backups and staged upgrades.
- **Plausible numbers don't match Google Analytics** (reliability): Visitor counts differ from GA4 by design: Plausible needs no cookie consent and is blocked less, while GA4 may use modeled data. Plausible says a 10-20% gap is normal; a CSS-Tricks test saw about 15% more unique visitors in Plausible. Imported GA history follows GA's methodology and won't line up with native data.
- **Plausible dashboard locked after exceeding pageview limit** (pricing): One month over your tier is ignored, but two consecutive months over triggers an upgrade notice; if you don't upgrade within a week the dashboard is locked (stats keep being collected). A traffic spike or bot wave can force a more expensive tier.
- **Google Analytics import to Plausible is limited** (integrations): GA4 imports come in as daily aggregates only up to the first native Plausible visit. Goals and ecommerce revenue are not imported, UTM data isn't available from the GA API, and browser versions, exit pages and scroll depth are missing for imported periods. GA4 retention (max 14 months) limits how far back you can go.

## What users like

- **Simple one-page dashboard anyone can read**: The most cited reason people switch from GA4: all key metrics on one page, readable by non-analysts, with filters instead of report menus.
- **Cookieless and privacy-friendly**: No cookies or personal data are stored, which is why many sites run it without a consent banner (Plausible advises checking with your legal team). It also counts visitors who decline GA's cookie consent.
- **Lightweight script that doesn't slow pages**: The tracking script is tiny compared with Google Analytics, so it has negligible impact on page speed.
- **Open source with a self-hosted Community Edition**: The code is AGPL-licensed and can be self-hosted for free, giving full data ownership, though with fewer features than Cloud.
- **Shared and embeddable dashboards**: Growth and above include shared links and embedded dashboards, popular with agencies, open-source projects and public 'open startup' pages.
- **No extra charges for occasional traffic spikes**: Exceeding your pageview tier for a single month requires no action, and plans can be changed or cancelled any time with prorated billing and no long-term contracts.

## Pricing

- **Starter**: $9 (monthly) — hidden costs: Pageviews AND custom events count toward the tier, summed across all sites in a team. Yearly billing = 2 months free.
- **Growth**: $14 (monthly) — hidden costs: Price scales with combined pageviews + custom events. Two consecutive months over the limit force an upgrade or the dashboard is locked.
- **Business**: $19 (monthly) — hidden costs: Most features people outgrow Starter for live here, so real-world cost is about double Starter at the same traffic. 15% nonprofit/education/open-source discount is annual-only.
- **Enterprise**: monthly — hidden costs: Custom quote through sales.
- **Community Edition (self-hosted)**: $0 (free) — hidden costs: Your own server, ClickHouse + Postgres maintenance, backups and upgrades.

## Who should and shouldn't use it

- **Bloggers and content sites** — Good fit: Pageviews, sources and top pages on one screen is exactly what they need, and the script doesn't hurt page speed.
- **EU businesses avoiding cookie banners** — Good fit: Cookieless, no personal data, and EU-focused privacy positioning; many sites run it without consent prompts after legal review.
- **Agencies reporting to clients** — Good fit: Shared links, embedded dashboards and team access on Growth/Business make client reporting simple.
- **Indie hackers and open-source projects** — Depends: Love the simplicity, but no free cloud plan; many self-host CE or pick tools with free tiers. Open-source projects get 15% off Business annually.
- **Self-hosters wanting the full feature set** — Avoid: CE lacks funnels, revenue, SSO and advanced bot filtering, and ships only about twice a year.
- **Product teams needing user-level analytics** — Avoid: No individual sessions, cohorts, retention or feature flags; PostHog, Mixpanel or Amplitude fit better.
- **Performance marketers** — Avoid: No ad-platform connections or attribution modelling; GA4 remains the better fit for paid-ads work.
- **High-traffic publishers (millions of pageviews)** — Depends: Works technically, but cost reaches $169-339/month at 10M pageviews depending on plan.

## Alternatives

- **Umami**: Open-source, cookieless and visually similar, with no feature split between free and paid; cloud has a free tier up to 100k events. Trade-off: smaller team and fewer polished features like funnels-in-cloud parity.
- **Fathom Analytics**: Closed-source but nearly identical privacy-first feature set, starting at 100k pageviews for $15/month, so better value for mid-traffic sites. Trade-off: no self-hosting option.
- **PostHog** (https://www.tryorbye.com/products/posthog): Switch when you need product analytics, session replay, feature flags and A/B tests with a large free tier. Trade-off: far more complex and it also needs a proxy for ad blockers.
- **Google Analytics**: Free, with ad-platform integration and attribution that Plausible lacks. Trade-off: cookie consent, complex GA4 interface and Google data collection.
- **Matomo**: Open-source, self-hostable analytics closer to GA in depth (heatmaps, ecommerce, funnels via plugins). Trade-off: heavier interface and setup.
- **Simple Analytics**: Another EU privacy-first, cookieless tool aimed at the same buyers. Trade-off: closed-source, no self-hosting.
- **Mixpanel** (https://www.tryorbye.com/products/mixpanel): For event-based product analytics with funnels, retention and cohorts. Trade-off: not a drop-in website-traffic dashboard and uses identified users.

## FAQ

### Is Plausible Analytics worth it?

For blogs, marketing sites and agencies that want simple, cookieless traffic stats, yes: setup takes minutes and the dashboard is easy to read. It is not worth it if you need product analytics, user-level sessions or ad attribution, or if you run a hobby site and don't want to pay at least $9/month.

### Is Plausible Analytics free?

The cloud version is not free: there is a 30-day trial with no credit card, then plans start at $9/month for 10k pageviews. The self-hosted Community Edition is free (AGPL) but lacks funnels, revenue goals, SSO and advanced bot filtering.

### How much does Plausible cost?

At 10k monthly pageviews: Starter $9, Growth $14, Business $19 per month. At 100k: $19/$29/$39. At 1M: $69/$104/$139. At 10M: $169/$254/$339. Yearly billing gives 2 months free. Pageviews and custom events across all sites count toward the tier.

### Why is Plausible not showing any stats?

Usually the snippet isn't in the <head>, the page cache still serves the old HTML, a consent tool or CSP blocks the script, or you're testing on localhost or with an ad blocker. Check the page source for the snippet and the Network tab for a request to plausible.io returning 200.

### Does Plausible get blocked by ad blockers?

Less than Google Analytics, but some blocklists do block plausible.io; Plausible estimates 5-25% of visitors can be hidden depending on audience. Serving the script through a proxy on your own domain (Cloudflare, Vercel, Netlify, Nginx, WordPress plugin) recovers most of them.

### Does Plausible need a cookie banner?

Plausible uses no cookies and stores no personal data, which is why many sites run it without consent banners. Plausible itself says to confirm with your legal team whether consent is required in your situation.

### Why are Plausible numbers different from Google Analytics?

The tools count differently. Plausible doesn't need consent and is blocked less, so it often shows more visitors; GA4 can add modeled data. Plausible says a 10-20% difference is normal.

### What happens if I exceed my Plausible pageview limit?

Nothing for a single month. After two consecutive months over the limit you're asked to upgrade; if you don't within a week, dashboards are locked until usage drops or you upgrade. Stats keep being collected.

### Does Plausible have funnels?

Yes, but only on the Business plan and above in Plausible Cloud. Funnels are not available in the self-hosted Community Edition.

### Is self-hosted Plausible the same as Plausible Cloud?

No. The Community Edition is the same codebase but lacks funnels, user journeys, ecommerce revenue, SSO and the Sites API, uses only basic bot filtering, ships about twice a year and has community support only.

### Did Plausible raise its prices?

Yes. A long-time customer reports the 100k plan going from $96 to $190 per year in July 2022, with existing subscribers grandfathered. In November 2023 funnels and revenue moved to a new Business plan; existing subscribers could keep their old plan at the same price.

### Can I import Google Analytics data into Plausible?

Yes, GA4 properties can be imported (up to 5 per dashboard) as daily aggregates up to your first native Plausible visit. Goals, revenue and UTM data are not imported and some reports are unavailable for imported periods.

### What is the best Plausible alternative?

Umami for a free, fully open-source option; Fathom Analytics for a managed privacy tool with better mid-traffic pricing; PostHog if you need product analytics and session replay; GA4 if you need ad attribution for free.

---
Try or Bye aggregates problem patterns from user reviews, forums, and app stores. Methodology: https://www.tryorbye.com/methodology