Privacy-Friendly Analytics: The Complete Guide for 2026

You want to know where your visitors come from and what they do on your website. You don't want to follow them around the internet to find out.
That's the whole idea of privacy-friendly analytics. The trouble is the label. Nobody checks it. A tool can print "privacy-friendly" on its homepage and still set cookies, keep a profile of every visitor, or need a consent banner before it counts anything.
So I wouldn't trust the label. I'd ask five questions, and this guide goes through them. I run Clickport, so I'm not a neutral party. At the end I answer the same five questions for my own product, including the answers that don't flatter it.
- Nobody regulates the privacy-friendly label. Ask what a tool stores, how it counts a visitor, and what the reports can do.
- A 2019 report recorded a 90.8% fall in Google Analytics users on the ICO's own website after it changed its consent tool.
- Without a lasting identifier you lose returning-visitor statistics, cross-device profiles, and advertising audiences.
- No cookies doesn't end the consent question. EU and UK rules also cover browser storage and device signals.
- Clickport calculates a daily visitor identifier on the server, sets no tracking cookies, and shows sources, engagement, goals, revenue, and bots.
What is privacy-friendly analytics?
Privacy-friendly analytics measures website activity while limiting how visitors are identified and followed. It answers business questions about traffic, content, and conversions without building a lasting profile of each visitor.
That still gives you useful reports. You can measure an enquiry, trace the pages before it, compare the source, and see the revenue from a connected payment. What you don't get is a file on a person.
Why do cookie banners change your numbers?
Cookie-based analytics needs consent in the EU and the UK. When a visitor doesn't give it, a tool such as Google Analytics can't record that visit in the normal way. So the banner decides part of what you see.
How big is that part? Two public examples give you an idea.
A 2019 report on the ICO's own website recorded a 90.8% fall in Google Analytics users after the regulator changed its consent tool. The daily average went from 119,417 users to 10,967. The figures came from a Freedom of Information request. This is the UK's privacy regulator, measuring its own website.
An Advance Metrics study looked at more than 1.2 million users on international B2B websites. 25.4% accepted all cookies at the first banner level. 68.9% closed or ignored the banner.
These are two cases with their own banners and audiences. They don't predict your numbers. But they show why the consent setup is part of every comparison between two analytics tools. For a brand with several country sites, the same effect skews the comparison between countries. I explain that in one brand, several country domains.
The question to ask: does the tool need consent before it counts a visit, and in which countries?
How does a tool count visitors without cookies?
A tracking cookie gives the browser a number that can stay for months or years. A tool without cookies has to recognise a visitor in another way, or not at all.
A common answer is an identifier that the server calculates and that expires quickly. The details decide how private it is. What goes into the calculation? How long does the identifier last? Is the raw IP address stored anywhere?
One more thing belongs here. A short-lived identifier doesn't make the data anonymous by itself. Page addresses, search terms, and custom event values can still contain personal information. A vendor that tells you "it's all anonymous" without conditions is selling you something.
The question to ask: what goes into the visitor identifier, how long does it last, and what happens to the IP address?
What do you give up?
Every tool that drops the lasting identifier loses the same four things.
- Returning visitors. When the identifier changes every day, the tool can't tell you that a visitor from Monday came back on Friday.
- Cross-device profiles. A phone and a laptop count as two visitors.
- Advertising audiences. There is no remarketing list and no demographic profile.
- Blocked scripts. An ad blocker can block any analytics script. That includes the privacy-friendly ones.
For most websites, I think that's a fair trade. You still see sources, pages, engagement, goals, and revenue. If your business depends on remarketing audiences, you need an advertising tool, with consent, for that part.
The question to ask: which reports does the tool not have, and does the vendor say so openly?
Do you still need a cookie banner?
"No cookies" doesn't end the question. The rules in the EU and the UK cover storage on the visitor's device and reading from it. Cookies are one case. Browser storage and device signals are others.
So check what the tool stores and reads, and then check your other tools. A video embed or an advertising tag can need consent even when your analytics doesn't. The cookie-banner guide explains the checks.
Read the main France, Germany, and UK conditions
France: CNIL's route requires measurement for the publisher's exclusive benefit and anonymous statistical results. Cross-site tracking and combining the data with unrelated processing fall outside it. CNIL also gives information and retention recommendations. Its self-assessment process is not product certification.
Germany: Section 25 TDDDG generally requires consent for device storage or access. DSK guidance says analytics is not automatically necessary to provide the service a visitor requests. There is no blanket cookieless exemption.
United Kingdom: The ICO's exception concerns aggregate statistics used to improve a service. It requires clear information and a simple, free way to object. Individual activity logs and advertising purposes fall outside this route. Don't assume that a tool's session history qualifies.
Data-protection duties remain separate where personal data is involved. EU hosting alone doesn't settle them. This guide is general information, not a legal assessment of your site.
The question to ask: what does the tool store on the device and read from it, apart from cookies?
What can you do with the reports?
Privacy is half of the decision. The other half is whether the reports help you run the website. A plain visit counter protects everyone's privacy and tells you nothing.
I'd check four things. Can the tool show which sources bring results, and not only visits? Can it show what people do on a page? Can it show where a journey stops? And can it tell you how much of the traffic is bots?
The question to ask: can I get from a traffic total to the visits behind it?
How does Clickport answer these questions?
Here are my answers, in the same order.
Consent. Clickport sets no tracking cookies. It does use browser storage and browser signals, so include it in your consent check. I don't claim a blanket exemption, because the rules differ by country.
The identifier. The server takes the IP address, the browser header, and the date. It calculates a daily visitor identifier from them with a secret key. The same visitor gets the same identifier for one day, so one person with ten pageviews counts as one visitor. The next day, the identifier is different. The analytics rows store parsed device and location fields, not the raw IP address. The tracker keeps a session marker in sessionStorage, and it reads technical signals, such as graphics renderer information, to detect bots.
What does Clickport use instead of tracking cookies?
The tracker uses sessionStorage, which is browser storage for the current tab, to keep a session marker. It uses localStorage for an exclusion preference. It also stores experiment assignments and configuration there if the site owner sets up an experiment.
The server uses the IP address, browser header, and date to calculate a daily visitor identifier. It stores parsed device and location fields, rather than raw IP addresses, in visitor analytics rows. A different date changes the daily identifier. It doesn't delete the stored analytics or destroy the secret used to calculate identifiers.
The tracker also reads technical signals for bot detection, including graphics renderer information. Daily identifiers and session histories don't prove that the data is anonymous. Page addresses, search terms, copied text, and custom event values can contain personal information, so review what your site sends.
For a basic report, you don't need to send a visitor's name or email address. Keep those details out of analytics events.
What you give up. All four things on the list above. Clickport doesn't build advertising audiences or a lasting cross-device profile.
Where the data lives. Visitor analytics is hosted in the EU. You control your site data, with export and deletion controls. The product is funded by subscriptions.
The reports. This is the part I care about most. Select a source or a page and the whole dashboard follows your selection. You can move from a traffic total to the activity behind it.
| What you want to know | What Clickport shows | What you can do next |
|---|---|---|
| Which sources bring results? | Goals and connected revenue alongside sources and campaigns | Put more effort into the channels that bring enquiries or sales. |
| Which pages need work? | Scroll depth, active time, and frustration signals | Find weak pages and inspect the activity behind them. |
| Where do visitors stop? | Funnels, flows, and session timelines | Improve the steps between arrival and a completed goal. |
| What explains a traffic spike? | Sources, sessions, and bot detection reasons | Investigate the traffic and remove unwanted sessions from your reports. |
| What is happening right now? | Realtime visits, pages, and sources | Watch a launch or campaign as visitors arrive. |

