Stacked imbalance vs single imbalance footprint: one highlighted cell vs a run of adjacent imbalances

What separates a single imbalance from a stacked imbalance

A single imbalance is one footprint cell where volume on one side outweighs the volume it is compared against by your chosen ratio. A stacked imbalance is a series of those cells on the same side, at adjacent price levels, inside the same bar. One describes a lopsided trade count at a single price level. The other describes that condition repeating across a range of neighboring prices.

What counts as either one is not fixed. Both depend on how your footprint is configured: the ratio, any minimum volume filter, the comparison method and the price row size. Two traders looking at the same ES bar can see different highlighting because their settings differ, not because the market did something different.

How a single imbalance is formed

Most footprint tools compare bid and ask volume diagonally. Ask volume at one price is compared with bid volume one row lower, because a buyer lifting the offer at 5000.25 is usually measured against sellers hitting the bid at 5000.00. If ask volume is at least, say, three times the diagonal bid volume, the ask cell is highlighted. The same logic runs in reverse for bid-side imbalances. If you want the full mechanics of that diagonal comparison, the guide to Sierra Chart diagonal imbalance settings covers it in detail.

A single highlighted cell tells you one thing: at that price row, during that bar, aggressive volume on one side was disproportionate to the comparison cell. It says nothing about the rows above or below it. On a thin row, for example 6 contracts against 2, it can be highlighted while representing very little actual trading.

How a stacked imbalance is formed

A stacked imbalance appears when imbalances on the same side line up across consecutive price rows. A common convention is three or more adjacent rows, but there is no universal standard. Some traders use two, some use four or more.

The key word is adjacent. Three ask imbalances in a bar separated by balanced rows are three single imbalances, not a stack. For a stack, every row in the run needs to meet the condition, with no gap.

The practical difference in reading:

• A single imbalance points to a price.
• A stack points to a zone, a range of prices where one side was consistently more aggressive in that bar.

Neither is a buy or sell signal. They describe what traded. Whether that zone matters later depends on context you add yourself, such as location relative to value, session high or low, or prior structure.

Side-by-side comparison

Why your settings change the display

This is where most confusion comes from. The same tape can produce a stack, a lone cell or nothing at all depending on four groups of settings.

Imbalance ratio

A 150% ratio flags far more cells than a 400% ratio. With a low ratio, stacks appear often and lose meaning. With a high ratio, singles become rare and stacks of three almost never form. When you compare charts with another trader, compare ratios first.

Minimum volume filter

Without a volume floor, rows with tiny counts can produce extreme ratios. A filter that ignores cells below a set volume removes those, which can break a stack into separate cells or remove it entirely. On ES during the regular session, a small floor may change little. Overnight, the same floor can remove most highlights.

Price row size

This is the setting that changes stacks the most. ES and NQ trade in 0.25 ticks, CL in 0.01. If each footprint row is one tick, a three-row stack on ES spans 0.75 points. If you group four ticks per row, each row is 1 point and a three-row stack spans 3 points. The grouped rows also add volume together, which can turn a broken run of single-tick imbalances into one continuous stack, or wash a strong single-tick imbalance out by combining it with balanced neighbors.

CL makes this obvious: at 0.01 per tick, one-tick rows produce very tall bars with sparse cells, so traders often group ticks. Change the grouping and the stacks move.

Data granularity

Imbalances are computed from bid and ask volume per price, which requires tick by tick data. In Sierra Chart, footprints are built with the Numbers Bars study, and Global Settings >> Data/Trade Service Settings >> Intraday Data Storage Time Unit should be set to 1 tick. If historical bars were stored at a coarser unit, their bid and ask split may be missing or approximated, and the imbalance highlighting on older bars will not match what you saw live. The Sierra Chart Tick by Tick Data Configuration page explains the requirement, and the Sierra Chart footprint tick data requirements article shows how to verify historical cells.

How to check what your footprint is highlighting

Use this routine on any Numbers Bars chart before trusting the colors.

1. Open the Numbers Bars study settings and note the imbalance-related inputs: comparison method (diagonal or horizontal), ratio and any minimum volume. Input names vary between versions, so read the labels in your own study rather than assuming. The Numbers Bars documentation describes the available options.
2. Note the price row size in the chart or study settings, then convert it to points for your instrument. One row of 4 ticks on NQ is 1 point. One row of 10 ticks on CL is 0.10.
3. Pick one highlighted cell and check the math by hand. Find the comparison cell, divide, and confirm the result meets your ratio and volume filter.
4. Check whether your setup has a dedicated stacked or consecutive imbalance option. If it does, confirm how many rows it requires. If it does not, you identify stacks visually by counting adjacent highlighted cells.
5. Change one setting at a time, such as the ratio from 300% to 200%, and watch which cells appear or disappear. This shows how fragile a given stack is.
6. Record your final settings with the chart, for example in a saved study collection, so every chart you compare uses the same rules.

If you would rather start from a configured layout and adjust from there, a Sierra Chart footprint chartbook with bid ask volume, delta and imbalance highlighting already set up gives you a baseline to test against.

Reading examples across instruments

ES: at one-tick rows, a three-row ask stack covers 0.75 points. During active hours, cells often carry hundreds of contracts, so a stack usually reflects real participation. During thin overnight trading, run the same check with a volume floor before reading much into it.

NQ: same 0.25 tick, but NQ moves through more ticks per bar. Many traders group ticks, which changes the stack count. Know your grouping before you compare NQ stacks with ES stacks.

CL: with a 0.01 tick, grouping is close to mandatory for a readable footprint, and stack behavior depends heavily on that choice.

EURUSD: spot forex has no centralized exchange volume, so a bid and ask footprint built from a broker feed is not equivalent to an exchange footprint. If you study euro order flow, the CME Euro FX futures contract (6E) provides exchange-reported trade data. CME Group's Euro FX futures page lists the contract specifications.

Conclusion

A single imbalance marks aggression at one price. A stacked imbalance marks the same aggression repeated across adjacent levels, which is why many traders treat it as a zone rather than a point. Both are products of your settings: ratio, volume filter, row size and data quality decide what gets highlighted. Before comparing charts, studying stacks or building a routine around them, verify the math on a few cells and keep your settings fixed. For the full settings walkthrough, see Sierra Chart footprint imbalance settings.

FAQ

Can a stacked imbalance span more than one bar?

By the usual definition, no. A stack is a run of adjacent imbalances within a single bar. Imbalances at similar prices in consecutive bars are separate events, though you can note them together in your review.

Is a stack of five rows more meaningful than a stack of three?

Not automatically. A longer stack covers more price, but the count also depends on row size. A five-row stack at one tick per row on ES covers less price than a three-row stack with four ticks per row.

Why do stacks disappear when I reload the chart?

Often because historical data was stored at a coarser time unit than live data, so the bid and ask split differs after reload. Confirm the Intraday Data Storage Time Unit is 1 tick and that the history was downloaded at that setting.

Should bid-side and ask-side stacks use the same ratio?

Most traders keep them symmetrical so the display is not biased toward one side. If you change one, document why and test it on replay.

Do stacked imbalances work on range or volume bars?

The calculation is the same, since it is per price row within a bar. The bar type changes how much volume each bar collects, so stacks may appear more or less often than on time bars.

If you want a footprint workspace that is ready to inspect and adjust, browse the Sierra Chart chartbooks available at SierraOnShop.