<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><generator uri="https://jekyllrb.com/" version="3.9.2">Jekyll</generator><link href="https://plausible.io/blog/feed.xml" rel="self" type="application/atom+xml"/><link href="https://plausible.io/" rel="alternate" type="text/html"/><updated>2026-11-18T12:15:34+00:00</updated><id>https://plausible.io/blog/feed.xml</id><title type="html">Plausible Analytics</title><subtitle>Plausible is a lightweight and open-source Google Analytics alternative. Your website data is 100% yours and the privacy of your visitors is respected.</subtitle><entry><title type="html">Google Analytics lacks many features to be a true Plausible replacement</title><link href="https://plausible.io/blog/google-analytics-lacks-plausible-features" rel="alternate" type="text/html" title="Google Analytics lacks many features to be a true Plausible replacement"/><published>2026-11-18T01:00:00+00:00</published><updated>2026-11-18T01:00:00+00:00</updated><id>https://plausible.io/blog/google-analytics-lacks-plausible-features</id><content type="html" xml:base="https://plausible.io/blog/google-analytics-lacks-plausible-features"><![CDATA[<p>Plausible just works. You don’t need a course to understand the dashboard. One click filters all the reports. Send a client a link, and they can explore the numbers without creating an account. Someone skips a step and buys anyway? Your funnel can handle that too.</p> <p>None of this feels particularly remarkable. Until you try doing it in Google Analytics.</p> <ol id="markdown-toc"> <li><a href="#a-dashboard-you-dont-have-to-build" id="markdown-toc-a-dashboard-you-dont-have-to-build">A dashboard you don’t have to build</a></li> <li><a href="#a-click-that-carries-your-question-through-the-dashboard" id="markdown-toc-a-click-that-carries-your-question-through-the-dashboard">A click that carries your question through the dashboard</a></li> <li><a href="#a-funnel-that-lets-people-take-a-shortcut" id="markdown-toc-a-funnel-that-lets-people-take-a-shortcut">A funnel that lets people take a shortcut</a></li> <li><a href="#a-link-your-client-can-actually-open" id="markdown-toc-a-link-your-client-can-actually-open">A link your client can actually open</a></li> <li><a href="#realtime-without-leaving-the-dashboard-you-know" id="markdown-toc-realtime-without-leaving-the-dashboard-you-know">Realtime without leaving the dashboard you know</a></li> <li><a href="#counting-visits-without-asking-visitors-to-accept-analytics-cookies" id="markdown-toc-counting-visits-without-asking-visitors-to-accept-analytics-cookies">Counting visits without asking visitors to accept analytics cookies</a></li> <li><a href="#more-of-the-bot-cleanup-done-before-you-open-your-stats" id="markdown-toc-more-of-the-bot-cleanup-done-before-you-open-your-stats">More of the bot cleanup done before you open your stats</a></li> <li><a href="#the-option-to-look-inside-or-run-it-yourself" id="markdown-toc-the-option-to-look-inside-or-run-it-yourself">The option to look inside, or run it yourself</a></li> <li><a href="#enough-features-for-whom" id="markdown-toc-enough-features-for-whom">Enough features for whom?</a></li> </ol> <h2 id="a-dashboard-you-dont-have-to-build">A dashboard you don’t have to build</h2> <p>Open Plausible and your visitors, traffic sources, pages, locations, devices and goals are <a href="https://plausible.io/plausible.io">already there</a>. You can change the date and start looking around. Nobody needs to decide which reports belong in your dashboard before you can use it.</p> <p>GA4 gives you reports, report collections and a separate area called Explorations for building more reports. You can customize a great deal. You can also spend a great deal of time customizing things you expected to find when you opened your analytics.</p> <p>An analyst might enjoy that freedom. Someone who needs to check how yesterday’s newsletter performed before getting on with today’s work might appreciate a finished dashboard.</p> <h2 id="a-click-that-carries-your-question-through-the-dashboard">A click that carries your question through the dashboard</h2> <p>Say you want to know which sources brought people who signed up.</p> <p>In Plausible, click your signup goal. The dashboard now shows the traffic that converted: where it came from, which pages people visited, the devices they used. Click a country if you want to narrow it down further. The rest of the dashboard follows along.</p> <p>You don’t have to work out where the next part of your question belongs. You keep clicking on what interests you.</p> <p>GA4 has filters, comparisons and segments. You can investigate these questions there too. What it doesn’t give you is Plausible’s <a href="https://plausible.io/docs/filters-segments">click-to-filter workflow</a> across one dashboard. You move between reports and choose how to break down the data, or build an exploration with the dimensions and metrics you need.</p> <p>It’s easy to count “segmentation” as a feature in both products and leave it there. But those are quite different experiences of having a question and getting an answer.</p> <h2 id="a-funnel-that-lets-people-take-a-shortcut">A funnel that lets people take a shortcut</h2> <p>Someone views a product, skips the details page and buys it. That sounds like a successful visit.</p> <p>But put “View product → View details → Purchase” into a funnel that requires every step, and that person becomes a drop-off. They bought the product. They just didn’t follow your instructions for buying it.</p> <p>Plausible’s <a href="https://plausible.io/docs/funnel-analysis">flexible funnels</a> let you keep those middle steps visible without making them compulsory. Visitors need to complete the first and last steps to count as converted. You can see whether they viewed the details without treating everyone who skipped them as a lost customer.</p> <p>GA4’s <a href="https://support.google.com/analytics/answer/9327974">funnel explorations</a> stop counting someone in subsequent steps when they skip a step. An open funnel lets people enter partway through, but it doesn’t make the middle steps optional. You can remove the details step to measure product-to-purchase conversion, but then you lose that step from the same funnel.</p> <p>Did people buy, and which steps did they actually need along the way? You should be able to answer both in the same funnel.</p> <h2 id="a-link-your-client-can-actually-open">A link your client can actually open</h2> <p>“Here’s the dashboard.”</p> <p>Ideally, that should be the whole message.</p> <p>With Plausible’s <a href="https://plausible.io/docs/shared-links">shared links</a>, someone can open your dashboard without an account. They can change dates and explore the numbers themselves. You can add a password or restrict a link to a particular segment if they should only see part of the data.</p> <p>GA4’s native report links require the recipient to <a href="https://support.google.com/analytics/answer/10607999">have access to the property</a>. You can export a report or create something in Looker Studio, but now you’re sending a snapshot or maintaining another reporting setup.</p> <p>Sending someone your dashboard shouldn’t come with an onboarding task.</p> <h2 id="realtime-without-leaving-the-dashboard-you-know">Realtime without leaving the dashboard you know</h2> <p>You’ve just launched something. Visitors are arriving. Naturally, you want to know where they’re coming from and what they’re doing.</p> <p>In Plausible, select <a href="https://plausible.io/real-time-web-analytics">Realtime</a>, or press R. The same dashboard switches to live activity and updates automatically. The sources, pages and goals are still there. So are the filters.</p> <p>GA4 has realtime reports too. The catch is that they’re a separate, more limited view. Google’s <a href="https://support.google.com/analytics/answer/11198161">data freshness documentation</a> describes realtime as covering fewer dimensions and metrics than its other reporting, with standard intraday processing typically taking two to six hours.</p> <p>The questions don’t suddenly become simpler because a launch is happening right now. Being able to use the same reports and filters matters just as much while it’s underway.</p> <h2 id="counting-visits-without-asking-visitors-to-accept-analytics-cookies">Counting visits without asking visitors to accept analytics cookies</h2> <p>Plausible doesn’t use cookies or persistent identifiers, or build profiles of individual visitors. You can understand which pages people read and which sources bring conversions without following someone around the web.</p> <p>That means you don’t need a cookie consent banner <a href="https://plausible.io/privacy-focused-web-analytics">for Plausible itself</a>. Other tools on your website may still need one.</p> <p>GA4’s usual measurement uses cookies. Google offers <a href="https://support.google.com/analytics/answer/10000067">consent mode</a>, including an advanced implementation that can send cookieless pings when consent is denied. Eligible properties can also use <a href="https://support.google.com/analytics/answer/11161109">behavioral modeling</a> to estimate otherwise unobservable activity.</p> <p>Those are ways of adapting Google’s measurement to consent choices. They don’t turn GA4 into Plausible’s approach to collecting aggregate stats without persistent visitor identifiers in the first place.</p> <p>“Configure consent handling, then work out whether modeling applies” is a fairly substantial task to take on just to count website visits.</p> <h2 id="more-of-the-bot-cleanup-done-before-you-open-your-stats">More of the bot cleanup done before you open your stats</h2> <p>A traffic spike should give you something useful to investigate. It shouldn’t routinely give you a new cleanup job.</p> <p>Plausible <a href="https://plausible.io/docs/bot-traffic-filtering">filters bot and spam traffic automatically</a>. That includes detecting automated browsers, blocking known bots and referrer spam, filtering known data center IP ranges and checking for traffic patterns that don’t look like human browsing. These checks run before the traffic reaches your dashboard.</p> <p>GA4 <a href="https://support.google.com/analytics/answer/9888366">automatically excludes known bots</a> too. Google also documents <a href="https://support.google.com/analytics/answer/18765056">custom traffic filters</a>, currently rolling out to eligible properties, that let you exclude suspicious traffic by combining attributes like location, browser and source. But identifying a pattern and configuring a rule is work you have to do.</p> <p>We <a href="https://plausible.io/blog/testing-bot-traffic-filtering-google-analytics">tested the difference in May 2025</a> by installing both tools on the same site and sending only simulated bot traffic. We tried an obviously non-human browser identity, bots posing as normal browsers and visits from data center IP addresses. GA4 recorded traffic from all three tests. Plausible recorded none. We checked GA4’s standard reports after allowing time for processing, and the bot traffic was still there.</p> <p>No tool catches every bot. But automatic filtering, with improvements applied in the background, leaves less cleanup for you. That’s more time to understand real visitors instead of identifying fake ones.</p> <h2 id="the-option-to-look-inside-or-run-it-yourself">The option to look inside, or run it yourself</h2> <p>With Plausible, you can <a href="https://github.com/plausible/analytics">inspect the source code</a>. If you want to operate the software on your own infrastructure, there’s <a href="https://plausible.io/self-hosted-web-analytics">Plausible Community Edition</a>.</p> <p>You can use our managed service or run Plausible yourself. If you choose to self-host, you’re responsible for the servers, updates and maintenance.</p> <p>There isn’t a Google Analytics edition you can install on your own server. Exporting data to BigQuery gives you another way to work with the data; it doesn’t let you run Google Analytics.</p> <p>For someone who chose Plausible partly because they could inspect and host it, that’s a missing capability. No amount of extra reports makes up for it.</p> <h2 id="enough-features-for-whom">Enough features for whom?</h2> <p>Google Analytics offers capabilities Plausible doesn’t, including remarketing audiences and cross-device measurement. If those are what you need, they matter.</p> <p>But so does opening a dashboard without needing a course. So does handing it to a client without an access request. So does measuring your website without adding analytics cookies to your visitors’ browsers.</p> <p>For the people who choose Plausible, they’re often the features they came for.</p>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Useful Plausible features that GA4 lacks or makes harder to use.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png"/><media:content medium="image" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">What is server-side tracking and how to set it up?</title><link href="https://plausible.io/blog/server-side-tracking-guide" rel="alternate" type="text/html" title="What is server-side tracking and how to set it up?"/><published>2026-11-11T18:30:00+00:00</published><updated>2026-11-11T18:30:00+00:00</updated><id>https://plausible.io/blog/server-side-tracking-guide</id><content type="html" xml:base="https://plausible.io/blog/server-side-tracking-guide"><![CDATA[<p>You can measure website visits and goal conversions without collecting personal profiles. For instance, when an account is created on your website, its server can send a simple signup event to your analytics tool. You decide what to send and the visitor does not need to load an analytics script for that event to be recorded.</p> <p>This is server-side event tracking. It gives you control over the data leaving your website and helps you record successful actions even when browser tracking is blocked.</p> <p>This guide explains the privacy and data quality benefits, then walks through recording a confirmed signup with Plausible’s Events API.</p> <ol id="markdown-toc"> <li><a href="#what-does-server-side-tracking-mean-here" id="markdown-toc-what-does-server-side-tracking-mean-here">What does server-side tracking mean here?</a></li> <li><a href="#why-consider-server-side-events" id="markdown-toc-why-consider-server-side-events">Why consider server-side events?</a> <ol> <li><a href="#privacy-control-exactly-what-data-you-send" id="markdown-toc-privacy-control-exactly-what-data-you-send">Privacy: control exactly what data you send</a></li> <li><a href="#data-quality-record-confirmed-actions-without-browser-blockers" id="markdown-toc-data-quality-record-confirmed-actions-without-browser-blockers">Data quality: record confirmed actions without browser blockers</a></li> <li><a href="#keep-browser-measurements-alongside-confirmed-outcomes" id="markdown-toc-keep-browser-measurements-alongside-confirmed-outcomes">Keep browser measurements alongside confirmed outcomes</a></li> </ol> </li> <li><a href="#what-can-server-side-tracking-miss" id="markdown-toc-what-can-server-side-tracking-miss">What can server-side tracking miss?</a></li> <li><a href="#how-plausibles-events-api-works" id="markdown-toc-how-plausibles-events-api-works">How Plausible’s Events API works</a> <ol> <li><a href="#example-track-a-confirmed-signup" id="markdown-toc-example-track-a-confirmed-signup">Example: Track a confirmed signup</a> <ol> <li><a href="#1-add-the-goal" id="markdown-toc-1-add-the-goal">1. Add the goal</a></li> <li><a href="#2-send-the-event-after-the-account-is-saved" id="markdown-toc-2-send-the-event-after-the-account-is-saved">2. Send the event after the account is saved</a></li> <li><a href="#3-forward-the-visitor-details-correctly" id="markdown-toc-3-forward-the-visitor-details-correctly">3. Forward the visitor details correctly</a></li> <li><a href="#4-prevent-duplicate-sends-and-protect-signup" id="markdown-toc-4-prevent-duplicate-sends-and-protect-signup">4. Prevent duplicate sends and protect signup</a></li> <li><a href="#5-verify-the-result" id="markdown-toc-5-verify-the-result">5. Verify the result</a></li> </ol> </li> </ol> </li> <li><a href="#start-with-one-confirmed-action" id="markdown-toc-start-with-one-confirmed-action">Start with one confirmed action</a></li> </ol> <h2 id="what-does-server-side-tracking-mean-here">What does server-side tracking mean here?</h2> <p>Server-side means the collection happens on a server rather than in the visitor’s browser. An analytics service then turns that data into reports. You can add collection to your own website or use a service that measures traffic passing through its servers.</p> <p>There are three approaches worth distinguishing:</p> <ul> <li><strong>Server logs</strong> record requests for pages, images and other files reaching a web server, including requests from bots. Log analysis tools turn those records into reports.</li> <li><strong>Client-side tracking</strong> uses JavaScript in the visitor’s browser to record pageviews and interactions such as clicks.</li> <li><strong>Server-side events</strong> record actions your website’s server confirms, such as a successfully created account, and send them directly to your analytics tool.</li> </ul> <p>Our <a href="/blog/server-log-analysis">server logs vs JavaScript analytics article</a> covers the differences in detail. Here, we’ll focus on setting up server-side events. You choose when an action counts and send an event at that point. There is no need to import or analyse server logs.</p> <h2 id="why-consider-server-side-events">Why consider server-side events?</h2> <p>Server-side events give you control over what your website sends and let you record successful actions without depending on a separate analytics request from the browser.</p> <h3 id="privacy-control-exactly-what-data-you-send">Privacy: control exactly what data you send</h3> <p>Your website’s server sends the analytics event. You choose what information to include before it leaves your server. That includes the event name and any extra details. You can send it directly to your analytics tool without loading a third-party analytics script in the visitor’s browser.</p> <p>For a completed signup, you can send an event describing the action while keeping the person’s email address and account details in your own database. Send only the details you need rather than the full contents of the signup form. Check page URLs and custom properties, the extra details you attach to events, for personal information too.</p> <p>This control is useful when your organisation wants to minimise data collection or restrict third-party scripts as part of its privacy requirements.</p> <p>Moving collection to a server does not automatically make it GDPR compliant. What you collect and what the recipient does with it still matter. Sending data to Google Analytics or an advertising service through your server does not, by itself, change what those services do with it. Server logs can also retain IP addresses and sensitive URLs, so check what your own website and hosting provider store too.</p> <h3 id="data-quality-record-confirmed-actions-without-browser-blockers">Data quality: record confirmed actions without browser blockers</h3> <p>A browser ad blocker can prevent an analytics script from loading or stop it from sending data. Once your website’s server has completed an action, it can send the event directly to your analytics tool. A browser extension cannot block that server-to-server request and the visitor does not need to keep the tab open for it to be sent.</p> <p>You can also record the outcome at the point it becomes true. Send <code class="language-plaintext highlighter-rouge">Signup</code> after your website creates an account rather than counting a click on “Create account” or a visit to a thank-you page. With the event sent once after account creation, a failed form submission or a reload of the confirmation page should not produce another signup event.</p> <p>That improves the meaning and delivery of your conversion data, but you still need to handle failed API requests and prevent duplicate sends. Automated activity from bots also needs to be filtered out. Your website’s account records remain the source to check for how many accounts were created. Analytics helps you understand which visits led to those signups.</p> <h3 id="keep-browser-measurements-alongside-confirmed-outcomes">Keep browser measurements alongside confirmed outcomes</h3> <p>Adding server-side events does not require removing browser tracking. You can keep pageviews, referral information and scroll depth from the browser while sending confirmed signups from your server.</p> <p>Combining browser measurements with server-confirmed outcomes lets you understand both the visit and its result. Your analytics tool needs to support both collection methods. Browser behavior, such as scrolling, still needs to be measured in the browser.</p> <p>This lets you see how people use your pages alongside the actions your server confirms. It does not recover browser measurements that were blocked or never sent. A server-side signup can still be counted without its original referral source if there is no matching visit and you send no referral or campaign details. Record each signup in one place so the browser and server do not both count it.</p> <h2 id="what-can-server-side-tracking-miss">What can server-side tracking miss?</h2> <p>Your server can record what it handles, but it cannot automatically see everything happening in the visitor’s browser. These are limits on what a server-only setup collects. Adding server-side events does not remove information already collected by browser tracking or disable those reports in your dashboard.</p> <ul> <li><strong>Interactions that do not contact the server.</strong> Scrolling through an article, clicking an outbound link or opening a menu may happen entirely in the browser. You need browser code to observe those actions and send an event if you want to measure them.</li> <li><strong>Pageviews that do not reach your server.</strong> A page loaded from the browser’s cache or navigation handled entirely within a single-page website may not produce a new request to your server. Recording server requests alone will miss those views.</li> <li><strong>Where a visitor originally came from.</strong> A server-side signup does not automatically tell you the visitor’s original referral source or campaign. Your setup needs to supply those details or connect the event to a visit where they were already recorded. How that connection works depends on your analytics tool. Recording the signup does not recover a landing pageview that was never recorded.</li> </ul> <p>Browser tracking is useful for collecting the wider picture of a visit, including pageviews, referral sources, campaigns and engagement measurements. Your server can add confirmed outcomes. With server-only collection, you need to supply visit details explicitly and browser-only behavior still needs browser code to measure it.</p> <p>Server-side tracking also needs code you maintain: deciding when to send events, handling failed sends and preventing duplicates. The walkthrough below uses browser pageviews alongside one server-side signup event, so it does not require moving all collection to your server.</p> <h2 id="how-plausibles-events-api-works">How Plausible’s Events API works</h2> <p>Plausible is <a href="/privacy-focused-web-analytics">privacy-friendly by default</a>, including when you use our JavaScript snippet in the browser. It uses no cookies or persistent visitor identifiers and does not track people across websites. Server-side collection gives you additional control over what you send, but you do not need it to make Plausible privacy-friendly.</p> <p>These privacy principles apply to both our script and our API. Our hosted service processes and stores visitor data in the EU. Plausible uses visitors’ IP addresses and browser details to count visitors without storing those original values. Our <a href="https://plausible.io/data-policy">data policy</a> explains how they are used.</p> <p>For browser tracking, Plausible also offers an <a href="https://plausible.io/docs/proxy/introduction">optional proxy</a> that routes the script and analytics requests through your own domain to bypass most ad blockers. This keeps collection in the browser; it is different from sending events directly from your server.</p> <p>The <a href="https://plausible.io/docs/events-api">Events API</a> is a way for your website’s server to send analytics data directly to Plausible. Your server sends a request describing what happened and Plausible processes it for the same dashboard used by browser tracking.</p> <p>It accepts two types of events:</p> <ul> <li><strong>Pageviews</strong>, sent with the event name <code class="language-plaintext highlighter-rouge">pageview</code>. Send one when a visitor views a page you want to record.</li> <li><strong>Custom events</strong>, sent with a name you choose, such as <code class="language-plaintext highlighter-rouge">Signup</code> or <code class="language-plaintext highlighter-rouge">Purchase</code>. These record actions you define. Add a matching custom event goal to see their conversions in your dashboard.</li> </ul> <p>Each event needs a name, a full page URL and the domain you added to Plausible. Your server also needs to pass the visitor’s browser and IP details correctly, as explained in step 3 below.</p> <p>You can include optional information:</p> <ul> <li><strong>Referral sources and campaigns:</strong> send the referral URL in <code class="language-plaintext highlighter-rouge">referrer</code> and UTM campaign parameters in the page <code class="language-plaintext highlighter-rouge">url</code>.</li> <li><strong>Custom properties:</strong> use <code class="language-plaintext highlighter-rouge">props</code> to add details such as a product category or plan type, without sending personal information.</li> <li><strong>Revenue:</strong> use <code class="language-plaintext highlighter-rouge">revenue</code> to send an amount and currency for revenue tracking, with the dashboard setup described in our <a href="https://plausible.io/docs/ecommerce-revenue-tracking">revenue tracking guide</a>.</li> </ul> <p>The API records what you send. It does not automatically find pageviews, signups or other activity on your website. You decide when your server should send each event. Browser measurements such as scroll depth still need to be collected in the browser.</p> <h3 id="example-track-a-confirmed-signup">Example: Track a confirmed signup</h3> <p>Keep browser tracking in place and add one event when your server successfully creates an account. You’ll need a site added to Plausible and a developer with access to your website’s server code. If you only control a page editor, see our <a href="https://plausible.io/docs/integration-guides">integration guides</a>.</p> <h4 id="1-add-the-goal">1. Add the goal</h4> <p>In your Plausible site settings, add a custom event goal named <code class="language-plaintext highlighter-rouge">Signup</code>, matching the capitalization exactly. See the <a href="https://plausible.io/docs/custom-event-goals">goal setup instructions</a>.</p> <p>Count only successfully created accounts. If a browser script already sends <code class="language-plaintext highlighter-rouge">Signup</code>, stop that event when you move it to the server. Keep browser pageview and engagement tracking enabled.</p> <h4 id="2-send-the-event-after-the-account-is-saved">2. Send the event after the account is saved</h4> <p>While handling the visitor’s signup submission, send this request after the account has been saved successfully:</p> <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>curl <span class="nt">-i</span> https://plausible.io/api/event <span class="se">\</span>
  <span class="nt">-H</span> <span class="s1">'Content-Type: application/json'</span> <span class="se">\</span>
  <span class="nt">-H</span> <span class="s2">"User-Agent: </span><span class="k">${</span><span class="nv">VISITOR_USER_AGENT</span><span class="k">}</span><span class="s2">"</span> <span class="se">\</span>
  <span class="nt">-H</span> <span class="s2">"X-Forwarded-For: </span><span class="k">${</span><span class="nv">VISITOR_IP</span><span class="k">}</span><span class="s2">"</span> <span class="se">\</span>
  <span class="nt">--data</span> <span class="s1">'{
    "name": "Signup",
    "url": "https://example.com/signup",
    "domain": "example.com"
  }'</span>
