A footprint chart breaks a price bar into rows and shows executed bid and ask volume at each price. It makes order flow easier to inspect, but it does not turn volume delta or an imbalance into a forecast.
That is the useful distinction. The display is a measurement of trades already recorded by a particular feed. Any claim about what happens next is a separate hypothesis.
What a footprint chart actually shows
A footprint chart, also called a cluster chart or Numbers Bars on some platforms, combines the bar's price range with traded volume at each price row. Sierra Chart documents bid volume, ask volume and their difference inside Numbers Bars; Quantower describes its Cluster chart as a footprint view of executed volume, buy volume and sell volume at each price (Sierra Chart: Numbers Bars, Quantower: Cluster chart).
price row bid | ask
higher sell executions | buy executions
middle sell executions | buy executions
lower sell executions | buy executionsThe usual convention assigns trades at the ask to aggressive buyers and trades at the bid to aggressive sellers. The reason is mechanical: a marketable buy order lifts the available offer, while a marketable sell order hits the bid. Both platform guides expose this bid-versus-ask classification and allow the rows to be grouped or coloured in different ways (Sierra Chart: Numbers Bars, Quantower: Cluster chart).
Delta is arithmetic, not a signal
Footprint delta is ask-traded volume minus bid-traded volume. Positive delta means more volume was classified at the ask; negative delta means more was classified at the bid. Sierra Chart offers Ask Volume minus Bid Volume fields, while Quantower defines delta as the difference between buy and sell traded volume (Sierra Chart: Numbers Bars, Quantower: Cluster chart).
delta = ask-traded volume - bid-traded volumeThat subtraction is objective once the feed and classification are fixed. Its interpretation is not. Positive delta can accompany a rising bar, a stalled bar, or a falling bar. Traders may label the last case absorption, but the chart alone cannot prove that passive sellers absorbed buying or that those sellers will remain.
An imbalance highlight is also a display rule. Platforms can compare bid and ask volume horizontally or diagonally and colour a row when a chosen relationship is met. Change the comparison method, row aggregation, or threshold and the highlighted pattern can change. A coloured stack is therefore a configured event, not a universal market object (Sierra Chart: Numbers Bars settings, Quantower: Cluster chart settings).
Footprint, DOM and order-book imbalance are different
A footprint records executed trades. A depth-of-market display shows resting liquidity currently available. cTrader defines DOM as open buy and sell orders at different prices, while footprint platforms define their clusters from trades executed at each price (cTrader: Depth of market, Quantower: Cluster chart).
This distinction matters when reading research. Cont, Kukanov and Stoikov studied order-flow imbalance built from limit orders, market orders and cancellations at the best bid and ask. Cartea, Donnelly and Jaimungal studied volume imbalance in the limit-order book. Both found short-horizon relationships with price changes or the direction of the next market order in their exchange datasets, but neither result validates every coloured footprint pattern (Cont, Kukanov and Stoikov: The Price Impact of Order Book Events, Cartea, Donnelly and Jaimungal: Enhancing Trading Strategies with Order Book Signals).
The evidence supports a narrower claim: order flow can contain short-lived information in specific limit-order-book data. It does not supply a portable entry rule, a holding period, or proof that a footprint setup survives costs.
Why the feed can change the answer
A footprint needs reliable executed-volume data and a rule for classifying trades. That is straightforward only when the venue and feed provide the necessary records. Sierra Chart says accurate Numbers Bars require tick-by-tick intraday data; Quantower's available cluster fields depend on the connected data source (Sierra Chart: Numbers Bars, Quantower: Cluster chart).
For spot FX and many CFDs, the limitation is sharper. The BIS describes global FX as an over-the-counter market, and cTrader defines Tick Volume as the count of price changes rather than shares or contracts traded (BIS: OTC foreign exchange markets, cTrader: Tick Volume). A broker feed can still be analysed, but its tick count or local liquidity is not an exchange-wide tape. Calling it a full-market footprint would overstate the data.
This is also why a footprint, Cumulative Volume Delta, Depth of Market, and Volume Profile should not be treated as interchangeable. They answer different descriptive questions.
How you'd actually test it
Start by replacing the visual story with an event a program can reproduce. Freeze the instrument, venue, data feed, timezone, bar construction, price-row aggregation, bid/ask classification, and imbalance rule before looking at results.
| Visual claim | Testable specification |
|---|---|
| Stacked buy imbalance continues upward | Define the stack, entry time, exit, stop, and maximum holding period |
| Positive delta with a down bar signals absorption | Define the delta condition, bar condition, confirmation, and invalidation without discretionary labels |
| A footprint extreme marks exhaustion | Define the extreme from prior data and compare it with matched non-extreme observations |
Then preserve event order. The rule must use only trades available when the decision would have been made. Include spread, commission, slippage and latency assumptions; a microstructure edge can be smaller than its execution friction. Split rule design from judgement with unseen data, and report every tested variant rather than only the attractive threshold. The cTrader backtest verification checklist and the data-gap audit show how to verify the engine and the feed before trusting the curve.
A stronger test also compares the setup with simple baselines: the same entry without the footprint condition, a price-only condition, and shuffled or matched events. If the extra data does not improve an out-of-sample result after costs, the chart added detail rather than edge.
realbacktesting is a trading-software studio for cTrader built around verifiable tests. Its proof standard is relevant here for one reason: a result should be reproducible in the engine and data environment that generated it.
Frequently asked
Is a footprint chart the same as Volume Profile?
No. A footprint shows executed bid and ask volume inside individual bars; Volume Profile aggregates volume by price over a selected range.
Does positive delta mean price must rise?
No. Positive delta only says more volume was classified at the ask in the chosen sample. Directional meaning must be specified and tested separately.
Can cTrader tick volume create a true footprint?
Tick Volume counts price changes, not executed contracts or shares. It can measure activity in the broker feed, but it is not the same input as exchange-reported bid and ask trade volume.
What is footprint absorption?
Absorption is an interpretation in which aggressive trading meets enough passive liquidity to stop price progressing. A footprint can suggest that pattern; it cannot identify participants or guarantee a reversal.
The stubborn takeaway
A footprint chart can make executed order flow legible. The edge, if any, begins only after the picture becomes a fixed rule tested on the same kind of data that produced it.