Skip to main content

How to Get Started with Plausible Analytics (Privacy-Friendly Tracking in 2026)

Google Analytics can feel overwhelming, invasive, and complex for beginners. Plausible Analytics is the lightweight, privacy-friendly alternative that collects only what you actually need — visitors, pageviews, bounce rates, and traffic sources — without cookies, IP tracking, or selling your data. It's fully GDPR and CCPA compliant out of the box. In 2026, Plausible offers both a hosted plan (starting free) and a self-hosted Community Edition for total data control. This guide walks you through everything: choosing your setup, installing the tracking script, configuring goals, and reading your dashboard — all in plain English, no developer degree required.

What You Need

  • A website you can edit (WordPress, static HTML, Next.js, or similar)
  • Access to your site's HTML or a plugin like 'Insert Headers and Footers' for WordPress
  • A Plausible account — sign up free at plausible.io
  • For self-hosted only: a VPS (e.g., DigitalOcean, ~$5-20/mo), Ubuntu 22.04+, and Docker installed
  • For self-hosted only: basic comfort with a command line terminal
  • 15-30 minutes for hosted setup; 1-2 hours for self-hosted

Step 1: Choose Between Plausible Hosted or Self-Hosted

Before anything else, decide which version of Plausible fits your situation. There are two options: the hosted service at plausible.io, and the free self-hosted Community Edition (CE v5.2.1).

The hosted version is the right choice for most beginners. You sign up, add your site, paste a script, and you're done. No servers, no maintenance. Plans start free for under 10,000 pageviews per month, then jump to $9/month for up to 100,000 pageviews. Data is stored on EU servers by default.

The self-hosted Community Edition (open-source, AGPL license) is completely free but requires you to run it on your own server. You'll need a VPS with at least 2GB of RAM (DigitalOcean's basic droplet at $6-12/month works well), Docker installed, and PostgreSQL as the database. You clone the official GitHub repo at github.com/plausible/analytics, set environment variables like SECRET_KEYBASE, BASE_URL, and DATABASE_URL, then run the app with docker-compose up. Expect 1-2 hours for setup if you're new to servers.

Both versions give you the same core stats: unique visitors, pageviews, bounce rate, top pages, referrer sources, devices, and browsers — all without setting a single cookie or collecting personal data.

Recommendation for 2026 beginners: start with hosted. You can always migrate to self-hosted later if your needs change.

Pro Tip: If you're unsure, go hosted first. Plausible lets you export your data at any time, so switching to self-hosted later won't mean losing your history.

Plausible Analytics (Hosted)

Zero setup, EU-hosted by default, free for small sites, and you're tracking within 15 minutes. No server knowledge needed.

Visit →

Step 2: Create Your Plausible Account and Add Your Website

Go to plausible.io and click 'Start free trial'. Enter your email address and create a password. No credit card is required to start.

