Give each panel one job.
A useful order-flow workspace separates price, executed trades, liquidation events and resting liquidity. They can describe the same asset without representing the same activity. The example below is a layout exercise; no order is submitted and the figures are hypothetical.
| Panel | Job in this example |
|---|---|
| Main chart | Keep price and the selected trading account visible. |
| Ticker Trades | Follow the current asset across selected public venues. |
| Liquidations | Keep a saved local record of reported liquidation events for a chosen asset. |
| Heatmap Chart in Analytics | Inspect recorded resting depth alongside candle context. |
Choose Default for the general trading arrangement or Order Flow for the layout with Liquidations and Ticker Trades. Both can be resized and saved. Analytics has its own arrangement rather than replacing your Trade layout.
Decide whether the tape should follow you.
Add Trades when you want BTC to stay visible while you browse other markets. Add Ticker Trades when you want the tape to follow the selected asset. If you switch the trading ticker from BTCUSDT to ETHUSDT, Ticker Trades selects ETH; Trades continues showing BTC.
The asset link does not restrict the tape to the exchange selected for trading. For example, an ETH ticker can be paired with public ETH prints from several selected sources. Check source status in the module settings because not every source lists every asset.
Use units that make the filter interpretable.
For a hypothetical BTC print at 50,000 USD, a size of 2 BTC has a notional value of 100,000 USD. A minimum notional filter of 100,000 would include that print. A 0.2 BTC print at the same price has 10,000 USD notional and would be hidden.
Schizo’s approximate USD display treats USDT and USDC as $1. It does not make prices or instruments identical across venues. Coin units help compare asset quantity; approximate USD helps compare notional size. Choose the display that matches the question.
A size filter controls what is displayed; it is not a promise to stop receiving smaller trades from an exchange. To reduce active feed work, deselect sources you do not need or pause the instance.
Know the difference between scrolling, leaving and pausing.
| Action | Result |
|---|---|
| Scroll a Trade Liquidations module out of view | It keeps recording reported events while deployed and unpaused. |
| Leave Analytics for Trade | Analytics modules unload and release their subscriptions. |
| Pause Trades, Ticker Trades or Liquidations | That instance releases its feeds; the paused setting survives refresh. |
| Refresh a Liquidations module | Its saved local rows can be restored within the retention limits. |
| Resume after a pause | New events resume; missed events are not reconstructed. |
Liquidations retains the newest 3,000 saved events within seven days. A second unpaused module can still need a shared source, so pausing one panel need not close every connection used elsewhere in the workspace.
Keep heatmap history honest.
Open Analytics, add Heatmap Chart, choose an asset and select a small source set. SD and HD are both available; the difference is price grouping. Use the profile and depth lens to inspect the recorded quantities rather than relying only on colour intensity.
The heatmap starts from live books and any local history already saved for that configuration. It cannot fill an earlier gap from price candles. Resting orders can change or be cancelled, and a liquidation feed is a record of reported events rather than a map of every hidden trigger.
Return to Journal for your own derivatives executions and review. Public tape activity is market context, not your personal fills.