Tick-by-tick data is market data that records individual reported events within a feed’s coverage rather than summarizing activity over fixed time intervals. These may be trades, updates to quoted buying and selling prices, or changes to an order book—a record of buy and sell orders. Event-level detail does not imply coverage of every event from every trading venue.
Records and Timestamps
A feed records each reported execution individually, with price, quantity when supplied and feed-defined timestamps. Check record types and indicators: displayed rows can instead be quotes or other non-trade price observations.
A timestamp identifies a feed-defined point in the event’s lifecycle. It may mark the market event, the venue’s sending time or receipt by a data-capture server; even an exchange timestamp need not mean execution time. Timestamp resolution is the smallest time unit represented. Nanosecond resolution alone establishes neither nanosecond accuracy nor low delivery delay.
Trades, Quotes and Order-Book Data
Trade ticks report executions, not offers to trade. Quotes describe bids, or buying prices, and asks, or selling prices, together with available quantities where supplied. Quoted quantity is not executed volume. Order-book events describe additions, cancellations or modifications to the buy and sell orders represented by the feed, either individually or grouped by price. Trade ticks alone cannot reconstruct that book.
For currency markets, tick-by-tick data may describe provider- or account-specific price observations rather than market-wide transactions. Some currency streams, however, are sampled rather than event-by-event: when several prices occur within a sampling window, only the price in effect at its end is sent, omitting intermediate changes. Differently aligned sampling windows can also cause subscribers to observe different prices during rapid movement.
Cash-index observations instead may be calculated benchmark values. An index feed carries the calculated value in an index-value message, rather than a report that someone traded the index. Even bid/ask-labelled index values can be calculated rather than executable quotes; they differ from trades in index-linked futures or funds.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedHistorical and Real-Time Delivery
Tick-by-tick data can be delivered live or retrieved historically. “Real time” concerns delivery timing, while “tick-by-tick” concerns granularity: streaming alone does not establish event-level detail, since a live service may send sampled prices or aggregated snapshots.
| Criteria | Real-time tick data | Historical intraday tick data |
|---|---|---|
| Access routes | Real-time tick dataLive feeds through APIs or platforms; subscriptions and permissions may apply | Historical intraday tick dataHistorical records through APIs or platforms, including batch downloads |
Aggregation and Research Uses
A fixed-interval OHLCV bar summarizes opening, highest, lowest and closing prices plus total traded volume. It does not preserve the full sequence of trades, their individual sizes or their timing within the interval.
In a hypothetical minute, four one-unit trades occur at 100, 101, 99 and 100. Another minute containing the sequence 100, 99, 101 and 100 has the same OHLCV values, including volume of four units, but the high and low occur in the opposite order. Tick-by-tick data preserves that distinction when those events are retained.
That detail supports market microstructure research—the study of how orders, quotes and trades interact—and execution analysis or backtesting. Quote events can also reveal changing spreads, the difference between bid and ask prices. Historical observations still require assumptions about order timing, available liquidity and slippage, the difference between expected and actual execution prices. They do not prove that a hypothetical order would have filled or that a strategy will be profitable.
| Feature | Benefit | Use case |
|---|---|---|
| Trade records | BenefitPreserves individual reported executions within feed coverage | Use caseMarket microstructure and execution-algorithm analysis |
| Price and time | BenefitRecords execution price and feed-defined timestamps; resolution is not accuracy | Use caseStudy small price changes and event timing |
| Trade size | BenefitReports executed quantity when supplied, not quoted liquidity | Use caseExamine per-trade size and volume bursts |
| Live feed | BenefitDelivers ongoing data; sampling and coverage still need checking | Use caseMonitor activity and inform execution decisions |
| Historical records | BenefitPreserves past event detail for research | Use caseBacktest short-horizon strategies with fill and slippage assumptions |
Coverage and Data Handling
Before using tick-by-tick data, check the instruments, venues, event types and fields represented, as well as sampling rules and omissions. Event datasets are available for equities and futures, including commodity and currency futures. Even an unsampled order-book (market-depth) feed can exclude some orders. Historical trade records may contain late insertions, cancellations of erroneous reports or corrections to price and quantity; these affect interpretation of the event sequence. A book-update feed changes a stored view of bids and offers. In IBKR’s documented market-depth feed, a reset message tells the receiver to empty that stored book before applying new entries: the new entries build a fresh book, rather than continue updating the earlier one.
Large historical datasets require storage and processing capacity even when accessed through cloud services or APIs. Compression and incremental processing—reading manageable portions rather than loading everything at once—can reduce resource demands where supported.