Export

Console reports are aggregates; reconciliation, backup, or your own warehouse needs the raw rows. Export is an async job, not a screenshot of a report, and rows older than retention are already gone; see Retention & deletion.

ConsoleAll-platform analyticsDataData export

The top of the page creates a job; below it, recent jobs are listed with id, kind, row count, created time, and status.

Metrics & definitions

• Kind: the menu shows events, sessions, persons, autocapture, and consent_log: events, sessions, people, autocapture records, and consent receipts.
• Format: the form has no format control and submits JSONL. CSV can only be requested through the API.
• Status: queued, running, then done, failed, or expired.
• Validity: a finished file is gzip and is kept for 48 hours. After that the job is expired and the file is gone.
• Rows: exported rows, not visitors on a chart.

How to use it

Choose a kind such as events, pick a start and end date, and click Create job. The list shows the id and status.

The console can create export jobs and show their status, but cannot download the file yet. Contact support when you need an export file delivered.

Access & limits

• The free tier cannot create an export. The Pro tier allows at most 3 jobs per day; higher tiers are not capped at 3.
• One job may span at most 365 days, and at most 2 jobs run at once per project.
• The caller needs report-read access. A member whose access is limited by a permission scope cannot start a raw export.
• An oversized range or a plan limit is rejected when you create the job.

FAQ

Are export-only properties exported? Yes. They are still in the event row; analyses simply cannot break down by them.

Retention & deletion

A scheduled job deletes expired detail rows, and one person's data can also be handled on its own. Both live in the privacy center, not under Data in the analytics menu.

ConsoleConfigurationPrivacy center

The four day counts are under Data minimisation & retention, and requests are under Data subject requests (DSAR) on the same page. The broader compliance guide is Privacy & compliance.

Metrics & definitions

• Four day counts: event rows, autocapture, person profiles, and consent receipts are set separately. The starting values are 365 days for events, 90 for autocapture, and 730 each for profiles and consent receipts.
• Event rows: stay in sync with the project's data-retention days, capped by the plan.
• Daily aggregates: contain no personal data and are not deleted on these timers.
• Tiered decay: if on, some columns are cleared before the deadline; see Data quality.
• Deleting a data source or an event definition: does not purge history on this schedule.

Data subject requests

Request types are access, export, restrict processing, and erasure. You locate the subject by email, login id, device id, or person id. Email is matched after a server-side hash.

Access and export run immediately, and the result can be downloaded when done. Restrict and erasure stop processing new events for that subject as soon as you submit them, then wait out the cooling-off period. The period is a number of days, starting at 3; domestic mode caps it at 3. You can cancel during the wait, which resumes processing.

How to use it

Set event retention to a length the plan allows and save. To erase one person, create a request, choose erasure, and enter the subject. A bulk raw export is a different path; see Export.

Access & limits

The privacy center menu is only for Owner and Admin. Child mode locks event retention to the day count on that mode and forces the anonymous tier. Fields locked by a regional preset cannot be edited until the preset is released.

FAQ

Why did very old detail disappear from a report? Check retention before you look for a collection outage.

Is restrict the same as erasure? No. It only stops processing new events, and you can cancel it during the cooling-off period.

Is clearing quarantine related to retention? No. Quarantine holds events that were never stored.