Goals and connected payments show which sources bring enquiries and sales. Recognised AI Search visits get their own channel, and the ChatGPT traffic guide shows how to investigate them. Scroll depth and active time are recorded automatically, and the engagement guide explains each measure. Funnels and flows show where a journey stops. Detected bots are filtered before they reach your reports, and Bot Center shows the reason for each exclusion. Reports use all collected events, without sampling. For revenue, connect a payment integration or the Revenue API.
Start your free Clickport trial and ask these questions of your own traffic. You get all features for 30 days without a credit card.
If you run Clickport next to Google Analytics, the totals will differ. This note explains why.
How does GA4 Consent Mode affect the comparison?
Analytics tools can show different totals because of consent settings, blocked scripts, bot filtering, and counting methods. Compare the same dates and goal definitions when you investigate a difference.
Google's Consent Mode documentation separates Basic and Advanced Mode. Basic Mode blocks Google tags before consent interaction. If consent is not granted, no tag data is sent.
Advanced Mode loads tags with consent defaults and can send cookieless measurements while storage is denied. Eligible GA4 reports can include estimated behaviour. Google's modeling guide explains the requirements and the indicator for estimated data.
Consent Mode changes tag behaviour. It doesn't obtain consent for you or establish that your setup meets privacy law.
Which report should you try first?
Choose what you want to improve. Clickport gives you a direct route from that question to the relevant report.
Put Clickport to work
Start with the result you want
Connect your traffic sources, page activity, and goals in Clickport. Choose a question above to see your next step.
Your next step: choose an important page and the action you want visitors to take.
How do you get started?
Add your site and install one script. Clickport starts collecting core activity automatically, with sources, pages, engagement, and bot filtering ready to use.
- Install the tracker. Follow the installation guide and confirm the connection with Verify installation in Settings.
- Open your dashboard. Use Realtime to see incoming visits, then explore the sources and pages that bring traffic.
- Create a goal. Choose an enquiry, signup, or purchase and use the goals guide to measure it.
Keep your current analytics running alongside Clickport during the trial. You can compare the reports while you set up your goals and payment data. The trial includes all features and up to 10 sites. That means you can use it across your projects or client websites from the start.
AI Search referrals appear through the normal tracker. To also see server-side reads from AI systems, add an AI Agents connector. It gives you a separate view of the pages those systems fetch.
Frequently asked questions
What is privacy-friendly analytics?
It measures website activity while limiting visitor identification and data reuse. Clickport combines traffic sources, engagement, goals, revenue, journeys, and bot filtering without tracking cookies.
Is privacy-friendly analytics GDPR-compliant?
The name alone doesn't establish compliance. Your tool, configuration, purpose, and consent setup determine the requirements. Clickport provides EU-hosted analytics, data controls, and information about its collection methods.
Do I still need a cookie banner?
It depends on your website tools and the applicable rules. Clickport uses no tracking cookies, but browser storage and device signals also matter. Use the cookie-banner guide linked above to assess the setup.
Will I get less data than with Google Analytics?
Clickport gives you sources, campaigns, engagement, goals, revenue, and journeys in one dashboard. Its visitor identity doesn't follow a person across devices or days. You can investigate website performance without that lasting profile.
Is this the same as fingerprinting?
Clickport uses a daily identifier and technical browser signals for bot detection. It doesn't create a permanent advertising profile. The expandable data section above explains the information involved.
Measure the result, not the person
You don't need a lasting profile of each visitor to improve a website. You need to know which sources bring results, which pages lose people, and where a journey stops.
Ask the five questions of any tool you consider, mine included. I built Clickport to pass them with a daily identifier and no tracking cookies. The trade is real, and I listed it above. For most websites it's the right one.
Start your 30-day free trial. All features are included, and no credit card is required. The switching guide takes you through the move from Google Analytics.
Updated September 18, 2026: rebuilt as a guide. Five questions for any analytics tool come first, and the Clickport answers follow. Added two public consent examples and the list of what you give up.

Comments
Loading comments...
Leave a comment