Sessions · Plans and data
Limits
Each package sets how many recordings start and how many journey steps arrive in a month, and how long recordings may be kept.
Limits by package
Loading the limits…
Recordings a month
A recording counts once, when its first chunk is stored; the rest of its chunks are free. The month is the calendar month in UTC, and the count starts again on the 1st.
Past the month's recordings, a new recording's first chunk is refused (403, monthly-limit) and the recorder stops for that page. Recordings already going on finish. Nothing is lost from your app: its pages go on as before, only unrecorded.
Journey steps a month
Each journey step your server sends counts. Past the month's steps, Sessions refuses the rest of the month's steps as monthly-limit, and the SDK drops them. Your app's log says so once a month, and once again when Sessions takes steps again. The journeys you have stay.
A person who objected sends no steps at all, and routes in journey.skip_routes are no one's step: use it for autosaves and polling, which would otherwise count.
Recordings kept for
A recording goes, its rows and files, the set number of days after it ends. You choose that number in Sessions, in the project's Settings → Recordings kept, up to what your package allows. When a smaller package takes over, a setting above its limit comes down to it.
How long journey steps, key flow runs and stuck point occurrences are kept is the same for every package: What Sessions keeps.
Before a limit is reached
When a project has used 80 % of a monthly limit, and again when it's used up, the project's admins get an e-mail, once each a month. Sessions' pages say so too while it lasts. A larger package raises the limits at once; see Sessions' page for the packages.