Data Retention in Noibu
Last updated: October 30, 2026
This page explains how long each type of data is kept in Noibu, both in the Noibu Console and when queried through MCP.
At a glance
Data type | Where | Retention |
|---|---|---|
HTTP requests (GET/POST) | Console | 7 days |
Session replay recordings | Console | 30 days (90 days on select plans) |
Issues | Console | 90 days |
Page Analysis (heatmaps, scroll maps, journeys, performance views) | Console | Up to 90 days, rolling (new) |
Performance data | Console | 180 days |
Session, event & Page Analysis data | MCP | 90–180 days |
Noibu Console
HTTP request data: 7 days
Request-level data (GET and POST requests) is available for 7 days.
Session replays: 30 days
Session replay recordings can be viewed for 30 days.
Some accounts have an extended 90-day replay window as part of a custom agreement. If you're not sure which applies to you, reach out to your Noibu account team.
Issues: 90 days
Issues are retained for 90 days.
Page Analysis: up to 90 days ✨ New
Page Analysis now supports a custom look-back of up to 90 days. This includes heatmaps, scroll maps, journeys and performance views.
A few things to know:
Each selection can cover up to 30 days.
The 90-day window is still filling in. We started building it on August 2, and coverage grows by one day at a time. You'll have a full rolling 90 days by early November.
Older periods may show the current page layout. Beyond the most recent 30 days, exact historical page snapshots are limited. You may see today's live page instead of how it looked at the time. The click and scroll data still reflects the period you selected.
Performance data: 180 days
Performance data is retained for 180 days.
MCP
Underlying session, event and Page Analysis data queried through MCP is retained for 90–180 days.
Questions?
Contact your Noibu account team or reach out to support.