Documentation

Plan comparison

Free

For trying the product out. One project, and 30 days of history.

Starter

For a small team. More projects and more people, with 90 days of history.

Pro

For a product with real traffic. High limits everywhere and 180 days of history.

Enterprise

For larger organisations. Unlimited resources, and a retention period you agree with us.

When limits are reached

We email the account owner at 80% of your plan’s monthly event limit and again at 100%. Once the limit is reached, the API answers with a 429 error — the standard “too many requests” reply — and records nothing more until the next billing cycle. Nothing is queued or caught up afterwards: as soon as the tracking script sees that error it stops sending for the rest of the page, so everything people do from that point on is simply not recorded. If you need those events, move up a plan before you reach the limit rather than after. Other limits (projects, funnels and so on) only stop you creating new ones and leave what you already have working.

Data retention

Events older than your plan’s retention period are deleted automatically. Upgrading extends the window over everything you already have, so history you could not see becomes visible again. Downgrading does not delete anything at once; events beyond the new window are removed within the hour. Flows are the exception: however long your plan keeps everything else, the Flows page never reaches back more than 90 days. On the Pro plan that is 180 days of events, statistics and funnels, and 90 days of flows.

What a trait key is

The trait keys row counts the traits your tracker may attach to a visitor. A trait is one whole word such as plan:pro — nothing splits it at the colon, so plan:pro and plan:free use two of your slots rather than one. Traits are registered automatically the first time they arrive, and you can see and delete them under Settings → Trait Keys. How to send them is described under session traits.