</code></pre></div></div> <p>This shows the request format, not a complete signup integration. Add the equivalent request to your server code. Replace <code class="language-plaintext highlighter-rouge">example.com</code> in both the full page URL and site domain. Set the two variables from the visitor’s actual browser and IP details, as described next.</p> <h4 id="3-forward-the-visitor-details-correctly">3. Forward the visitor details correctly</h4> <p>Copy the visitor’s original <code class="language-plaintext highlighter-rouge">User-Agent</code> header, which describes their browser and device, and set <code class="language-plaintext highlighter-rouge">X-Forwarded-For</code> to their IP address. Using your server’s details can distort visitor counts or cause bot filtering to reject the event.</p> <p>If your site uses a CDN or proxy, follow your hosting provider’s instructions for finding the real visitor IP. Trust forwarding headers only from your configured services. If <code class="language-plaintext highlighter-rouge">X-Forwarded-For</code> contains a list, the visitor’s IP must be the first valid address.</p> <p><strong>Cloudflare:</strong> if <code class="language-plaintext highlighter-rouge">CF-Connecting-IP</code> is present, Plausible uses it instead of <code class="language-plaintext highlighter-rouge">X-Forwarded-For</code>. Set it to the visitor’s IP too, rather than the proxy’s outgoing address. See the <a href="https://plausible.io/docs/events-api#request-headers">header guidance</a>.</p> <p>To join an existing visit, the event must carry the visitor’s own IP and <code class="language-plaintext highlighter-rouge">User-Agent</code>, use the same website hostname and arrive within 30 minutes of their last event. It then retains that visit’s referral and campaign information.</p> <p>Without a match, it starts a new visit, potentially a new visitor too. Its source comes from the optional <code class="language-plaintext highlighter-rouge">referrer</code> field or UTM parameters in <code class="language-plaintext highlighter-rouge">url</code>; without either, it appears as Direct / None. The example above sends neither. For server-only collection, supply those details when the visit is first recorded. Later matching events retain the original source. See the <a href="https://plausible.io/docs/events-api#how-server-side-events-are-attributed">attribution rules</a>.</p> <h4 id="4-prevent-duplicate-sends-and-protect-signup">4. Prevent duplicate sends and protect signup</h4> <p>Send once per successful account creation, including when your website retries its code. A timed-out request may already have reached Plausible, so retrying can count it twice.</p> <p>Set a time limit for the analytics request and handle failures separately. An analytics connection problem should not prevent account creation.</p> <h4 id="5-verify-the-result">5. Verify the result</h4> <ul> <li>Complete a test signup on your own website, then check that <code class="language-plaintext highlighter-rouge">Signup</code> appears under goal conversions in Plausible. Check total conversions too, since duplicate events from one visitor may not increase unique conversions.</li> <li>Submit a form that fails: it should send no signup event. Confirm browser pageviews and engagement measurements still arrive.</li> <li>Start a fresh visit from a known referral or campaign link, then sign up and check the conversion’s source.</li> <li>Inspect response headers. <code class="language-plaintext highlighter-rouge">202 Accepted</code> alone does not guarantee recording; <code class="language-plaintext highlighter-rouge">x-plausible-dropped: 1</code> means the event was dropped.</li> </ul> <p>To check which IP Plausible sees, send a separate test with <code class="language-plaintext highlighter-rouge">X-Debug-Request: true</code> from the same server or worker as your real events. It returns HTTP 200 with the IP address. Check that address and the outgoing <code class="language-plaintext highlighter-rouge">User-Agent</code> belong to the visitor. Debug requests are not recorded, so remove the debug header for real events. See the <a href="https://plausible.io/docs/events-api#debugging">debugging instructions</a>.</p> <h2 id="start-with-one-confirmed-action">Start with one confirmed action</h2> <p>Start with a signup your server can verify. Keep the event free of account details, send it once after account creation succeeds and test that it appears in your dashboard. Check failed submissions and duplicate requests too.</p> <p>Once that works, use the same approach for other actions your website’s server confirms. The <a href="https://plausible.io/docs/events-api">Events API reference</a> covers pageviews, custom properties and revenue when you need to extend your setup.</p>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[A practical guide to server-side event tracking: control the data you send and record successful signups with Plausible's Events API.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/server-side-tracking-signup-dashboard.png"/><media:content medium="image" url="https://plausible.io/uploads/server-side-tracking-signup-dashboard.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">Google Analytics pricing: Free GA4 and paid GA360 explained</title><link href="https://plausible.io/blog/google-analytics-pricing" rel="alternate" type="text/html" title="Google Analytics pricing: Free GA4 and paid GA360 explained"/><published>2026-10-22T10:00:00+00:00</published><updated>2026-10-22T10:00:00+00:00</updated><id>https://plausible.io/blog/google-analytics-pricing</id><content type="html" xml:base="https://plausible.io/blog/google-analytics-pricing"><![CDATA[<p><strong>The standard version of Google Analytics 4 (GA4) is free. Its paid enterprise version, Google Analytics 360 (GA360), requires a quote. Google does not publish a current dollar price list.</strong></p> <p>That is the subscription answer. The more useful question is what you get for the money, including the work it takes to turn your analytics into something your team can use.</p> <p>Here’s how the free and paid versions work, where the GA360 price figures come from and what to consider before upgrading or renewing.</p> <p><em>All dollar amounts are US dollars. Sources checked in October 2026.</em></p> <ol id="markdown-toc"> <li><a href="#is-google-analytics-free" id="markdown-toc-is-google-analytics-free">Is Google Analytics free?</a></li> <li><a href="#how-much-does-google-analytics-360-cost" id="markdown-toc-how-much-does-google-analytics-360-cost">How much does Google Analytics 360 cost?</a> <ol> <li><a href="#what-makes-a-ga360-bill-increase" id="markdown-toc-what-makes-a-ga360-bill-increase">What makes a GA360 bill increase?</a></li> </ol> </li> <li><a href="#what-are-you-buying-when-you-upgrade-to-ga360" id="markdown-toc-what-are-you-buying-when-you-upgrade-to-ga360">What are you buying when you upgrade to GA360?</a></li> <li><a href="#the-costs-outside-the-subscription" id="markdown-toc-the-costs-outside-the-subscription">The costs outside the subscription</a> <ol> <li><a href="#setting-up-and-maintaining-measurement" id="markdown-toc-setting-up-and-maintaining-measurement">Setting up and maintaining measurement</a></li> <li><a href="#getting-reports-into-peoples-hands" id="markdown-toc-getting-reports-into-peoples-hands">Getting reports into people’s hands</a></li> <li><a href="#running-the-surrounding-tools" id="markdown-toc-running-the-surrounding-tools">Running the surrounding tools</a></li> </ol> </li> <li><a href="#ga360-still-depends-on-your-consent-setup" id="markdown-toc-ga360-still-depends-on-your-consent-setup">GA360 still depends on your consent setup</a></li> <li><a href="#plausible-enterprise-simpler-web-analytics-at-scale" id="markdown-toc-plausible-enterprise-simpler-web-analytics-at-scale">Plausible Enterprise: simpler web analytics at scale</a> <ol> <li><a href="#how-plausible-enterprise-compares-with-ga360" id="markdown-toc-how-plausible-enterprise-compares-with-ga360">How Plausible Enterprise compares with GA360</a></li> <li><a href="#which-questions-can-each-tool-answer" id="markdown-toc-which-questions-can-each-tool-answer">Which questions can each tool answer?</a></li> </ol> </li> <li><a href="#try-the-reports-before-choosing-the-subscription" id="markdown-toc-try-the-reports-before-choosing-the-subscription">Try the reports before choosing the subscription</a></li> </ol> <h2 id="is-google-analytics-free">Is Google Analytics free?</h2> <p><a href="https://marketingplatform.google.com/about/analytics/">Standard Google Analytics</a> has no subscription fee. You can use it for a business website without buying GA360. A growing audience does not automatically trigger a paid plan.</p> <p>GA4 already includes <a href="https://marketingplatform.google.com/about/analytics/features/">traffic reports, campaign measurement, ecommerce reporting and funnel explorations</a>. GA360 gives organizations higher limits and additional enterprise capabilities within GA4.</p> <table> <thead> <tr> <th>Product</th> <th>Subscription cost</th> <th>What that covers</th> </tr> </thead> <tbody> <tr> <td>GA4 Standard</td> <td>Free</td> <td>Website and app analytics within standard limits</td> </tr> <tr> <td>GA4 360</td> <td>Custom quote; no public Google dollar price list</td> <td>Higher limits, additional controls and enterprise support</td> </tr> </tbody> </table> <p>You can still incur costs around the free version. An agency might manage your implementation. Your team might export data to BigQuery or maintain custom reports. Those expenses are separate.</p> <p>Free GA4 does not come with a mandatory agency bill. Equally, a GA360 license does not necessarily cover all the work around it.</p> <h2 id="how-much-does-google-analytics-360-cost">How much does Google Analytics 360 cost?</h2> <p>Google does not publish a dollar price list on its <a href="https://marketingplatform.google.com/about/analytics-360/">Analytics 360 page</a>. You can <a href="https://marketingplatform.google.com/about/contact-us/">contact Google’s enterprise sales team or a Google Marketing Platform sales partner</a> for a quote.</p> <p>A <a href="https://www.cardinalpath.com/blog/ua-360-vs-ga4-360-pricing-model">reseller article published in 2022</a> described a suggested $50,000 annual starting price. This is a historical reference point, not a verified current minimum. You need a current quote to establish what your organization would pay.</p> <p><em>The <a href="https://www.cardinalpath.com/blog/ua-360-vs-ga4-360-pricing-model">suggested $150,000 annual starting price for Universal Analytics 360</a> refers to the older product. It should not be confused with GA4 360 pricing or presented as today’s minimum.</em></p> <h3 id="what-makes-a-ga360-bill-increase">What makes a GA360 bill increase?</h3> <p><a href="https://support.google.com/marketingplatform/answer/9013858">Google’s billing documentation</a> describes a base fee covering the first 25 million monthly events, followed by tiered fees for additional volume. The per-event rate falls at higher tiers.</p> <p>An event allowance is not a visitor allowance. Someone can arrive on a page, scroll, view another page and submit a form during one visit. Your configuration determines which interactions generate events. Google excludes certain events from billing, including user engagement, spam and hidden system events.</p> <p><a href="https://support.google.com/analytics/answer/11526072">Subproperties</a> and roll-up properties can add processing charges too. They let organizations split reporting into subsets or combine multiple properties. For example, <a href="https://support.google.com/analytics/answer/11539651">Google documents an additional roll-up event charge</a> at half the source-event cost, subject to your contract.</p> <p>Ask for a quote based on <strong>billable events and your complete property structure</strong>. Pageviews alone will not tell you what the bill should be.</p> <p>Eligible admins can also <a href="https://support.google.com/marketingplatform/answer/9013858">preview usage and sample pricing in Google Marketing Platform</a>. Google notes that the preview rates are not contractual and can vary by market. It is a useful check against your usage, rather than a substitute for your agreement.</p> <h2 id="what-are-you-buying-when-you-upgrade-to-ga360">What are you buying when you upgrade to GA360?</h2> <p>GA360 makes sense when a specific limit or enterprise requirement gets in the way of work you already do.</p> <p>For example, a team that needs complete daily BigQuery exports above the standard allowance has a concrete capacity problem. An organization that needs separate reporting for regional teams may have a property-management requirement.</p> <p>Several differences appear in <a href="https://support.google.com/analytics/answer/11202874">Google’s Standard versus 360 documentation</a>:</p> <table> <thead> <tr> <th>Capability</th> <th>GA4 Standard</th> <th>GA4 360</th> </tr> </thead> <tbody> <tr> <td>Event parameters</td> <td>25 per event</td> <td>100 per event</td> </tr> <tr> <td>Audiences</td> <td>100 per property</td> <td>400 per property</td> </tr> <tr> <td>Daily BigQuery export</td> <td>1 million events per day</td> <td><a href="https://support.google.com/analytics/answer/9358801">Up to 20 billion events per day</a></td> </tr> <tr> <td>Enterprise service-level agreements</td> <td>Not included</td> <td>Covered by a 360 contract</td> </tr> </tbody> </table> <p>Streaming BigQuery exports are a separate option with no event-volume limit in either version. <a href="https://support.google.com/analytics/answer/9358801">Google describes streaming as a best-effort service</a> that may have data gaps and incurs additional BigQuery charges. Exceeding the daily export allowance does not mean every export route requires GA360, but streaming is not equivalent to a complete daily export.</p> <p>GA360 also offers longer retention options. One detail frequently gets lost in comparisons: the free version’s 14-month retention setting does <strong>not</strong> mean all your traffic reports vanish after 14 months. Google’s <a href="https://support.google.com/analytics/answer/7667196">retention setting governs explorations and funnel reports</a>, not standard aggregated reports.</p> <p>Retention also depends on data type and property size. Google limits user-level and key-event data retention to 14 months even in GA360; the longer settings apply to other event data. Large standard properties and XL 360 properties are limited to two months of event-level retention.</p> <p>These differences can justify an upgrade. They do not make GA4 a different product to use. Higher limits won’t make a confusing report easier for your colleagues to understand.</p> <h2 id="the-costs-outside-the-subscription">The costs outside the subscription</h2> <p>A useful analytics budget includes the work needed to get from a visitor arriving on your site to a report someone acts on.</p> <h3 id="setting-up-and-maintaining-measurement">Setting up and maintaining measurement</h3> <p>Installing a tag is only the beginning if you need custom events, consent configuration or a reporting pipeline. Someone has to define those events, test that they fire correctly and maintain them when your website changes.</p> <p>That work may be handled internally, by an agency or through your GA360 partner. Check what is included before adding a separate allowance for it.</p> <h3 id="getting-reports-into-peoples-hands">Getting reports into people’s hands</h3> <p>Consider your last campaign review. Could the marketing team see which landing pages generated signups? Or did someone have to build an exploration, export a spreadsheet and explain why the numbers differed from another report?</p> <p>Count that time. A report that requires specialist help every month has an ongoing cost even when the software subscription is free.</p> <h3 id="running-the-surrounding-tools">Running the surrounding tools</h3> <p>If you use BigQuery, server-side tagging infrastructure or a paid consent management platform, include the relevant costs. Replacing analytics will not remove a consent platform you still need for advertising or other tools.</p> <p>For a practical estimate, fill in this worksheet using your own invoices and working hours:</p> <table> <thead> <tr> <th>Recurring cost</th> <th>Your monthly amount</th> </tr> </thead> <tbody> <tr> <td>GA360 license, if applicable</td> <td>Annual license fee divided by 12</td> </tr> <tr> <td>Additional usage</td> <td>Charges outside your included allowance</td> </tr> <tr> <td>Agency or partner services</td> <td>Work not already included in the license</td> </tr> <tr> <td>Infrastructure and other tools</td> <td>The share attributable to analytics</td> </tr> <tr> <td>Internal maintenance and reporting</td> <td>Monthly hours multiplied by your internal hourly cost</td> </tr> </tbody> </table> <p>Add those amounts and multiply by 12 for a recurring annual estimate. Record one-time implementation costs separately. If your traffic is seasonal, use a full year of invoices or model the months individually.</p> <h2 id="ga360-still-depends-on-your-consent-setup">GA360 still depends on your consent setup</h2> <p>There is another question a price comparison needs to answer: will the upgrade fix the problem that made you look for one?</p> <p>If you need higher export limits, GA360 can help. If your concern is relying on cookie consent to measure your website, buying more capacity leaves that collection model in place.</p> <p>With <a href="https://support.google.com/analytics/answer/10000067">basic Consent Mode</a>, Google’s tags remain blocked when a visitor does not consent. Advanced Consent Mode sends cookieless signals and can support modeling to fill gaps, subject to <a href="https://support.google.com/analytics/answer/11161109">eligibility requirements</a>. Modeled activity and directly observed visits are different kinds of evidence. Google also states that advanced Consent Mode does not increase GA360 event-based billing.</p> <h2 id="plausible-enterprise-simpler-web-analytics-at-scale">Plausible Enterprise: simpler web analytics at scale</h2> <p>Plausible is a privacy-first, open source alternative to Google Analytics. We built it to help you understand your website without tracking people across the internet. We don’t use cookies or collect personal data about website visitors, so <a href="/data-policy">our analytics don’t require a consent banner</a>. We’re an independent business funded by subscriptions, with visitor data kept on <a href="/eu-hosted-web-analytics">European-owned infrastructure in the EEA</a>.</p> <p>You don’t have to move to GA360 to keep measuring a growing website. Plausible shows which campaigns bring signups, which pages generate revenue and where visitors abandon a funnel.</p> <p>And simpler analytics doesn’t mean smaller websites. The largest site in our network receives around one billion monthly pageviews. Organizations including Hugging Face, MongoDB and Basecamp use Plausible.</p> <p>Our Enterprise plans extend that approach to organizations with higher traffic, more sites and larger teams. They can include Single Sign-On (SSO) using SAML 2.0, the Sites API for programmatic site management, a managed proxy to reduce blocking and scheduled raw event data exports for your warehouse. We agree the features and limits with you, so you can get higher capacity without taking every Enterprise feature.</p> <p>Check out the details of our Enterprise plans <a href="/enterprise-web-analytics">here</a>.</p> <h3 id="how-plausible-enterprise-compares-with-ga360">How Plausible Enterprise compares with GA360</h3> <p>For an Enterprise decision, look at how each product collects data, supports your workflows and charges for usage:</p> <table> <thead> <tr> <th>Requirement</th> <th>Plausible Enterprise</th> <th>Google Analytics 360</th> </tr> </thead> <tbody> <tr> <td>Analytics consent</td> <td>No cookies; no consent banner needed for Plausible</td> <td><a href="https://support.google.com/analytics/answer/10000067">Basic Consent Mode blocks tags without consent; advanced mode sends cookieless signals and supports modeling</a>, subject to eligibility</td> </tr> <tr> <td>Cross-device measurement</td> <td>Deliberately does not recognize the same person across devices</td> <td><a href="https://support.google.com/analytics/answer/9213390">User-ID can connect activity across devices and platforms</a> when implemented in accordance with Google’s policies</td> </tr> <tr> <td>Advertising audiences</td> <td>Campaign and conversion reporting without building remarketing audiences</td> <td><a href="https://support.google.com/analytics/answer/9379420">Google Ads integration</a> supports conversion sharing and remarketing</td> </tr> <tr> <td>Reporting across websites</td> <td><a href="https://plausible.io/docs/consolidated-views">Consolidated View</a> is available from the Business plan, including Enterprise. It combines native traffic across sites in a team; excludes imported data and revenue goals</td> <td><a href="https://support.google.com/analytics/answer/11526039">Roll-up properties</a> require GA360, Google’s paid enterprise version. They combine source properties; subproperties provide filtered datasets</td> </tr> <tr> <td>Raw data for your warehouse</td> <td><a href="https://plausible.io/docs/raw-data-export">Daily event- and session-level exports</a> to S3-compatible storage, ready for your own loading pipeline</td> <td><a href="https://support.google.com/analytics/answer/11202874">Native BigQuery exports</a>, including daily and streaming options</td> </tr> <tr> <td>Data retention</td> <td>No retention limit: stats are kept for as long as you’re subscribed</td> <td><a href="https://support.google.com/analytics/answer/7667196">Up to 50 months for other event data</a>; user-level and key-event data are limited to 14 months. Property-size limits also apply</td> </tr> <tr> <td>Pricing basis</td> <td>Custom plan based on pageviews plus custom events, required features and limits</td> <td>Base fee plus tiered billable-event charges; subproperties and roll-ups can add costs</td> </tr> </tbody> </table> <h3 id="which-questions-can-each-tool-answer">Which questions can each tool answer?</h3> <p>Several Google workflows below are also available in free GA4. GA360 adds higher limits and enterprise controls.</p> <table> <thead> <tr> <th>Analytical question</th> <th>Better fit</th> </tr> </thead> <tbody> <tr> <td>Which <a href="https://plausible.io/docs/top-referrers">marketing channels</a> bring the most visitors?</td> <td>Both</td> </tr> <tr> <td>Which landing pages have the highest <a href="https://plausible.io/docs/goal-conversions">conversion rates</a>?</td> <td>Both; configure goals in Plausible and <a href="https://support.google.com/analytics/answer/13128484">key events in GA360</a></td> </tr> <tr> <td>Where do visitors abandon a <a href="https://plausible.io/docs/funnel-analysis">signup funnel</a>?</td> <td>Both, with funnel steps configured</td> </tr> <tr> <td>Which campaigns generate the most <a href="https://plausible.io/docs/ecommerce-revenue-tracking">recorded website revenue</a>?</td> <td>Both, with revenue tracking configured; attribution differs</td> </tr> <tr> <td>What <a href="https://plausible.io/docs/user-journeys">paths do visitors take before converting</a>?</td> <td>Both; Plausible’s user journeys currently exclude revenue and property-filtered goals</td> </tr> <tr> <td>How do individuals behave across devices and apps?</td> <td><a href="https://support.google.com/analytics/answer/9213390">GA360, with User-ID configured</a>; Plausible deliberately does not link people across devices</td> </tr> <tr> <td>Can we build remarketing audiences from analytics behavior?</td> <td><a href="https://support.google.com/analytics/answer/9379420">GA360, through Google Ads integration</a>; Plausible does not build remarketing audiences</td> </tr> <tr> <td>Can we export event-level data for our warehouse?</td> <td>Both; <a href="https://plausible.io/docs/raw-data-export">Plausible delivers daily exports to S3-compatible storage</a> for your own warehouse pipeline</td> </tr> <tr> <td>Can we measure conversions without cookies or persistent visitor profiles?</td> <td><a href="https://plausible.io/data-policy">Plausible, by design</a></td> </tr> </tbody> </table> <p>If your workflow depends on cross-device customer measurement or activating analytics audiences in Google Ads, those are capabilities Plausible deliberately doesn’t provide. And if you need events in BigQuery within minutes, our daily raw exports won’t meet that requirement. Check the workflows you rely on before replacing them.</p> <p>Plausible’s <a href="https://plausible.io/docs/subscription-plans#how-usage-is-calculated">pageviews and custom events</a> also won’t necessarily match your GA4 billable-event count. Compare quotes using the volume and requirements for each product, rather than assuming the same event allowance buys the same thing.</p> <p><strong>Need a simple and privacy-friendly enterprise analytics tool?</strong> <a href="https://plausible.io/contact">Discuss a Plausible Enterprise plan with us</a>. Tell us your traffic volume, the sites you manage and the reports your team relies on. We’ll explain how Plausible would handle them and put together a quote.</p> <p><a href="https://plausible.io/plausible.io">Explore Plausible’s live dashboard</a> to see how the reporting works.</p> <h2 id="try-the-reports-before-choosing-the-subscription">Try the reports before choosing the subscription</h2> <p>You don’t have to decide from a feature table. <a href="https://plausible.io/register">Start a 30-day free trial</a> and run Plausible alongside your existing analytics. No credit card is required.</p> <p>Use it for an actual reporting task: review a campaign, compare landing-page conversions or investigate a signup funnel. Check whether your colleagues can get the answers they need and understand how those answers were measured.</p> <p>The standard trial includes Business plan features. <a href="https://plausible.io/contact">Contact us</a> to discuss your Enterprise requirements such as SSO or scheduled exports.</p> <p>Your website can grow without making individual tracking the foundation of your analytics. Plausible is built for that choice.</p>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[How much does Google Analytics cost? Understand free GA4 limits, GA360 pricing and the costs of running your setup.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/google-analytics-360-cohort-exploration.png"/><media:content medium="image" url="https://plausible.io/uploads/google-analytics-360-cohort-exploration.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">Shopify, Squarespace and Webflow analytics: What you can track and what’s missing</title><link href="https://plausible.io/blog/cms-built-in-analytics" rel="alternate" type="text/html" title="Shopify, Squarespace and Webflow analytics: What you can track and what’s missing"/><published>2026-10-02T07:00:00+00:00</published><updated>2026-10-02T07:00:00+00:00</updated><id>https://plausible.io/blog/cms-built-in-analytics</id><content type="html" xml:base="https://plausible.io/blog/cms-built-in-analytics"><![CDATA[<p>Shopify, Squarespace, Webflow and other website builders/content management systems offer analytics within their platforms. What can those reports tell you, why do their numbers differ from other tools and can you export the data? The answers depend on which platform you use.</p> <p>You should be able to answer website performance questions without collecting more personal data or taking on Google Analytics’ complexity. While you also should not have to buy another tool to get information your website platform already provides, unless it really adds value.</p> <p>This guide discusses capabilities of popular content management systems’ or website builders analytics, includes common doubts and questions people have about each platform, then looks at when independent analytics solves a problem.</p> <ol id="markdown-toc"> <li><a href="#what-can-your-platforms-analytics-actually-tell-you" id="markdown-toc-what-can-your-platforms-analytics-actually-tell-you">What can your platform’s analytics actually tell you?</a> <ol> <li><a href="#squarespace" id="markdown-toc-squarespace">Squarespace</a> <ol> <li><a href="#can-i-trust-the-numbers-and-export-a-report" id="markdown-toc-can-i-trust-the-numbers-and-export-a-report">Can I trust the numbers and export a report?</a></li> </ol> </li> <li><a href="#wix" id="markdown-toc-wix">Wix</a> <ol> <li><a href="#why-do-its-numbers-disagree-with-google-analytics" id="markdown-toc-why-do-its-numbers-disagree-with-google-analytics">Why do its numbers disagree with Google Analytics?</a></li> </ol> </li> <li><a href="#shopify" id="markdown-toc-shopify">Shopify</a> <ol> <li><a href="#why-do-i-have-orders-without-matching-tracked-conversions" id="markdown-toc-why-do-i-have-orders-without-matching-tracked-conversions">Why do I have orders without matching tracked conversions?</a></li> </ol> </li> <li><a href="#wordpresscom" id="markdown-toc-wordpresscom">WordPress.com</a> <ol> <li><a href="#what-do-the-built-in-stats-include" id="markdown-toc-what-do-the-built-in-stats-include">What do the built-in stats include?</a></li> </ol> </li> <li><a href="#ghost" id="markdown-toc-ghost">Ghost</a> <ol> <li><a href="#do-i-still-need-separate-analytics-after-ghost-60" id="markdown-toc-do-i-still-need-separate-analytics-after-ghost-60">Do I still need separate analytics after Ghost 6.0?</a></li> </ol> </li> <li><a href="#webflow" id="markdown-toc-webflow">Webflow</a> <ol> <li><a href="#can-analyze-export-data-and-is-it-cookie-free" id="markdown-toc-can-analyze-export-data-and-is-it-cookie-free">Can Analyze export data, and is it cookie-free?</a></li> </ol> </li> </ol> </li> <li><a href="#what-native-built-in-analytics-are-good-at" id="markdown-toc-what-native-built-in-analytics-are-good-at">What native built-in analytics are good at</a></li> <li><a href="#when-independent-analytics-solves-a-problem" id="markdown-toc-when-independent-analytics-solves-a-problem">When independent analytics solves a problem</a> <ol> <li><a href="#you-need-to-answer-questions-beyond-the-platforms-standard-reports" id="markdown-toc-you-need-to-answer-questions-beyond-the-platforms-standard-reports">You need to answer questions beyond the platform’s standard reports</a></li> <li><a href="#you-need-one-set-of-metrics-across-several-sites" id="markdown-toc-you-need-one-set-of-metrics-across-several-sites">You need one set of metrics across several sites</a></li> <li><a href="#you-need-to-understand-what-affects-data-accuracy" id="markdown-toc-you-need-to-understand-what-affects-data-accuracy">You need to understand what affects data accuracy</a></li> <li><a href="#you-want-a-different-approach-to-visitor-privacy" id="markdown-toc-you-want-a-different-approach-to-visitor-privacy">You want a different approach to visitor privacy</a></li> <li><a href="#you-need-ownership-exports-and-reporting-outside-the-cms" id="markdown-toc-you-need-ownership-exports-and-reporting-outside-the-cms">You need ownership, exports and reporting outside the CMS</a></li> <li><a href="#you-want-analytics-to-be-the-providers-main-product" id="markdown-toc-you-want-analytics-to-be-the-providers-main-product">You want analytics to be the provider’s main product</a></li> </ol> </li> <li><a href="#how-plausible-extends-built-in-cms-analytics" id="markdown-toc-how-plausible-extends-built-in-cms-analytics">How Plausible extends built-in CMS analytics</a> <ol> <li><a href="#which-campaigns-and-pages-lead-to-a-result" id="markdown-toc-which-campaigns-and-pages-lead-to-a-result">Which campaigns and pages lead to a result?</a></li> <li><a href="#how-do-you-add-it-to-your-existing-site" id="markdown-toc-how-do-you-add-it-to-your-existing-site">How do you add it to your existing site?</a></li> <li><a href="#which-google-searches-bring-people-to-your-pages" id="markdown-toc-which-google-searches-bring-people-to-your-pages">Which Google searches bring people to your pages?</a></li> <li><a href="#can-you-combine-sites-and-send-reports-to-clients" id="markdown-toc-can-you-combine-sites-and-send-reports-to-clients">Can you combine sites and send reports to clients?</a></li> <li><a href="#what-visitor-data-does-plausible-collect" id="markdown-toc-what-visitor-data-does-plausible-collect">What visitor data does Plausible collect?</a></li> </ol> </li> <li><a href="#frequently-asked-questions" id="markdown-toc-frequently-asked-questions">Frequently asked questions</a></li> </ol> <h2 id="what-can-your-platforms-analytics-actually-tell-you">What can your platform’s analytics actually tell you?</h2> <h3 id="squarespace">Squarespace</h3> <p>Squarespace is a website builder for publishing content, selling products and running membership sites.</p> <p>Squarespace Analytics shows visits and unique visitors over time, which pages people view, how they found the site and which search terms brought them there. Depending on your plan and commerce setup, it can also report form and button conversions, sales, purchase-funnel activity and abandoned carts.</p> <p>Its <a href="https://support.squarespace.com/hc/en-us/articles/206544167-Squarespace-Analytics">official analytics guide</a> lists the panels available and the plans that include them. For checking which pages get attention or whether traffic is growing, it may already provide enough information.</p> <h4 id="can-i-trust-the-numbers-and-export-a-report">Can I trust the numbers and export a report?</h4> <p>Squarespace currently says that analytics reports cannot be exported. If a spreadsheet is part of your monthly reporting, that is a concrete limitation.</p> <p>Visitor counts need some context too. Squarespace explains that when analytics cookies are disabled, each pageview counts as its own visit. One person reading several pages can therefore produce several visits. Attribution and conversion reporting can also be affected. <a href="https://support.squarespace.com/hc/en-us/articles/360001264507-The-cookies-Squarespace-uses">How Squarespace’s cookie settings change analytics</a>.</p> <p>So a higher count than Google Analytics does not, by itself, mean Squarespace found more people. Check the consent settings and compare the same metric before judging either total.</p> <p>For monthly reporting, distinguish between checking trends in Squarespace and delivering a spreadsheet of those trends. The dashboard supports the first task; its lack of analytics exports prevents the second.</p> <h3 id="wix">Wix</h3> <p>Wix is a website builder with integrated tools for running an online business.</p> <p>Wix Analytics shows sessions, unique visitors, traffic sources, entry pages, locations, devices and new versus returning visitors. Sites using Wix business apps can also get reports for sales, stores, bookings, events and other app-specific activity. Its <a href="https://support.wix.com/en/analytics-for-your-site-and-business">analytics guides</a> explain the available reports, sharing and alerts.</p> <p>Unlike Squarespace, Wix lets you <a href="https://support.wix.com/en/article/scheduling-wix-analytics-report-emails">download analytics reports as CSV files and schedule report emails</a>. Scheduled reports are delivered as CSV attachments in table view. Downloading charts as CSV, PNG or SVG files requires Analytics Pro. You do not need another analytics tool solely to export a standard report table from Wix.</p> <h4 id="why-do-its-numbers-disagree-with-google-analytics">Why do its numbers disagree with Google Analytics?</h4> <p>The totals can differ because the tools may not observe the same visits. When Wix’s cookie banner is active, Wix Analytics collects data only after a visitor accepts analytics cookies. Wix and Google also use different bot-filtering methods, so traffic removed by one tool may remain in the other. Wix describes both causes in its <a href="https://support.wix.com/en/article/discrepancies-between-wix-analytics-data-in-other-tracking-tools">discrepancy guide</a>, while its <a href="https://support.wix.com/en/article/displaying-a-cookie-banner-on-your-site">cookie-banner documentation</a> explains how consent controls collection.</p> <p>That is why the first step is to make the comparison equivalent. Match sessions with sessions over the same dates and time zone, then confirm that both tools run on the same pages, follow the intended consent settings and handle your own visits as expected. If the disputed metric is time on page, compare its definition too: Wix calculates time from the gap between pageviews, so it cannot calculate the metric for a visit that never moves to another page.</p> <p>Even after those checks, the totals do not need to match exactly. For recurring client reports, choose one source and state what it counts. Treat a sudden gap between the tools as a reason to inspect the setup before presenting it as a real change in traffic.</p> <h3 id="shopify">Shopify</h3> <p>Shopify is an ecommerce platform for managing storefronts, orders, products and customers.</p> <p><a href="https://help.shopify.com/en/manual/reports-and-analytics/shopify-reports">Shopify Analytics</a> shows sales, orders, online-store sessions, conversion rate and other store activity from the Shopify admin. More detailed reports cover acquisition, customer behavior, finances, inventory, marketing and product performance, with availability depending on your Shopify plan. You can <a href="https://help.shopify.com/en/manual/reports-and-analytics/shopify-reports/report-types/custom-reports/export-reports">export most reports from the admin</a>, including as CSV files for spreadsheet analysis. Our <a href="/blog/shopify-analytics">Shopify Analytics guide</a> walks through the dashboard and report categories.</p> <h4 id="why-do-i-have-orders-without-matching-tracked-conversions">Why do I have orders without matching tracked conversions?</h4> <p>Shopify counts orders and converted sessions differently. One session can produce multiple separate purchases, which creates multiple orders but only one converted session. Shopify also documents that consent choices can reduce the session data available for reporting. <a href="https://help.shopify.com/en/manual/reports-and-analytics/discrepancies/customer-discrepancies">Shopify’s customer and session discrepancy guide</a>.</p> <p>Use your order records to establish which purchases happened. Use traffic and conversion reporting to investigate how measured visits led to them. Do not assume that every missing analytics conversion means a missing sale.</p> <p>Also check for measurement changes. Shopify’s September 21–23, 2026 rollout changed session handling and filtered identified bot sessions out of session-related reports by default. Shopify says this can change sessions and conversion rates without changing order or sales counts. <a href="https://help.shopify.com/en/manual/reports-and-analytics/discrepancies/analytics-updates">Shopify’s update</a>.</p> <p>A change in reported conversion rate therefore needs two checks: did sales change, or did the number of measured sessions change? Review both before concluding that checkout performance has improved or declined.</p> <h3 id="wordpresscom">WordPress.com</h3> <p>WordPress.com is a managed hosting platform for building and publishing WordPress sites.</p> <p>WordPress.com includes Jetpack Stats. Other WordPress sites may use a different analytics plugin, so first check which tool supplies the stats in your dashboard.</p> <p>Jetpack Stats shows views and visitors, popular posts and pages, referrers, locations, devices, outbound-link clicks and subscriber activity. Historical access and more detailed reports depend on the WordPress.com plan. It supports CSV downloads, although its all-time most-viewed list and corresponding export are limited to the top 500 posts and pages. <a href="https://wordpress.com/support/stats/">WordPress.com’s stats guide</a>.</p> <h4 id="what-do-the-built-in-stats-include">What do the built-in stats include?</h4> <p>WordPress.com defines a visitor as an individual it recognizes in the selected period and a view as a page load or reload. One visitor reading three posts can therefore generate three views. A higher view count than visitor count is expected when people read more than one page. <a href="https://wordpress.com/support/stats/understand-your-sites-traffic/">WordPress.com’s traffic guide</a> explains how both metrics are counted.</p> <p>Before paying for another tool to access older reports, check whether the history or export you need is already available on your WordPress.com plan.</p> <h3 id="ghost">Ghost</h3> <p>Ghost is a publishing platform built around websites, newsletters and memberships.</p> <p>Ghost shows unique visitors, total views, top content and traffic sources, with filters for public visitors, free members and paid members. Separate reports cover newsletter subscribers, open and click rates, membership growth and recurring revenue. Its web analytics is cookie-free, although Ghost records member IDs and membership status for logged-in readers. <a href="https://ghost.org/help/native-analytics/">Ghost’s analytics documentation</a>.</p> <h4 id="do-i-still-need-separate-analytics-after-ghost-60">Do I still need separate analytics after Ghost 6.0?</h4> <p>Whether you still need separate analytics depends on what you need to measure beyond Ghost. If your questions are which articles attract readers and which content brings members, Ghost already connects those results and provides cookie-free traffic measurement.</p> <p>A separate tool adds value when it answers something Ghost does not, such as reporting across other sites, tracking particular website actions or maintaining continuity with analytics you already use.</p> <p>History is a separate consideration. Ghost <a href="https://ghost.org/help/native-analytics/">documents</a> that its native web analytics starts with Ghost 6.0 and cannot import data from third-party analytics tools. If you already have years of reporting elsewhere, switching entirely to Ghost affects the comparisons you can make in the new dashboard.</p> <h3 id="webflow">Webflow</h3> <p>Webflow is a visual website builder and content management system.</p> <p>Webflow Analyze is an add-on that reports sessions, unique visitors, bounce rate, time on page, traffic sources, devices and click behavior. You can also define goals for clicks on specific buttons and links. The <a href="https://help.webflow.com/hc/en-us/articles/34200153798163-Intro-to-Webflow-Analyze">official Webflow Analyze documentation</a> explains its site overview, goals and page-level insights.</p> <h4 id="can-analyze-export-data-and-is-it-cookie-free">Can Analyze export data, and is it cookie-free?</h4> <p>Analyze uses local storage rather than cookies to recognize visitors. Webflow says privacy compliance depends on the tracking mode and consent setup. It also says historical analytics becomes inaccessible when Analyze is disabled.</p> <p>Exports are supported. Webflow <a href="https://webflow.com/updates/export-csv-analyze">introduced CSV exports in April 2026</a>. You can take supported chart and table data into a spreadsheet for client reports or further analysis.</p> <p>If you plan to stop using Analyze, export the reports you need before disabling it. Cookie-free collection and continued access to reporting are separate questions.</p> <h2 id="what-native-built-in-analytics-are-good-at">What native built-in analytics are good at</h2> <p>Native reporting has a clear advantage when the question belongs to the platform’s own work: products and orders in Shopify, newsletters and memberships in Ghost or published content in WordPress.com.</p> <p>It also puts reporting somewhere you already visit. If you only need a regular check of traffic and popular pages, an existing dashboard can be enough.</p> <p>For a monthly review, start with the reports already available: traffic trends, popular pages and the sales or membership results relevant to your site. Check the date range and try an export. That establishes what you can report today and what, if anything, is missing.</p> <h2 id="when-independent-analytics-solves-a-problem">When independent analytics solves a problem</h2> <p>Built-in analytics is strongest when the question stays inside one platform. Independent analytics becomes useful when the question crosses that boundary: another site, a campaign, a CMS migration or a requirement the platform was not designed to meet.</p> <h3 id="you-need-to-answer-questions-beyond-the-platforms-standard-reports">You need to answer questions beyond the platform’s standard reports</h3> <p>A platform decides which reports make sense for most of its customers. Your questions may be more specific: Which campaign produced qualified enquiries? Where do people leave a signup or checkout flow? What do visitors read before purchasing? How much revenue came from a landing page rather than simply how many orders were placed?</p> <p>Independent analytics can add custom conversions, campaign attribution, funnels, visitor paths, segmentation and integrations with search or advertising data. These capabilities only add value when they answer a real question. More reports do not make the data more useful by themselves.</p> <h3 id="you-need-one-set-of-metrics-across-several-sites">You need one set of metrics across several sites</h3> <p>A Shopify store and a separate WordPress publication may both have useful reports, but they may define visits, engagement and conversions differently. Reviewing them together means reconciling dashboards before interpreting the result.</p> <p>Using one analytics tool across those sites provides a common measurement method, date range and conversion vocabulary. This is useful for agencies, organisations with regional sites and businesses whose store, blog and marketing pages run on different systems. It still requires correct installation on every site and consistent definitions for outcomes such as signups or enquiries.</p> <h3 id="you-need-to-understand-what-affects-data-accuracy">You need to understand what affects data accuracy</h3> <p>No analytics tool records an unquestionable version of reality. Visitor counts change with consent choices, blocked scripts, bot filtering, internal traffic, time zones and the way a tool defines a visit or a unique visitor. A platform may also count an order, member or subscriber from its own database while a web analytics tool counts only activity it observed on the site.</p> <p>An independent tool gives you another collection method and more control over exclusions, events and definitions. That can produce a dataset better suited to your questions, but independence alone does not make it accurate. Check what is collected, what is filtered and which activity is missed before comparing numbers between tools.</p> <h3 id="you-want-a-different-approach-to-visitor-privacy">You want a different approach to visitor privacy</h3> <p>Privacy depends on how analytics recognizes visitors and what happens to the resulting data. Relevant questions include whether it uses cookies or persistent identifiers, whether it creates profiles across days or sites, where the data is processed and whether it is used for advertising.</p> <p>Consent can affect the reports themselves. Wix says visitors who do not consent to analytics cookies are omitted from its reports. Squarespace says disabling analytics cookies can prevent it from connecting activity into one visit. In those cases, consent changes which activity is measured or how visits are counted.</p> <p>An independent tool can offer a measurement model that does not rely on analytics cookies or persistent visitor profiles. The tradeoff may be less information about an individual’s behaviour across days or devices. For many sites, aggregate answers about pages, sources and conversions are enough. Other services on the site may still require consent.</p> <h3 id="you-need-ownership-exports-and-reporting-outside-the-cms">You need ownership, exports and reporting outside the CMS</h3> <p>Access to a dashboard is not the same as control over the data. You may need to export a complete history, automate a report through an API, combine website data with another source or give a client access without also opening the CMS.</p> <p>Check what can be exported, the level of detail included, row or date limits and what happens when the subscription ends. Also check whether the provider lets you delete the data and whether it uses that data for any purpose beyond providing analytics.</p> <p>Keeping analytics separate can also preserve one reporting history through a redesign, domain change or move to another CMS. You still need to install and verify tracking on the new site. An independent tool cannot recreate visits that were never recorded and importing old data depends on what the previous tool can export.</p> <h3 id="you-want-analytics-to-be-the-providers-main-product">You want analytics to be the provider’s main product</h3> <p>Analytics is one feature among many for a CMS or website builder. Its development competes with editing, hosting, commerce and account-management work. A dedicated analytics provider succeeds or fails on the quality of its measurement, reporting, integrations and support.</p> <p>That focus does not guarantee a better product. It does give you a useful way to assess one: review its documentation, release history, support for your platform and response to changes in browsers, privacy rules and marketing channels. The question is whether analytics is important enough to your work to justify a tool whose roadmap centres on it.</p> <h2 id="how-plausible-extends-built-in-cms-analytics">How Plausible extends built-in CMS analytics</h2> <p>Plausible is an independent, <a href="/privacy-focused-web-analytics">privacy-friendly</a> web analytics tool built as a <a href="/simple-web-analytics">simpler alternative to Google Analytics</a>. It works alongside your CMS rather than replacing the reports that belong there, such as Shopify orders, Ghost memberships or newsletter delivery.</p> <p>The aim is to make the website journey understandable in one place. The dashboard connects where measured visits came from, which content people used and which visits produced a signup, enquiry or sale. It does this without cookies, persistent visitor identifiers or the layers of reports and configuration associated with Google Analytics.</p> <h3 id="which-campaigns-and-pages-lead-to-a-result">Which campaigns and pages lead to a result?</h3> <p>Use <a href="/docs/goal-conversions">goals and conversions</a> to define results such as enquiries, signups, downloads or purchases. You can then <a href="/docs/filters-segments">filter the dashboard</a> by campaign, source, landing page, device or location and see the pages and behaviour associated with that result.</p> <p>For example, one article may attract the most readers while another produces more enquiries. Looking at traffic and goals together makes that distinction visible. If revenue values are configured, <a href="/docs/ecommerce-revenue-tracking">revenue attribution</a> can show which campaigns, sources and landing pages brought sales rather than simply how many orders the store processed.</p> <p>For a path you already know, <a href="/docs/funnel-analysis">Funnel analysis</a> on the Business plan shows completion and drop-off between steps. <a href="/docs/user-journeys">User journeys</a>, also on the Business plan, work in the other direction: start with a page or event and see what people did next, or start with a conversion and work backwards to what led there. Both depend on the relevant pages and events being measured correctly.</p> <h3 id="how-do-you-add-it-to-your-existing-site">How do you add it to your existing site?</h3> <p>If your site runs on WordPress, the <a href="/wordpress-analytics-plugin">official WordPress plugin</a> handles installation and lets you view Plausible inside WordPress. It can also exclude logged-in administrators, enable enhanced measurements and track WooCommerce revenue. The <a href="/docs/wordpress-integration">WordPress setup guide</a> explains which options to enable.</p> <p>For Shopify, the <a href="/docs/shopify-integration">Shopify integration guide</a> covers both storefront activity and customer events such as add to cart, checkout and purchase. The setup uses a script and a custom pixel. Adding only the theme script does not measure checkout pages, so the custom pixel matters if you want the complete purchase journey.</p> <p>There are also specific setup guides for <a href="/docs/squarespace-integration">Squarespace</a>, <a href="/docs/wix-integration">Wix</a>, <a href="/docs/webflow-integration">Webflow</a> and <a href="/docs/ghost-integration">Ghost</a>. These links are most useful after you decide that the platform’s own reports leave a gap. Check your website plan’s custom-code requirements before installing.</p> <h3 id="which-google-searches-bring-people-to-your-pages">Which Google searches bring people to your pages?</h3> <p>Google no longer includes search terms in the referral information sent when someone clicks a result, so a web analytics script cannot recover them on its own. The <a href="/google-search-console">Google Search Console integration</a> brings queries, clicks, impressions, click-through rate and position into Plausible. You can examine search terms for a page, country or device segment alongside the traffic and conversions already in the dashboard.</p> <p>The integration uses Search Console data, with a reporting delay of about 24 to 36 hours and Google’s sampling and privacy limits. You can filter search query data by page, country or device. With goals configured, you can also see which search keywords and landing pages are associated with signups or purchases. The reporting is aggregated and does not identify the person behind a query or purchase.</p> <h3 id="can-you-combine-sites-and-send-reports-to-clients">Can you combine sites and send reports to clients?</h3> <p>You can manage sites together, give colleagues or clients <a href="/docs/users-roles">role-based dashboard access</a> and use <a href="/docs/shared-links">private shared links</a> without giving them access to the underlying CMS.</p> <p><strong>Consolidated View</strong> combines native traffic data from sites in a team. It excludes imported history and revenue goals. It aggregates site activity rather than identifying the same person across unrelated websites. <a href="/docs/consolidated-views">Consolidated View details</a>.</p> <p>For reports outside Plausible, there are <a href="/docs/export-stats">CSV exports</a> or choose another option for <a href="/docs/data-access">accessing your data</a>, such as the Stats API. Dashboard exports have row limits and the separate full native-stats export excludes imported data. If you are moving from another tool, check the <a href="/docs/csv-import">historical import requirements</a> before assuming its data can be transferred.</p> <h3 id="what-visitor-data-does-plausible-collect">What visitor data does Plausible collect?</h3> <p>Plausible does not use cookies, local storage or persistent browser identifiers to track visitors. We do not store raw IP addresses, build personal profiles or use your website data for advertising. Daily visitor identifiers are limited to one site and device, then reset every 24 hours. You retain ownership of your data, which is processed and stored in the EU. <a href="/data-policy">Our data policy</a> explains the method and service providers.</p> <p>The tradeoff is intentional: you cannot use Plausible to recognize an identifiable person returning days later. Other services on your website may still require consent even though Plausible itself does not require an analytics cookie banner.</p> <p>If your current reports already answer your questions, there is no reporting gap to fill. If one of these needs remains, you can <a href="https://plausible.io/plausible.io">explore the live dashboard</a> or <a href="/register">try Plausible</a> alongside your existing setup. Include the subscription and any platform upgrade needed for custom scripts in the comparison.</p> <h2 id="frequently-asked-questions">Frequently asked questions</h2> <style>.cms-faq{margin-top:1.5rem;border-top:1px solid #e5e7eb}.cms-faq details{border-bottom:1px solid #e5e7eb;padding:1rem 0}.cms-faq summary{align-items:center;color:#111827;cursor:pointer;display:flex;font-weight:600;justify-content:space-between;list-style:none}.cms-faq summary::-webkit-details-marker{display:none}.cms-faq summary::after{align-items:center;background:#eef2ff;border-radius:9999px;color:#4f46e5;content:"+";display:inline-flex;flex:0 0 auto;font-size:1.25rem;height:1.75rem;justify-content:center;line-height:1;margin-left:1rem;width:1.75rem}.cms-faq details[open] summary::after{content:"-"}.cms-faq p{color:#4b5563;line-height:1.7;margin:.75rem 2.75rem 0 0}</style> <div class="cms-faq"> <details> <summary>Can I export Squarespace analytics into a spreadsheet?</summary> <p>No. Squarespace currently says its analytics reports cannot be exported. Orders or other downloadable site data should not be confused with traffic-report exports. A separate analytics installation can provide exportable reporting going forward, but it cannot automatically recover your old Squarespace stats. See <a href="https://support.squarespace.com/hc/en-us/articles/206544167-Squarespace-Analytics">Squarespace’s current answer</a>.</p> </details> <details> <summary>Wix shows fewer sessions than Search Console clicks. Is tracking broken?</summary> <p>Not necessarily. Search Console counts clicks that lead from Google results to your site, while Wix counts sessions recorded on the website. One click does not map one-to-one to one session. Google can count repeated clicks differently depending on the result and report aggregation, while Wix ends a session after 30 minutes of inactivity. Wix also says traffic from visitors who do not accept cookies, or who use certain ad blockers, does not appear in its traffic reports. Align the dates and definitions, then investigate a sudden change rather than expecting the totals to match. See Google’s <a href="https://support.google.com/webmasters/answer/7042828">click-counting documentation</a> and Wix’s <a href="https://support.wix.com/en/article/wix-analytics-traffic-sales-and-behavior-overviews">Traffic Overview</a> and <a href="https://support.wix.com/en/article/discrepancies-between-wix-analytics-data-in-other-tracking-tools">discrepancy guide</a>.</p> </details> <details> <summary>Why does Shopify show orders when my conversion report is empty?</summary> <p>Shopify can report more orders than converted sessions because one session can contain multiple separate purchases. Consent choices can also reduce session counts and other session-based metrics. Compare orders with converted sessions rather than expecting them to match. Shopify explains both causes in its <a href="https://help.shopify.com/en/manual/reports-and-analytics/discrepancies/customer-discrepancies">customer and session discrepancy guide</a>.</p> </details> <details> <summary>Ghost and Plausible show different countries. Which should I trust?</summary> <p>Country totals alone do not prove that one tool missed people or the other counted bots. The tools may use different geolocation databases, collection methods and filtering rules. Compare the same dates, then inspect the affected traffic and check collection failures and filtering. Check Plausible’s <a href="/docs/bot-traffic-filtering">bot filtering</a> and <a href="/docs/troubleshoot-integration">integration troubleshooting</a> guides so you can investigate the actual setup.</p> </details> <details> <summary>Can I keep my own WordPress visits out of Plausible?</summary> <p>Yes. Plausible’s official plugin excludes logged-in administrator visits by default and lets you configure other user roles. Logged-out browsing needs separate exclusion. See the <a href="/docs/wordpress-integration">WordPress plugin settings</a> and <a href="/docs/excluding">visitor exclusion options</a>.</p> </details> <details> <summary>Can I see traffic from all my websites in one dashboard?</summary> <p>Yes. The sites do not need to use the same CMS. Install Plausible on each site and use <strong>Consolidated View</strong> for combined native traffic reporting. Individual site dashboards remain available. Imported history and revenue goals are excluded from the combined view, as explained in the <a href="/docs/consolidated-views">Consolidated View guide</a>.</p> </details> </div>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Answers to real questions about Squarespace, Wix, Shopify, WordPress.com, Ghost and Webflow analytics: accuracy, exports, privacy and when to add Plausible.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png"/><media:content medium="image" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">What is direct traffic? What does it include, and why is its share the highest?</title><link href="https://plausible.io/blog/direct-traffic" rel="alternate" type="text/html" title="What is direct traffic? What does it include, and why is its share the highest?"/><published>2026-09-16T08:00:00+00:00</published><updated>2026-09-16T08:00:00+00:00</updated><id>https://plausible.io/blog/direct-traffic</id><content type="html" xml:base="https://plausible.io/blog/direct-traffic"><![CDATA[<p>Is “Direct” your biggest traffic source, ahead of search, social, AI assistants and referrals from other websites? You put effort into those channels, yet the biggest row in your report doesn’t tell you where anyone came from. And some of those “direct” visitors are landing on URLs you wouldn’t expect anyone to remember, let alone type.</p> <p>So where are they actually coming from?</p> <p><strong>Direct means your analytics couldn’t identify the source of the visit.</strong> Typing your address is one way to get there. Clicking an untagged newsletter link, opening a recommendation in a messaging app, or following a link that loses its source information can produce the same result. In Plausible, these visits appear as <strong>Direct / None</strong>.</p> <p><strong>Some of this can absolutely reflect brand strength</strong>: people remember you, choose to come back, or recommend you to someone else. The question is how much of your traffic reflects that familiarity, and how much you could identify with better campaign tagging.</p> <p>If you’re looking at Google Analytics, its <strong>(direct) / (none)</strong> label refers to the same basic issue: <a href="https://support.google.com/analytics/answer/15258820?hl=en">no clear source for the traffic</a>. The concerns below apply there too; the dashboard steps are for Plausible.</p> <ol id="markdown-toc"> <li><a href="#why-is-direct-traffic-my-biggest-source" id="markdown-toc-why-is-direct-traffic-my-biggest-source">Why is direct traffic my biggest source?</a></li> <li><a href="#nobody-is-typing-these-long-urls-where-are-those-visits-coming-from" id="markdown-toc-nobody-is-typing-these-long-urls-where-are-those-visits-coming-from">Nobody is typing these long URLs. Where are those visits coming from?</a></li> <li><a href="#why-are-new-visitors-showing-up-as-direct-theyve-never-heard-of-us" id="markdown-toc-why-are-new-visitors-showing-up-as-direct-theyve-never-heard-of-us">Why are new visitors showing up as direct? They’ve never heard of us</a></li> <li><a href="#we-sent-a-newsletter-why-did-direct-go-up-instead-of-email" id="markdown-toc-we-sent-a-newsletter-why-did-direct-go-up-instead-of-email">We sent a newsletter. Why did direct go up instead of email?</a></li> <li><a href="#we-already-added-utms-why-is-traffic-still-showing-as-direct" id="markdown-toc-we-already-added-utms-why-is-traffic-still-showing-as-direct">We already added UTMs. Why is traffic still showing as direct?</a></li> <li><a href="#are-browsers-and-privacy-tools-hiding-the-source" id="markdown-toc-are-browsers-and-privacy-tools-hiding-the-source">Are browsers and privacy tools hiding the source?</a></li> <li><a href="#direct-traffic-suddenly-spiked-is-it-bots" id="markdown-toc-direct-traffic-suddenly-spiked-is-it-bots">Direct traffic suddenly spiked. Is it bots?</a></li> <li><a href="#how-can-i-make-my-traffic-reports-more-accurate" id="markdown-toc-how-can-i-make-my-traffic-reports-more-accurate">How can I make my traffic reports more accurate?</a> <ol> <li><a href="#first-check-where-visits-start-and-what-has-changed" id="markdown-toc-first-check-where-visits-start-and-what-has-changed">First, check where visits start and what has changed</a></li> <li><a href="#tag-your-campaign-links-with-utms" id="markdown-toc-tag-your-campaign-links-with-utms">Tag your campaign links with UTMs</a></li> <li><a href="#use-a-proxy-to-count-visits-that-blockers-would-hide" id="markdown-toc-use-a-proxy-to-count-visits-that-blockers-would-hide">Use a proxy to count visits that blockers would hide</a></li> <li><a href="#exclude-internal-and-test-traffic" id="markdown-toc-exclude-internal-and-test-traffic">Exclude internal and test traffic</a></li> </ol> </li> <li><a href="#can-i-find-out-where-the-rest-of-my-direct-traffic-came-from" id="markdown-toc-can-i-find-out-where-the-rest-of-my-direct-traffic-came-from">Can I find out where the rest of my direct traffic came from?</a></li> <li><a href="#should-i-worry-about-a-high-direct-share" id="markdown-toc-should-i-worry-about-a-high-direct-share">Should I worry about a high direct share?</a> <ol> <li><a href="#doesnt-direct-traffic-also-show-brand-strength" id="markdown-toc-doesnt-direct-traffic-also-show-brand-strength">Doesn’t direct traffic also show brand strength?</a></li> <li><a href="#what-should-i-actually-be-concerned-about" id="markdown-toc-what-should-i-actually-be-concerned-about">What should I actually be concerned about?</a></li> </ol> </li> </ol> <h2 id="why-is-direct-traffic-my-biggest-source">Why is direct traffic my biggest source?</h2> <p>Because Direct can collect visits from several places whose sources aren’t identifiable for some reason.</p> <p>Google, Bing, LinkedIn, an AI assistant or a referring website each represents an identifiable source. Direct combines returning customers, email readers, private recommendations and other visits with missing source information. That mixture can be bigger than any individual source, or even a whole channel such as organic search or social.</p> <p>You don’t need to be a famous brand for direct traffic to be your biggest source.</p> <p>If you run a product that customers return to every day, some of those visits may simply be people opening a bookmark or choosing your site from their browser history. Your own team can contribute visits too.</p> <h2 id="nobody-is-typing-these-long-urls-where-are-those-visits-coming-from">Nobody is typing these long URLs. Where are those visits coming from?</h2> <p>They don’t have to type them. Someone can reach a specific product page or article through:</p> <ul> <li>A link in an email, WhatsApp message, Slack conversation or another app.</li> <li>A link in a PDF, slide deck or downloaded document.</li> <li>A copied URL pasted into the address bar.</li> <li>A bookmark or a suggestion from their browser history.</li> <li>A QR code pointing to the page.</li> </ul> <p>When a browser opens a link, it can tell your site where the visitor came from. That information is called the <strong>referrer</strong>. Apps and documents don’t always supply one, and an untagged URL may offer no other clue.</p> <p>Traffic with an unknown origin is often called <strong>dark traffic</strong>. When it comes from private sharing, such as a recommendation in a group chat, you’ll also hear <strong>dark social</strong>. That describes one part of the list above, so a long URL alone isn’t enough to tell you it was shared privately.</p> <p>You can still see how many visits you received, which pages people viewed and whether they converted. It’s the source of those visits that’s unknown.</p> <p>App behavior varies depending on the app, device and how the link opens. Plausible <a href="https://plausible.io/docs/top-referrers#we-attempt-to-uncover-some-direct-traffic">recognizes some Android app referrals</a> when that information is available.</p> <p>For a particular article or product page, check where you’ve recently shared it. A direct spike on the day it appeared in a newsletter gives you something concrete to investigate, even if it doesn’t identify every visit.</p> <h2 id="why-are-new-visitors-showing-up-as-direct-theyve-never-heard-of-us">Why are new visitors showing up as direct? They’ve never heard of us</h2> <p>Someone recommends your product in a private message. The recipient has never heard of you, but opens the link. If there’s no referrer or campaign information, their very first visit can be direct. They don’t need to know your address or have visited before.</p> <p>The reverse is also worth remembering: someone who knows your brand and searches for it on Google normally arrives as organic search when they click an unpaid result. Brand familiarity and traffic source are different things.</p> <h2 id="we-sent-a-newsletter-why-did-direct-go-up-instead-of-email">We sent a newsletter. Why did direct go up instead of email?</h2> <p>Check the links in the email you actually sent. Do they include UTM tags?</p> <p>Without tags, a click from an email client that supplies no useful referrer can appear as direct. Your newsletter may be bringing people in without getting named in the report.</p> <p>UTM tags give the link a source and campaign name your analytics can read. If you haven’t used them before, <a href="#tag-your-campaign-links-with-utms">there’s an example below</a>.</p> <p>Not every untagged campaign becomes direct. A social network may still identify itself, but you might lose the distinction between a paid ad and an organic post. Tags help with that too.</p> <h2 id="we-already-added-utms-why-is-traffic-still-showing-as-direct">We already added UTMs. Why is traffic still showing as direct?</h2> <p>Adding tags to a spreadsheet or an ad setup isn’t the final check. They need to reach the page where your analytics records the visit.</p> <p><strong>Open the actual published link and follow it through to the destination.</strong> Check these three things:</p> <ul> <li><strong>Did a redirect drop the tags?</strong> A shortener, email click tracker or redirect from an old URL may discard the query parameters. Redirects don’t always do this, so test yours before blaming them.</li> <li><strong>Does the landing page record visits?</strong> If tracking is missing there, your analytics may only see the visitor after they click further into the site, without the original campaign information. Check the tracking installation on that specific page (<a href="https://plausible.io/docs/troubleshoot-integration">here’s how to do it in Plausible</a>).</li> <li><strong>Are you testing during an existing session?</strong> In Plausible, clicking another tagged link during an active session doesn’t replace that session’s original source. For a reliable test, use a device and network combination that hasn’t visited in the past 30 minutes. Opening an incognito window may not be enough. See <a href="https://plausible.io/docs/top-referrers#utm-parameters-not-appearing-in-campaigns">our UTM testing notes</a>.</li> </ul> <h2 id="are-browsers-and-privacy-tools-hiding-the-source">Are browsers and privacy tools hiding the source?</h2> <p>They can, but “privacy” doesn’t explain every direct visit.</p> <p>A referring site can suppress the referrer, and browser settings or extensions can restrict it. If no usable campaign information arrives either, a recorded visit can end up as direct.</p> <p>But browsers often remove only the <strong>specific page</strong>, while keeping the referring website. A click from <code class="language-plaintext highlighter-rouge">thatblog.com/article</code> may tell your analytics <code class="language-plaintext highlighter-rouge">thatblog.com</code>. You still know the source. Our <a href="/blog/referrer-policy">referrer policy post</a> explains that loss of detail.</p> <p>The common browser policy also drops the referrer when navigating from HTTPS to HTTP. Going from HTTP to HTTPS doesn’t inherently do the same. <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy">MDN’s policy reference</a> covers the differences.</p> <p>And if a blocker prevents analytics from recording a visit altogether, that visit is missing from the report. It doesn’t automatically become direct. You can’t use the Direct percentage to count people using privacy tools.</p> <h2 id="direct-traffic-suddenly-spiked-is-it-bots">Direct traffic suddenly spiked. Is it bots?</h2> <p>Possibly. Automated visits can inflate Direct if your analytics counts them without source information. But the source label alone doesn’t tell you whether a visitor is human.</p> <p>Look at when the increase started. Did you send a campaign, get a mention, change redirects or update tracking? If a known source dropped at the same time, test its links. That timing is a clue, not proof that all those visits moved into Direct.</p> <p>Then look at the spike itself. Repetitive page requests, unusual bursts, an unexpected device or location mix, and little meaningful activity together are reasons to investigate bots. A high bounce rate or a particular country alone isn’t enough. Our <a href="/blog/spike-in-website-traffic">traffic spike investigation</a> goes through the checks.</p> <p><strong>Plausible filters bot traffic automatically.</strong> We exclude known bots and crawlers, traffic from known data center IP ranges, known referrer spam, and traffic patterns that look automated. These filters are on by default and we update them as new patterns emerge. Here’s <a href="https://plausible.io/docs/bot-traffic-filtering">how the filtering works</a>.</p> <p>We also <a href="/blog/testing-bot-traffic-filtering-google-analytics">ran a controlled bot experiment</a>, sending automated visits to a test site, including visits that identified themselves as ordinary browsers. Google Analytics counted the simulated traffic; Plausible rejected it in our tests.</p> <p>Some bots can still get through. If suspicious traffic persists in Plausible, <a href="/contact">contact us</a> with the dates and patterns you’ve noticed. Adding UTMs won’t fix bot traffic: they identify campaign links, while filtering excludes automated visits from your stats.</p> <h2 id="how-can-i-make-my-traffic-reports-more-accurate">How can I make my traffic reports more accurate?</h2> <p>Start by checking which visits you’re trying to understand. Then you can decide whether you need better campaign tags, help counting missed visits, or a way to keep your own testing out of the reports.</p> <h3 id="first-check-where-visits-start-and-what-has-changed">First, check where visits start and what has changed</h3> <p><strong>Check where those visits start.</strong> In Plausible, click <strong>Direct / None</strong> in Sources, then look at <strong>Entry Pages</strong>. Lots of visits to a login page or dashboard suggest a different explanation from lots of visits to a newly published article. For homepage visits, check whether people go on to log in or explore the product.</p> <p>Also check the actual count, not just the percentage. If direct stays at 200 visits while total visits fall from 1,000 to 500, its share doubles from 20% to 40%. In that case, investigate what happened to your other traffic sources.</p> <h3 id="tag-your-campaign-links-with-utms">Tag your campaign links with UTMs</h3> <p><strong>UTM tags give the link a source and campaign name your analytics can read.</strong> For example:</p> <p><code class="language-plaintext highlighter-rouge">https://example.com/new-feature?utm_source=newsletter&amp;utm_medium=email&amp;utm_campaign=september-update</code></p> <p>This identifies the source as <code class="language-plaintext highlighter-rouge">newsletter</code>, the medium as <code class="language-plaintext highlighter-rouge">email</code>, and the campaign as <code class="language-plaintext highlighter-rouge">september-update</code>.</p> <p>Start with external links you control: newsletters, ads, social profiles and posts, partner placements, and downloadable documents. In Plausible, open <strong>Campaigns</strong> to see tagged traffic and filter by the campaign to check activity and goal conversions.</p> <p>Use our <a href="/utm-builder">UTM builder</a> to create the links, or the <a href="/utm-checker">UTM checker</a> to check ones you’ve already made. The <a href="/blog/utm-tracking-tags">full UTM guide</a> covers naming conventions and the other parameters.</p> <p>Keep UTMs on incoming campaign links. Use events or goals for clicks within your own website, and keep personal information such as email addresses out of the tags.</p> <h3 id="use-a-proxy-to-count-visits-that-blockers-would-hide">Use a proxy to count visits that blockers would hide</h3> <p>For those missed visits, Plausible offers a <a href="https://plausible.io/docs/proxy/introduction">proxy setup</a>. It serves the analytics script through your own domain, helping it get past many blockers so more visits are counted.</p> <p>A proxy does not restore a referrer or UTM tags that were stripped before the visitor arrived, though. It can improve overall traffic accuracy, without necessarily reducing Direct.</p> <h3 id="exclude-internal-and-test-traffic">Exclude internal and test traffic</h3> <p>If your team regularly tests the site, Plausible’s <a href="https://plausible.io/docs/excluding">traffic exclusion controls</a> can keep those visits out of your stats. You can exclude your office IP addresses or your own browser. If staging or preview sites use the same tracking setup, a hostname allowlist lets you record only your live website’s hostnames. These controls stop unwanted visits from being recorded; they don’t identify the sources of the remaining direct traffic.</p> <h2 id="can-i-find-out-where-the-rest-of-my-direct-traffic-came-from">Can I find out where the rest of my direct traffic came from?</h2> <p>If the source information wasn’t collected, you can’t reliably reconstruct it from the Direct total. Adding UTMs now won’t identify past visits.</p> <p>For future visits, start by getting your own campaign links in order. That still leaves links other people share without tags, and customers returning through bookmarks. Those visits won’t all become identifiable just because your campaigns are tagged correctly.</p> <p>Even tagged links have limits. If someone forwards your newsletter URL into a group chat, its UTM tags can still say <code class="language-plaintext highlighter-rouge">newsletter</code>. You know which campaign link was used, but not every place it was shared.</p> <h2 id="should-i-worry-about-a-high-direct-share">Should I worry about a high direct share?</h2> <h3 id="doesnt-direct-traffic-also-show-brand-strength">Doesn’t direct traffic also show brand strength?</h3> <p><strong>Yes, some of it does.</strong> People remembering your address, bookmarking your content and returning to buy are signs that you’ve given them a reason to come back. Recommendations shared privately can also reflect trust in your brand, even when analytics can’t identify the conversation.</p> <p>The limit is that Direct mixes those visits with untagged campaigns and other missing-source traffic. You can’t count the whole row as brand-driven demand, or assume that a rise means awareness has grown.</p> <p>Ask customers how they heard about you, especially when recommendations or offline activity matter to your business. Their answers, more searches for your brand, and direct visitors taking meaningful actions give you a stronger case than the Direct percentage alone.</p> <h3 id="what-should-i-actually-be-concerned-about">What should I actually be concerned about?</h3> <p>Unexplained changes and campaigns you can’t evaluate deserve attention. A high direct share by itself isn’t a reason to assume something is wrong.</p> <p>There isn’t a universal “healthy” direct percentage. Compare against your own history, using the same metric and similar periods.</p> <p>After you fix your tags, Direct may fall while Email or another source rises. That can be the same traffic becoming easier to identify. You haven’t necessarily lost visitors; you’ve learned more about where they’re coming from.</p> <div x-data="" x-show="!document.cookie.includes('logged_in=true')" class="cta-box my-8 rounded-lg border border-indigo-100 bg-indigo-50 p-6"> <p class="text-base font-semibold text-gray-900 mt-0 mb-0">Check the links in your next campaign</p> <div class="mt-4 flex flex-wrap" style="gap: 0.75rem;"> <a href="/utm-builder" onclick="plausible('CTA Click', {props: {position: 'Inline', type: 'Blog', button: 'Build a UTM link'}})" class="cta-box-primary inline-flex items-center justify-center px-4 py-2 border border-transparent text-sm font-medium rounded-md text-white bg-indigo-600 hover:bg-indigo-500 focus:outline-none transition duration-150 ease-in-out"> Build a UTM link </a> <a href="/utm-checker" onclick="plausible('CTA Click', {props: {position: 'Inline', type: 'Blog', button: 'Check an existing link'}})" class="cta-box-secondary inline-flex items-center justify-center px-4 py-2 text-sm font-medium rounded-md bg-white focus:outline-none transition duration-150 ease-in-out" style="border: 1px solid #C7D2FE; color: #4338ca;"> Check an existing link </a> </div> </div>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Why is Direct your biggest traffic source? Are those visits bots? Why are tagged campaigns still showing as direct? Answers and practical checks.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/direct-traffic-plausible.png"/><media:content medium="image" url="https://plausible.io/uploads/direct-traffic-plausible.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">Web analytics: what it is, how it works and how to use it</title><link href="https://plausible.io/blog/web-analytics" rel="alternate" type="text/html" title="Web analytics: what it is, how it works and how to use it"/><published>2026-09-11T07:00:00+00:00</published><updated>2026-09-11T07:00:00+00:00</updated><id>https://plausible.io/blog/web-analytics</id><content type="html" xml:base="https://plausible.io/blog/web-analytics"><![CDATA[<p>Web analytics helps you understand how people find and use your website. How many people visit? Where do they come from? Which pages do they view? And do they sign up, buy something or complete another important goal?</p> <p>Those are simple questions, but answering them well can help you decide what to publish, which campaigns to continue and where your website needs work. This guide covers how web analytics works, the metrics worth knowing and how to put the data to use.</p> <ol id="markdown-toc"> <li><a href="#what-is-web-analytics" id="markdown-toc-what-is-web-analytics">What is web analytics?</a></li> <li><a href="#why-is-web-analytics-important" id="markdown-toc-why-is-web-analytics-important">Why is web analytics important?</a></li> <li><a href="#how-does-web-analytics-work" id="markdown-toc-how-does-web-analytics-work">How does web analytics work?</a></li> <li><a href="#important-web-analytics-metrics" id="markdown-toc-important-web-analytics-metrics">Important web analytics metrics</a> <ol> <li><a href="#sources-pages-and-campaigns" id="markdown-toc-sources-pages-and-campaigns">Sources, pages and campaigns</a></li> <li><a href="#goals-funnels-and-journeys" id="markdown-toc-goals-funnels-and-journeys">Goals, funnels and journeys</a></li> </ol> </li> <li><a href="#how-to-set-up-web-analytics" id="markdown-toc-how-to-set-up-web-analytics">How to set up web analytics</a></li> <li><a href="#common-web-analytics-mistakes" id="markdown-toc-common-web-analytics-mistakes">Common web analytics mistakes</a></li> <li><a href="#choosing-a-web-analytics-tool" id="markdown-toc-choosing-a-web-analytics-tool">Choosing a web analytics tool</a></li> <li><a href="#web-analytics-with-plausible" id="markdown-toc-web-analytics-with-plausible">Web analytics with Plausible</a></li> <li><a href="#frequently-asked-questions" id="markdown-toc-frequently-asked-questions">Frequently asked questions</a></li> </ol> <h2 id="what-is-web-analytics">What is web analytics?</h2> <p>Web analytics is the collection, measurement and analysis of website data. Most of it falls into three areas:</p> <ol> <li><strong>Acquisition:</strong> How visitors find you through search, referrals, social media, email and campaigns.</li> <li><strong>Engagement:</strong> Which pages and actions visitors interact with.</li> <li><strong>Conversion:</strong> Whether they complete an important outcome such as a purchase, signup or enquiry.</li> </ol> <p>Put together, these reports show the journey from arrival to outcome. An ecommerce store, for example, can see which campaign brought visitors to a product page, how many started checkout and how many purchased. A publisher can find the articles that attract search traffic and lead to newsletter signups.</p> <h2 id="why-is-web-analytics-important">Why is web analytics important?</h2> <p>Without analytics, you are largely guessing whether your website is doing its job. With it, you can:</p> <ul> <li>understand which channels bring useful traffic;</li> <li>find popular and underperforming content;</li> <li>compare campaigns using conversions rather than clicks alone;</li> <li>identify drop-off in signup or checkout funnels;</li> <li>prioritize mobile, browser or location-specific improvements; and</li> <li>investigate unexpected traffic spikes and drops.</li> </ul> <p>The purpose is not simply to collect numbers. It is to find what is working, what needs attention and what to do next.</p> <p>That does not mean every decision has to begin in a dashboard. Analytics is most useful when it gives context to something you have already noticed or helps you check an assumption. If customers say that checkout is difficult, the funnel can show how widespread the problem is. If an article suddenly gets more attention, the sources report can show where those readers came from and whether they explored anything else.</p> <h2 id="how-does-web-analytics-work">How does web analytics work?</h2> <p>Most tools use a small JavaScript snippet added to each page. When someone loads a page, it sends a pageview event containing information such as the page URL, referrer, campaign parameters, device and browser.</p> <p>The analytics service then turns those events into familiar reports for visitors, visits, pages, sources and conversions. Along the way, it may filter known bots and group individual sources into broader channels.</p> <p>You can record custom events beyond pageviews, including form submissions, downloads, signups, cart activity and purchases.</p> <p>Some tools use cookies or persistent identifiers to recognize browsers across visits. Others, including Plausible, provide <a href="/cookieless-web-analytics">cookieless web analytics</a> without creating persistent visitor profiles.</p> <p>JavaScript is the most common method, but it is not the only one. Server logs can see requests that browser scripts miss, although they also include bots and requests for files. <a href="/blog/server-side-tracking-guide">Server-side events</a> are useful for actions confirmed by your backend, such as a successfully created account. Some websites combine these methods because each captures a different part of the activity.</p> <h2 id="important-web-analytics-metrics">Important web analytics metrics</h2> <p>An analytics dashboard can show dozens of metrics, but you can understand most websites with a relatively small set. Start with the size of the audience, learn where it came from, then look at what those visitors did. Add more measurements only when they help answer a real question.</p> <table> <thead> <tr> <th>Metric</th> <th>What it means</th> </tr> </thead> <tbody> <tr> <td><strong>Visitors</strong></td> <td>Distinct visitors measured during a period</td> </tr> <tr> <td><strong>Visits or sessions</strong></td> <td>Separate periods of activity</td> </tr> <tr> <td><strong>Pageviews</strong></td> <td>Total tracked page loads</td> </tr> <tr> <td><strong>Views per visit</strong></td> <td>Average pages viewed during a visit</td> </tr> <tr> <td><strong>Visit duration</strong></td> <td>Time measured during a visit</td> </tr> <tr> <td><strong>Bounce rate</strong></td> <td>Visits with little or no further engagement</td> </tr> <tr> <td><strong>Conversions</strong></td> <td>Completed actions you define as important</td> </tr> <tr> <td><strong>Conversion rate</strong></td> <td>Percentage of visitors that complete a goal</td> </tr> <tr> <td><strong>Revenue</strong></td> <td>Purchase value connected to conversions</td> </tr> </tbody> </table> <p>You will find most of these metrics in any general web analytics product. Their exact definitions can differ, though, so check how each tool calculates them before comparing dashboards. Here are <a href="https://plausible.io/docs/metrics-definitions">Plausible’s metric definitions</a>.</p> <h3 id="sources-pages-and-campaigns">Sources, pages and campaigns</h3> <p>Source reports show whether visitors came from search, referrals, social media, email, advertising or direct traffic. Entry pages show where visits began; top pages show what people viewed; exit pages show where visits ended.</p> <p>These reports are most useful together. A list of top pages tells you what is popular, but not why people reached those pages or whether the visits were valuable. Filtering the dashboard by a page connects that content to its sources, audience and goals.</p> <p>Direct is a fallback when referral information is unavailable, not only people typing your address. Use <a href="/blog/utm-tracking-tags">UTM parameters</a> on campaign links to make attribution clearer.</p> <p>Traffic is only the starting point. Filter a source or page and look at engagement, goals and revenue too. A smaller source with a strong conversion rate may be much more valuable than the one sending the most visitors.</p> <h3 id="goals-funnels-and-journeys">Goals, funnels and journeys</h3> <p>A goal can be a thank-you page or an event such as Signup or Purchase. A funnel measures a known sequence, for example Product page → Cart → Checkout → Purchase.</p> <p>This makes it easy to see where visitors stop. If you do not know the path in advance, <a href="/blog/website-journey-analytics">website journey analytics</a> can instead show what happened before or after a particular page or event.</p> <p>Not every website needs a complicated funnel. A personal site may only need to measure contact-form submissions. A publication may care about newsletter signups. The point is to choose actions that reflect why the site exists rather than turning every click into a goal.</p> <h2 id="how-to-set-up-web-analytics">How to set up web analytics</h2> <p>It is tempting to design a complete tracking plan before installing anything. For most websites, a smaller start works better. Set up the basic traffic reports and one or two meaningful goals, use them for a while and let real questions guide what you add next.</p> <ol> <li><strong>Define the website’s purpose.</strong> Choose one or two primary outcomes.</li> <li><strong>Choose a suitable tool.</strong> Consider reports, privacy, ease of use, performance and cost.</li> <li><strong>Install it on every relevant page.</strong> Include subdomains or checkout pages where needed.</li> <li><strong>Verify the installation.</strong> Visit the site and confirm the pageview appears once in real time.</li> <li><strong>Configure and test goals.</strong> Measure completed outcomes where possible.</li> <li><strong>Tag campaigns consistently.</strong> Use agreed lowercase UTM values, but never add UTMs to internal links.</li> <li><strong>Review useful comparisons.</strong> Compare periods and segment by source, page, campaign, device or country.</li> </ol> <p>Our guide to <a href="/blog/check-website-traffic">checking your own website traffic</a> walks through the complete process.</p> <p>Once data starts arriving, give it enough time to become representative. Real-time reports are useful for confirming that tracking works, but a handful of visits cannot tell you whether a page or campaign is successful. Look at an appropriate date range and compare it with a similar period.</p> <h2 id="common-web-analytics-mistakes">Common web analytics mistakes</h2> <p>Most analytics mistakes come from reading a number without asking what produced it or what the page was meant to do. The dashboard may be accurate while the conclusion drawn from it is not.</p> <p><strong>Treating more traffic as automatic success.</strong> A spike looks encouraging, but it may come from bots, an irrelevant referral or visitors who have no interest in what you offer. Traffic matters when it reaches the intended audience and produces useful outcomes.</p> <p><strong>Judging engagement without page context.</strong> A visitor can find an answer on one page and leave satisfied. An exit from a thank-you page is expected; an exit halfway through checkout is more interesting. A bounce or exit is not automatically bad.</p> <p><strong>Expecting different sources to match.</strong> Search engines count search clicks, ad platforms count ad clicks, servers count requests and web analytics products apply different visitor and session rules. Read why <a href="/blog/why-analytics-numbers-dont-match">analytics numbers do not match</a>.</p> <p><strong>Tracking everything.</strong> It is easy to assume that data may become useful later. In practice, hundreds of undocumented events make reports harder to trust and create unnecessary privacy risk. Collect events that answer real questions and make sure everyone understands what they mean.</p> <h2 id="choosing-a-web-analytics-tool">Choosing a web analytics tool</h2> <p>Start with the decisions you need to make, since products with similar labels can solve quite different problems. General website analytics products such as Plausible and GA4 cover traffic, pages, campaigns and conversions. Behavior analytics products add heatmaps or session replay, while product analytics focuses on user histories, feature adoption and retention. Competitive analytics products estimate other websites’ traffic, but they cannot replace first-party analytics on a site you own.</p> <p>You may need more than one category, but you probably do not need every category. A content site may be perfectly served by general web analytics and search-performance data. A software company may use web analytics for its marketing site and separate product analytics inside the application.</p> <p>Compare tools using:</p> <ul> <li>reports and integrations;</li> <li>ease of use;</li> <li>data collection and privacy;</li> <li>documented metric definitions;</li> <li>script performance;</li> <li>data ownership and hosting; and</li> <li>subscription and operational costs.</li> </ul> <p>If you need multi-month user or account retention, you may need product analytics too. Our <a href="/blog/web-analytics-vs-product-analytics">web analytics vs product analytics guide</a> explains the difference.</p> <p>Whichever product you choose, test it with the people who will actually use it. A long feature list is not much help if answering a routine question requires specialist training or another custom report.</p> <h2 id="web-analytics-with-plausible">Web analytics with Plausible</h2> <p>We’re <a href="https://plausible.io/">Plausible Analytics</a>, and we have been building a simpler approach to web analytics since 2019. We bring visitors, visits, pageviews, sources, campaigns, pages, locations, devices, goals, revenue, funnels and journeys into one real-time dashboard. You can start with the overview, then click any entry to filter the rest of the dashboard and investigate further.</p> <p>We do not use cookies, collect personal data or create persistent visitor profiles. Our script is <a href="/lightweight-web-analytics">lightweight</a>, our cloud service is hosted in the EU and our code is <a href="/open-source-website-analytics">open source</a>.</p> <p>We built it this way because most website owners do not need an individual history of every visitor. They need to understand what brings people to the site, which content works and whether visitors complete the actions that matter. Keeping those answers together also makes the dashboard useful to people who are not full-time analysts.</p> <p>If that sounds like the kind of web analytics you need, you can explore our <a href="https://plausible.io/plausible.io">live public dashboard</a> or <a href="/register">start a free 30-day trial</a>.</p> <h2 id="frequently-asked-questions">Frequently asked questions</h2> <style>.web-analytics-faq{margin-top:1.5rem;border-top:1px solid #e5e7eb}.web-analytics-faq details{border-bottom:1px solid #e5e7eb;padding:1rem 0}.web-analytics-faq summary{align-items:center;color:#111827;cursor:pointer;display:flex;font-weight:600;justify-content:space-between;list-style:none}.web-analytics-faq summary::-webkit-details-marker{display:none}.web-analytics-faq summary::after{align-items:center;background:#eef2ff;border-radius:9999px;color:#4f46e5;content:"+";display:inline-flex;flex:0 0 auto;font-size:1.25rem;height:1.75rem;justify-content:center;line-height:1;margin-left:1rem;width:1.75rem}.web-analytics-faq details[open] summary::after{content:"-"}.web-analytics-faq p{color:#4b5563;line-height:1.7;margin:.75rem 2.75rem 0 0}</style> <div class="web-analytics-faq"> <details><summary>What are the two main types of web analytics?</summary><p>The two main types are on-site and off-site analytics. On-site analytics measures activity on a website you control, including visits, traffic sources, pages and conversions. Off-site analytics uses external data to estimate another website's traffic, search visibility or wider market performance. If you want accurate data for your own website, you should install an on-site analytics tool.</p></details> <details><summary>Is GA4 the same as web analytics?</summary><p>No. Web analytics is the wider practice of collecting and analyzing website data, while GA4 is one product used to do it. Different web analytics products can collect data differently and offer different approaches to privacy, reporting and metric definitions. You do not need to use GA4 specifically to understand your website traffic and conversions.</p></details> <details><summary>Can web analytics work without cookies?</summary><p>Yes. Cookies can help an analytics product recognize the same browser across multiple visits, but they are not required to measure aggregate traffic, sources, pages, campaigns and conversions. Plausible provides this information without cookies or persistent visitor identifiers, so you can understand how your website performs without creating long-term profiles of individual visitors.</p></details> </div>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Learn what web analytics measures, how it works, which metrics matter and how to use website data to improve traffic and conversions.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png"/><media:content medium="image" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">Web analytics vs product analytics: core difference and how to choose?</title><link href="https://plausible.io/blog/web-analytics-vs-product-analytics" rel="alternate" type="text/html" title="Web analytics vs product analytics: core difference and how to choose?"/><published>2026-09-03T01:00:00+00:00</published><updated>2026-09-03T01:00:00+00:00</updated><id>https://plausible.io/blog/web-analytics-vs-product-analytics</id><content type="html" xml:base="https://plausible.io/blog/web-analytics-vs-product-analytics"><![CDATA[<p>A visitor finds your SaaS through a comparison page, reads your pricing page and starts a trial. Then they create a project, invite a teammate and return three days later.</p> <p>That looks like one customer journey. In analytics, however, it contains two different sets of questions:</p> <ul> <li><strong>Web analytics:</strong> Where did the visitor come from? Which landing page and campaign led to the signup? Where did people leave the signup flow?</li> <li><strong>Product analytics:</strong> Did the new account reach its activation milestone? Which features did it use? Did it return in week two? Do invited teams retain better than solo users?</li> </ul> <p>The difference is not simply “website data” versus “app data.” Both types of tools can track pages, events and funnels. The more useful distinction is the decision you are trying to make and the level of continuity the answer requires.</p> <p>Web analytics is mostly used to improve acquisition, content and conversion. Product analytics is used to improve how people activate, adopt features and receive value from a product. The data needed depends on the question: a feature count is much simpler than a retention cohort that follows the same accounts for several months.</p> <p>This guide explains where that line sits, where <a href="/for-saas">Plausible</a> fits and when you should use a dedicated product analytics platform instead.</p> <ol id="markdown-toc"> <li><a href="#what-is-web-analytics" id="markdown-toc-what-is-web-analytics">What is web analytics?</a></li> <li><a href="#what-is-product-analytics" id="markdown-toc-what-is-product-analytics">What is product analytics?</a></li> <li><a href="#web-analytics-vs-product-analytics-at-a-glance" id="markdown-toc-web-analytics-vs-product-analytics-at-a-glance">Web analytics vs product analytics at a glance</a></li> <li><a href="#where-plausible-fits" id="markdown-toc-where-plausible-fits">Where Plausible fits</a></li> <li><a href="#where-plausible-is-not-trying-to-compete-with-product-analytics-tools" id="markdown-toc-where-plausible-is-not-trying-to-compete-with-product-analytics-tools">Where Plausible is not trying to compete with product analytics tools</a></li> <li><a href="#plausible-or-posthog" id="markdown-toc-plausible-or-posthog">Plausible or PostHog?</a></li> <li><a href="#saas-use-cases-plausible-does-cover" id="markdown-toc-saas-use-cases-plausible-does-cover">SaaS use cases Plausible does cover</a> <ol> <li><a href="#signup-funnels" id="markdown-toc-signup-funnels">Signup funnels</a></li> <li><a href="#marketing-attribution-through-to-a-meaningful-conversion" id="markdown-toc-marketing-attribution-through-to-a-meaningful-conversion">Marketing attribution through to a meaningful conversion</a></li> <li><a href="#custom-events-and-properties" id="markdown-toc-custom-events-and-properties">Custom events and properties</a></li> <li><a href="#ab-test-result-tracking" id="markdown-toc-ab-test-result-tracking">A/B test result tracking</a></li> </ol> </li> <li><a href="#how-to-choose-between-web-analytics-product-analytics-or-both" id="markdown-toc-how-to-choose-between-web-analytics-product-analytics-or-both">How to choose between web analytics, product analytics or both</a></li> </ol> <h2 id="what-is-web-analytics">What is web analytics?</h2> <p><a href="/blog/web-analytics">Web analytics</a> helps you understand how people find and use a website, and whether they complete the actions the website is designed to encourage.</p> <p>It is best suited to questions such as:</p> <ul> <li>How much traffic did we get, and which sources sent it?</li> <li>Which search queries, referral sites and campaigns brought qualified visitors?</li> <li>Which landing pages attract traffic and lead to signups?</li> <li>How many visitors viewed pricing, started registration and completed it?</li> <li>Did the new homepage or campaign improve the conversion rate?</li> </ul> <p>The core web analytics workflow is <strong>acquisition → engagement → conversion</strong>.</p> <p>Acquisition reports cover referral sources, search, paid and organic campaigns, and UTM parameters. Content reports cover landing pages, popular pages, entry and exit pages, and engagement. Goals and funnels connect that activity to outcomes such as a demo request, newsletter subscription, trial signup or purchase.</p> <p>This is useful beyond the marketing department. Founders, content teams and growth teams all need to know what brings the right audience to a site and what helps that audience convert.</p> <h2 id="what-is-product-analytics">What is product analytics?</h2> <p>Product analytics helps you understand how people use a software product and whether that experience delivers value. It can be as simple as counting uses of a feature or as involved as following the same users and accounts across days, weeks or months.</p> <p>It is built for questions such as:</p> <ul> <li>What percentage of new accounts reaches the activation milestone?</li> <li>How often is a particular feature or workflow used?</li> <li>Did usage of a feature increase after a release?</li> <li>How long does activation take?</li> <li>Which onboarding steps predict successful adoption?</li> <li>Do people who use a particular feature retain better?</li> <li>What is the day 7, week 4 or month 3 retention rate?</li> <li>How does behavior differ by signup cohort, plan or account type?</li> </ul> <p>The core product analytics workflow is <strong>activation → engagement → retention</strong>.</p> <p>Questions about total feature usage or changes after a release may be answered with aggregate events and properties. Retention and behavioral cohorts require the events in the analysis to be associated with the same users over time. Product analytics platforms use user identifiers for this purpose; some also support separately configured group identifiers for account- or workspace-level analysis. A user profile is not always required simply to record events, but a consistent identifier is what lets the platform group people by actions they took and calculate whether they returned later.</p> <p>Identity does not define product analytics. It becomes necessary for a particular class of questions: <strong>who did something, what else they did and whether they came back later</strong>. “Who” may mean a pseudonymous user, workspace or account rather than a named person.</p> <h2 id="web-analytics-vs-product-analytics-at-a-glance">Web analytics vs product analytics at a glance</h2> <table> <thead> <tr> <th> </th> <th>Web analytics</th> <th>Product analytics</th> </tr> </thead> <tbody> <tr> <td>Main question</td> <td>How do people find and convert on our website?</td> <td>How do users adopt and keep using our product?</td> </tr> <tr> <td>Typical journey</td> <td>First visit to conversion</td> <td>Signup to activation, engagement and retention</td> </tr> <tr> <td>Common units</td> <td>Visitors, visits, pages and conversions</td> <td>Events, users, accounts, features and cohorts</td> </tr> <tr> <td>Common reports</td> <td>Sources, campaigns, landing pages, goals and conversion funnels</td> <td>Onboarding, feature adoption, behavioral cohorts and retention curves</td> </tr> <tr> <td>Time horizon</td> <td>Often a visit, campaign or reporting period</td> <td>Often a user lifecycle across days or months</td> </tr> <tr> <td>Typical owners</td> <td>Marketing, content, growth and founders</td> <td>Product, data and customer success teams</td> </tr> <tr> <td>Identity requirements</td> <td>Often works without recognizing returning visitors</td> <td>Overall usage counts may not need identity; cohorts and retention usually do</td> </tr> </tbody> </table> <p>The categories overlap. A web analytics tool may support custom events and funnels. A product analytics tool may report acquisition sources and landing pages. The presence of an “events” or “funnels” feature does not settle which category a tool belongs to. What matters is whether you are trying to improve how people find and convert on a website or how they use and get value from a product.</p> <p>Start instead with two questions:</p> <ol> <li><strong>What are you trying to improve?</strong> Acquisition, content and website conversion usually point to web analytics. Activation, product engagement, feature adoption and retention point to product analytics.</li> <li><strong>What continuity does the answer require?</strong> Counting uses of a feature is one thing. Building retention cohorts or tracing account journeys across sessions requires a stable user or account identifier.</li> </ol> <p>The first question identifies the analytical job. The second identifies the data model and type of tool needed to do it.</p> <h2 id="where-plausible-fits">Where Plausible fits</h2> <p>Plausible is a web analytics tool. It measures traffic and behavior without cookies, personal data or persistent identifiers. That focus does not prevent it from answering selected questions about product usage.</p> <p>Its natural strengths are:</p> <ul> <li>Traffic acquisition and marketing attribution</li> <li>Pages, landing pages and content performance</li> <li>Referral sources, channels and UTM campaigns</li> <li>Goals, conversion rates and revenue attribution</li> <li>Custom events and properties</li> <li>Defined conversion funnels and open-ended user journeys</li> </ul> <p>For a SaaS business, that covers the journey from a campaign, search result or referral through to a trial signup or another meaningful conversion. You can also send selected events from the product, such as <code class="language-plaintext highlighter-rouge">Created Project</code> or <code class="language-plaintext highlighter-rouge">Invited Teammate</code>, to measure their frequency or include them in a conversion funnel.</p> <p>Plausible can therefore answer questions like:</p> <ul> <li>Which campaign drove the most trial signups?</li> <li>Which landing page visitors are most likely to create a project?</li> <li>Where do visitors drop out between pricing, signup and onboarding completion?</li> <li>Which plan or experiment variant has the higher conversion rate?</li> <li>How often was a feature used during a selected period?</li> </ul> <p>Feature usage is a product analytics question that does not always need an individual history. Plausible can count a feature event and segment it using non-personal <a href="/docs/custom-props/introduction">custom properties</a>. It cannot tell you whether the people who used the feature in January returned in February.</p> <p>That limitation follows directly from Plausible’s privacy model. A person who visits on different days may be counted as a different visitor because Plausible does not use a persistent identifier to recognize them. Do not send names, email addresses, account IDs, pseudonymous cookie IDs or other personal identifiers as custom properties.</p> <h2 id="where-plausible-is-not-trying-to-compete-with-product-analytics-tools">Where Plausible is not trying to compete with product analytics tools</h2> <p>Tools like Amplitude and Mixpanel are event-based analytics platforms with reports for product questions such as funnels, behavioral cohorts and retention. In both tools, events can be associated with a user identifier so activity from the same user can be analyzed together. Their documentation also describes separate group-level features for analyzing companies, workspaces or other account-like entities; these require additional instrumentation and may depend on the product or plan.</p> <p>Plausible overlaps with a portion of product analytics; it is not trying to reproduce that persistent behavioral model with a simpler interface. It does not provide:</p> <ul> <li>Persistent user profiles or separately configured account/group profiles</li> <li>Multi-day user-level histories</li> <li>Signup cohorts followed through later periods</li> <li>Retention curves such as day 1, day 7 or week 4 retention</li> <li>Comparing later retention for cohorts defined by earlier product behavior</li> <li>User-level feature adoption or frequency analysis</li> </ul> <p>Suppose 500 people sign up in August. Plausible can answer “How many project-creation events happened in August?” It cannot answer “Of that August signup cohort, how many activated within seven days and were still active four weeks later?” The second question requires connecting each account’s signup, activation and return events over time. Plausible deliberately does not maintain that connection.</p> <p>Plausible can instead tell you how many visitors completed a signup or activation event during August, the sources and campaigns associated with those conversions, and where visitors dropped out of a defined funnel. Those are useful answers, but they are not a retention cohort.</p> <p>This is also why a “unique visitor” in web analytics should not be treated as a SaaS user count. Your billing system or product database is the source of truth for accounts, subscriptions and churn.</p> <p>For a broader view of other use cases outside Plausible’s scope, including session replay, retargeting and user-level tracking, read <a href="/when-not-to-use-plausible">when Plausible is not the right fit</a>.</p> <h2 id="plausible-or-posthog">Plausible or PostHog?</h2> <p>PostHog comes up a lot in this comparison because it now offers web analytics too, alongside product analytics, session replay, feature flags, experiments and surveys. So for many teams the real choice is between one large platform and a focused tool.</p> <p>PostHog makes sense if your team wants all of that in one place and is happy to manage what gets collected. Its <a href="https://posthog.com/docs/privacy/gdpr-compliance">GDPR documentation</a> says it automatically captures data that can be personal data, so you need a way for visitors to consent. There is a <a href="https://posthog.com/docs/privacy/cookieless-tracking">cookieless mode</a>, but you have to turn it on, and session replay and surveys don’t work for visitors who haven’t consented. PostHog Cloud EU runs on <a href="https://posthog.com/blog/posthog-cloud-eu">AWS in Frankfurt</a>. PostHog is venture funded and has <a href="https://posthog.com/handbook/story">raised around $194m</a> since 2020.</p> <p>Plausible makes sense if what you need is website analytics, done in a way that needs no consent banner from day one. There’s nothing to configure for privacy because there’s no personal data to begin with. We’re a self-funded company incorporated in Estonia, and visitor data stays on <a href="/eu-hosted-web-analytics">EU-owned infrastructure</a> at Hetzner in Germany and UpCloud in Finland.</p> <p>Plenty of SaaS teams use both. Plausible on the marketing site, where you want every visitor counted without a banner, and a product analytics tool inside the logged-in app.</p> <h2 id="saas-use-cases-plausible-does-cover">SaaS use cases Plausible does cover</h2> <p>The boundary does not mean Plausible stops being useful when someone clicks “Sign up.” Many SaaS teams need a focused set of product and growth signals without building a full user-level analytics system.</p> <h3 id="signup-funnels">Signup funnels</h3> <p>You can combine pages and events into a funnel such as:</p> <ol> <li>Viewed pricing</li> <li>Started signup</li> <li>Completed registration</li> <li>Created first project</li> </ol> <p>Plausible shows how many visitors complete each step and the drop-off between them. You can filter the funnel by source, campaign, landing page, device, location or another available dimension to find where a particular segment struggles.</p> <p>This works well for a defined conversion or onboarding path. It is not a substitute for following a signup cohort through a 30-day lifecycle. See the <a href="/docs/funnel-analysis">funnel analysis documentation</a> for setup details and current limits.</p> <h3 id="marketing-attribution-through-to-a-meaningful-conversion">Marketing attribution through to a meaningful conversion</h3> <p>A signup count alone can reward channels that bring a lot of low-intent traffic. A more useful setup sends a later milestone, such as <code class="language-plaintext highlighter-rouge">Created Project</code>, <code class="language-plaintext highlighter-rouge">Booked Demo</code> or <code class="language-plaintext highlighter-rouge">Upgraded</code>, as a goal.</p> <p>You can then filter that goal by referral source, channel, UTM campaign or landing page. This answers questions such as “Which campaign brought visitors who reached activation?” without building profiles for those visitors.</p> <p>Attribution has limits in any privacy-friendly system. Plausible is strongest when the journey happens within the same visitor session across your site and subdomains. It is not designed to stitch a person across devices or recognize a lead who returns weeks later from another browser.</p> <h3 id="custom-events-and-properties">Custom events and properties</h3> <p><a href="/docs/custom-event-goals">Custom event goals</a> let you measure actions that do not produce a distinct pageview: CTA clicks, form completions, video plays, project creation or any other event you choose to send.</p> <p><a href="/docs/custom-props/introduction">Custom properties</a> add non-personal context to a pageview or event. A SaaS team might attach:</p> <ul> <li><code class="language-plaintext highlighter-rouge">plan=starter</code> or <code class="language-plaintext highlighter-rouge">plan=pro</code> to a signup event</li> <li><code class="language-plaintext highlighter-rouge">role=admin</code> or <code class="language-plaintext highlighter-rouge">role=member</code> to a feature event</li> <li><code class="language-plaintext highlighter-rouge">logged_in=true</code> to separate public-site and in-product activity</li> <li><code class="language-plaintext highlighter-rouge">variant=A</code> or <code class="language-plaintext highlighter-rouge">variant=B</code> to an experiment exposure or conversion</li> </ul> <p>For example, you could attach <code class="language-plaintext highlighter-rouge">logged_in=true</code> or <code class="language-plaintext highlighter-rouge">logged_in=false</code> to a goal event. Plausible can then show the visitors, total events and conversion rate for each value. This helps you compare how the event is used in logged-in and logged-out contexts, but it does not create a history of what each logged-in user did before or after that event. You can explore this kind of property breakdown in our <a href="https://plausible.io/plausible.io">live demo</a>.</p> <p>Properties let you filter and compare behavior. They must not contain information that identifies or persistently singles out a person.</p> <h3 id="ab-test-result-tracking">A/B test result tracking</h3> <p>Plausible can measure the outcome of a website A/B test. Send the assigned variant as a custom property, then compare goal completions and conversion rates for each variant.</p> <p>Plausible does <strong>not</strong> split traffic, assign variants, manage feature flags or decide whether a result is statistically significant. You need your own code or an experimentation tool for those parts. Plausible measures the resulting visits and conversions.</p> <p>Our guide to <a href="/blog/ab-testing">A/B testing a website</a> explains the setup and the statistical cautions.</p> <h2 id="how-to-choose-between-web-analytics-product-analytics-or-both">How to choose between web analytics, product analytics or both</h2> <p>Use web analytics when your main questions are about traffic, content, campaigns and conversion:</p> <ul> <li>Where are visitors coming from?</li> <li>Which pages and campaigns generate signups or revenue?</li> <li>Where does a short signup or checkout funnel lose people?</li> <li>Did a landing-page experiment improve conversion?</li> </ul> <p>Use product analytics when your main questions are about activation, product engagement, feature adoption or retention:</p> <ul> <li>How often is a key feature or workflow used?</li> <li>Did overall usage change after a product release?</li> <li>Which signup cohorts retain after 30 or 90 days?</li> <li>How does retention differ between people who did or did not use a particular feature?</li> <li>How does feature adoption develop over a customer’s lifecycle?</li> <li>Which individual accounts have or have not reached an activation milestone?</li> </ul> <p>The first two questions only require overall usage totals. The remaining questions need events to be linked to the same users or accounts, using a dedicated product analytics system or your own product data.</p> <p>Use both when acquisition and product retention are both important enough to analyze deeply. This is common for a growing SaaS company: Plausible can provide a simple, privacy-friendly view of the marketing site and acquisition funnel, while Amplitude, Mixpanel or another product analytics system provides the linked event data needed for cohorts and retention.</p> <p>The numbers from two tools may not match exactly because they use different identity models, time windows and definitions. That does not make either one automatically wrong. Define which system owns each metric: for example, Plausible for website visitors and campaign conversions, your application database for accounts and revenue, and a product analytics tool for cohorts and retention.</p> <p>If your needs sit in the overlap, write down the exact question. “Can it track events?” is too broad. Ask instead:</p> <ul> <li>Do we need an event total or a history for each user?</li> <li>Is this a conversion funnel or a multi-week lifecycle?</li> <li>Do we need to compare traffic segments or behavioral cohorts?</li> <li>Is identifying the same account later essential to the answer?</li> </ul> <p>Those questions make the choice much easier.</p> <p>Plausible is built for teams that want clear answers about acquisition, website behavior and conversion without tracking people across the internet, or across months of product use. It can also measure selected activity inside a product. If that matches your needs, explore <a href="/for-saas">Plausible for SaaS</a> or start a <a href="/register">free 30-day trial</a>. If you need retention cohorts or long-term user and account histories, choose a dedicated product analytics tool, whether or not you also use Plausible for your website.</p>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Web analytics and product analytics overlap more than their names suggest. Learn which questions each can answer, what data they require and where Plausible fits.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/web-analytics-vs-product-analytics.png"/><media:content medium="image" url="https://plausible.io/uploads/web-analytics-vs-product-analytics.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">How to check your own website traffic accurately</title><link href="https://plausible.io/blog/check-website-traffic" rel="alternate" type="text/html" title="How to check your own website traffic accurately"/><published>2026-07-28T12:00:00+00:00</published><updated>2026-07-28T12:00:00+00:00</updated><id>https://plausible.io/blog/check-website-traffic</id><content type="html" xml:base="https://plausible.io/blog/check-website-traffic"><![CDATA[<p>Checking your website traffic can sound like a matter of finding one number. In practice, it starts with a more useful question: are people finding the site, and what happens when they do?</p> <p>The most accurate way to answer that question is to install a <a href="/blog/web-analytics">web analytics tool</a> on the site you own. This gives you first-party data based on visits that actually happened, rather than an outside tool’s estimate.</p> <p>This guide helps you set up measurement, learn to read the dashboard, and gradually turn raw traffic into something you can act on. The examples use Plausible Analytics, but the same basic questions apply to any web analytics.</p> <ol id="markdown-toc"> <li><a href="#1-install-analytics-on-your-website" id="markdown-toc-1-install-analytics-on-your-website">1. Install analytics on your website</a> <ol> <li><a href="#make-sure-your-analytics-is-working" id="markdown-toc-make-sure-your-analytics-is-working">Make sure your analytics is working</a></li> </ol> </li> <li><a href="#2-choose-a-useful-date-range" id="markdown-toc-2-choose-a-useful-date-range">2. Choose a useful date range</a></li> <li><a href="#3-check-visitors-visits-and-pageviews" id="markdown-toc-3-check-visitors-visits-and-pageviews">3. Check visitors, visits and pageviews</a></li> <li><a href="#4-find-where-your-traffic-comes-from" id="markdown-toc-4-find-where-your-traffic-comes-from">4. Find where your traffic comes from</a></li> <li><a href="#5-check-which-pages-people-visit" id="markdown-toc-5-check-which-pages-people-visit">5. Check which pages people visit</a></li> <li><a href="#6-check-campaign-traffic-with-utm-parameters" id="markdown-toc-6-check-campaign-traffic-with-utm-parameters">6. Check campaign traffic with UTM parameters</a></li> <li><a href="#7-check-conversions-and-goals" id="markdown-toc-7-check-conversions-and-goals">7. Check conversions and goals</a></li> <li><a href="#8-diagnose-a-traffic-spike-or-drop" id="markdown-toc-8-diagnose-a-traffic-spike-or-drop">8. Diagnose a traffic spike or drop</a></li> <li><a href="#why-a-public-traffic-checker-can-never-measure-your-site-accurately" id="markdown-toc-why-a-public-traffic-checker-can-never-measure-your-site-accurately">Why a public traffic checker can never measure your site accurately</a></li> <li><a href="#a-simple-weekly-website-traffic-check" id="markdown-toc-a-simple-weekly-website-traffic-check">A simple weekly website traffic check</a></li> </ol> <h2 id="1-install-analytics-on-your-website">1. Install analytics on your website</h2> <p>Before you can interpret traffic, you need somewhere reliable to record it. A website traffic checker can <strong>only estimate</strong> a site’s traffic numbers; it cannot tell you exactly how many people visited. For that, your website needs to send data to an analytics platform.</p> <aside class="my-6 border-l-2 border-indigo-200 pl-4 text-sm leading-6 text-gray-600"> <strong class="text-gray-700">Worth knowing:</strong> Many SEO tools only estimate clicks from search engines using keyword rankings, search volumes and assumed click-through rates. Some broader traffic tools also estimate direct, social, referral and other channels using sampled browsing data. Neither gives you the measured first-party traffic of a site you own. The differences can be massive. We explain <a href="#why-a-public-traffic-checker-cannot-measure-your-site-accurately">how these estimates differ</a> later in this guide. </aside> <p>Most analytics tools do this using a small JavaScript snippet. You add the snippet to the <code class="language-plaintext highlighter-rouge">&lt;head&gt;</code> of every page you want to measure. Depending on how your site is built, you may instead use an official plugin, an integration, or a tag manager.</p> <p>The exact setup depends on the analytics tool and how your site is built, but the basic process is usually:</p> <ol> <li>Add your website to the analytics tool.</li> <li>Copy the tracking snippet or select the relevant integration.</li> <li>Add it to your website, either directly or through your content management system, framework or tag manager.</li> <li>Visit your website and verify that your visit appears in the dashboard.</li> </ol> <p>If you are using Plausible, our <a href="https://plausible.io/docs/plausible-script">installation guides</a> cover popular platforms and frameworks.</p> <h3 id="make-sure-your-analytics-is-working">Make sure your analytics is working</h3> <p>After installing analytics, it is a good practice to check that it is receiving visits. You can open your website in a private window, visit a page, and look for that visit in your tool’s real-time report. If it appears, your basic tracking is working.</p> <p>Some tools make this easier. Plausible, for example, has an automatic <a href="https://plausible.io/docs/troubleshoot-integration">integration verification tool</a> that checks whether the tracking script is installed correctly. You can also run it again from your site settings after changing your setup.</p> <p>If your test visit does not appear, use our tool-independent <a href="https://plausible.io/blog/is-analytics-working-correctly">guide to checking whether analytics is working</a>. It covers common causes as well as less-common setups involving single-page applications and subdomains.</p> <p>If tracking works but your totals differ from Google Analytics, Search Console, an advertising platform or another source, that does not automatically mean something is broken. These tools measure different things in different ways. Our guide to <a href="https://plausible.io/blog/why-analytics-numbers-dont-match">why analytics numbers do not match</a> explains how to interpret those differences.</p> <p>Once visits are coming through, resist the urge to judge the first number you see. A traffic total only becomes meaningful when you place it in time.</p> <h2 id="2-choose-a-useful-date-range">2. Choose a useful date range</h2> <p>The useful date range depends on what prompted you to open the dashboard. Are you checking a campaign you launched this morning, reviewing an ordinary month, or wondering whether the site has grown over the past year?</p> <ul> <li>Use <strong>Today</strong> or <strong>Last 24 hours</strong> to check a launch, active campaign or sudden incident.</li> <li>Use <strong>Last 7 days</strong> for recent operational changes.</li> <li>Use <strong>Last 30 days</strong> for a steadier view of normal performance.</li> <li>Use <strong>6–12 months</strong> to see seasonality and long-term direction.</li> </ul> <p>Turn on a comparison with the previous period or the same period last year. “10,000 visitors” has little meaning on its own. “10,000 visitors, up 18% from the previous 30 days” gives you context.</p> <p>In Plausible, the date picker lets you compare your selected range with the previous period, the same period a year earlier or a custom period. See the documentation on <a href="https://plausible.io/docs/guided-tour#compare-your-stats-over-time">comparing your stats over time</a>.</p> <p>Use a same-length previous period to understand recent momentum, and a year-over-year comparison to see how the site has changed over a longer cycle. Comparing the same dates across years is also useful for separating real growth from seasonal effects. For example, comparing December with November could make a retail site look unusually strong; comparing it with the previous December gives you a fairer view of its growth.</p> <p>With that context in place, you can read the headline numbers without mistaking normal fluctuation for a meaningful change.</p> <h2 id="3-check-visitors-visits-and-pageviews">3. Check visitors, visits and pageviews</h2> <p>Start with visitors, visits and pageviews. Together, they move you from <strong>how many people came</strong>, to <strong>how often they came</strong>, to <strong>how much they explored</strong>.</p> <table> <thead> <tr> <th>Metric</th> <th>What it tells you</th> <th>Simple example</th> </tr> </thead> <tbody> <tr> <td><strong>Visitors</strong></td> <td>How many distinct people or devices visited during the selected period</td> <td>One person visits twice: one visitor</td> </tr> <tr> <td><strong>Visits</strong> or <strong>sessions</strong></td> <td>How many separate browsing sessions happened</td> <td>The same person returns later: two visits</td> </tr> <tr> <td><strong>Pageviews</strong></td> <td>How many pages were loaded</td> <td>They view three pages in each visit: six pageviews</td> </tr> </tbody> </table> <p>For example, a visitor who loads five pages during one session generally produces one visitor, one visit and five pageviews. If that person returns in a separate session, visits increase again. The exact definitions vary: analytics products use different identification methods and session rules, so numbers from two tools should not be expected to match exactly.</p> <p>If you are looking at a Plausible dashboard, the <a href="https://plausible.io/docs/metrics-definitions">metrics definitions</a> explain exactly how each number is calculated.</p> <p>Which metric matters most depends on your question:</p> <ul> <li>Use <strong>visitors</strong> to understand audience size.</li> <li>Use <strong>visits</strong> to understand how often the site is used.</li> <li>Use <strong>pageviews</strong> to understand how much content was consumed.</li> <li>Use <strong>views per visit</strong>, <strong>visit duration</strong> and <strong>bounce rate</strong> to add engagement context.</li> </ul> <p>Do not treat pageviews as people. A documentation site may have many pageviews because visitors need several pages to solve a problem. A single-purpose landing page may succeed with one pageview if the visitor submits the form or buys the product.</p> <p>These totals tell you the size and shape of the activity, but not what created it. The next question is where those visitors came from.</p> <h2 id="4-find-where-your-traffic-comes-from">4. Find where your traffic comes from</h2> <p>Open the <strong>Sources</strong> or <strong>Acquisition</strong> report. This turns an anonymous traffic total into a more understandable story: people may have discovered you through a search, followed a recommendation, clicked a campaign, or returned directly.</p> <p>In Plausible, these reports sit together under Sources. This guide to <a href="https://plausible.io/docs/top-referrers">channels, sources and campaigns</a> explains how incoming traffic is classified and how to move from a broad channel to a specific referrer or campaign.</p> <p>Depending on your analytics tool, traffic may be grouped into channels such as:</p> <ul> <li>Organic Search</li> <li>Direct</li> <li>Referral</li> <li>Organic Social</li> <li>Email</li> <li>Paid Search or Paid Social</li> <li>Affiliates</li> <li>AI referrals</li> </ul> <p>Start with channels for the broad picture, then drill into exact sources. If Organic Search grew, was it Google, Bing or another search engine? If Referral traffic spiked, which site linked to you? If AI traffic increased, did it come from ChatGPT, Perplexity or another service?</p> <p>Our guide to <a href="/track-ai-traffic">AI traffic analytics</a> explains how to connect those referrals to landing pages, engagement and conversions.</p> <p>“Direct” does not always mean someone typed your address into the browser. It is the fallback when reliable referral or campaign information is missing. Bookmarks, untagged emails, private messages, apps, redirects and links that strip referral information can all appear as Direct.</p> <p>To judge traffic quality, click a source to filter the rest of the dashboard. Then check its landing pages, engagement and conversions. The source with the most visitors is not necessarily the most valuable source.</p> <p>For search queries, connect Google Search Console or view its Performance report. Analytics tells you what visitors did after arriving; Search Console tells you which Google queries and pages produced impressions and clicks. Plausible users can <a href="https://plausible.io/docs/google-search-console-integration">connect Search Console</a> to bring those queries into the dashboard.</p> <p>Knowing where someone came from gives you one half of the journey. To understand what drew them in, and whether the visit delivered on its promise, you need to pair the source with the page they reached.</p> <h2 id="5-check-which-pages-people-visit">5. Check which pages people visit</h2> <p>Your pages reports continue the story from acquisition into behavior. They answer three related questions:</p> <ul> <li><strong>Top Pages:</strong> Which pages received the most views?</li> <li><strong>Entry Pages or Landing Pages:</strong> Where did visits begin?</li> <li><strong>Exit Pages:</strong> Where did visits end?</li> </ul> <p>Plausible’s <a href="https://plausible.io/docs/top-pages">pages report guide</a> shows where to find these views and how to filter the rest of the dashboard by a page.</p> <p>Start with entry pages when evaluating acquisition. A landing page with growing traffic may have gained search visibility, been shared, or received a campaign push. Filter by that page and check which sources delivered its visitors and whether those visitors converted.</p> <p><img src="/uploads/analyze-entry-pages-and-traffic-sources.png" alt="Plausible dashboard filtered by blog entry pages, showing their traffic sources and visitor details" title="Analyzing entry pages and their traffic sources in Plausible Analytics"/></p> <p>Use Top Pages to see what people consumed after arriving. Review engagement alongside traffic: a high-traffic page with poor engagement and no conversions may attract the wrong audience, fail to answer the query, or simply do its job quickly. Context matters.</p> <p>Exit pages are clues, not automatic problems. Every visit has to end somewhere. An exit from a thank-you page can signal success, while frequent exits from the first step of checkout deserve investigation.</p> <p>Our guide to <a href="https://plausible.io/blog/analyzing-landing-pages">analyzing landing pages</a> shows how to combine page, source and conversion data.</p> <p>Sometimes the source and landing page are enough to explain a visit. But when you are responsible for the link, such as an ad, newsletter, QR code or social post, you can make that trail much clearer before the visitor even arrives.</p> <h2 id="6-check-campaign-traffic-with-utm-parameters">6. Check campaign traffic with UTM parameters</h2> <p>That is the role of campaign tagging. Referral data alone is not enough for reliable campaign tracking. Links in email, apps, QR codes, documents and private messages may otherwise be recorded as Direct, and a platform name alone cannot distinguish one campaign from another.</p> <p>UTM parameters are labels added to the destination URL. A tagged link can look like this:</p> <p><code class="language-plaintext highlighter-rouge">https://example.com/pricing?utm_source=newsletter&amp;utm_medium=email&amp;utm_campaign=summer-launch&amp;utm_content=top-button</code></p> <p>The five standard parameters are:</p> <ul> <li><code class="language-plaintext highlighter-rouge">utm_source</code>: the specific platform or sender, such as <code class="language-plaintext highlighter-rouge">newsletter</code>, <code class="language-plaintext highlighter-rouge">linkedin</code> or <code class="language-plaintext highlighter-rouge">google</code></li> <li><code class="language-plaintext highlighter-rouge">utm_medium</code>: the type of marketing, such as <code class="language-plaintext highlighter-rouge">email</code>, <code class="language-plaintext highlighter-rouge">social</code> or <code class="language-plaintext highlighter-rouge">cpc</code></li> <li><code class="language-plaintext highlighter-rouge">utm_campaign</code>: the initiative, such as <code class="language-plaintext highlighter-rouge">summer-launch</code></li> <li><code class="language-plaintext highlighter-rouge">utm_content</code>: the creative or link variation, such as <code class="language-plaintext highlighter-rouge">top-button</code></li> <li><code class="language-plaintext highlighter-rouge">utm_term</code>: commonly used for a paid-search term or another useful targeting label</li> </ul> <p>At minimum, use a consistent source and campaign name. Lowercase values and a shared naming convention prevent <code class="language-plaintext highlighter-rouge">Newsletter</code>, <code class="language-plaintext highlighter-rouge">newsletter</code> and <code class="language-plaintext highlighter-rouge">news-letter</code> from fragmenting your reports.</p> <p>If UTM tagging is new to you, this <a href="https://plausible.io/blog/utm-tracking-tags">guide to UTM parameters</a> explains how the tags work and how to name them consistently. You can then create correctly formatted links with our free <a href="https://plausible.io/utm-builder">UTM builder</a>. After people click them, open the Campaigns report and drill into source, medium, campaign, term or content. Then filter by the campaign to see the pages viewed, engagement and goals completed by those visitors.</p> <p>Tip: Never add UTMs to ordinary internal links on your own site. Doing so can overwrite the visitor’s original acquisition information and split one journey into misleading campaign data.</p> <p>Now you can connect a visit to the effort that brought it in. But traffic, even perfectly attributed traffic, is not the final outcome. The next step is to ask whether the visitor did something valuable.</p> <h2 id="7-check-conversions-and-goals">7. Check conversions and goals</h2> <p>Traffic tells you that people arrived. Conversions tell you whether the visit accomplished something that matters to the visitor, to your organization, or ideally to both.</p> <p>A conversion might be:</p> <ul> <li>Reaching a thank-you or order-confirmation page</li> <li>Submitting a lead or contact form</li> <li>Signing up for a trial or newsletter</li> <li>Completing a purchase</li> <li>Downloading a file</li> <li>Clicking a key button, outbound link or email address</li> </ul> <p>etc.</p> <p>In Plausible, you can configure a pageview goal for a destination such as <code class="language-plaintext highlighter-rouge">/thank-you</code>, or use a custom event for actions that do not create a new pageview. The <a href="https://plausible.io/docs/goal-conversions">goal conversion guide</a> walks through both options. Ecommerce and subscription sites can also attach revenue data to suitable conversion events.</p> <p>Once goals are collecting data, check both <strong>conversions</strong> and <strong>conversion rate</strong>. A source may bring fewer visitors but convert a much larger share of them. Filter by a goal to see which sources, campaigns, landing pages, countries and devices are associated with the result.</p> <p>Test every goal yourself after setup. Confirm that one real action produces one conversion, the event name is correct, the value or currency is right where relevant, and routine page loads do not trigger the goal accidentally.</p> <p><img src="/uploads/plausible-goals-report.png" alt="Plausible goals report showing unique conversions, total conversions and conversion rates" title="Goals and conversion rates in Plausible Analytics"/></p> <p>At this point, the dashboard is no longer just a counter. You can trace a line from acquisition to behavior to outcome. That same line becomes especially useful when something suddenly looks wrong or unexpectedly good.</p> <h2 id="8-diagnose-a-traffic-spike-or-drop">8. Diagnose a traffic spike or drop</h2> <p>When traffic changes suddenly, it is tempting to jump straight to an explanation. Instead, retrace the path you have just built: confirm the measurement, establish the timeframe, identify the affected metric, then narrow the change by source, page and outcome.</p> <p>Start by confirming that the data is trustworthy. Do not begin rewriting content or increasing ad spend until you have ruled out a tracking issue.</p> <p>Work through these checks in order:</p> <ol> <li><strong>Confirm the timing.</strong> Find the day or hour the change began and compare it with a normal period.</li> <li><strong>Check the analytics setup.</strong> Look for a removed or duplicated script, a recent site release, consent changes, a domain or subdomain change, broken single-page-app tracking, or a new exclusion rule.</li> <li><strong>Separate visitors, visits and pageviews.</strong> If only pageviews changed, navigation or duplicate tracking may be responsible. If all three moved, the audience probably changed.</li> <li><strong>Find the affected segment.</strong> Is the change sitewide or concentrated in one source, campaign, page, country, device or browser?</li> <li><strong>Check engagement and conversions.</strong> A spike with almost no engagement or conversions may be bot or spam traffic. A drop in traffic with stable conversions may be less serious than it first appears.</li> <li><strong>Match the dates to real events.</strong> Check launches, newsletters, ad budgets, press coverage, social posts, outages, holidays and seasonal demand.</li> <li><strong>Investigate search separately.</strong> Use Search Console to compare clicks, impressions, queries, pages, countries and devices. Check for ranking changes, indexing problems, algorithm updates and changes in search demand.</li> </ol> <p>Add annotations for launches, site releases and campaigns so future changes are easier to explain. Keep a simple record of what changed, when it changed and which segment moved.</p> <p>For a deeper checklist, read <a href="https://plausible.io/blog/drop-in-website-traffic">how to investigate a drop in website traffic</a>. If the graph moved in the other direction, see our guide to <a href="https://plausible.io/blog/spike-in-website-traffic">investigating a traffic spike</a>.</p> <h2 id="why-a-public-traffic-checker-can-never-measure-your-site-accurately">Why a public traffic checker can never measure your site accurately</h2> <p>If you have searched for a quick way to measure your traffic, you have probably found public tools that ask you to enter a domain. It is important not to mistake their output for your real website data.</p> <p>These tools can be useful for rough competitor research, but they do not have access to a site’s analytics account. They are estimating from the outside rather than measuring visits as they happen. That is why installing analytics is essential when you want to understand your own site.</p> <p>Many SEO tools estimate <strong>organic search traffic</strong> using the keywords a site ranks for, the estimated number of searches for each keyword, its ranking position and an assumed click-through rate. They then add those predicted clicks together. This can provide a useful indication of a site’s visibility in search, but it does not count visits from direct traffic, social media, email, referrals or offline campaigns.</p> <p>Some products, including Semrush Traffic Analytics and Similarweb, also estimate total traffic and its channel mix. They use samples of browsing activity, often called clickstream data, along with statistical models and other public data to estimate direct, social, referral, search and other traffic. These reports cover more than search, but they are still projections from a sample rather than actual visits recorded on the website itself. Estimates are especially less dependable for small or niche sites where the provider has little data.</p> <p>So, before using a public traffic number, check what it represents. An <strong>organic traffic estimate</strong> and an <strong>estimated total visits</strong> figure are not interchangeable.</p> <table> <thead> <tr> <th>First-party analytics</th> <th>Competitor traffic estimate</th> </tr> </thead> <tbody> <tr> <td>Collected from real activity on a site you control</td> <td>Modeled from sources available to the provider</td> </tr> <tr> <td>Can show pages, campaigns, events and conversions recorded on your site</td> <td>May show estimated search traffic or modeled traffic across several channels</td> </tr> <tr> <td>Useful for operating and improving your own website</td> <td>Useful for rough benchmarking and discovering competitors</td> </tr> <tr> <td>Affected by your setup, consent approach, bot filtering and blocked scripts</td> <td>Affected by the provider’s data coverage and model; smaller sites can have sparse or volatile estimates</td> </tr> </tbody> </table> <p>An estimate is not necessarily “wrong” because it differs from your analytics. It simply answers a different question with different data. Even first-party tools can disagree because they define visitors and sessions differently, filter bots differently, and may be blocked at different rates.</p> <p>For measuring your own site, the takeaway is simple: use a well-configured first-party analytics tool as your main source and validate important outcomes, such as purchases or signups, against your own records.</p> <p><strong>Use public estimates only for rough competitor comparisons, not to measure your website.</strong></p> <h2 id="a-simple-weekly-website-traffic-check">A simple weekly website traffic check</h2> <p>You do not need to analyze every report every day. In fact, repeatedly refreshing a dashboard often creates anxiety rather than insight. A calm weekly routine is enough for most websites:</p> <ol> <li>Set the last seven days and compare with the previous seven days.</li> <li>Check visitors, visits and pageviews for unusual movement.</li> <li>Review sources and campaigns to see what caused the change.</li> <li>Review entry pages to see where acquisition grew or declined.</li> <li>Check conversions and conversion rate to judge traffic quality.</li> <li>Investigate only the segments that changed materially.</li> <li>Add an annotation for any launch, campaign, outage or site update.</li> </ol> <p>The goal is not to collect the largest possible number of metrics. It is to keep hold of that trustworthy chain from <strong>where people came from</strong>, to <strong>what they viewed</strong>, to <strong>what they did next</strong>, and to notice when any part of that story meaningfully changes.</p> <p>To see how these reports work together, explore the <a href="https://plausible.io/plausible.io">Plausible live demo</a> alongside the <a href="https://plausible.io/docs/guided-tour">guided dashboard tour</a>. You can filter the dashboard by sources, pages and goals without creating an account.</p> <p>When you are ready to measure traffic on your own site, you can <a href="https://plausible.io/register">start a free trial</a>.</p>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Learn how to measure your website traffic, understand visitors, visits, pageviews, sources and pages, track campaigns and conversions, and investigate sudden changes.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png"/><media:content medium="image" url="https://plausible.io/uploads/check-website-traffic-plausible-dashboard.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">EU-hosted analytics isn’t the same as EU-owned analytics</title><link href="https://plausible.io/blog/eu-hosted-analytics-vs-eu-owned-analytics" rel="alternate" type="text/html" title="EU-hosted analytics isn’t the same as EU-owned analytics"/><published>2026-07-09T10:50:55+00:00</published><updated>2026-07-09T10:50:55+00:00</updated><id>https://plausible.io/blog/eu-hosted-analytics-vs-eu-owned-analytics</id><content type="html" xml:base="https://plausible.io/blog/eu-hosted-analytics-vs-eu-owned-analytics"><![CDATA[<p>More analytics tools now advertise “EU hosting”, “EU data residency” or an “EU region”. That sounds reassuring, especially if you’re choosing an analytics tool for privacy or GDPR reasons.</p> <p>But EU-hosted does not always mean EU-owned. And that difference matters.</p> <p>EU hosting tells you something useful about data location. It does not, by itself, answer who owns the company, who controls the infrastructure or which jurisdiction applies to the provider.</p> <p><em>This is not legal advice. It is a practical guide to the questions worth asking when you review analytics vendors. If your organization has strict GDPR, procurement or data transfer requirements, involve your legal or data protection team.</em></p> <ol id="markdown-toc"> <li><a href="#what-eu-hosted-usually-means" id="markdown-toc-what-eu-hosted-usually-means">What EU-hosted usually means</a></li> <li><a href="#what-eu-owned-adds" id="markdown-toc-what-eu-owned-adds">What EU-owned adds</a></li> <li><a href="#how-this-helps-you-decide" id="markdown-toc-how-this-helps-you-decide">How this helps you decide</a></li> <li><a href="#why-this-became-a-bigger-issue-after-schrems-ii" id="markdown-toc-why-this-became-a-bigger-issue-after-schrems-ii">Why this became a bigger issue after Schrems II</a></li> <li><a href="#examples-from-analytics-tools" id="markdown-toc-examples-from-analytics-tools">Examples from analytics tools</a></li> <li><a href="#what-plausible-means-by-eu-owned-analytics" id="markdown-toc-what-plausible-means-by-eu-owned-analytics">What Plausible means by EU-owned analytics</a></li> <li><a href="#what-to-ask-before-choosing-an-analytics-tool" id="markdown-toc-what-to-ask-before-choosing-an-analytics-tool">What to ask before choosing an analytics tool</a></li> </ol> <h2 id="what-eu-hosted-usually-means">What EU-hosted usually means</h2> <p>When vendors say “EU-hosted”, they often mean one of several different things:</p> <ul> <li>Your data is stored in an EU data center.</li> <li>You can select an EU region when creating a project.</li> <li>EU visitor traffic is routed through EU infrastructure.</li> <li>Some data stays in the EU, while other processing or support access may still happen elsewhere.</li> <li>EU residency is available only on certain plans or only if you configure the SDK correctly.</li> </ul> <p>Those details matter.</p> <p>That is why “EU-hosted” should be treated as the start of the conversation, not the end of it.</p> <h2 id="what-eu-owned-adds">What EU-owned adds</h2> <p>EU-owned analytics answers a different set of questions:</p> <ul> <li>Who is the legal entity providing the service?</li> <li>Is the company incorporated in the EU or EEA?</li> <li>Who owns and operates the infrastructure?</li> <li>Are there US-owned cloud providers or subprocessors touching visitor data?</li> <li>Is EU processing the default, or a configuration option?</li> <li>Is the provider subject to foreign jurisdiction, such as US disclosure laws?</li> </ul> <p>Think of it as three layers:</p> <table> <thead> <tr> <th>Layer</th> <th>What it tells you</th> <th>What it does not tell you</th> </tr> </thead> <tbody> <tr> <td>EU-hosted</td> <td>The data is stored or processed in a European data center</td> <td>Who owns the company or infrastructure</td> </tr> <tr> <td>EU-operated</td> <td>The service is provided by an EU or EEA legal entity</td> <td>Whether all infrastructure and subprocessors are European</td> </tr> <tr> <td>EU-owned infrastructure</td> <td>The servers or cloud infrastructure are owned by European companies</td> <td>Whether the analytics product itself is privacy-friendly</td> </tr> </tbody> </table> <p>For example, a tool could store analytics data in Frankfurt but still be operated by a US-incorporated company. Another tool could be incorporated in Europe but rely on a US-owned cloud provider for key parts of its service. Both setups may be perfectly acceptable for some organizations, but neither is the same as an EU-owned analytics provider using European-owned infrastructure by default.</p> <p>The difference is not just theoretical. <a href="https://www.law.cornell.edu/uscode/text/18/2713">18 USC 2713</a> says that a provider of electronic communication service or remote computing service must comply with obligations to preserve, back up or disclose covered information within its “possession, custody, or control” regardless of whether that information is located inside or outside the United States.</p> <p>Whether and how that law applies to a specific analytics vendor is a legal question. But it illustrates the broader point: server location alone does not answer every jurisdiction question.</p> <h2 id="how-this-helps-you-decide">How this helps you decide</h2> <p>EU-owned analytics makes the most sense when your goal is to reduce the number of privacy and procurement questions you need to resolve.</p> <p>If a vendor is non-EU-owned, or if it relies on non-EU-owned infrastructure for visitor data, you may need to spend more time reviewing:</p> <ul> <li>whether personal data is transferred outside the EU or EEA</li> <li>which transfer mechanism applies</li> <li>whether additional safeguards are needed</li> <li>whether foreign disclosure laws are relevant</li> <li>which subprocessors can access visitor data</li> <li>whether EU residency is the default or something your team must configure correctly</li> </ul> <p>That does not mean a non-EU provider is automatically unsuitable. It means the review is usually more involved.</p> <p>The European Data Protection Board’s <a href="https://www.edpb.europa.eu/documents/recommendation/recommendations-012020-on-measures-that-supplement-transfer-tools-to_en">Recommendations 01/2020</a> exist because international transfers can require transfer tools and supplementary measures to ensure an EU level of protection. If you can choose an analytics provider where the company, hosting and visitor-data infrastructure are all European, you can often avoid a lot of that extra transfer analysis in the first place.</p> <p>That is the practical reason EU-owned can make more sense. It is not a magic compliance badge. It is a simpler, lower-friction starting point for teams that care about privacy, GDPR and vendor risk.</p> <h2 id="why-this-became-a-bigger-issue-after-schrems-ii">Why this became a bigger issue after Schrems II</h2> <p>The reason people care about this is not because of a vague preference for European vendors. It comes from years of legal uncertainty around EU-US data transfers.</p> <p>In 2020, the Court of Justice of the European Union invalidated the EU-US Privacy Shield in the <a href="https://curia.europa.eu/jcms/upload/docs/application/pdf/2020-07/cp200091en.pdf">Schrems II ruling</a>. The Court’s press release explains that GDPR transfers to a third country generally require an adequate level of protection, or appropriate safeguards and enforceable rights.</p> <p>The <a href="https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/eu-us-data-transfers_en">EU-US Data Privacy Framework</a> is the current adequacy mechanism for participating US companies. The European Commission says the framework was adopted after new US safeguards were introduced to address points raised by the Court in Schrems II. The need for that framework itself shows why jurisdiction remains part of the privacy conversation.</p> <p>So when a vendor promotes EU hosting, the useful follow-up is: EU hosting under whose control?</p> <h2 id="examples-from-analytics-tools">Examples from analytics tools</h2> <p>You can see the difference across the analytics market.</p> <p>Some tools offer EU data residency while remaining operated outside the EU.</p> <p><a href="https://posthog.com/privacy">PostHog’s privacy policy</a> says its hosted services are offered by PostHog Inc., and that PostHog is headquartered in the United States. Its <a href="https://posthog.com/docs/privacy">privacy compliance documentation</a> says PostHog Cloud EU is a managed version with servers hosted in Frankfurt. Again, the EU cloud option may be useful for many teams, but it is not the same claim as being an EU-incorporated analytics provider on European-owned infrastructure.</p> <p><a href="https://docs.mixpanel.com/docs/privacy/eu-residency">Mixpanel’s EU residency documentation</a> says that Mixpanel stores user data on US servers by default, while giving customers the option to process and store customer personal data in Europe through its EU Data Residency Program. It also says new EU projects must send data to the EU endpoint, and that projects using the wrong residency location need to create a new project and migrate data.</p> <p><a href="https://support.google.com/analytics/answer/12017362?hl=en">Google’s Analytics documentation for EU, Switzerland and UK data</a> says that data from devices in those regions is collected through local domains and servers before traffic is forwarded to Analytics servers for processing. <a href="https://business.safety.google/adsprocessorterms/">Google’s data processing terms</a> also say that Google may process customer personal data in any country where Google or its subprocessors maintain facilities. That is a useful example of the distinction: regional collection is not the same thing as EU-only processing or EU ownership.</p> <p>Matomo is a good reminder that not every non-EU example is the same. Its <a href="https://matomo.org/matomo-cloud-privacy-policy/">Cloud privacy policy</a> says personal data in a customer’s Matomo Cloud instance and backups are stored in Europe, while InnoCraft, the company behind Matomo, is based in New Zealand. Matomo also notes that New Zealand has an EU adequacy decision, which the <a href="https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en">European Commission lists among its adequacy decisions</a>. That is a different legal posture from a US-operated provider, but it still shows why “where data is stored” and “who operates the service” are separate questions.</p> <p>This distinction is now showing up in SaaS vendor research too. For example, FoundersDeck’s <a href="https://foundersdeck.dev/eu-jurisdiction-database">EU SaaS Jurisdiction Database</a> separates legal entity, hosting, EU residency and CLOUD Act exposure instead of treating “EU region available” as the whole answer. Databases like this can be useful starting points, but you should still verify each vendor’s legal entity, infrastructure and subprocessors against the vendor’s own documentation.</p> <p>The important thing is not to assume based on a badge or a landing page phrase. Check the legal entity, infrastructure and subprocessors.</p> <h2 id="what-plausible-means-by-eu-owned-analytics">What Plausible means by EU-owned analytics</h2> <p>At Plausible, EU hosting is not a checkbox or an enterprise add-on.</p> <p>Plausible is incorporated in Estonia, built by a team based in the EU and hosted on infrastructure owned by European companies. Visitor data is processed and stored in the EU. It is not transferred to the United States or any other country outside the EU.</p> <p>In practice, that means:</p> <ul> <li>Visitor data is processed and stored in the EU.</li> <li>We store visitor data on servers owned by Hetzner, a German company, in Falkenstein, Germany.</li> <li>We use UpCloud, a Finnish company, for database hosting and storage of data exports.</li> <li>We use Bunny, a Slovenian company, as our CDN, while analytics processing and storage stays on our EU infrastructure.</li> <li>These are the only three providers that touch visitor data, and all three are European-owned.</li> <li>We do not use US-owned cloud providers such as AWS, Google Cloud or Microsoft Azure to store or process visitor data.</li> <li>We do not sell visitor data, share it with advertising companies or use it to build profiles across websites.</li> </ul> <p>This is not a regional toggle we added for compliance purposes. It is a deliberate infrastructure decision. It is EU-ownership by design.</p> <p>For the fuller version, including links for legal and procurement teams, see our <a href="https://plausible.io/eu-hosted-web-analytics">EU-hosted analytics page</a>, <a href="https://plausible.io/data-policy">data policy</a>, <a href="https://plausible.io/privacy">privacy policy</a> and <a href="https://plausible.io/dpa">DPA</a>.</p> <p>This ownership and infrastructure setup is only one part of the privacy story. Plausible is also designed for simple reach measurement without cookies, cross-site tracking or advertising profiles. For the consent and data minimization side, see this <a href="https://plausible.io/blog/legal-assessment-gdpr-eprivacy">independent legal assessment of Plausible under GDPR and the ePrivacy Directive</a> written by Steffen Gross, a data protection expert and lawyer.</p> <p>This is the difference between saying “your data can be hosted in Europe” and saying “your analytics runs under European ownership and European infrastructure by default”.</p> <h2 id="what-to-ask-before-choosing-an-analytics-tool">What to ask before choosing an analytics tool</h2> <p>If you’re choosing analytics for privacy, GDPR or procurement reasons, don’t stop at the hosting claim. Ask three simple questions:</p> <ul> <li>Where is visitor data processed and stored?</li> <li>Who owns the company, infrastructure and subprocessors involved?</li> <li>Is EU handling the default, and can the vendor document it clearly?</li> </ul>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[EU-hosted analytics can help with data residency, but it does not always mean EU ownership or European-owned infrastructure.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/eu-hosted-vs-eu-owned-analytics.png"/><media:content medium="image" url="https://plausible.io/uploads/eu-hosted-vs-eu-owned-analytics.png" xmlns:media="http://search.yahoo.com/mrss/"/></entry><entry><title type="html">Do ad blockers block Plausible Analytics?</title><link href="https://plausible.io/blog/do-ad-blockers-block-plausible-analytics" rel="alternate" type="text/html" title="Do ad blockers block Plausible Analytics?"/><published>2026-06-26T09:00:00+00:00</published><updated>2026-06-26T09:00:00+00:00</updated><id>https://plausible.io/blog/do-ad-blockers-block-plausible-analytics</id><content type="html" xml:base="https://plausible.io/blog/do-ad-blockers-block-plausible-analytics"><![CDATA[<p>Short answer: Plausible can be blocked, but far less often than other privacy-invasive tools such as Google Analytics. And if missing visits from blockers matter for your site, you can proxy Plausible through your own domain to bypass most of the remaining blocks and get more accurate stats.</p> <p>Plausible is a <a href="https://plausible.io/privacy-focused-web-analytics">privacy-friendly</a>, cookieless analytics tool. We do not track people across websites, build user profiles, sell visitor data, or use persistent identifiers. Our <a href="https://plausible.io/data-policy">data policy</a> explains exactly what we collect and why. Because of that, Plausible is not treated the same way as Google Analytics by many privacy-conscious people, browsers and blocklists.</p> <p>But ad blockers are not one single thing with one single policy. Some block only ads. Some block known invasive trackers. Some block anything with “analytics” in the URL. Some users configure their browser to block all JavaScript. So the most accurate answer is:</p> <ul> <li>Plausible’s default script is blocked far less often than Google Analytics.</li> <li>Some aggressive blockers can still block Plausible because they block all analytics tools, not just privacy-invasive ones.</li> <li>If you want the most complete data, you can run Plausible through a <a href="https://plausible.io/docs/proxy/introduction">proxy</a>, which makes the script and event endpoint load from your own domain.</li> </ul> <p>Let’s unpack what that means in practice.</p> <ol id="markdown-toc"> <li><a href="#why-plausible-is-blocked-less-often-than-google-analytics" id="markdown-toc-why-plausible-is-blocked-less-often-than-google-analytics">Why Plausible is blocked less often than Google Analytics</a></li> <li><a href="#how-the-plausible-proxy-reduces-ad-blocker-impact" id="markdown-toc-how-the-plausible-proxy-reduces-ad-blocker-impact">How the Plausible proxy reduces ad blocker impact</a></li> <li><a href="#is-using-a-proxy-ethical" id="markdown-toc-is-using-a-proxy-ethical">Is using a proxy ethical?</a></li> <li><a href="#proxy-options-in-plausible" id="markdown-toc-proxy-options-in-plausible">Proxy options in Plausible</a></li> <li><a href="#why-your-own-plausible-visit-might-not-show-up" id="markdown-toc-why-your-own-plausible-visit-might-not-show-up">Why your own Plausible visit might not show up</a></li> <li><a href="#why-plausible-and-ga4-numbers-are-often-different" id="markdown-toc-why-plausible-and-ga4-numbers-are-often-different">Why Plausible and GA4 numbers are often different</a></li> <li><a href="#should-you-worry-about-ad-blockers-when-using-plausible" id="markdown-toc-should-you-worry-about-ad-blockers-when-using-plausible">Should you worry about ad blockers when using Plausible?</a></li> <li><a href="#frequently-asked-questions" id="markdown-toc-frequently-asked-questions">Frequently asked questions</a></li> </ol> <h2 id="why-plausible-is-blocked-less-often-than-google-analytics">Why Plausible is blocked less often than Google Analytics</h2> <p>Ad blockers and browser privacy protections do more than block ads. They can also block known tracking domains, third-party scripts and requests that match tracking patterns. When a script does not load, the analytics tool cannot record the visit.</p> <p>Google Analytics is specifically targeted by many of these protections because it is part of Google’s advertising and tracking ecosystem. Plausible does not use cookies or persistent identifiers, track people across websites or collect personal data, so it is much less likely to be blocked.</p> <p>Firefox and Safari block Google Analytics by default, but not Plausible. At the time of writing, <a href="https://github.com/uBlockOrigin/uAssets/blob/master/filters/privacy.txt">uBlock Origin’s own Privacy list</a> contains specific Google Analytics rules but no <code class="language-plaintext highlighter-rouge">plausible.io</code> entry. That is not a guarantee that every uBlock Origin setup allows Plausible: visitors can enable other lists or custom rules, and DNS blockers, company firewalls and disabled JavaScript can all block analytics requests.</p> <p>In one Plausible study, we compared Google Analytics and Plausible on a site that received a large amount of tech-savvy traffic from Hacker News and Reddit. Plausible was installed using a proxy to get the clearest view of total human traffic, while Google Analytics was installed normally.</p> <p>The result: <a href="https://plausible.io/blog/google-analytics-adblockers-missing-data">Google Analytics missed 58% of visitors</a> in that audience.</p> <p>That is an extreme case, because Hacker News and Reddit audiences are more likely to use ad blockers, privacy browsers and stricter browser settings than average visitors. But it shows the underlying problem clearly: if your audience uses privacy tools, Google Analytics can miss a large share of real traffic.</p> <p>GA4 has the same structural issue. It is still Google Analytics, still integrates with Google’s ad ecosystem and is still commonly blocked. Plausible can still be blocked, but it cannot and should not override someone deliberately disabling JavaScript or blocking all measurement. For blockers that target a known analytics domain, proxying is the practical option.</p> <h2 id="how-the-plausible-proxy-reduces-ad-blocker-impact">How the Plausible proxy reduces ad blocker impact</h2> <p>A <a href="https://plausible.io/docs/proxy/introduction">Plausible proxy</a> lets you serve the Plausible script and send events through your own domain instead of <code class="language-plaintext highlighter-rouge">plausible.io</code>.</p> <p>For a standard installation, the site-specific script URL looks like this:</p> <div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code>https://plausible.io/js/pa-XXXXX.js
</code></pre></div></div> <p>With a proxy, your site can load it through a first-party URL on your own domain, such as:</p> <div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code>https://yourdomain.com/js/script.js
</code></pre></div></div> <p>The exact script and event URLs depend on your proxy setup, but the principle is the same: the browser sees the analytics request as a first-party request from your own website, not as a request to a known analytics service.</p> <p>This bypasses most blockers that target third-party tracking domains and known tracking URLs. It does not affect visitors who disable JavaScript or block your own domain.</p> <h2 id="is-using-a-proxy-ethical">Is using a proxy ethical?</h2> <p>Proxying changes how the request reaches Plausible, not what Plausible collects. It still does not build advertising audiences, identify individual visitors or use cookies. You can review the details in our <a href="https://plausible.io/data-policy">data policy</a>. Visitors who disable JavaScript or block your own domain can still avoid being counted.</p> <h2 id="proxy-options-in-plausible">Proxy options in Plausible</h2> <p>Choose the setup that fits your site:</p> <ul> <li><strong>WordPress:</strong> enable the proxy in the official <a href="https://plausible.io/wordpress-analytics-plugin">Plausible Analytics WordPress plugin</a>.</li> <li><strong>Developer-managed site:</strong> use the <a href="https://plausible.io/docs/proxy/introduction">proxy documentation</a> for Cloudflare, Netlify, Nginx, Vercel and other supported setups.</li> <li><strong>Enterprise:</strong> use Managed Proxy, where you point a CNAME at our infrastructure and we handle the ongoing setup.</li> </ul> <h2 id="why-your-own-plausible-visit-might-not-show-up">Why your own Plausible visit might not show up</h2> <p>One reason people ask “does Plausible get blocked by ad blockers?” is that they visit their own site and do not see themselves in Real-Time.</p> <p>Before assuming an ad blocker is the cause, run Plausible’s <a href="https://plausible.io/docs/troubleshoot-integration">integration verification tool</a>. If it confirms that tracking works, the issue is usually specific to your own browser, account or network rather than your visitors’ traffic.</p> <p>If you use the official WordPress plugin, logged-in administrator visits are <a href="https://plausible.io/docs/wordpress-integration">excluded by default</a>. You can enable the Administrator role in the plugin’s “Track analytics for user roles” setting when you need to test your own visits.</p> <p>Otherwise, check your browser’s Network tab after reloading the page. Look for the Plausible script request, which starts with <code class="language-plaintext highlighter-rouge">pa-</code>, and the event request. A blocked request usually identifies the extension or policy responsible. Other common causes are an incorrect snippet or domain, a Content Security Policy, testing a staging site, network-level blocking or missing pageview tracking in a single-page app.</p> <p>We have a full guide on <a href="https://plausible.io/blog/is-analytics-working-correctly">checking whether your analytics setup is working correctly</a>, plus a <a href="https://plausible.io/docs/troubleshoot-integration">Plausible troubleshooting guide</a>.</p> <h2 id="why-plausible-and-ga4-numbers-are-often-different">Why Plausible and GA4 numbers are often different</h2> <p>If Plausible shows more visitors than GA4, that is usually expected.</p> <p>GA4 can be blocked, prevented from running after a consent decline, or use modeled data to fill gaps. Plausible does not need cookies or a consent banner from our side, and a proxy can reduce its remaining ad blocker gap. The tools also define visitors, sessions, bot traffic and attribution differently, so not every difference comes from blocking. In <a href="https://plausible.io/blog/testing-bot-traffic-filtering-google-analytics">our bot-filtering test</a>, GA4 counted simulated bot traffic that Plausible excluded. Read our guide on <a href="https://plausible.io/blog/why-analytics-numbers-dont-match">why analytics tools never show the same numbers</a>.</p> <h2 id="should-you-worry-about-ad-blockers-when-using-plausible">Should you worry about ad blockers when using Plausible?</h2> <p>It depends on your audience and how precise you need the numbers to be.</p> <p>If you run a general website, Plausible’s standard script is likely enough. You will already <a href="https://plausible.io/most-accurate-web-analytics">avoid the biggest accuracy problems</a> that affect GA4: cookie consent gaps, heavier tracking, Google-specific blocking and privacy-hostile design.</p> <p>If you run a site for developers, privacy-conscious users, open source communities, security professionals or other technical audiences, you should consider proxying Plausible. Those audiences use ad blockers and privacy tools at much higher rates.</p> <p>If you make business decisions from small changes in conversion rate, traffic source performance or campaign ROI, proxying can also be worth it. A small amount of missing data can matter when you are optimizing at the margins.</p> <h2 id="frequently-asked-questions">Frequently asked questions</h2> <style>.adblocker-faq{margin-top:1.5rem;border-top:1px solid #e5e7eb}.adblocker-faq details{border-bottom:1px solid #e5e7eb;padding:1rem 0}.adblocker-faq summary{align-items:center;color:#111827;cursor:pointer;display:flex;font-weight:600;justify-content:space-between;list-style:none}.adblocker-faq summary::-webkit-details-marker{display:none}.adblocker-faq summary::after{align-items:center;background:#eef2ff;border-radius:9999px;color:#4f46e5;content:"+";display:inline-flex;flex:0 0 auto;font-size:1.25rem;height:1.75rem;justify-content:center;line-height:1;margin-left:1rem;width:1.75rem}.adblocker-faq details[open] summary::after{content:"-"}.adblocker-faq p{color:#4b5563;line-height:1.7;margin:.75rem 2.75rem 0 0}</style> <div class="adblocker-faq"> <details> <summary>Do ad blockers block Plausible Analytics?</summary> <p>Some can, but Plausible is blocked far less often than Google Analytics. Strict filter lists, custom rules and network-level blockers may still block it.</p> </details> <details> <summary>Does Plausible use cookies or need a cookie banner?</summary> <p>No. Plausible is cookieless by design and does not use persistent identifiers. You <a href="https://plausible.io/blog/legal-assessment-gdpr-eprivacy">do not need a cookie consent banner</a> just because you use Plausible, though obligations can depend on the rest of your site and your jurisdiction.</p> </details> <details> <summary>Does a Plausible proxy bypass all ad blockers?</summary> <p>A proxy bypasses <b>most</b> blockers that target third-party analytics domains, but it will not count visitors who disable JavaScript or block your own domain.</p> </details> <details> <summary>Is Plausible more accurate than Google Analytics?</summary> <p>For many sites, yes. Plausible is blocked less often, does not depend on cookie consent and filters bots more aggressively by default. Read <a href="https://plausible.io/most-accurate-web-analytics">the full comparison</a>.</p> </details> <details> <summary>Can I test how much data GA4 is missing?</summary> <p>Yes. Run Plausible and GA4 side by side for a few weeks, then compare visitors, pageviews and conversions on the same pages.</p> </details> </div> <div x-data="" x-show="!document.cookie.includes('logged_in=true')" class="cta-box my-8 rounded-lg border border-indigo-100 bg-indigo-50 p-6"> <p class="text-base font-semibold text-gray-900 mt-0 mb-0">Want to see the difference on your own site? Run Plausible alongside GA4 and compare the data.</p> <div class="mt-4 flex flex-wrap" style="gap: 0.75rem;"> <a href="/register" onclick="plausible('CTA Click', {props: {position: 'Inline', type: 'Blog', button: 'Start free trial'}})" class="cta-box-primary inline-flex items-center justify-center px-4 py-2 border border-transparent text-sm font-medium rounded-md text-white bg-indigo-600 hover:bg-indigo-500 focus:outline-none transition duration-150 ease-in-out"> Start free trial </a> <a href="https://plausible.io/docs/proxy/introduction" onclick="plausible('CTA Click', {props: {position: 'Inline', type: 'Blog', button: 'View live demo'}})" class="cta-box-secondary inline-flex items-center justify-center px-4 py-2 text-sm font-medium rounded-md bg-white focus:outline-none transition duration-150 ease-in-out" style="border: 1px solid #C7D2FE; color: #4338ca;"> Read proxy setup guide </a> </div> </div>]]></content><author><name>Hricha Shandily</name></author><summary type="html"><![CDATA[Plausible is blocked far less often than Google Analytics, but some blockers can still block any analytics script. Here's how blocking works and how Plausible's proxy option closes most of the remaining gap.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://plausible.io/uploads/plausible-script-successfully-loaded.webp"/><media:content medium="image" url="https://plausible.io/uploads/plausible-script-successfully-loaded.webp" xmlns:media="http://search.yahoo.com/mrss/"/></entry></feed>