For a company website, blog or portfolio that mainly needs traffic, content and enquiry statistics, Plausible is often a sensible starting point. GA4 is a stronger fit when Google Ads conversions, advertising audiences or analysis across repeat visits are part of the job. The right choice depends on what you need to measure and how you configure it. 2, 25
A useful analytics setup should help you make a decision: which article deserves a follow-up, whether a campaign brings enquiries, or where people stop using a form. A larger dashboard is only helpful if you use the additional information.
For websites serving people in the EU, the choice also involves consent, the information sent from visitors’ devices and where that information is processed.
Information checked on 23 October 2026. This comparison covers GA4 and the hosted Plausible service.
What each tool is good at
| What you need | Google Analytics 4 | Plausible |
|---|---|---|
| Routine website reporting | Broad reporting across websites and apps. 4 | Focused reporting on traffic, pages and goals. 1 |
| Google Ads workflows | Direct integration for conversions and advertising audiences. 2 | No equivalent audience syncing or retargeting infrastructure. 25 |
| Conversion tracking | Key events that can feed Google Ads conversions. 2 | Goals; funnels and revenue on the Business plan. 26, 27 |
| Recognising repeat visitors | Supports returning-user reporting where the implementation can recognise them. 15 | Does not recognise the same visitor across different days or devices. 14 |
| Hosted service cost | Standard Analytics has no licence fee. 4 | Paid subscription; the tier depends on usage and features. 3 |
Use the table to match features to the decisions you need to make.
For a local service business, a report showing which pages bring completed enquiries may be enough. For a business using Analytics audiences and conversions in Google Ads, the integration may justify GA4’s additional setup.
Plausible’s subscription is an explicit cost. With either product, also budget for implementation, checking events and maintaining consent settings. A free licence does not make that work disappear.
What Plausible collects without cookies
Plausible uses no cookies or persistent visitor identifiers. Its policy describes processing IP addresses and User-Agent information to calculate daily visitors, without storing those raw values. It retains event and session records and displays aggregate statistics. 1
That distinction matters: cookieless analytics still involves data processing. It is more accurate to describe the measurement design than to say that the service collects nothing.
Plausible says its hosted visitor analytics are processed and stored in the EU on infrastructure owned by European companies. The business is incorporated in Estonia. That hosting arrangement is useful if keeping visitor analytics within the EU is a requirement. 21
Do you need a cookie banner in the EU?
There are two related questions:
- Does the implementation store or access information on a visitor’s device? The ePrivacy rules cover more than cookies, and an applicable consent exemption needs to be assessed.
- Does it process personal data? If so, GDPR obligations also apply.
The European Data Protection Board’s guidance makes clear that removing cookies does not automatically place a tracking method outside the device-access rules. National implementation and regulator guidance matter. 5
For Estonia, the Data Protection Inspectorate states that analytics cookies allowing direct or indirect identification require prior voluntary consent. It also says withdrawing consent must be as easy as giving it. 6
With a conventional GA4 setup that uses analytics cookies, plan for consent before those cookies are used. A banner that appears after the tracking has already started does not solve that sequencing problem.
Can Plausible run without consent?
Some configurations may operate without consent, depending on the measurement method, purpose and applicable national rules. Check those conditions against your actual setup.
France illustrates why the details matter. CNIL allows certain limited audience measurement configurations to operate without consent. Its conditions include narrowly defined purposes and anonymous statistical outputs. 7
CNIL’s July 2025 self-assessment framework excludes marketing measurement such as campaign performance and calls for disabling UTM and campaign identifier collection. This describes that framework’s scope; it is not an EU-wide ban on campaign parameters or an exhaustive account of every possible legal analysis. 8
If you rely on an audience measurement exemption, confirm that it covers the features you actually enable. Adding marketing reports should prompt a fresh check.
Also assess the other services on the website. Changing the analytics provider alone does not decide whether your remaining scripts need consent.
Is Google Analytics banned in the EU?
A blanket claim that Google Analytics is banned across the EU is not a sound basis for choosing a tool.
The European Commission currently lists US organisations participating in the EU–US Data Privacy Framework as covered by an adequacy decision. Google states that Google LLC and covered US subsidiaries have certified adherence to that framework. 9, 10
That supports a route for eligible international transfers; it is not blanket approval of a GA4 installation. The EDPB says businesses must check active certification and its scope, and that the other GDPR obligations continue to apply. 11
Google also describes regional collection and removal of EU users’ IP addresses before further Analytics processing. Regional collection should not be confused with a commitment that all subsequent processing stays inside the EU. 22
Consent Mode does not mean that nothing is sent
Google documents two implementations:
| Implementation | Behaviour without consent |
|---|---|
| Basic Consent Mode | The relevant Google tags stay blocked. No measurement data or consent status is sent to Google. |
| Advanced Consent Mode | Tags can load and send cookieless pings while consent is denied. |
Consent Mode passes choices to tags; it neither supplies a banner nor establishes legal permission. Inspect the actual requests too. 12
GA4 can also use behavioural modelling to estimate missing activity. That requires sufficient data and eligibility checks. Google’s requirements include at least 1,000 daily users sending consented events on seven of the previous 28 days, alongside other conditions; even meeting the published thresholds does not guarantee eligibility. 13
For a small website, “Consent Mode will fill in the missing visits” is therefore a poor assumption. Modelled figures are estimates, not recovered observations of every visitor.
Do ad blockers affect Plausible as well as GA4?
Yes. Both can lose measurements when requests are blocked. Plausible acknowledges that some privacy tools and blocklists block its script. It also documents serving requests through your own domain to reduce blocking. 16
That does not make either tool a complete visitor census. A proxy changes how requests travel; it does not establish a legal basis for sending them or remove consent requirements.
There is no reliable percentage you can apply to every website to “correct” its totals. The audience, browser settings and implementation need to be considered. Treat a sudden difference as something to investigate.
Why GA4 and Plausible show different numbers
Even when both are working, their reports need not match.
The visitor definitions differ. GA4 distinguishes total, active, new and returning users. Plausible’s visitor identity does not persist across days. Someone returning on several days can therefore contribute more than one visitor to a longer Plausible reporting period. Comparing a monthly Plausible visitor figure with GA4 active users is not a direct comparison of the same metric. 14, 15
Consent changes what is observed. Different consent settings change which visits are measured. The gap between two totals does not isolate refusal from blocking. 12
Bot filters differ. GA4 excludes known bots, while Plausible describes its own filtering rules and acknowledges that some legitimate VPN traffic can also be filtered. Neither is a guarantee that every recorded visit is human. 17, 18
Implementation can add or lose pageviews. In a single-page application, overlapping automatic history tracking and manual events can count the same navigation twice. Check one real navigation at a time before blaming the analytics provider. 19
Start a comparison with the same date range, time zone, included pages and event definitions. Then test an initial page load, a route change and the consent choices. For a focused debugging guide, see why GA4 can count one SPA pageview twice.
Server or CDN statistics are another measurement system. They may include automated requests and activity that never executes browser analytics, so a higher server total is not proof that it found more real people. 20
Measure the action that matters to the business
For a service website, I would start with a small measurement plan:
- Visits to the main service pages.
- Opening the enquiry form.
- Successful submission of the enquiry.
- Clicks on the email or phone contact links.
Keep those events separate. Clicking “Send” is not the same as a submission that the server accepts. Clicking an email address is not proof that an email was sent.
Record the success event after the application confirms that the enquiry was accepted, and compare it with the enquiries actually received. Do not expect every accepted enquiry to appear in browser analytics: consent and blocking can still affect the event.
Use event names and safe page categories rather than names, email addresses or message contents. Google specifically warns about personal information leaking into Analytics through URLs, titles and event data. Check what your site sends, whichever tool you choose. 23
An analytics platform can show where people leave a flow. It cannot decide whether an enquiry became a suitable client. That remains a separate business record.
Which would I choose?
For a company website, portfolio or blog: start by evaluating Plausible if the job is to understand content, traffic sources and enquiries, and you do not need persistent visitor histories. Check the consent position for the selected features.
For a business using Google Ads heavily: favour GA4 when its conversion and audience integrations are part of your actual workflow. Keeping an existing, useful setup can be more sensible than migrating just to obtain a larger visitor number.
For a shop: decide from the reporting requirements. Plausible can report revenue and funnels; needing those features alone does not settle the choice. Advertising workflows and the need to understand repeat customers may matter more. 26, 27
Before adopting either tool, write down the questions you expect it to answer. If a report will not change a decision, it probably does not need to be part of the initial setup.
Have the EU cookie rules changed?
Proposals should be distinguished from rules already in force. When checked on 23 October 2026, the Digital Omnibus procedure covering proposed GDPR and ePrivacy changes was still awaiting a committee decision in the European Parliament. Do not configure a website as though those proposals have already replaced the existing requirements. 24)
If you need help connecting analytics events to what your website actually does, tell me about your website.
Sources
- Plausible — visitor data policy
- Google — connecting Analytics and Google Ads
- Plausible — plans and billing
- Google — Analytics product overview
- EDPB — technical scope of ePrivacy Article 5(3)
- Estonian Data Protection Inspectorate — website activities and cookies
- CNIL — consent exemptions for audience measurement
- CNIL — July 2025 audience measurement self-assessment
- European Commission — current adequacy decisions
- Google — frameworks for international data transfers
- EDPB — 2026 Data Privacy Framework FAQ for businesses
- Google — basic and advanced Consent Mode
- Google — behavioural modelling requirements
- Plausible — definitions of visitor and traffic metrics
- Google — total, active, new and returning users
- Plausible — blockers and first-party proxying
- Google — exclusion of known bot traffic
- Plausible — filtering bots and spam
- Google — measuring single-page applications
- Cloudflare — why network and browser analytics differ
- Plausible — location of hosted visitor analytics
- Google — regional data collection and IP handling
- Google — keeping personal information out of Analytics
- European Parliament — Digital Omnibus procedure 2025/0360(COD))
- Plausible — product limits and returning visitors
- Plausible — funnel analysis
- Plausible — revenue tracking
Building a feature for your web application?
The useful part of a technical approach is how it works for your users. I build interfaces, connect them to existing APIs and help product teams improve features, including loading, empty and error states.
Explore frontend development for your application
Related work and examples
Dashboard
A COVID data explorer grew into a personal dashboard and a collection of everyday web tools. A long-running React project where I learned to connect interfaces, interactive charts and real data.