Plausible takes about ten minutes to set up. No tag managers, no cookie banners, no consent prompts. Here’s every step.
I’ve set up Plausible on dozens of sites over the past few years, from small blogs to mid-size e-commerce stores. The process is the same every time, and it’s one of the reasons I keep recommending it as a privacy-first analytics tool. This guide walks you through every step, from account creation to sharing your dashboard with your team.
What You’ll Need
Before you start, make sure you have:
- A website you can edit (access to the HTML head, or a CMS that lets you add scripts)
- About 10-15 minutes
- A credit card or PayPal for the trial signup (Plausible is paid after the 30-day trial)
That’s it. No Google Tag Manager account, no cookie consent platform, no additional JavaScript libraries. Plausible runs a single lightweight script — under 1 KB — and doesn’t use cookies at all.
Step 1: Create Your Plausible Account
Head to plausible.io and click the free trial button. You’ll need an email address and a password.
What I always do first is add the site domain right away during onboarding. Plausible asks for this immediately. Enter your bare domain — yourdomain.com, not https://www.yourdomain.com. Plausible tracks all subdomains and paths under whatever you enter here, so keep it simple.
If you’re running a subdomain like blog.yourdomain.com as a separate property, add that as its own site instead.
One thing worth noting: Plausible offers both a cloud-hosted version and a self-hosted community edition. This guide covers the cloud version. The self-hosted setup involves Docker and is a different process entirely.
Step 2: Add the Tracking Script
After adding your domain, Plausible gives you a tracking snippet. It looks like this:
<script defer data-domain="yourdomain.com" src="https://plausible.io/js/script.js"></script>Paste this into the <head> section of your website. Where exactly depends on your platform:
Static HTML: Open your main HTML file and add it before the closing </head> tag.
WordPress: Use a plugin like “Insert Headers and Footers” or add it to your theme’s header.php. Plausible also has an official WordPress plugin that handles this for you.
Next.js / React: Add it to your _document.js or layout.tsx head section.
Webflow / Squarespace / Wix: Each has a “custom code” section in settings where you paste the snippet into the head area.
A common mistake here is adding the script to the body instead of the head. It will still work, but the defer attribute is designed for head placement — it tells the browser to download the script without blocking page rendering and execute it after the HTML is parsed.
Also, make sure you replace yourdomain.com with your actual domain. I’ve seen people skip this step and wonder why nothing shows up.
Step 3: Verify It’s Working
Once the script is live, open your website in a browser and then check your Plausible dashboard. You should see yourself as a real-time visitor within a few seconds.
If nothing appears, check these common issues:
- Ad blocker: Some ad blockers block Plausible’s default script URL. Try visiting your site in an incognito window with extensions disabled.
- Domain mismatch: The
data-domainattribute must exactly match what you entered in your Plausible account. - Caching: If your site uses aggressive caching (CDN, page cache plugin), clear the cache so the new script tag is served to browsers.
- Script not in head: View your page source (Ctrl+U) and confirm the Plausible snippet is present in the
<head>section.
If you’re using a proxy setup to avoid ad blockers (Plausible supports this), the script URL will be different. Check their docs for the proxy configuration.
Step 4: Set Up Goals and Events
Basic pageview tracking works out of the box. But if you want to track specific actions — form submissions, button clicks, file downloads, signups — you’ll need to set up goals.
Plausible supports two types of goals:
Pageview goals: Track visits to a specific page. Useful for thank-you pages after a form submission. In your Plausible dashboard, go to your site settings, click “Goals,” and add a pageview goal with the path (e.g., /thank-you).
Custom event goals: Track any interaction using JavaScript. First, create the goal in your Plausible dashboard (Settings > Goals > Add Goal > Custom Event). Give it a name like Signup or Download.
Then trigger it in your site’s code. You’ll need to use the enhanced script variant first. Update your snippet to:
<script defer data-domain="yourdomain.com" src="https://plausible.io/js/script.tagged-events.js"></script>Now you can fire custom events with JavaScript:
// Track a button click
document.getElementById('signup-btn').addEventListener('click', function() {
plausible('Signup');
});
// Track with custom properties
plausible('Download', {props: {format: 'PDF', title: 'Analytics Guide'}});The event name in your JavaScript must match the goal name in your Plausible dashboard exactly. Case matters.
I’ve written more about why tracking the right events matters in my guide on conversion rate optimisation best practices. Getting your goals right is the foundation of meaningful analytics.
Step 5: Configure Custom Properties (Optional)
Custom properties (sometimes called custom dimensions) let you attach extra data to your events. This is useful when you need more context than just “an event happened.”
For example, if you track downloads, you might want to know which file format was downloaded:
plausible('Download', {props: {format: 'PDF', category: 'Whitepapers'}});Or for an e-commerce site, you could track product categories on purchase events:
plausible('Purchase', {props: {category: 'Electronics', value: '149.99'}});Custom properties show up in your Plausible dashboard under the goal they’re attached to. You can filter and break down your data by any property you’ve sent.
A few things to keep in mind:
- Property names and values are strings. Even numbers should be sent as strings.
- You can send up to 30 custom properties per event.
- Properties are only visible in the dashboard after at least one event with that property has been recorded.
Don’t go overboard. Track what you’ll actually look at. I’ve made the mistake of setting up fifteen custom properties only to realise I only ever checked two of them.
Step 6: Share Your Dashboard
One of the features I appreciate most about Plausible is how easy it is to share your analytics. No account creation needed for viewers.
Go to your site settings and click “Visibility.” You have two options:
Public dashboard: Makes your stats visible to anyone with the link. Some companies do this for transparency — it’s a nice touch.
Shared link: Generates a private URL you can send to clients or team members. They can view the dashboard without logging in. You can optionally add a password for extra security.
This is one area where Plausible is genuinely better than most analytics tools. If you’ve ever tried giving a client access to analytics data, you know the usual process involves creating accounts, setting permissions, and explaining a complex interface. With Plausible, you send a link and you’re done.
If you’re comparing options for your team, I wrote a detailed comparison of Plausible and Umami that covers dashboard sharing and other differences.
Tips from Real Use
After running Plausible across multiple sites, here are the things I wish someone had told me on day one:
Use the proxy script in production. Ad blockers affect roughly 15-30% of visitors depending on your audience. Plausible’s documentation covers how to proxy the script through your own domain. It takes an extra 10 minutes and dramatically improves data accuracy.
Set up goals before you need them. Plausible only tracks goal conversions from the moment you create them — there’s no retroactive data. If you think you might want to track something, set it up now.
Check your data weekly, not daily. With a smaller, privacy-friendly dataset, daily numbers can be noisy — especially on lower-traffic sites. Weekly trends tell a much clearer story. Let it steep.
Don’t replicate your old GA setup. If you’re coming from a complex analytics configuration, resist the urge to recreate every single tracking event. Start with three to five key goals and add more only when you have a specific question to answer.
Use the API for reporting. Plausible has a straightforward stats API. If you need to pull data into a spreadsheet or build a custom report, the API is well-documented and doesn’t require OAuth — just an API key.
Combine with server-side data when needed. Plausible gives you the visitor-facing picture. For deeper analysis — revenue attribution, LTV calculations, funnel modelling — pair it with your server-side data. Plausible isn’t trying to be a full business intelligence tool, and that’s a feature, not a limitation.
The whole setup genuinely takes about ten minutes for the basics, and maybe thirty if you configure goals and custom properties. That’s a fraction of the time you’d spend on most analytics platforms, and you get clean, privacy-respecting data from the start.
