← THE CHARTSPOD LEDGEROPEN TERMINAL →
CHARTSPOD · HEATMAP HISTORY

ChartsPod Heatmap History: Live Sessions and Missing Depth

A liquidity heatmap shows depth over time. Whether you see the past depends on how depth was captured. Know the difference before reading a gap.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

Before reading history on ChartsPod's liquidity heatmap, determine whether the depth you see was recorded during your session or served from stored history: open the heatmap, note the earliest timestamp with depth, close the tab for a known period, reopen and see whether that period fills. ChartsPod's public pages do not state a retention period, so measure it. Treat any unrecorded interval as unknown, not as an empty book, and check whether trades printed during it.

Recorded vs stored depth

Where heatmap history comes fromWhere heatmap history comes from. Left, Recorded in session: Starts when you open the view; Gaps when tab sleeps or disconnects; Complete while you watch; Lost on reload unless stored. Right, Stored history: Available on open; Fills past periods; Retention set by provider; Resolution may be lower.RECORDED IN SESSIONStarts when you open the viewGaps when tab sleeps or disconnectsComplete while you watchLost on reload unless storedSTORED HISTORYAvailable on openFills past periodsRetention set by providerResolution may be lower
Measure which one you have. Original ChartsPod editorial graphic.

Measure it in five minutes

Heatmap history testHeatmap history test. Steps: 1. Open heatmap — Note earliest depth time; 2. Wait — 10 minutes watching; 3. Close tab — Known gap, e.g. 20 min; 4. Reopen — Does the gap fill?; 5. Record — Retention and behaviour1Open heatmapNote earliest depthtime2Wait10 minutes watching3Close tabKnown gap, e.g. 20min4ReopenDoes the gap fill?5RecordRetention andbehaviour
Result tells you how to interpret blanks. Original ChartsPod editorial graphic.

Control names in the terminal can change between releases. If a label differs from this guide, look for the setting that does the job described.

Practical habits

Open the heatmap early in your session so the recorded portion covers the period you care about. If you return after a break, note the gap before reading levels.

When saving a screenshot of an important level, include the time range and whether the depth was continuous. When a level matters for a trade, confirm it on the live order book at that moment rather than relying on earlier heatmap colour.

Example: a misread gap

Illustrative: a trader opens the heatmap at 10:00 and sees a dense bid band from 10:00 onwards, with nothing before. They conclude the bids appeared at 10:00. The close-and-reopen test shows the heatmap records only while open; the bids may have been there for hours. The correct note is 'bids present from at least 10:00'.

Reading missing depth

ObservationInterpretation
Blank band, trades printed during itNot recorded
Blank band, no tradesPossibly disconnected; check feed
Thin band, normal tradesLiquidity genuinely thin

Run the history test on a perpetual's liquidity heatmap.

Open the live chart in ChartsPod

Know whether heatmap history is recorded or stored, and never read unrecorded time as zero liquidity.

Related: TensorCharts vs ChartsPod: Compare Crypto Heatmap Coverage, How to Diagnose Missing Order-Flow Data in ChartsPod.

Put Heatmap History next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Questions readers ask

How much heatmap history does ChartsPod keep?

Its public pages do not state a retention period; measure it with the close-and-reopen test.

Why is part of my heatmap blank?

Depth may not have been recorded for that period; check whether trades printed.

Is a blank area zero liquidity?

Not unless you confirm depth was being recorded.

Sources and methodology

ChartsPod capabilities were checked against its public overview, documentation index, markets and indicator pages on 17 October 2026. Exact control names inside the terminal can change between releases, so this guide describes what to set and check rather than quoting menu labels. Venue availability is shown per tool in the terminal. Worked examples use illustrative numbers. ChartsPod's public pages do not state heatmap history retention; this guide shows how to measure it.

  1. ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.
  2. ChartsPod documentation — guides for order flow, derivatives, alerts, backtests, journal and workspaces.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.