How to Set Up Plausible Analytics on WordPress (Step-by-Step)

Google Analytics has been the default for over a decade. But if you care about your visitors’ privacy — or want GDPR compliance without a cookie consent banner cluttering your site — Plausible Analytics is worth a serious look.

Plausible is lightweight, open-source, and cookie-free. Its tracking script is under 1 KB (Google Analytics loads 45 KB+), it collects zero personal data, and it’s GDPR, CCPA, and PECR compliant out of the box — no banner required.

This guide covers the full setup on WordPress: account creation, plugin install, configuration, and verifying your first pageview.

Why Plausible Instead of Google Analytics

I switched sites to Plausible not because it’s trendy, but because GA4 created real problems: a consent banner that killed conversion rates, a 45 KB script dragging down Core Web Vitals, and a dashboard so complicated that half my clients couldn’t find basic traffic numbers. Plausible solves all three.

• No cookies, no consent banner. Plausible doesn’t use cookies. Under GDPR and the ePrivacy Directive, that means no popup required in the EU — which is a measurable improvement to first impressions.
• 1 KB tracking script. GA4 loads 45 KB+ of JavaScript. On a WordPress site already juggling plugin scripts, that difference shows up in Total Blocking Time and LCP scores. (See Core Web Vitals optimization without Google Analytics for the full picture.)
• One-page dashboard. Visitors, pageviews, bounce rate, referral sources, countries, devices — on a single screen. No training, no certification required.
• Your data stays yours. Plausible doesn’t feed data into an ad network. Google Analytics does, by design.
• Open source. The code is auditable on GitHub. Self-hosting is an option if you want zero third-party involvement.

If you’re still weighing Plausible against Matomo — which offers more control but significantly more complexity — the Matomo vs Plausible comparison breaks down which fits which type of site.

What You Need Before Starting

WordPress admin access and a Plausible account. That’s it — no developer needed.

Plausible Cloud starts at $9/month for up to 10,000 monthly pageviews, with a 30-day free trial and no credit card required upfront. [FACT-CHECK: verify current pricing tier and trial terms at plausible.io/pricing]

Step 1: Create Your Plausible Account

Go to plausible.io and register. The onboarding is straightforward:

