Depth of Market trading reads the resting buy and sell interest displayed at different prices. It can reveal the shape of the visible queue right now. It cannot tell you that the queue will remain there, that hidden liquidity does not exist, or that the next price move is settled.
That is the useful tension in the DOM: it is closer to the auction than a candle, but it is still only a partial, fast-changing view of the auction.
What Depth of Market actually shows
Depth of Market, or DOM, is a price ladder of displayed buy and sell liquidity. cTrader describes it as open buy and sell orders at different prices; its Algo interface exposes bid and ask entries with their price and volume and emits an event when depth changes (cTrader DOM guide, cTrader MarketDepth API).
On a central limit order book, a limit order rests until it trades, is modified or is cancelled. Price determines which quote is better; within a price level, the venue's matching rules determine queue priority. CME's explanation of exchange limit orders and the SEC's description of order-based and level-book feeds both make the distinction between displayed orders, executions, modifications and cancellations explicit (CME on limit orders, SEC on order-book reporting).
Offers / asks resting sell interest above the market
---------------- best ask
Spread no resting quote between best ask and best bid
---------------- best bid
Bids resting buy interest below the marketThe ladder is a snapshot of displayed interest, not a ledger of every trading intention. The SEC documents both hidden exchange orders and trading away from displayed venues; cTrader separately notes that a symbol's pricing depends on the broker and its liquidity providers (SEC hidden-volume data, cTrader markets guide).
How traders read the queue
A DOM method normally watches change rather than one static wall. The useful observations are mechanical:
| Observation | What it establishes | What it does not establish |
|---|---|---|
| Bid size is larger than ask size near the top | The displayed near-side book is imbalanced | That price must rise |
| An ask level repeatedly refreshes after trades | Displayed supply keeps reappearing | The identity or total inventory of the seller |
| A level disappears before trading | Liquidity was cancelled or moved | Why it was removed |
| Several levels thin at once | Less displayed size stands between price and a move | The size of hidden or off-venue liquidity |
| A market order consumes a level | Aggressive flow traded through resting size | That the move will continue |
This produces three common families of rules. Imbalance rules compare bid and ask queues. Absorption rules look for repeated aggressive trades without the expected price progress. Liquidity-withdrawal rules watch resting size vanish ahead of price. None is complete without an exact sampling window, entry trigger, fill model and exit.
The nearby Cumulative Volume Delta explainer covers executed aggressive flow. DOM is different: it focuses on resting interest and its updates. Putting the two together may form a hypothesis, but it still does not turn either measure into a signal by declaration.
Why a large order is not a promise
Displayed orders can be cancelled legitimately as conditions change. They can also be entered with abusive intent. The legal distinction is intent: CME Rule 575 and the CFTC's interpretive guidance define spoofing around bidding or offering with an intent to cancel before execution, while explicitly separating that from good-faith cancellation or modification (CME Rule 575 advisory, CFTC anti-spoofing guidance).
That matters for interpretation. A wall that disappears is not, by itself, proof of spoofing. A wall that stays is not, by itself, proof of support. The DOM shows order-book events; it does not expose the participant's motive.
Hidden liquidity creates a second limit. The SEC's market-structure work shows that undisplayed orders can execute on exchanges and that off-exchange venues do not typically display resting orders. The SEC order-feed description also distinguishes displayed orders from orders marked hidden (SEC hidden-volume data, SEC on order-book reporting). Visible depth is therefore not synonymous with total available liquidity.
What the evidence supports
There is credible evidence that order-book imbalance contains information at very short horizons. Cont, Kukanov and Stoikov found a relationship between order-flow imbalance and short-interval price changes in U.S. equities. Lipton, Pesavento and Sotiropoulos separately linked top-of-book quote imbalance to the probability and timing of the next market event in their sample (Cont, Kukanov and Stoikov, Lipton, Pesavento and Sotiropoulos).
The careful conclusion is smaller than the trading folklore. Those papers study particular electronic order books, variables and short horizons. They support testing queue imbalance as an explanatory feature. They do not establish that any visual DOM pattern has portable positive expectancy after spread, fees, latency and adverse selection.
The distinction between statistical association and tradable edge is especially important here. A feature may help predict the next quote change yet still lose money if the expected move is smaller than the cost of entering and exiting. It may also decay before a retail order reaches the market.
The FX and CFD caveat
A retail FX or CFD DOM is not a consolidated map of the global currency market. BIS research describes spot FX as over-the-counter, fragmented across venues and partly opaque. cTrader states that symbol pricing varies by broker and depends on its liquidity providers and trading conditions (BIS review of the FX market, cTrader markets guide).
So a cTrader DOM can be a valid view of executable liquidity made available to that account through that broker. It should not be relabelled as the whole market. A rule developed on one feed may change when the broker, liquidity mix, account type or symbol changes.
How you'd actually test it
Do not backtest a screenshot pattern. Test a time-ordered event rule.
- Record every depth update with its timestamp, side, price and displayed volume, plus trades or quote changes needed to label what happened next.
- Define the feature before looking at results: levels included, aggregation method, sampling frequency, minimum persistence and treatment of cancelled orders.
- Define the decision time. The rule may use only depth events already received, never the completed sequence that became obvious later.
- Model queue position for passive orders and latency for all orders. A touch at your limit price does not prove your order was filled.
- Charge spread, commission and slippage. Compare the expected move with the round-trip cost, not with zero.
- Separate development from out-of-sample evaluation. Re-test across sessions, volatility regimes, symbols and, for FX/CFDs, broker feeds.
- Compare against simple baselines: no DOM filter, top-of-book imbalance alone, and a rule using only price and executed flow.
- Report expectancy, drawdown, fill rate, adverse movement after fills and sensitivity to small parameter changes. Include the intervals when the book changed too quickly to act.
cTrader's API provides depth entries and update events, which makes event capture possible, but the historical test still needs data you actually recorded (cTrader MarketDepth API, cTrader DOM guide). The pending-order backtesting guide explains why a touched price is not automatically a fill, while the intrabar backtesting guide covers the timing error hidden by completed bars.
realbacktesting is a trading-software studio for cTrader built around reproducible tests. Applied to DOM trading, the proof standard is blunt: another tester should be able to rebuild the queue state, the decision and the fill from the same event data.
Frequently asked
Does a large bid mean price will rise?
No. It means a large bid is displayed at that moment. The order can trade, move or cancel, while hidden and off-venue liquidity remains outside the visible ladder (CME Rule 575 advisory, SEC hidden-volume data).
Is cTrader DOM the whole FX order book?
No. Spot FX is fragmented and over-the-counter, and cTrader pricing depends on the broker's liquidity providers and conditions (BIS review of the FX market, cTrader markets guide).
Can DOM trading be backtested?
Yes, if the test has historical, time-stamped depth events and an honest queue and fill model. Completed candles cannot reconstruct orders that appeared, moved and vanished inside the bar (cTrader MarketDepth API, intrabar backtesting guide).
Takeaway
The DOM can show where displayed liquidity is leaning. Only recorded events, realistic fills and unseen data can show whether that lean was worth trading.