Running Plausible?

Plausible missing visits or self-host misbehaving? We fix it.

Plausible is deliberately small, and that is usually a feature until it is not. The self-hosted container falls over on a ClickHouse upgrade, the ad-blockers still eat 20% of the signal even on first-party domain, the goals you defined in April do not match the ones the warehouse reports, and the dashboard that was fast at 100k pageviews grinds at 10M. We tidy each piece so the numbers mean what you think they mean.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

plausible-ingest.log

still failing

What it is

Plausible at a glance

Plausible is a privacy-first, cookieless web analytics tool built in Europe and open-sourced in 2019. The commercial cloud version is run by Plausible Analytics OÜ in Estonia, and the same Elixir codebase can be self-hosted under AGPL with a Docker Compose or Kubernetes deployment backed by PostgreSQL and ClickHouse.

The product is deliberately narrow: pageviews, unique visitors, top pages, sources, countries, goals and custom events, with a single lightweight script tag. No cookies, no cross-site identifiers, no fingerprinting, which is the main pitch and the main reason Plausible is on the shortlist when a legal team says Google Analytics has to go. It is complementary to product analytics tools like Amplitude or PostHog rather than a replacement for them.

Type
Lightweight, cookieless web analytics
First released
2019
License
AGPL v3 for self-hosted; proprietary SaaS tier
Maintained by
Plausible Analytics OÜ, Estonia
Typically used for
Cookieless pageview and visitor analytics, source attribution, goal tracking, GDPR-friendly site measurement

The honest version

Plausible pros and cons

No technology is all upside. This is where Plausible earns its place and where it tends to cause trouble.

Where Plausible is strong

  • Cookieless by designNo cookie banner is required under GDPR or ePrivacy for Plausible-only analytics, which removes an entire category of consent friction from the site.
  • The script is tinyThe tracker is under 1KB gzipped, which barely registers on a Core Web Vitals score next to Google Analytics or a session replay tool.
  • Dashboard is readable without trainingA single page shows the handful of metrics most teams actually act on, which means marketing, product and support can all read it without a coaching session.
  • Self-hosting is a real optionThe open-source edition runs the same product as the cloud, so teams with data residency requirements have a credible path to keep everything on their own infrastructure.
  • First-party proxy supportRouting the script and events through your own domain sidesteps most ad-blockers, which materially improves sample coverage versus a third-party endpoint.
  • Reasonable pricing for cloudThe hosted plan prices by pageviews rather than per seat, which suits content sites and smaller SaaS teams without rewarding growth with a licence spike.

Where Plausible bites

  • Thin on product analytics featuresNo funnels across sessions, no cohort retention, no identified-user path analysis. Teams who need those have to pair Plausible with a product analytics tool.
  • Ad-blockers still cut coverageEven with a first-party proxy, sophisticated ad-blockers detect the script by other means and strip it. The sample is bigger than GA's but still not complete.
  • Self-hosted operations are not casualA ClickHouse plus PostgreSQL stack is not a Dockerfile-and-forget. Backups, upgrades and query tuning are real responsibilities that teams underestimate.
  • Custom property cardinality is cappedSoft limits on unique values per property mean you cannot shove user IDs or URLs in as custom props without breaking the dashboard.
  • Historical comparisons are session-sensitiveThe 30-minute visit window means pageviews, visits and unique visitors move together in ways that occasionally surprise people who are used to GA4 definitions.
  • Integrations ecosystem is modestFewer third-party integrations than GA4, fewer plugins than PostHog, and most of the ecosystem is community-maintained rather than official.

Sound familiar?

Common Plausible problems we fix

The Plausible problems that bring people to us, and what you have once each one is fixed.

proxy misconfigured: /api/event returns HTML

First-party proxy sends traffic to the wrong place

A reverse proxy rule that forwards /api/event to the site rather than to Plausible, which responds with the site HTML. Every event is lost and the dashboard shows nothing.

Proxy routing clean, events arriving

Script blocked: /js/plausible.js 404

Tracker script does not load

A CDN cache miss, a strict CSP that forbids the tracking domain, or an ad-blocker rule aimed at Plausible's known paths. The dashboard underreports in direct proportion to the blocked share.

Script delivered to a representative share of traffic

