Skip to main content

Library · Free preview · Module 4 of 18

Bookmap Heatmap Trading Explained

The Bookmap Heatmap module breaks down how colored liquidity displays and executed volume dots reveal what is really happening beneath price, and where that picture can quietly mislead you.

The Bookmap Heatmap module breaks down how colored liquidity displays and executed volume dots reveal what is really happening beneath price, and where that picture can quietly mislead you.

Reading Liquidity Instead of Just Price

Most chart-watchers see one thing: price. The Bookmap heatmap module in the Education Library is built around a different question: where is resting liquidity actually sitting, and what happens when price meets it? A heatmap visualizes the order book over time, with every price level on the vertical axis and color intensity showing how much displayed size is resting there right now. Layered on top, volume dots mark each executed trade, sized by how many contracts changed hands. The two layers together let a trader compare what the market is offering against what actually traded, a distinction a candlestick chart simply cannot show.

This matters because a level that looks important on a heatmap is not automatically meaningful. A bright band of resting liquidity is a claim, not a fact, until real order flow tests it. The module's central habit is to treat every heatmap observation as a hypothesis that price then confirms or rejects, never as a standalone signal.

The Core Mechanic: Displayed Liquidity vs. Executed Liquidity

The distinction between resting orders, or displayed size, and executed orders, the volume dots, is the foundation of the whole module. Displayed liquidity can vanish in an instant: a resting order can be pulled before price ever reaches it, a behavior generally described as pulling rather than genuine support or resistance. Executed liquidity is a settled fact by comparison; contracts traded, and the size of that print says something about who was actually willing to transact, not just who was willing to advertise a price.

Because displayed size and executed size behave so differently, the discipline here is simple to state and hard to practice: never treat color alone as evidence. A heatmap band only becomes informative once trade activity interacts with it and price responds one way or another.

Absorption and Icebergs: Two Signature Behaviors

Absorption happens when aggressive market orders repeatedly hit a level and price still fails to move through it in proportion to the volume traded. If several hundred contracts trade into a level and price only concedes a tick or two before rotating back, the read is that passive size absorbed the aggression: someone kept offering size at that price rather than letting it run. Absorption is a process rather than an instant judgment. The useful habit is comparing the first test of a level against the retest, since the first touch often just reveals surprise, while the retest reveals whether anyone is still willing to defend the price.

A related but distinct behavior is the iceberg order: a large resting order that only displays a fraction of its true size, refreshing at the same price every time a piece of it fills. The heatmap color alone cannot prove an iceberg exists. The evidence has to come from execution specifically, repeated fills at one exact price with the displayed size refreshing rather than depleting. It is tempting to reason backward from a stable-looking wall and assume an iceberg sits behind it, but a wall that never gets traded into is simply untested, not proof of hidden size. The read only holds up when print size and displayed size are compared together over several minutes, not from a single snapshot.

BehaviorDisplayed liquidityExecuted volumeLikely read
Wall holdingStays visible through the testMultiple sizeable prints into the levelAbsorption, passive side is defending
Wall pullingDisappears before contactLittle to no volume traded into itStale level, treat prior support or resistance as void

A Worked Illustration

Picture a futures contract sitting below a level that has shown a bright resting band for several minutes. Price approaches, and three sizeable volume dots print directly into that level, yet price only advances a tick or two before rotating back several ticks, while the heatmap band stays visible throughout. That combination, repeated executed size, a level that will not concede, and a rotation back, is a textbook absorption read: aggressive buyers met a passive seller willing to hold the price. It says nothing about the next ten minutes; it only says the first test failed. The next useful piece of information is the retest itself, whether the same level gets defended again or finally gives way once the passive side runs out of size to offer.

Now compare a different scenario. A heatmap shows a wall above the day's high, but as price lifts toward it, the wall disappears within seconds and no large print ever trades into it. That is pulling, not defense, and a trader who treats the vanished wall as resistance is reacting to a level that no longer exists on the book.

What the Heatmap Does Not Tell You

The heatmap describes a moment in the order book, not a forecast. Displayed size can be canceled at any instant, so a wall that looks defended one second can be gone the next, sometimes described as spoof-like behavior, and this is one reason a heatmap read should never be the sole basis for a decision. Depth and dot size are also shaped by how a data feed aggregates trades, so identical real activity can look different across platforms, and thin overnight liquidity can make a level appear far more significant than it would during regular hours. News events are a particular hazard: heatmap history built up over the prior hour can become irrelevant within seconds once a headline changes participation and volatility.

Two further boundaries are worth holding onto. A heatmap concept is not a trade entry; recognizing absorption or a pulled wall frames a question about liquidity behavior, but a live trade still needs its own trigger, stop placement, and size limit. And a valid heatmap read has to be visible before the outcome is known. Reconstructing a clean-looking absorption story after the fact, once the final move is already obvious, teaches little about using the tool in real time. The module's practice habit reflects this directly: review recent sessions, mark moments where the observable was visible before the resolution, and record what confirmed or invalidated the read, including examples that failed. That is what turns heatmap literacy into a repeatable skill rather than pattern-matching in hindsight.

Risk disclosure. This preview is educational content from the Bookmap Heatmap module of the OptionFlow & OrderFlow Education Library. No trade signals, no buy/sell recommendations, no profit claims, no performance promises. Trading involves risk of loss, including the possible loss of all invested capital. Past patterns do not predict future results. The Education Library and the GEX Levels Indicator are sold separately.

Bookmap Heatmap in the full Library. This free preview covers the core ideas. The paid Education Library includes 30 full lessons in the Bookmap Heatmap module alone — part of 435 written lessons across 18 modules for one-time $249.99, lifetime in-site access. See the full curriculum or get the Library.

Get the full Bookmap Heatmap module.