How Analytics Works Without Tracking Cookies
Understanding the technology behind privacy-first analytics and how modern tools provide useful insights without third-party cookies, ad profiles, or cross-site tracking.
Traditional analytics tools like Google Analytics rely on cookies to identify visitors. They set a unique identifier that persists across sessions, allowing them to track returning visitors and build user profiles.
This creates problems: tracking cookies generally require consent, third-party cookies enable cross-site tracking, and the data often feeds advertising profiles.
How Cookieless Analytics Works
Privacy-first analytics tools use different approaches to provide useful insights while collecting as little as possible:
1. Minimal, Aggregate-Focused Data Collection
Instead of building a profile of each person, privacy-first analytics records only what's needed for traffic reports. When a pageview occurs:
- The page URL is recorded (what was visited)
- The referrer is recorded (where they came from)
- Basic device info is recorded (browser, OS, screen size)
- Geographic location is derived from the IP (country/region/city level)
- The IP itself is discarded, never stored
2. Counting Unique Visitors
Tools differ in how they tell a new visitor from a returning one. Common approaches are:
- Daily rotating hash: hash of site + IP + user agent with a salt that changes every day; no storage in the browser, but no returning-visitor data beyond a day
- First-party, per-site identifier: a random ID kept in the site's own storage; never shared with other sites or ad networks, but it is stored on the device, so it needs consent in the EU/UK
Invoker uses the daily rotating hash by default (Privacy mode), so nothing is stored on your visitors' devices. Sites that want returning visitors and multi-day journeys can opt in to the per-site identifier (Enhanced mode). Either way, nobody is tracked across websites. Details below.
3. No Cross-Site Tracking
Each website's analytics is completely isolated. The same visitor on two different sites using the same analytics tool cannot be connected. This is fundamentally different from Google Analytics, where visitor data feeds into Google's advertising ecosystem.
Ad-Tech Analytics vs Invoker
| Capability | Ad-tech analytics (cookie-based) | Invoker (Privacy mode) |
|---|---|---|
| Track pageviews | ||
| Track referrer sources | ||
| Geographic location | ||
| Device/browser info | ||
| UTM campaign tracking | ||
| Custom event tracking | ||
| Unique visitors and sessions | ||
| Returning visitors across days | ||
| Build advertising profiles | ||
| Cross-site tracking | ||
| Shares data with ad networks | ||
| No third-party cookies | ||
| Nothing stored on the visitor's device | ||
| Data never sold or used for ads |
Technical Implementation
What Data is Collected
When a visitor loads a page with the Invoker script, we collect:
- Page URL: The current page path
- Referrer: Where the visitor came from (if available)
- User Agent: Browser and OS information
- Screen Size: Screen and viewport dimensions
- UTM Parameters: Campaign tracking data (if present)
What Happens to IP Addresses
IP addresses are used to derive approximate geographic location using a local DB-IP database on our own servers, so no third-party lookup service ever sees your visitors' IPs. The IP is used only while the hit is processed (for location, IP blocking and the daily visitor hash below) and is never stored, in full, truncated or hashed on its own.
Privacy Mode: The Daily Rotating Hash
Privacy mode is the default for every Invoker site. The script stores nothing on the visitor's device: no cookies, no localStorage, no sessionStorage and no fingerprinting. Instead, our server recognises a visitor for one day:
- It calculates an HMAC-SHA256 hash of the site, IP address and user agent
- The hash is keyed with a random salt that is created for each UTC day
- The salt is deleted when the day ends, so after that nobody, including us, can link the hash back to an IP address or to the same person on another day
- The IP address and user agent are used only for this calculation and are never stored
Sessions are worked out on the server too: a visitor's hits with less than 30 minutes of inactivity between them form one session. Because no identifier is stored on or read from the device, Privacy mode is designed so you don't need a cookie banner for Invoker in most cases (this isn't legal advice).
Enhanced Mode: A First-Party Visitor ID
Sites that need returning visitors can turn on Enhanced mode in site settings and add data-mode="enhanced" to the script. The script then keeps two random, first-party values in the site's localStorage:
invoker_cid: a random visitor ID, scoped to your site onlyinvoker_session: a session ID that expires after 30 minutes of inactivity
That adds returning visitors, multi-day journeys, Visitor Logs across days and first-touch attribution. If storage is blocked, it falls back to the daily hash. Because it stores an ID on the device, Enhanced mode needs visitor consent in the EU and UK, so load the script only after consent there. Invoker never sets third-party cookies and never links visitors across websites in either mode.
Visitors can opt out with invoker.blockTrackingForMe(), and you can enable Do Not Track support per site. See our cookie policy and privacy policy for the full details.
Limitations and Trade-offs
Privacy-first analytics has real limitations. In Privacy mode:
- Daily unique visitors: Unique visitors are counted per day, so someone who visits on three days counts three times in a multi-day range
- No returning visitors: There's no new-vs-returning split, and Visitor Logs and journeys only cover a single day
- No multi-day attribution: First-touch attribution across days isn't available
- Shared networks: People sharing an IP address and browser (an office, mobile carrier NAT) can be merged, and a phone switching networks can be split in two
Enhanced mode removes most of these, at the cost of needing consent in the EU/UK. Some limits remain:
- Returning visitor accuracy: In Enhanced mode, visitors who clear storage or switch browsers or devices are counted again
- No cross-device identity: We don't identify people, so one person on a phone and a laptop is two visitors
- No ad-network data: No demographics or interests from advertising profiles
- Attribution: Attribution is first-party only, based on referrers and UTM parameters
For most websites, these limitations don't matter. You can still answer the important questions: What content is popular? Where does traffic come from? Are my campaigns working?
A Note on Fingerprinting
Some "cookieless" analytics tools rely entirely on fingerprinting—combining browser characteristics to recognise a device. That has drawbacks:
- It's harder for users to reset than clearing storage
- Precise fingerprints can single out individuals
- Regulators generally treat it like cookies under ePrivacy rules
Invoker doesn't fingerprint in either mode. Privacy mode uses a daily hash whose salt is deleted every day, and Enhanced mode uses a random first-party ID that visitors can clear.
Benefits of Privacy-First Analytics
Privacy mode stores nothing on the device, so it's designed to work without a cookie banner. If you opt in to Enhanced mode, load the script after consent in the EU and UK.
The Invoker script is about 3.5 KB gzipped and loads with defer, so it won't slow your pages down.
Data minimisation, no stored IPs and DNT options make it easier to meet GDPR, CCPA, and other privacy regulations.