Using Volume Profile with a Bookmap Liquidity Heatmap
Volume Profile and the liquidity heatmap answer different questions. Using them together works best when you preserve that distinction instead of treating every bright band and high-volume node as the same thing.
Volume Profile shows where trading occurred
Volume Profile organizes executed volume by price over a selected period. It helps identify where the market spent and transacted the most volume, rather than where limit orders were merely displayed. Common reference points include the Point of Control (POC), value-area boundaries, High Volume Nodes (HVNs), and Low Volume Nodes (LVNs).
These are historical execution references. They can describe areas of prior acceptance or lower participation, but they do not reveal the current state of the order book by themselves.
The heatmap shows resting liquidity through time
Bookmap’s heatmap focuses on displayed limit-order liquidity. Brighter bands indicate larger concentrations of resting orders, and the time dimension shows whether those orders persisted, migrated, pulled, or were consumed. That is a different measurement from Volume Profile.
Keeping the measurements separate prevents a common analytical error: assuming a high-volume node and a bright liquidity band are interchangeable. They can overlap, but one describes completed transactions and the other describes displayed passive interest.
Confluence: when history and current liquidity overlap
A useful confluence occurs when a meaningful historical volume area is close to persistent current liquidity and price is approaching with clear structure. The overlap creates a location worth observing because both prior execution and current order-book behavior are concentrated nearby.
Confluence still needs live confirmation. Watch whether the liquidity holds or pulls, whether aggressive orders increase, and whether price is rejected or accepted through the area. The overlap is a context filter, not a promise that the level will hold.
Conflict: when the two layers disagree
Conflict can be equally informative. A prior HVN may sit in an area where current liquidity has become thin. A bright current wall may appear in a price zone with little historical traded volume. An LVN may offer a low-participation path, but new resting liquidity can change that path before price arrives.
Rather than forcing the layers to agree, record which one is current and which one is historical. Then let execution and price response determine whether the old profile remains relevant.
POC, value area, HVN, and LVN in practice
- POC: the price with the greatest executed volume in the selected profile.
- Value area: the range containing the chosen percentage of profile volume, depending on platform settings.
- HVN: a concentration of traded volume that can reflect prior acceptance.
- LVN: a lower-volume area that can reflect faster auctioning or lower historical acceptance.
These labels are useful references, but their relevance depends on the profile window. A session profile, composite profile, or short intraday profile can produce different levels. Always document which window you used.
Add footprint and CVD at the test
When price reaches a profile/heatmap area, footprint-style execution and CVD can show how aggressively participants are trading into it. Strong buying into persistent offers with poor upward progress has a different meaning from strong buying that consumes the offers and accepts above them.
The best analysis keeps all three dimensions separate: historical executed volume, current displayed liquidity, and live aggressive execution. The relationship among them is the evidence.
A repeatable profile + heatmap workflow
- Choose the profile window before the test.
- Mark POC, value-area edges, major HVNs, and meaningful LVNs.
- Overlay the nearest persistent heatmap liquidity and structural levels.
- Watch how liquidity changes as price approaches.
- Record footprint/delta/CVD behavior at the test.
- Classify the result as rejection, acceptance, or unresolved and define invalidation.
KS8 Pro groups these layers into one advisory workflow so the analyst can compare context without assuming any single layer is sufficient.