DataVisitors measures how people find and use your website and your product — page views, events, funnels and the people behind them — without putting a cookie on a single visitor.
How it fits together
Everything you measure belongs to a project, and every project belongs to a workspace. Your team, your plan and your billing live on the workspace. Keys, goals, alerts, shields and boards live on the project.
Workspace
The people who can see your data, their roles, and the plan that pays for it.
Project
One site or one product. It has its own keys, tracking rules, goals, alerts and boards.
Keys
An install key sends events and reads nothing. A read key queries and sends nothing. A managing key changes the project itself.
Events
A page view, an event you named, or a row from an import. Each one is stamped with a time and a project.
The screens you sign in to are this application. Every event goes to the analytics service at api.datavisitors.com, which is the only thing that ever writes your analytics data.
What you can measure
- Traffic — visitors, page views, sessions, referrers, campaigns, devices, browsers and countries, live and historical.
- Product use — events you name, funnels, retention, segments, journeys and attribution, broken down by the properties you send.
- Outcomes — goals that turn an event or a page into a conversion you can report on and be alerted about.
Accounts open by invitation. DataVisitors is in its waitlist period. If you do not have an invitation yet, join the waitlist: you get one confirmation mail, and an invitation when a place opens.
What we do not do
- We never set a cookie on your visitors. The tracking script does not touch
document.cookieunder any privacy regime. - We never build a device fingerprint and never share an identifier across sites.
- We never keep a raw IP address. It is used for a moment to derive a coarse country and is then discarded.
- We never pool or sell what you collect. Your data is yours, and exporting it is on every plan.
Under a regime or a consent that allows it, the tracker may store one first-party identifier on the device, for your site alone. Cookieless by default explains exactly when that happens and what it changes.