Plausible Analytics Problems & Issues
Real user-reported problems, complaints, and limitations for Plausible Analytics. Based on analysis of 14 signals.
Overall score: 72/100
Issues by Category
Plausible not tracking visitors after installation
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.
Self-hosted Plausible CE is overrun by bot traffic
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.
Ad blockers still block Plausible unless you set up a proxy
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.
Plausible numbers don't match Google Analytics
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 raised prices and grandfathered older subscribers
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.
Why is Plausible so expensive for high-traffic sites?
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.
No free plan for Plausible Cloud
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.
Plausible dashboard locked after exceeding pageview limit
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.
Funnels, revenue and custom properties locked to the Business plan
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 open source edition missing features
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.
Plausible custom events and goals not showing
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
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.
Self-hosted Plausible upgrades break pageview logging
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.
Google Analytics import to Plausible is limited
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.
Regret Patterns
Common reasons users regret choosing Plausible Analytics.
Self-hosted to save money, then drowned in bot traffic
Moving to the free Community Edition removes the data-center IP and behavioural bot filtering, so visitor counts inflate and the stats become unreliable.
Needed funnels or revenue and had to double the bill
Starter covers basic stats, but funnels, custom properties and revenue require Business, roughly twice Starter's price at the same traffic.
Trusted numbers that ad blockers were quietly cutting
Sites with technical audiences launched without a proxy and later realised a meaningful share of visits was missing.
Created goals after the campaign launched
Events sent before a goal existed aren't backfilled, so early campaign conversions were never counted.
Outgrew it for product analytics
Teams expected to answer user-level and retention questions and had to add PostHog or Mixpanel alongside it.
Traffic growth pushed them up several tiers
Because pageviews and custom events across all sites count toward one tier, adding event tracking or another site can push a team into a pricier tier.
When Plausible Analytics Breaks Down
Specific scenarios where Plausible Analytics fails or underperforms.
Developer or privacy-conscious audience
Without a proxy, a larger share of visits is blocked by strict blocklists and dashboards undercount.
Aggressive page caching or optimisation plugins
Cached HTML without the snippet, or plugins like WP Rocket and Cloudflare optimisations altering the script, stop tracking until caches are purged and the script is excluded.
Self-hosted CE on a bot-heavy site
Basic user-agent filtering lets data-center bots through, inflating visitors many times over.
Major Community Edition upgrade
ClickHouse version and config changes between major versions can stop pageview logging until migrations are fixed or rolled back.
Server-side tracking via Events API or custom proxy
If the real visitor IP isn't forwarded in X-Forwarded-For, events are silently dropped as bots while the API still returns 202.
Viral traffic spike two months in a row
The dashboard locks a week after the upgrade notice unless you move to a higher tier.