Goal 'signup' differs from warehouse by 18%

Goals disagree with source-of-truth data

A trigger that fires on page load of a thank-you page the user may navigate past, or a bot filter that strips real conversions along with the noise.

Goals match the business reality

ClickHouse: memory limit exceeded

Self-hosted queries fall over

A dashboard query over a long date range on a container that was sized for a quieter site. ClickHouse kills the query and the dashboard shows an error.

ClickHouse sized to the real workload

Postgres migration: relation already exists

Upgrade bails out mid-migration

A previous Plausible upgrade was interrupted, leaving the database in a half-migrated state. The next upgrade refuses to run until the state is reconciled.

Database aligned with the running version

Rocket Loader broke event tracking

Cloudflare optimization eats the tag

Cloudflare's Rocket Loader rewrites script tags to defer them, which races with Plausible's page load event. Some events fire against the wrong page, others never fire.

Tracker runs where the page actually loads

custom property has 5021 unique values

Dashboard slows as cardinality grows

A custom property that was supposed to be an enum is now carrying raw user IDs or URLs. ClickHouse holds up but queries take seconds longer and charts stall.

Custom properties back inside sensible limits

Request rate limited: 1000/min

Ingest rate limit hit on busy days

A campaign spike or a rogue script loop flooded the endpoint and cloud rate limiting kicked in. Later events are dropped.

Ingest paced inside the plan

What we do

Plausible help, from one wrong goal to the whole deployment

Reach out for one empty dashboard, or let us run the whole Plausible stack.

Rescue
Dashboard empty, self-hosted container refusing to upgrade, or goals disagreeing with the real numbers. We get it accurate before we tidy.
First-party proxy
Script and events routed through your own domain with sensible caching, CSP rules, and monitoring so an ad-block rule change does not go unnoticed.
Self-hosting
Docker Compose or Kubernetes deploy with proper backups, ClickHouse tuned to the traffic, PostgreSQL maintained, and upgrade runbooks that actually work.
Goals and custom events
Events aligned with the warehouse definition of a conversion, custom properties sized within the cardinality budget, and a reconciliation report when the numbers drift.
Migrations
Moving in from Google Analytics, Fathom or Simple Analytics, with a parallel period so historical comparisons are honest about the methodology change.
Managed Tech
Script coverage watched, self-hosted stack kept patched, ClickHouse health monitored, and a team to call when a Cloudflare feature update breaks the tracker.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Plausible alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Plausible questions

Something else? Call+1 737 727 7327

Why does Plausible undercount compared to Google Analytics?

Three reasons tend to account for most of the gap. Plausible has no fallback mechanism when the script is blocked, so ad-blocker rates show up directly in the number. The 30-minute visit window is tighter than GA's session logic. And Plausible deliberately filters bot traffic more aggressively. Running a first-party proxy closes much of the gap but not all of it.

Is self-hosting Plausible worth the operational effort?

For teams who want data on their own infrastructure, yes. For teams who just want a GA alternative with less consent friction, usually no. The cloud version is affordable, and running ClickHouse plus PostgreSQL plus the Elixir app is real work. We will tell you plainly which side of the line you are on before you commit.

Do I still need a cookie banner with Plausible?

Under current GDPR interpretation, Plausible's cookieless pageview measurement does not require consent, which is the reason many sites adopt it. Anything that adds identified users, custom cookies, or cross-site tracking changes that analysis, so the answer depends on what you combine Plausible with, not Plausible alone.

How do I bypass ad-blockers with Plausible?

The supported approach is a first-party proxy: your domain serves both the tracking script and the events endpoint, so the request never leaves your origin as far as the browser is concerned. This recovers most but not all of the signal, since some blocklists target scripts by content signature regardless of domain.

Can Plausible replace a product analytics tool like Amplitude?

No, and it is not trying to. Plausible answers questions about pages, sources and goals, not about user cohorts, funnels across sessions, or identified-user journeys. If your product questions need those, pair Plausible for site analytics with Amplitude, Mixpanel, or PostHog for product analytics.

How much does Plausible help cost?

An estimate is complimentary. Share whether you are on cloud or self-hosted, the current traffic volume, and the symptom you are seeing, and we come back with a bounded quote.

Free estimate

Plausible giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.