This guide compares the common resolutions used in market analysis, explains bid, ask and last prices, and shows why choosing the right data provider matters for realistic backtesting. We also distinguish the three DataPumpBridge source workflows: FreeQuotes for end-of-day prices, Interactive Brokers for second-based snapshots in our integration, and TaiPan for genuine tick-by-tick data.
What Is Tick Data?
True tick data records individual eligible market events rather than summarizing a fixed time window. A trade tick can represent an execution with a price and size; a quote tick can represent a bid or ask update without a trade. Tick frequency depends on market activity, so events are not necessarily evenly spaced.
A source that provides a price every second does not automatically provide every event that happened during that second. Several trades and quote changes can occur between two samples. Conversely, a quiet market may have no new trade in a given second.
Trade Ticks, Quote Ticks and Bid/Ask Data
Trade ticks show executed transactions; quote ticks show changes in bid and ask prices, sometimes including available size. Bid, ask and last-trade prices measure different things. Accurate execution research can require quote information and liquidity assumptions in addition to the last traded price.
Real Tick Data Compared with Time-Based Snapshots
A genuine trade-event history attempts to preserve individual recorded trade events, subject to the provider's feed filtering and coverage. A snapshot represents the market state sampled at a given time. It can be very useful for charting and analysis, but cannot reconstruct all transactions between samples.
What Are Second-Based Market Data Snapshots?
Second snapshots are observations at roughly one-second intervals or data aggregated to seconds, depending on the source and API. They offer finer time resolution than minute bars but are still not the same as a complete tick-event stream.
For example, a market could trade at 100.10, 100.40 and 100.20 inside one second. A sampled value of 100.20 does not reveal all three trades or their order. A second bar containing OHLC values would preserve more information about that second, but still not the complete intrasecond event sequence.
In the DataPumpBridge Interactive Brokers workflow, second-based snapshots are the relevant planned or implemented data granularity to describe, rather than advertising that module as a complete true-tick historical feed. This describes our product's intended behavior; it should not be read as a blanket claim that every Interactive Brokers API or market-data service is limited to snapshots.
What Is Minute Data?
Minute data summarizes eligible observations in defined intraday intervals. Standard one-minute bars typically contain open, high, low, close and volume (OHLCV). Five-minute and fifteen-minute bars use wider intervals. Providers may offer trade, bid, ask or midpoint bars, so the origin of a bar matters.
Why One-Minute OHLC Bars Cannot Reveal Event Order
Imagine a one-minute bar with open 100, high 105, low 98 and close 102. You cannot tell from those four prices whether a profit target at 104 was reached before a stop at 99. This ambiguity matters when backtesting strategies with intrabar exits.
Minute bars offer a useful compromise between storage requirements and intraday detail, but a bar is a summary rather than a recording of each transaction.
What Is Daily or End-of-Day Market Data?
End-of-day (EOD) data usually contains one row per completed trading session, with open, high, low, close and volume where available. It is widely used for daily indicators, swing trading, longer-term strategy research and portfolio evaluation.
Daily prices do not show what happened minute by minute. The market session definition also matters, particularly when comparing equities, overnight futures and adjusted stock histories. Some daily close values are settlement prices rather than the last trade.
Comparison: Tick Data vs. Second Snapshots vs. Minute and Daily Bars
| Data type | What it records | Main advantage | Main limitation |
|---|---|---|---|
| True tick data | Individual eligible trade or quote events | Highest event-level detail when the feed is complete | Large volumes, possible feed filtering, higher complexity |
| Second snapshot | Sampled or second-aggregated market observations | Fine time resolution and manageable records | Does not preserve every intervening tick |
| One-minute data | OHLCV for each minute | Useful intraday summary with moderate storage | Unknown intraminute price sequence |
| Daily EOD data | One trading-session summary | Compact history for daily strategies | No intraday price path |
Which Format Uses the Most Storage?
For a stock with a 390-minute regular trading session, one full day produces about 390 one-minute bars versus one EOD bar. At 252 illustrative trading sessions, that is about 98,280 minute bars versus 252 daily bars per symbol. Second-based observations can generate many more rows, while tick counts depend on actual market activity and feed coverage. The numbers are examples, not guarantees of record availability.
DataPumpBridge Data Sources: FreeQuotes, IB and TaiPan
The three data sources have different intended resolutions in DataPumpBridge. They should never be marketed as equivalent tick feeds.
| DataPumpBridge module | Supported market-price data category | Suitable research |
|---|---|---|
| FreeQuotes | EOD only – historical daily prices; not an intraday or tick source | Daily strategies, swing trading, historical price research |
| Interactive Brokers (IB) | Second-based snapshots in the DataPumpBridge integration; not described as genuine event-by-event tick history | Fine-grained observations where sampled data are sufficient |
| TaiPan | Real tick-by-tick data, as well as supported intraday and daily records, subject to the source's entitlements and coverage | Tick-sensitive analysis, trade/quote-event research and intraday strategies |
This comparison describes the DataPumpBridge module workflows, not all possible services or API functions offered by Yahoo Finance, Interactive Brokers or other data vendors. Coverage, permissions, bid/ask availability and historical depth depend on the relevant data source.
Which Historical Data Is Best for Your Trading Strategy?
Daily Trading Systems and Swing Strategies
For a strategy that calculates indicators after the market closes and acts at a later session, daily bars may be sufficient. Correct corporate actions, missing records and realistic execution assumptions still matter.
Intraday Systems and One-Minute Strategies
Strategies that enter or exit during the trading session typically require minute or finer data. One-minute bars can support many studies but can hide the order in which stops and targets were touched.
Event-Sensitive Strategies
If a strategy depends on individual trade events or changes in the bid/ask spread, true tick history may be required. A one-second snapshot is not a safe substitute when unobserved market events could change the outcome.
Portfolio and Multi-Asset Research
A consistent daily dataset can be more useful than high-frequency detail for portfolios rebalanced once per day. Use comparable session calendars, timestamps, corporate-action treatment and symbol histories.
What Does Bid, Ask and Last Mean?
Last is the price of an executed trade, while bid and ask refer to displayed buying and selling quotes. The difference between bid and ask is the quoted spread. These fields may arrive at different times and need not correspond to executable prices for a given order size.
Historical testing should consider commissions, slippage and liquidity, especially for shorter holding periods. A trade-price-only series can understate transaction costs. Quote snapshots help describe the market but do not guarantee a fill at the sampled price.
Can You Convert Tick Data into Minute or Daily Bars?
Often, yes: properly ordered eligible trade ticks can be aggregated into intervals to calculate open, high, low, close and volume. The chosen time zone, session boundary, price source and eligibility filters determine the results. Quote ticks require separate handling because quote changes are not trade volume.
The reverse is impossible without inventing data. A minute bar cannot recreate every historical trade inside that minute, and a second snapshot cannot reveal all ticks that occurred between samples.
Historical Market Data Quality and Backtesting Pitfalls
- Event loss: snapshots and aggregated bars omit information that an event-level feed might contain.
- Wrong price field: confusing bid, ask, midpoint and last trade creates inconsistent signals.
- Time-zone errors: daylight-saving changes and session boundaries can shift bars.
- Missing or duplicate records: downloads require validation and stable unique keys.
- Split adjustments: daily adjusted history may differ from raw intraday trades.
- Look-ahead bias: the complete interval bar is not known until the interval closes.
- Provider limitations: historical depth, request quotas and exchange permissions vary.
Clean and well-defined historical data are more important than choosing the largest possible dataset.
Local SQLite Storage and Incremental Downloads
A local SQLite database can preserve acquired daily, minute, sampled or tick observations separately from charting software. Each record should retain its provider, instrument, time frame, timestamp and price type. Separate tables or carefully constructed keys prevent accidental mixing of data categories.
Incremental updates can reduce repeated downloads by requesting only new or missing periods when the provider supports them. Historical corrections still require reconciliation, and exported CSV/ASCII files need duplicate-safe append procedures rather than indiscriminate overwriting.
Market Data in DataPumpBridge: With or Without NeuroShell Trader
DataPumpBridge for NeuroShell Trader integrates supported historical data into the charting platform while maintaining independent local SQLite history. DataPumpBridge Data Downloader is a separate application for users who do not need NeuroShell Trader; it focuses on local data acquisition and CSV/ASCII export.
Each application includes the three provider modules—FreeQuotes (EOD), Interactive Brokers (second snapshots) and TaiPan (real tick data)—under one application license. The included module does not include external provider subscriptions or exchange market-data rights.
Both applications use the same annual price and can be tested for 14 days. Purchase, PayPal payment and license activation take place within the installed software, not through website checkout. See Prices and Licensing for details.
Frequently Asked Questions
Is a one-second snapshot the same as true tick data?
No. A snapshot samples market information at a point in time or aggregates it to an interval. True tick data records individual eligible trade or quote events and may contain multiple events within a second.
Does DataPumpBridge FreeQuotes provide intraday or tick prices?
No. The FreeQuotes market-price workflow provides historical end-of-day prices, not second, minute or real tick data.
Does the DataPumpBridge IB module provide true historical tick events?
It is described here as providing second-based snapshots. That is not the same as preserving every individual market event; other Interactive Brokers services may have different capabilities.
Which DataPumpBridge source supports genuine tick data?
TaiPan is the source for real tick-by-tick market-data workflows, depending on feed availability, permissions and historical coverage.
Are minute bars enough for backtesting?
They may be enough for strategies whose signals and execution assumptions tolerate minute-level detail. They are insufficient to identify the exact sequence of individual events inside a minute.
Can I produce CSV files without NeuroShell Trader?
Yes. The standalone Data Downloader application is intended for local historical storage and CSV/ASCII export without requiring NeuroShell Trader.