Loading tutorials…
Loading tutorials…
Plausible is the easiest analytics tool to install — which is exactly why owners breeze through setup and lock in choices they later regret. The plan tier, timezone, and shared-link defaults are all hard to fix once data is flowing.
Who this is forOwners and founders switching to Plausible from GA4 (or starting fresh) who want privacy-first analytics that doesn't require a cookie banner. If you sell to EU customers or you're building on Stripe/Vercel/Linear and want the same minimalist aesthetic in your analytics, this is the start.
What you'll need
Step 1
Plausible bills by monthly pageviews + custom events combined. Pick a tier 25-50% above your expected volume so a traffic spike does not bump you mid-month.
Go to plausible.io and click Try it free for 30 days. Trial is full-featured, no credit card required.
Plans (2026): Growth starts $9/mo at 10K pageviews + events, scales up. Business adds funnels, custom properties, and longer history. Enterprise unlocks priority support and SSO.
Critical: a "pageview" counts as one billable event. A custom event (goal completion, button click, file download) also counts as one billable event. They are pooled — 8K pageviews + 5K events = 13K billable on a 10K plan.
Pick a tier ~25-50% above realistic monthly volume. Plausible is forgiving on temporary spikes — they will not auto-bill the next tier — but consistent overage triggers an email asking you to upgrade.
For sub-10K pageview sites, the Growth plan at $9/mo is the default. Most blogs, SaaS marketing sites, and small ecommerce stores live here for the first 12-24 months.
Step 2
After signup, you land on the Add a site screen. Enter the bare domain (no https://, no www) and pick the correct timezone — both are awkward to change later.
On the Add a site screen, enter the domain WITHOUT https:// and WITHOUT www: example "acme.com", not "https://www.acme.com". Plausible normalizes both www and non-www automatically.
Timezone: pick the timezone your business operates in. This controls how Day 1 / Day 2 reports bucket data and what time the daily/weekly email digests are sent.
You CAN change the timezone later (Site Settings → General → Reporting timezone) but historical reports stay in the old timezone — Plausible does not backfill.
After creating the site, Plausible shows you the install snippet. Do not install it yet — finish the account setup first so all the right tracking is in place from event 1.
For multi-domain businesses (acme.com + acme.io + acme.shop), you can either create separate sites OR use one site with subdomain tracking (covered in step 6). Decide upfront.
Step 3
Plausible can email you a weekly + monthly traffic digest plus a spike alert. Turn both on now or you will never look at the dashboard.
Site Settings → Email reports. Toggle Weekly traffic report ON. It arrives every Monday with last week's top stats.
Toggle Monthly traffic report ON. Arrives the 1st of every month with the previous month rollup. Forward this to your CEO/marketing lead automatically.
Site Settings → Email reports → Traffic spike notifications. Toggle ON. Plausible emails you when current-hour traffic exceeds the baseline by 3x — useful for catching viral moments AND bot floods early.
Add additional emails to receive these reports (Site Settings → Email reports → Add recipient). Useful for sending the weekly digest to a client or stakeholder without giving them dashboard access.
Why this matters: Plausible's biggest failure mode is "we set it up and never looked at it." Email digests force a weekly checkpoint without anyone remembering to log in.
Step 4
Plausible has Owner, Admin, and Viewer roles per site. Invite engineering and marketing as Admin; clients/stakeholders as Viewer; keep Owner to 1-2 people.
Site Settings → Visibility & Sharing → Team members → Invite team member.
Owner: the person who created the site, owns billing, can delete the site. Limit to 1-2 humans. Cannot be reassigned without contacting Plausible support.
Admin: can change settings, add goals, install scripts, invite users. Default for the marketing lead, developer, and operations.
Viewer: read-only dashboard access. Default for clients, board members, and anyone who only needs to see numbers.
For client-facing dashboards where you do NOT want to give Plausible login access, use Shared Links (Site Settings → Visibility & Sharing → Shared Links → Add Shared Link). Optional password protection. Send the URL to the client — they see the dashboard with no account required.
Audit team members quarterly. Plausible has no automatic offboarding — when an employee leaves, remove them manually.
Step 5
Office IPs, internal team browsing, and known bot traffic should be filtered before the snippet lands on the site. Otherwise you spend month one cleaning data.
Plausible automatically filters known bot user-agents (Googlebot, Bingbot, AhrefsBot, ~1,200 known crawlers). You do NOT need to configure this.
For internal-traffic exclusion, the recommended approach is the plausible-exclude localStorage flag. Visit your site, open DevTools → Console, run: localStorage.plausible_ignore="true". That browser is now excluded from tracking.
Have every team member do this once on every device they use. Document it in your onboarding wiki — new hires need to set this within their first week.
For office IP exclusion (more aggressive), you would need to either self-host (covered in tutorial #8) or use a CDN-level filter to skip the script on internal IPs. The localStorage approach is enough for most teams.
Site Settings → General → Excluded pages: add any internal paths you do NOT want tracked (e.g. /admin/*, /staging/*, /preview/*). Pageviews on these paths will not fire.
Step 6
If your site spans subdomains (app.acme.com, blog.acme.com) or multiple domains, decide upfront whether they share one Plausible site or get separate sites.
Default behavior: Plausible tracks pageviews on the exact domain you registered. blog.acme.com is NOT auto-tracked under acme.com.
Option A — one site with subdomain tracking: install the script with data-domain="acme.com" on all subdomains. All traffic rolls up to one dashboard. Cheaper (one plan) but less granular reporting.
Option B — separate sites per subdomain: install each subdomain as its own Plausible site. Granular reporting but doubles the cost (each site needs its own plan).
Recommended: one site for marketing-related subdomains (acme.com + blog.acme.com + docs.acme.com), separate site for the app (app.acme.com) because in-app behavior is fundamentally different from marketing.
For cross-domain tracking between completely separate domains (acme.com + acme.io), use the outbound-links + URL parameter approach — Plausible does not have a built-in cross-domain linker like GA4.
Step 7
Visit the dashboard with the test URL appended. You should see the empty-state with all reports ready. Confirm region, timezone, and date format are correct.
Go to plausible.io/[your-domain]. You will see the empty-state dashboard with all the standard reports (Top Sources, Top Pages, Devices, Countries) showing 0 visitors.
Click Sources → Channels. The list should be empty but the headers (Direct, Search, Social, Referral, Email, Paid Search) should all be visible.
Click the timezone label in the top right. Confirm it matches what you set in step 2.
Click the gear icon (Site Settings). Walk through every section once — General, Email reports, Goals, Funnels, Custom Properties, Team Members, Visibility & Sharing. Familiarity now saves time later.
You are now ready to install the tracking snippet — covered in detail in tutorial #2.
Common mistakes
Picking a plan tier without budgeting for custom events
What goes wrong: You pick the 10K Growth plan based on '8K pageviews/mo.' Then you add a 'scroll-depth' event firing on every page. Now you have 8K pageviews + 30K scroll events = 38K billable. Plausible emails you asking to upgrade to the 100K plan ($19/mo vs $9/mo). You do, then realize the scroll event is useless and you over-paid for 8 months.
How to avoid: Estimate pageviews + custom events combined when picking a plan. Audit every custom event for value before turning it on — see tutorial #3 for which events are worth tracking.
Setting the wrong timezone at site creation
What goes wrong: Reports look offset by a day forever. The Monday morning weekly digest arrives at 7 AM your time on Sunday because your timezone is set to America/Los_Angeles instead of your actual America/New_York. Year-over-year reports cross-fade across two days.
How to avoid: Set the correct timezone during site creation. If already wrong with <14 days of data, delete the site and recreate. Past 14 days, change it (Site Settings → Reporting timezone) and document the offset for historical reports.
No team members — only the founder has access
What goes wrong: When the founder is on vacation, the marketing lead can't pull the weekly numbers. The dev can't add a new goal. The agency can't update the snippet. Everyone is blocked on one person.
How to avoid: Always have 2+ Admins. Invite the marketing lead, the developer, and any agency working on the site as Admin. Clients get Viewer or a Shared Link. Document who has access.
Not enabling email reports
What goes wrong: Plausible gets installed. Two weeks later, no one has logged in. Three months later, no one has logged in. The data is being collected but never read. The $9/mo subscription is a sunk cost.
How to avoid: Enable Weekly + Monthly + Spike alerts in Site Settings → Email reports immediately after signup. Add the CEO + marketing lead as recipients. Force a weekly checkpoint without requiring login.
Including https:// or www in the site domain
What goes wrong: You add the site as 'https://www.acme.com' instead of 'acme.com'. Plausible accepts it but downstream the data-domain attribute on the snippet must match exactly. Half your pages stop tracking because they were served from 'acme.com' (no www).
How to avoid: Always register the bare domain: acme.com (no https://, no www). Plausible normalizes both www and non-www traffic automatically. If wrong, delete the site and recreate — there is no rename.
Not setting up Shared Links for clients
What goes wrong: A client asks for analytics access. You give them a Viewer seat. They forget their Plausible password, can't log in, ask you to export data manually every week. You spend 30 min/week being a manual report generator.
How to avoid: For clients and external stakeholders, use Shared Links (Site Settings → Visibility & Sharing → Shared Links). Optional password. Send the URL. They see the live dashboard with no account.
Recap
Done — what's next
How to install Plausible tracking on any site
Read the next tutorial
Hand it off
Account setup is the smallest part of getting Plausible to drive real decisions. Goal definitions, funnel design, UTM hygiene, and client-facing reports are where most teams stall. A vetted Plausible specialist on EverestX can set up the full account + goals + funnels + Shared Links in one focused 4-6 hour session — typically $60-100 total at $14-16/hr.
See specialist rates
Yes. Plausible does not use cookies, does not collect IP addresses (they are hashed and discarded), and does not collect any personal data. The EU Commission itself uses Plausible. You can remove your cookie banner if Plausible is your only tracking script.
No historical GA4 data can be imported into Plausible. GA4 and Plausible have fundamentally different data models. The migration path is: install Plausible alongside GA4, run both for 30-60 days to validate, then decommission GA4. See tutorial #7 for the full migration walkthrough.
GA4 is free but you pay in setup complexity, BigQuery export fees (if you need historical data), and the audit risk of cookie-banner non-compliance in the EU. Plausible starts at $9/mo for 10K pageviews + events. Most SMBs spend $9-39/mo on Plausible. Enterprise tier (1M+ pageviews) lands around $99-249/mo.
Yes — Plausible's script automatically detects History API navigation (used by all modern SPAs). Pageviews fire on every route change without any extra config. For Next.js App Router specifically, there is an official @plausible/nextjs package — covered in tutorial #2.
Hosted (plausible.io) is the managed SaaS — $9-249/mo by plan, zero ops burden. Self-hosted (open-source community edition, AGPL) runs on your infrastructure for free but you own ClickHouse, Postgres, and Docker ops. See tutorial #8 for the honest cost comparison — self-hosted is rarely cheaper after TCO unless you are 1M+ pageviews and have a real DevOps team.
Partially. Plausible tracks UTM parameters, referrer source, and goal completions — enough for most paid-ad attribution. What it does NOT do: feed conversion signals directly to Google Ads Smart Bidding (you still need GA4 or the Google Ads conversion tag for that), multi-touch attribution modeling, or cohort retention analysis. Most teams keep the Google Ads conversion tag firing alongside Plausible. See tutorial #6.
Plausible Analytics
Plausible has the simplest install of any analytics tool — one script tag. That's also why it's the easiest to install wrong: pick the wrong script variant, miss the data-domain attribute, or install through GTM without unblocking outbound clicks, and half your tracking silently breaks.
Plausible Analytics
Plausible's goal system is brutally simple — and that simplicity is what makes it powerful. Three types: pageview goals, custom events, and revenue goals. Most owners set up the wrong type, fire too many events, and blow past their plan. This is the discipline that prevents both.
Plausible Analytics
Most GA4 → Plausible migrations fail because owners flip the switch on day 1 and lose historical context. The right pattern is a 30-60 day parallel run: both tools firing, both dashboards monitored, then a clean cutover. This is the playbook.
Plausible Analytics
DIY Plausible is the right call up to a point. Then it isn't. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you're on.