Once inside your dashboard, click 'Add a website'. Type your domain name exactly as it appears in the browser — for example, yourdomain.com (no https://, no www unless your site uses it). Click 'Add snippet'.

Plausible will now show you your unique tracking script. It looks something like this:

<script defer data-domain="yourdomain.com" src="https://plausible.io/js/script.js"></script>

Copy this entire snippet — you'll need it in the next step.

While still in your account, take a moment to verify your site settings under 'Site Settings'. Here you can set your timezone (important for accurate daily reports), add team members, and configure your reporting email frequency. Setting the correct timezone now prevents confusing date discrepancies later.

If you have multiple websites, you can add them all under the same account. Each site gets its own separate dashboard and tracking script.

Pro Tip: Set your timezone during site setup, not after. Changing it later shifts your historical data alignment and makes trend comparisons unreliable.

Plausible Analytics (Hosted)

The onboarding wizard guides you step by step, making site setup take under 5 minutes even for first-timers.

Visit →

Step 3: Install the Plausible Tracking Script on Your Website

This is the most important step. The tracking script must be placed in your site's HTML before the closing </head> tag. Here's how to do it across the most common platforms:

WordPress: Install the free 'Insert Headers and Footers' plugin (by WPCode). Go to Settings > Insert Headers and Footers, paste your Plausible script into the 'Header' box, and save. Done.

Static HTML sites: Open your main HTML file (usually index.html or a shared header template), find the line that says </head>, and paste your script on the line directly above it.

Next.js: Open pages/_document.js (or app/layout.js in Next.js 13+), import Script from 'next/script', and add the Plausible script tag with strategy='afterInteractive'.

Shopify: Go to Online Store > Themes > Edit Code, open theme.liquid, and paste the script before </head>.

After pasting, save your changes and visit your website in a browser. Go back to your Plausible dashboard — within 1-2 minutes you should see a real-time visitor count appear. That confirms the script is working.

Note: In 2026, Plausible's updated script supports data-attributes for optional features like outbound click tracking (add data-track-outbound to the script tag). No need to swap scripts — just add the attribute.

Pro Tip: After installing, open your browser's developer tools (press F12), go to the Network tab, reload your page, and search for 'plausible' or 'script.js'. If it appears with a 200 status, your script is loading correctly.

WPCode (Insert Headers and Footers)

Free WordPress plugin that lets you add the Plausible script without touching theme files. Survives theme updates automatically.

Visit →

Step 4: Set Up Your First Goals to Track What Matters

Raw pageview data tells you who visited. Goals tell you what they did. In your Plausible dashboard, click on your site, then go to 'Goals' in the top navigation and click 'Add goal'.

There are three types of goals to know:

  1. Pageview goals: Triggered when someone visits a specific URL. Example: set /thank-you as a goal to track form submissions that redirect to a thank-you page. Just type the path and save.

  2. Custom event goals: Triggered by JavaScript. First, create the goal in your dashboard by typing the event name (e.g., 'Signup'). Then add the trigger to your site's code or button: onclick="plausible('Signup')". When a visitor clicks that button, the event fires.

  3. Revenue goals (2026 feature): For e-commerce, fire events with a revenue value: plausible('Purchase', {revenue: 29.99}). This shows total revenue alongside conversion counts in your dashboard.

You can also add custom properties to goals — up to 3 per goal. For example, tracking which subscription plan a user signed up for: plausible('Signup', {props: {plan: 'pro'}}).

Start with just 2-3 goals: your main conversion (contact form, signup), a key page visit (/pricing), and optionally a purchase event if you sell anything. Don't create 20 goals at once — keep it focused.

Pro Tip: Always test your goals in an incognito browser window after setting them up. Fire the event, then check the Goals section of your dashboard to confirm it registered before sharing with your team.

Plausible Analytics Dashboard

Goal setup takes under 2 minutes per goal directly inside the dashboard — no external tag manager or coding required for pageview goals.

Visit →

Step 5: Build a Funnel to See Where Visitors Drop Off

Funnels show you the exact point where potential customers leave before completing your desired action. In Plausible's dashboard, find 'Funnels' in the navigation (available on all plans as of 2026) and click 'Create funnel'.

A funnel needs between 2 and 8 steps. Each step is a URL path or a custom event. A typical e-commerce funnel looks like this:

Step 1: /products (browsing) Step 2: /cart (added to cart) Step 3: /checkout (started checkout) Step 4: /order-confirmation (completed purchase)

A content site might use: Step 1: /blog (blog listing) Step 2: /blog/any-post (reading content) Step 3: /newsletter (reached signup page)

Once you save the funnel, Plausible shows you the percentage of visitors who make it through each step and the drop-off rate between steps. A 70% drop-off between /cart and /checkout, for example, signals a checkout problem worth investigating.

Combine funnel insights with the 'Top Pages' report to see if specific traffic sources or devices correlate with better funnel completion. Use the filter button to segment: for example, view the funnel only for mobile visitors or only for traffic from Google.

Pro Tip: If you don't have enough traffic for meaningful funnel data yet (under 500 visitors/month), skip funnels for now. Set them up and let data accumulate for 4-6 weeks before drawing conclusions.

Plausible Analytics Dashboard

Funnels are built directly inside Plausible with no third-party tools needed. Results update in real time as visitors flow through your site.

Visit →

Step 6: Read Your Dashboard and Understand Your Key Metrics

Plausible's dashboard is intentionally minimal — everything fits on one screen. Here's what each section means for beginners:

Unique Visitors: Individual people who visited your site. One person visiting 5 times still counts as 1 unique visitor for that period.

Total Pageviews: Every page loaded. Higher than unique visitors is normal and healthy.

Bounce Rate: Percentage of visitors who left after viewing only one page. A high bounce rate (above 70-80%) on a blog is often normal. For a landing page designed to drive signups, you want this lower.

Visit Duration: Average time spent per session. Under 30 seconds often means the page didn't match what visitors expected.

Top Sources: Where your visitors came from. Direct means typed your URL or used a bookmark. Organic Search means Google/DuckDuckGo. The 2026 'Top Channels' report automatically groups these by channel type.

Top Pages: Your most-visited content. Sort by bounce rate to find which pages keep people engaged vs. which lose them immediately.

To compare periods, click the date range selector and choose 'Compare to previous period' or 'Year over Year'. Use filters (the funnel icon) to drill into specific segments — for example, show only visitors from the United States using a mobile device.

Set up a weekly email report under Account Settings > Email Reports so you get a summary delivered automatically.

Pro Tip: Don't check your dashboard every hour. Set it to weekly email reports and review monthly trends instead. Short-term fluctuations are normal and rarely actionable — patterns over weeks matter.

Plausible Analytics Dashboard

The single-page dashboard loads in under a second and shows everything you need without clicking through multiple reports or menus.

Visit →

Step 7: Import Google Analytics Data and Invite Your Team

If you're migrating from Google Analytics (GA4), you don't have to lose your historical data. Plausible supports direct GA4 data import to give you continuity.

To import: go to Site Settings > Import & Export > Import from Google Analytics. Follow the authorization steps to connect your Google account. Select the GA4 property you want to import from and choose the date range. Plausible will pull in historical pageviews, sessions, and source data, which will appear in your dashboard alongside new Plausible data.

Note that GA4 data uses different counting methods than Plausible, so imported numbers will look slightly different from what you saw in Google Analytics. This is normal — Plausible counts unique visitors more conservatively because it doesn't use cookies or fingerprinting.

To invite team members: go to Site Settings > People > Invite. Enter their email address and assign a role. 'Viewer' lets them see the dashboard but not change settings. 'Admin' gives full access.

You can also create a public dashboard link (Site Settings > Visibility > Make public) to share your stats transparently with an audience — some content creators and indie makers publish their public Plausible dashboards as a trust-building move.

Pro Tip: When sharing your dashboard publicly, review your Goals section first. Public dashboards show goal conversion data too, which may include information you'd rather keep private (like revenue figures).

Plausible Analytics Dashboard

The built-in GA4 importer means you don't need any third-party migration tools — it's handled entirely within your Plausible account settings.

Visit →

Step 8: Set Up Spike Alerts and Ongoing Monitoring

Once Plausible is collecting data, set up automated alerts so you know when something unusual happens without having to check manually.

Spike alerts notify you when your traffic suddenly jumps above a threshold you set — useful for catching viral content, a mention on a popular site, or a sudden traffic surge from a news article. Go to Site Settings > Spike Notifications > Add notification. Set your threshold (e.g., alert me when more than 100 visitors arrive within an hour) and choose email or Slack delivery.

For Slack notifications, you'll need to create a Slack incoming webhook URL (free, takes 2 minutes in your Slack workspace settings) and paste it into Plausible.

For ongoing maintenance, check a few things monthly:

  • Review your Goals report to see if conversion rates are trending up or down
  • Check Top Pages for any pages with unusually high bounce rates
  • Look at your Top Sources to see if any new referrers have appeared
  • Compare the current month to last month using the period comparison tool

For self-hosted users specifically: monitor your server's RAM usage monthly. Plausible CE requires at least 2GB RAM, and as traffic grows you may need to upgrade your VPS. Check the official changelog at github.com/plausible/analytics/releases — Plausible releases updates frequently in 2026, and staying current ensures you have the latest features and security patches.

Pro Tip: Bookmark your Plausible dashboard and add a weekly 10-minute 'analytics review' to your calendar. Consistent small reviews beat sporadic deep-dives for actually acting on your data.

Slack (for spike notifications)

Free for small teams. Connecting Plausible spike alerts to a Slack channel means your whole team sees traffic spikes instantly without anyone needing to log in to Plausible.

Visit →

Common Mistakes to Avoid

Pasting the script after the </head> tag instead of before it

Fix: The script must go inside the <head> section, on the line directly above </head>. If placed in the <body> or after </head>, it may not fire on all pageloads. Use browser dev tools (F12 > Network tab) to confirm the script loads with a 200 status.

Using an outdated Plausible script from a tutorial written before 2026

Fix: Always copy your script fresh from your Plausible dashboard under Site Settings > Script. The 2026 script version supports data-attribute toggles for features like outbound tracking. Old scripts miss these capabilities and may lack future compatibility.

Creating too many goals at once before understanding your data

Fix: Start with 2-3 goals maximum: your primary conversion action and one or two key pages. Review those for 30 days, then add more. Too many goals clutters your dashboard and makes it harder to know which numbers actually matter.

Self-hosting on a server with less than 2GB of RAM

Fix: Plausible Community Edition requires at least 2GB RAM to run reliably. Under-resourced servers cause crashes under normal traffic. Start with DigitalOcean's 2GB Basic Droplet ($12/month) and monitor RAM usage via your server's dashboard before scaling up.

Not testing custom events before treating the data as reliable

Fix: After adding a custom event (e.g., a button onclick trigger), open an incognito browser, perform the action yourself, and immediately check your Plausible Goals dashboard. Confirm the event appears before assuming it works. Broken events silently collect zero data.

Self-hosting without setting up regular database backups

Fix: Your Plausible data lives in a PostgreSQL database on your server. Set up automated daily backups to an external location (DigitalOcean Spaces, Backblaze B2, or similar). Without backups, a server failure means permanent data loss.

Frequently Asked Questions

The hosted version of Plausible at plausible.io offers a free trial but is not permanently free — plans start at $9/month for up to 100,000 pageviews per month as of 2026. The self-hosted Community Edition (CE) is completely free and open-source under the AGPL license, but you pay for your own server hosting, typically $5-20/month on a VPS. For most small sites under 10,000 pageviews per month, the hosted trial period gives you enough time to evaluate whether it suits your needs before committing.

In most cases, no. Plausible does not use cookies, does not collect personal data, and does not build user profiles or track individuals across sites. Because of this, it generally does not trigger cookie consent requirements under GDPR or CCPA. However, privacy laws vary by country and situation — if you're unsure, consult with a legal professional familiar with your jurisdiction. Plausible publishes a detailed data policy at plausible.io/data-policy that you can reference in your own privacy policy.

No — Plausible's tracking script is under 1KB in size, which is roughly 45 times smaller than the Google Analytics script. It loads asynchronously, meaning it does not block your page from rendering. In practice, most website performance tests show zero measurable impact from the Plausible script. This is one of the reasons it's popular with site owners who care about Core Web Vitals and page speed scores.

Yes. You can add as many websites as you need under a single Plausible account. Each site gets its own dashboard, tracking script, and goals — they don't interfere with each other. On the hosted plan, your pageview allowance is shared across all sites in your account, so a 100,000 pageview plan covers 100,000 total pageviews across all your sites combined, not 100,000 per site.

The main differences are privacy, simplicity, and data ownership. Google Analytics collects detailed personal data, uses cookies, and shares data with Google's advertising network. Plausible collects no personal data, sets no cookies, and never sells your data. The Plausible dashboard shows everything on a single screen and takes minutes to understand, while Google Analytics (GA4 in 2026) requires significant learning time to navigate. The trade-off is that Plausible gives you less granular data — you won't get demographic breakdowns or individual user session recordings, but for most small to medium sites, the data Plausible provides is all you realistically need.

Conclusion

Plausible Analytics gives you everything you actually need to understand your website traffic — without the privacy headaches, cookie banners, or complexity of traditional analytics tools. In 2026, setup takes as little as 15 minutes using the hosted version. Start by signing up at plausible.io, paste the script into your site, set 2-3 meaningful goals, and check your dashboard weekly. As your confidence grows, add funnels, spike alerts, and custom events. You'll have cleaner data, a faster site, and a clearer conscience about your visitors' privacy.

You Might Also Like