1. Enter your email and create a password
2. Add your website domain (e.g., yourdomain.com — without https://)
3. Choose your reporting timezone
4. You’ll land on a page showing your tracking snippet — keep it open, but you won’t need to copy it manually if you use the WordPress plugin

The 30-day trial gives you enough time to compare Plausible data against GA4 side-by-side, then make a clean decision.

Step 2: Install the Official Plausible WordPress Plugin

Plausible maintains an official WordPress plugin that handles script injection automatically. No theme file editing required.

1. In your WordPress admin, go to Plugins → Add New
2. Search for “Plausible Analytics”
3. Click Install Now, then Activate
4. Go to Settings → Plausible Analytics
5. Enter your domain name exactly as you registered it in Plausible
6. Click Save Changes

The plugin injects the tracking script on every page automatically. Domain spelling matters: if you registered example.com in Plausible but enter www.example.com in the plugin, nothing will track.

Alternative: Manual Install Without a Plugin

Prefer fewer plugins? Add this to your child theme’s functions.php:

add_action('wp_head', function() {
    echo '<script defer data-domain="yourdomain.com" src="https://plausible.io/js/script.js"></script>';
});

Replace yourdomain.com with your actual domain. The defer attribute prevents the script from blocking page rendering.

Step 3: Configure Plugin Settings

The plugin ships with a few optional features that are worth switching on immediately:

• Enhanced measurements. Tracks file downloads, outbound link clicks, and 404 errors automatically — no extra code. [FACT-CHECK: verify these are the exact enhanced measurement options in the current plugin version]
• Custom events. Track specific actions — form submissions, CTA clicks, video plays — by adding CSS class names to elements. Add plausible-event-name=Signup to any element you want to track. [FACT-CHECK: verify this is still the correct CSS class attribute syntax for custom events]
• Proxy the script. Routes the analytics script through your own domain so ad blockers can’t detect it. The plugin has a built-in toggle for this — no server configuration needed. [FACT-CHECK: verify the proxy option exists and is built into the plugin — it may require specific plugin settings or a server-side component]
• Exclude admin visits. Keeps your own page views out of the data. In plugin settings, turn off “Track administrator.” [FACT-CHECK: verify the exact setting name in the current plugin UI]

For a content site or blog, enabling enhanced measurements and admin exclusion is the practical minimum. Custom events become relevant once you have specific conversions to measure.

Step 4: Verify the Installation

1. Open your site in a browser while logged out — or use incognito if you’ve excluded admin visits
2. Visit 2–3 pages
3. Go to your Plausible dashboard at plausible.io/yourdomain.com
4. You should see “1 current visitor” in real-time within a few seconds

If nothing shows up:

• Domain mismatch. www.example.com and example.com are different sites in Plausible. Check what you registered.
• Caching plugin. WP Super Cache, W3 Total Cache, LiteSpeed Cache — all can serve a stale page without the tracking script. Purge the cache after activating the plugin.
• Ad blocker. If you’re testing in a browser with an ad blocker, it may be blocking the Plausible script. Use the proxy option in plugin settings, or test from a clean browser profile.

Step 5: Remove Google Analytics

Remove Google Analytics once Plausible is confirmed working. There’s no reason to run both — you’re loading GA’s 45 KB script for data you’re not using, and the consent banner requirement doesn’t disappear just because Plausible is also installed.

GA code tends to hide in several places on a WordPress site:

• Google Site Kit plugin — deactivate and delete it
• Theme settings — many themes have a “Google Analytics ID” field in the Customizer
• Header/footer injection plugins — check Insert Headers and Footers or equivalent
• functions.php — search for gtag, UA-, or G-
• Tag Manager — if you’re using GTM, remove the GA4 tag from there

Run PageSpeed Insights before and after. The improvement in Total Blocking Time is usually visible in a single test.

What Plausible Tracks (and What It Doesn’t)

This matters for your privacy policy and for answering questions from clients or stakeholders who are used to GA4 reports.

Plausible tracks:

• Page URLs and referral sources
• Browser and operating system (from User-Agent, without fingerprinting)
• Country (derived from IP — the IP itself is never stored)
• Screen size category (mobile, tablet, desktop)
• UTM parameters
• Custom events (if configured)

Plausible does not track:

• Individual visitors or cross-day sessions
• Personal data (no stored IP addresses, no cookies)
• Cross-site browsing behavior
• Demographics (age, gender, interests)

For a content-focused site, aggregate data is all you actually need. Which pages get traffic, where visitors arrive from, which devices they use — that’s the decision-relevant information. The rest is noise that GA4 trains you to want but rarely changes what you do.

Optional: Set Up Custom Goals

Plausible supports goal tracking for measuring specific conversions. Common setups for WordPress sites:

• Newsletter signups. Track form submissions with a custom event on your opt-in form.
• CTA button clicks. Add the class plausible-event-name=CTA+Click to any button. [FACT-CHECK: verify CSS class syntax is current]
• File downloads. Automatic with enhanced measurements — tracks PDF, ZIP, and other downloads.
• 404 pages. Also automatic with enhanced measurements. Shows which broken links are actually getting hit.

To create a goal: Plausible dashboard → Settings → Goals → Add Goal. Choose between pageview goals (triggered by a specific URL visit) and custom event goals (triggered by JavaScript events). [FACT-CHECK: verify this navigation path is current in the Plausible dashboard UI]

Plausible vs Google Analytics: Quick Comparison

FAQ

Is Plausible accurate without cookies?

Yes. Plausible uses a hash combining the visitor’s IP address, User-Agent, and a daily rotating salt to identify unique visitors within a single day — without storing any personal data. The hash resets daily, so no visitor can be tracked across sessions. [FACT-CHECK: verify this is still the accurate description of Plausible’s unique visitor identification method]

Can I use Plausible and Google Analytics together?

Technically yes, but it defeats the point. Running both means you still load the heavy GA script and still need a consent banner. The practical approach: run both for the 30-day trial to compare data, then remove GA once you’ve confirmed Plausible gives you what you need.

Does Plausible work with WooCommerce?

Yes. You can track WooCommerce events — add to cart, purchase completion — using custom events. The plugin also tracks revenue if you configure e-commerce goals. [FACT-CHECK: verify Plausible plugin currently supports WooCommerce revenue tracking and what version/configuration this requires]

What about self-hosting Plausible?

Plausible Community Edition is free and self-hostable on any VPS running Docker. You’ll need at least 2 GB RAM and comfort with basic Docker operations. The trade-off is real: you own updates, backups, and server maintenance. For most WordPress site owners without a sysadmin background, the cloud version removes that overhead at a cost that’s usually justified. [FACT-CHECK: verify minimum server requirements for self-hosted Plausible CE — RAM, Docker version, etc.]

What’s Next

Plausible is running. Visitors aren’t being tracked with cookies, the analytics script isn’t dragging down your page speed, and you don’t need a consent banner.

If you’re still evaluating options, the Matomo vs Plausible comparison covers the trade-offs in detail — Matomo gives more control but adds real operational weight. Worth reading if you’re managing a site with specific compliance requirements.

For what to optimize once analytics are in place, the technical SEO checklist for privacy-first sites picks up from here.