Identifiers
A random visitor id, kept in a first-party cookie or, in cookieless mode, a hash that changes every day. A session id for each visit.
IP address
Used as each request arrives: for approximate location, to filter out data-centre traffic and, in cookieless mode, to make the daily hash. It isn’t stored with your analytics. Server logs and our records of bot visits keep it for up to 30 days.
Device
The browser’s user agent, and the browser, operating system and device type read from it.
Approximate location
Country, region, city, time zone and approximate coordinates, worked out from the IP address.
Activity
Pages viewed, referrer and campaign (UTM) tags, link clicks, scroll depth, time on page, visit length, and the custom events you send.
Session recordings
Only if you turn on session replay: the pages a visitor sees and what they do on them. By default, what they type into forms, and email addresses, are masked in their browser and never reach us. Kept for 30 days.
Identified visitors
Only once you identify someone: their email address, plus any details you send, such as a name, company or plan.
Payments
From a payment provider you connect, or revenue events you send: amount, currency, product, dates, and the payer’s name and email address.
Imports
Events you import, for example from a CSV file.
Ask AI
The questions your team asks the assistant, and the analytics it reads to answer them.