UXWizz 10 is here — See what's new → View changelog

A cookieless analytics platform
you can self-host

Measure stats, goals, heatmaps, and recordings without persistent visitor identifiers. Keep analytics data on your own server.
  • Track stats, campaigns, events, and goals
  • Use heatmaps and recordings without persistent visitor identifiers
  • Keep analytics data on your own server
  • Choose your retention and privacy settings
Open the live demo Try UXWizz free
Built and maintained since 2012.
Cookieless analytics explained

How cookieless analytics works

UXWizz can measure visits without setting a persistent identifier for each visitor. You still get useful stats and behavior tools, with some limits to cross-session attribution.

What happens during a visit?

UXWizz creates or reuses a temporary session token, then connects enabled page activity to that visit.

You choose which events, behavior data, pages, and fields to capture or exclude.

How are IP addresses handled?

Store the IP address or enable SHA-256-based IP hashing. Hashing reduces direct exposure, but it does not make every collected data point anonymous.

What cookieless changes—and what it does not

  • Removed A persistent cookie that recognizes the same browser across later visits.
  • Preserved Traffic sources, navigation, events, goals, heatmaps, and recordings for the current session.
  • Still required Notices, masking, data minimization, retention choices, and a consent assessment.
  • Not guaranteed Cross-device identity, identical counts between tools, anonymity, or automatic compliance.

More than a cookieless pageview counter

Stats

See sessions, pages, referrers, campaigns, countries, browsers, and devices.

Goals and events

Track signups, purchases, forms, clicks, and other actions that matter.

Heatmaps

See where visitors click, move, and stop scrolling.

Session recordings

Replay selected visits to find broken journeys, confusing UI, and errors.

Segments and Ask AI

Compare visitor groups or ask questions about your traffic.

Self-hosted control

Choose the server, backups, access, retention, and deletion process.

Privacy and measurement

What changes without persistent identifiers

Removing persistent identifiers changes attribution and identity. Choose the approach with a clear view of its privacy and measurement effects.

Less persistent identity, less cross-session certainty

Without a long-lived cookie, later visits cannot be reliably linked to the same anonymous browser. Returning-visitor and multi-day attribution numbers can differ.

This fits teams that value current-session behavior, conversions, and aggregate trends over persistent profiles.

Behavior analytics requires careful configuration

Heatmaps and recordings can reveal bugs and friction, but they also capture more detail. Exclude sensitive pages and fields, mask inputs, and set a retention period.

UXWizz provides controls. The website owner decides what to collect and which notices or consent mechanisms are required.

Self-hosting changes who controls the data

Choose the host, region, database access, backups, retention, and deletion workflow. This reduces dependence on a shared analytics cloud.

Self-hosting is not automatic compliance. Security, purpose, transparency, data requests, and regional rules still matter.

Who benefits most?

  • Privacy-focused teams Keep behavior data on infrastructure they select.
  • Agencies Manage multiple client sites without per-site subscriptions.
  • Startups and SaaS teams Connect traffic, goals, errors, and recordings in one platform.
  • WordPress and PHP teams Use familiar PHP and MySQL infrastructure.
Download the Free Trial No email or credit card required.
UXWizz in practice

Set up cookieless analytics clearly

1. Install UXWizz where you want the data to live

Deploy on compatible PHP and MySQL infrastructure. The location you choose becomes the location of the analytics database.

2. Configure tracking and privacy controls

Enable only the data you need. Configure masking, exclusions, IP hashing, retention, Do Not Track, and consent behavior.

3. Validate the real implementation

Check browser storage, requests, exclusions, and opt-out behavior. Document the configuration and update the privacy notice.

4. Use quantitative and qualitative evidence together

Start with traffic, campaigns, events, and goals. Open the relevant segment, heatmap, error, or recording when a number needs explanation.

Technical and regulatory sources
Technical details reviewed by Cristian Buleandră, UXWizz founder and developer. This page provides product information, not legal advice.

Cookieless analytics FAQ

What is a cookieless analytics platform?
A cookieless analytics platform measures website traffic or behavior without placing persistent visitor-identification cookies in the browser. Implementations differ: some collect only aggregate pageviews, while others use short-lived session identifiers, server-side data, events, heatmaps, or recordings.
Does UXWizz set cookies on tracked visitors?
The UXWizz visitor tracker does not set visitor identification cookies. The separate administrator dashboard uses login cookies for authenticated dashboard users.
How does UXWizz identify the current session without cookies?
UXWizz stores a random current-session token in browser sessionStorage. It also uses sessionStorage as temporary cache for page and recording data before that data is sent to the self-hosted UXWizz server.
Does UXWizz use localStorage?
Yes. Depending on configuration and enabled features, localStorage can store opt-out or consent preferences, cache data, and A/B-test assignments. It is not the main identifier used to connect activity within the current visitor session.
Does cookieless analytics remove the need for consent?
Not automatically. Consent and notice requirements depend on the jurisdiction, storage and access technologies, collected data, purpose, and configuration. Cookieless does not mean storage-free, anonymous, or automatically compliant. Obtain qualified advice for your use case.
Can cookieless analytics include heatmaps and session recordings?
Yes. UXWizz can collect heatmap and session-recording data without visitor identification cookies. Because these features capture detailed behavior, website owners should mask sensitive inputs, exclude unsuitable pages, minimize collected data, and choose an appropriate retention policy.
Where does UXWizz store analytics data?
UXWizz stores analytics data in the MySQL-compatible database connected to your self-hosted installation. You choose the server, hosting provider, geographic location, database access, backup process, and retention configuration.
What is lost when persistent analytics cookies are removed?
The platform cannot rely on a long-lived cookie to recognize the same browser across later visits. Returning-visitor, unique-visitor, retention, and multi-day attribution numbers may therefore differ from cookie-based systems, while current-session traffic and behavior analysis remains available.

Get started

Learn

Use cases

About

Questions? Use the contact widget in the bottom-right corner.

XCS developer avatar Cristian Buleandră — Founder
StackOverflow GitHub Twitter

UXWizz - Self-Hosted Analytics


Follow UXWizz on social media


You can also email us at support@uxwizz.com
Your email address will only be used for this inquiry and will not be saved or used for marketing.