Short answers to the questions that come up most. Each links to the full detail where there is more to say.
Does OakData use cookies?
It stores a single first-partyidentifier in the visitor's browser to recognise them across pages and sessions. There are no third-party cookies and no cross-site tracking - the id is scoped to your site only. See identity resolution.
Do I need a cookie consent banner?
That depends on your jurisdiction and how you configure OakData - we can't give legal advice. Check your own obligations. Data-subject deletion and export are available when you need them - see data deletion (GDPR).
Will ad-blockers block it?
They can, if you load the tracker from a third-party domain. Serving it first-party from your own subdomain avoids filter lists entirely.
Are bots counted in my numbers?
No - crawlers and automated traffic are detected and hidden by default, and bot events are never billed. You can toggle them on to inspect them.
What counts as an event for billing?
Every captured action - pageviews, autocaptured clicks, and your custom events - is one event. Bot traffic is not billed, so a crawl spike can't push you toward a plan limit. See rate limits & quotas.
Can I track more than one site?
Yes - create a project per site, each with its own keys and dashboard. A single project can also span subdomains; filter by domain to split them.
Can an AI agent read my analytics?
Yes. Connect Claude, Cursor, or any MCP-capable agent to the MCP server and it reads your real user data as first-class tools. Everything is also available over the REST API.
How do I delete a person's data?
Erase or export everything for a single visitor - events, sessions, and replay chunks - over the secret-key API. Full details in data deletion (GDPR).
Didn't find your answer?
The rest of the docs go deeper on every topic above, and each concept page links to the relevant API. Start from the overviewif you're not sure where to look.