Read the tideline, not the visitor.
Web analytics that counts what your traffic leaves behind: which pages, from where, how many. Nobody is recognised and nothing is stored on their device. When you do need to follow a visitor, tidekeeper asks them first and keeps the proof.
Most sites need to know how much. A few need to know who came back.
Other tools make you choose a product. tidekeeper is both, and it draws the line itself, so you cannot cross it by accident.
Easy
on the shoreCounts without knowing who
- Views, visitors, sources, pages, places, devices, goals, live
- No cookie, no storage, nothing read from the device
- A visitor is recognised for one day, then the key is destroyed
- The address is used for the country and dropped
- Every visitor is counted
Built so there is nothing for a consent banner to ask about. Whether that is enough where you are is a legal judgment. Ours, with sources.
Hard
in the water · with consentRecognises a visitor who agreed
- Funnels across visits, retention, paths, attribution, revenue
- tidekeeper's own banner: "no" is as easy as "yes"
- A record of every answer, and of the words shown
- Find, export and delete one visitor's data in a minute
- Always says what share of visitors a figure covers
Everyone is still counted the easy way. Only those who said yes are followed, from that page on.
Every figure shows its working.
Click any number and tidekeeper tells you how it was made: what arrived, what was left out as a bot, what was counted without a visitor key. "Visitors this month" says plainly that it is a sum of daily counts, because that is what it is.
The same answer in the browser, the API, the terminal and the weekly email.
How this is counted
an example: /install · 7 days| Hits received | 11,204 |
| Bots | − 1,862 |
| Retries of the same hit | − 376 |
| Spam and wrong hostnames | − 50 |
| Views | 8,916 |
$ tidekeeper why eza.rocks views --page /installMay this site recognise you when you come back?
If you say no, your visit is still counted, without recognising you, and the site works the same.
Consent is part of the product, not your problem.
The banner, the record of each answer, the privacy policy text and the tools to answer "what do you hold about me?" all come with it. You cannot publish a banner where "no" is smaller than "yes".
One line. Under 2 KB. It cannot break your page.
<script defer src="/t.js" data-site="your-site.example"></script>
Served from your own domain. Your visitors' browsers talk to your site and nobody else. No third party to explain.
Count from your web server's own log.
Nothing runs in anyone's browser. The log is read where it lies, and only sums by the day leave that machine.
Import, checked before it is written.
From Plausible, umami or GoatCounter. Imported days are drawn hatched and said to be imported, and the whole import can be taken out again.
Hosted by us, in the EU. Nothing for you to run.
Your figures are kept in Nuremberg, Germany, under a data processing agreement, with no transfer outside the EU. There is nothing to install, patch or back up.
Have to keep it on your own infrastructure? That is a separate agreement, made with us directly.