Fast answer
Order-book signals need venue, timestamp, depth, and execution proof.
Before using an order-book signal, record the venue, pair, timestamp, bid/ask levels, spread, depth range, wall age, cancellation risk, expected slippage, entry rule, invalidation, stop plan, and final close record. A visible wall is not a complete signal.
If the provider posts order-book screenshots without a timestamp, venue, spread, depth range, and follow-up after the wall moves or disappears, lower the evidence confidence.
Market-data checks
What to inspect in order book signals.
Venue and pair
Order books are venue-specific. A wall on one exchange may not represent total market liquidity or executable demand.
Depth and spread
Check whether the signal uses top-of-book, several price levels, full depth, or a heatmap. Spread and slippage matter before entry.
Spoofing and cancellation risk
Large visible orders can move or vanish. A signal should show how it handles wall movement, fake liquidity, and failed reads.
Complete record
The provider should preserve the original screenshot, timestamp, update trail, filled or missed entry, stop outcome, and final close note.
Source context
Market data does not replace signal proof.
Coinbase explains an order book as a list of current bids and asks for a specific asset, including prices and quantities. That market-depth context does not prove a third-party order-book signal has edge, fill quality, or reliable reporting.
Review standard
A reviewable market-data call connects source, trigger, risk, and result.
For CSR evidence review, order book signals should preserve the original alert, source link or screenshot, timestamp, symbol, venue, time frame, entry condition, invalidation, stop, target, updates, and final status. A data point is not a substitute for a verifiable track record.