Audit order-flow data before trusting a signal

Separate event time from arrival time

Exchange timestamps describe when an event occurred under the venue's clock; local arrival timestamps describe when your system received it. Network delay and batching can make simultaneous market events arrive in a different order. Use the documented event-time convention for analysis, while retaining arrival latency as a quality signal.

Record product, venue, subscription depth, trade IDs or documented sequence fields, and reconnect boundaries. Do not assume every numeric ID is consecutive unless the protocol promises that property. For order books, apply the specified snapshot/delta rules and reset state on a fresh snapshot when required. A chart continuing to animate is not proof that its underlying state is complete.

Make unavailable data visible

A missing interval should remain missing until it is repaired from a compatible source. Filling it with zeros says that no activity occurred, which is a market claim. If a constituent exchange disappears, either pause the aggregate or clearly expose the reduced coverage. Otherwise a change in data availability can look like a change in demand.

For comparisons across providers, align venue coverage, units, reset times, classification and filtering. Some feeds exclude certain order categories or publish different subsets of events. A disagreement may be explainable without either arithmetic engine being wrong. Document the explanation rather than adjusting the data until the plots look alike.

One missing sell changes the story

Use the four-trade sequence +2, −0.5, +1 and −1.8 BTC. Complete CVD is +0.7 BTC. If the final sell is lost during a reconnect, the displayed result becomes +2.5 BTC. If the +1 BTC trade is processed twice while the rest remain intact, it becomes +1.7 BTC.

Both defective series look more bullish despite originating from the same real sequence. A useful audit compares unique event counts and total unsigned volume as well as the net delta. Where backfill cannot prove completeness, annotate the interval and exclude it from signal evaluation under a rule written before seeing whether that exclusion improves results.

A provider correction can change historical signals

Historical values may change after delayed events, backfills or revised aggregation. Save the observations available at decision time when evaluating a strategy. Testing only a cleaned final history can give the strategy information that was not available live. This is especially important when very short-lived divergences supply the entry trigger.