How to Backtest on Bookmap: Replay Mode Setup and Strategy Guide
Bookmap Replay lets you examine a recorded market session and practice decisions against the data it contains. It is useful for reviewing order flow, but a visual replay is not automatically a statistical backtest or a reconstruction of every hidden order.
Check the Data Before the Replay
Record the instrument, venue, session, feed and available depth. A replay cannot show messages that were never captured. Market depth, executed trades and your own order history are different data categories.
Bookmap's file documentation distinguishes feed files from order files and documents recording through REC or File → Record. Obtain a compatible recording and confirm its coverage before planning the test. Do not assume every date is available, or that all compatible data must have been recorded personally on your computer.
Open and Inspect a Replay
- Start Bookmap in Replay mode and load the intended compatible feed file.
- Check the instrument and timestamp before advancing the session.
- Confirm that the heatmap and trade data are present over the period you need.
- If reviewing your own recorded orders, load the corresponding order data as supported by the application.
- Test playback and pause controls on a short segment before beginning the evaluation.
Review current version and add-on requirements if a tool does not load. Historical chart backfill and a complete replay recording are not interchangeable guarantees.
Write the Rule Before Viewing the Outcome
For a hypothetical liquidity-retest exercise, define the price zone, required observation, entry trigger, invalidation and exit before continuing playback. Record when each condition becomes visible. A rule that uses information still forming at that moment is not necessarily biased; using a later-known outcome as if it were already available is.
Repeat the rule on sessions you did not use to choose it. Replaying the same memorable event until the entries look good is practice on a known outcome, not independent validation.
Interpret Order-Flow Evidence Carefully
| Observation | What it supports | What it does not establish alone |
|---|---|---|
| Displayed liquidity | Orders visible in the captured feed | All hidden interest or participant identity |
| A trade print | An execution represented in the data | The trader's motive or future direction |
| Order cancellation | Displayed interest was removed | Proof of spoofing or unlawful intent |
| A heatmap change | A change in displayed depth | A guaranteed support or resistance level |
The data can help explain market behavior, but explanations remain hypotheses unless separately supported. Avoid converting a visual pattern into a claim that you identified a specific institution.
Simulation Is Not a Live Fill
Bookmap's trading documentation describes trading and recorded order review. Confirm that your selected mode and account are simulated before practicing. Queue position, latency, partial fills and market impact can make live outcomes differ from a replay exercise.
Record commissions and assumed slippage separately where the simulator does not include them. A replay that shows a touched price does not prove your entire order would have filled there.
Keep a Reproducible Journal
Save the recording reference, source coverage, platform version, rule version, timestamps, hypothetical orders and outcome. Preserve rejected setups and losing examples. If a result depends on an add-on, record its version and settings too.
| Journal field | Example format |
|---|---|
| Session | Instrument, venue, date and timezone |
| Setup | Written condition and observation timestamp |
| Execution assumption | Order type, size, costs and fill model |
| Result | Simulated P/L and any unfilled quantity |
| Review | Whether the rule was followed and what remains uncertain |
This is a suggested record format, not a completed trading experiment.
Moving a Hypothesis to TradingView
Pineify can help turn a price-based rule into Pine Script, but do not assume it can import and reproduce Bookmap's proprietary depth feed or every order-flow condition. First confirm that the required data exists in the target environment. If it does not, changing the rule to available bar data creates a different test.
Do I need a compatible recording?
Yes. Verify the source, format and coverage before replaying. A chart's visible history does not prove that a complete order-book replay file exists.
Does replay reveal every hidden order?
No. Its evidence is limited by the feed and any supported analysis tools. Displayed depth alone does not identify all hidden liquidity or participant intent.
Is a replay result proof of a profitable strategy?
No. Evaluate unseen sessions, realistic execution assumptions and the complete set of qualifying trades. Keep simulated and live outcomes separate.