Data retention
How long your data stays available, how to keep less in a project, and what a downgrade does to your history.
Retention decides how long your events and analytics stay available in dashboards and reports. Your plan sets the maximum, and each project can choose to keep less.
By plan
| Plan | Retention |
|---|---|
| Free | 30 days |
| Starter | 1 year |
| Pro | 2 years |
| Business | Unlimited |
| Enterprise | Unlimited |
Per project
In Project settings you can set a project's retention to 30, 90, 180, 365 or 730 days. If you don't set it, the project follows your plan.
You can keep less than your plan allows, never more: setting 730 days on Starter still gives you 365. On Business and Enterprise, a project that follows the plan keeps everything.
Use a shorter retention on projects where you don't need history, such as a test project. It is an easy way to hold less personal data without touching the projects that matter.
What it covers
Retention covers events and analytics: page views, ecommerce events, custom events and the sessions built from them.
Orders are your business records and don't expire the same way. But the visit history that explains how an old order was attributed does expire, and when it goes, that order's journey details go with it.
Downgrading
Retention follows the plan you are on. Going from Business (unlimited) to Pro (2 years) makes everything older than 2 years unavailable.
Export what you need before downgrading. There is no grace period and no way to get it back afterwards.
The Usage page can export event and order totals as CSV. Do that first if you need a record of a period you are about to lose.
Related articles
Members and roles
Invite people to your team, see what each of the four roles can do, and choose which projects each person can see.
API keys
Create keys so your system can talk to Clakta, choose what each key can do, and keep them safe.
Plans and limits
What each plan includes, which limit you are likely to reach first, and when to upgrade.