Funding ticks are the raw, tick-by-tick price updates your prop firm uses to trigger stop losses, calculate drawdown, and execute market orders. Most retail traders never think about them. But in a funded account, where limits are calculated to the decimal and a single bad fill can be the difference between passing and failing a challenge, tick-level precision is not a detail. It's the foundation.
This guide explains what tick data is, why the quality of tick data varies between firms, and what it means for your strategy, your stop losses, and your challenge pass rate.
What Is a Tick?
A tick is a single price update. Every time a transaction occurs at a new price on an exchange, that's a tick. In a liquid market like BTC/USD, ticks arrive many times per second. In a quiet period, they might come every few seconds. But they never stop while the market is open.
For crypto, which trades 24/7, tick data is a continuous, never-ending stream of price updates from the exchange.
The distinction between a tick and a candle is critical. A 1-minute candle shows you 4 data points: open, high, low, close. It tells you the range of the minute and where price ended. But it hides everything that happened in between. If price spiked to the high at second 5 and then spent the rest of the minute recovering, the candle shows you the outcome, not the journey.
Tick data shows you the journey.
Aggregated Feeds vs Tick-by-Tick Data
This is where prop traders get caught out. Not all firms feed you the same data.
| Data type | What you see | What you miss | Risk to funded account |
|---|---|---|---|
| Aggregated (1-min candles) | OHLC per minute | Every price update inside the candle | May not show wicks that hit your stop |
| Bar/OHLCV (seconds) | OHLC per second | Sub-second price movements | Misses fast spikes in volatile markets |
| Tick data | Every price update | Nothing | Most accurate representation of execution |
| Institutional tick data | Every update with volume | Nothing | Full picture including order flow |
The gap between aggregated and tick-level data sounds technical. The consequences are practical.
The Wick Problem
Imagine Bitcoin is trading at $65,000. In one second, a large sell order hits the book, price drops to $64,700, and then buyers absorb it and price snaps back to $64,950 within the same second.
On a 1-minute candle: you see a wick on the low. If the wick reached below your stop at $64,800, your stop triggered, even though price was back above it almost immediately.
On a tick feed: you see every update. You know exactly what happened, in what sequence, and at what price your order executed.
The problem for prop traders isn't losing money on a stop. Stops are risk management. The problem is when your live execution is based on one data stream and your strategy was backtested on another. The wick that hit your stop in live trading might not appear on the backtest data you used to build the strategy. Your system looks clean in testing and fails in live.
This discrepancy is one of the most common sources of unexpected challenge failures among algorithmic traders.
Why Tick Data Quality Matters in a Prop Challenge
In a prop challenge, you're operating with hard limits: a daily loss cap and a max drawdown. These limits are calculated in real time against your actual equity, including floating P&L from open positions.
That means if price moves against you by 1 tick beyond your theoretical limit, the account breaches, even if it recovers immediately after. The precision of the tick data that your prop firm uses to calculate your drawdown determines exactly how tight that margin is.
There are three specific ways this affects challenge traders.
Stop loss execution. Your stop loss is triggered based on the price feed the platform receives. If the platform uses tick-level data from the exchange, your stop executes at the actual price the exchange reported. If the platform uses aggregated or delayed data, there may be discrepancies between what you see and what triggers your orders.
Drawdown calculation. Some prop firms calculate your max drawdown based on closed P&L only. Others, including Velotrade, calculate it based on floating equity. If your drawdown is calculated against live equity, the tick-level accuracy of your price feed matters for every open position. A 10-tick adverse move on a large position can push your floating equity closer to the limit than your closed P&L suggests.
Spread during volatility. In fast-moving markets, the spread between bid and ask widens. Aggregated data may show you a mid-price that doesn't reflect the actual spread at the moment your order executes. Tick data shows you the true bid and ask at every point in time. If you're entering during a news event, the difference between theoretical mid and actual fill can be significant.
How Different Trading Styles Are Affected
Tick data quality doesn't matter equally for all strategies. Here's how it breaks down by style.
Scalpers. This is where tick data matters most. Scalpers target moves of a few ticks to a few dozen ticks. If your data feed is missing intermediate price updates or your fills are based on aggregated prices, slippage at your scale eats the strategy entirely. Tick-level data and low-latency execution are not optional for scalping. They're the minimum requirement.
Algo/bot traders. If your system was backtested on tick data but runs in live on aggregated data, you're trading a different strategy than you think. The two data sets produce different signal timing, different entry/exit points, and different performance profiles. Always match your backtest data source to your live execution environment.
Swing traders. Less affected on a per-trade basis, but still relevant for stop placement. If you're placing stops at technical levels and your firm's data shows wicks that your charting platform doesn't, stops get hit on noise that your analysis didn't account for.
News traders. High impact. During a major announcement, BTC/USD can move 1-2% in under a second. The spread explodes. The tick stream captures this chaos precisely. An aggregated feed may show a smooth candle that masks 50 milliseconds of extreme volatility. If you're trading news events, you need to understand exactly what your execution environment looks like at the tick level during those periods.
Trading on a firm that uses institutional-grade data? Start your Velotrade challenge →
How Velotrade Handles Tick Data
Velotrade's trading infrastructure is built on institutional-grade connectivity. This affects tick data quality at 3 specific levels.
No phantom wicks. We don't manipulate price feeds. What you see on the chart is what executed across the exchange connection. The data feed is a direct representation of the market, not a smoothed or adjusted version of it.
High-frequency support. Scalpers need to see every tick. Our infrastructure supports high-frequency strategies that rely on capturing micro-movements. The latency between a tick arriving and your order filling is minimized at the infrastructure level.
Consistent data for drawdown calculation. The same price feed that drives your chart drives the drawdown calculation. There's no discrepancy between what you see and what the risk system tracks. This matters particularly for floating equity drawdown, where you need to know in real time how close you are to your limit.
How to Use Tick Data to Prepare for a Prop Challenge
You don't need to become a data engineer to benefit from tick-level thinking. These practical steps apply to any prop trader.
1. Backtest with tick data, not candle data. If your broker or data provider offers tick history, use it. The difference in strategy performance between tick-level and candle-level backtests is often substantial, especially for short-term strategies. Tools like TradingView, MetaTrader 5, and dedicated algo platforms all support tick-level backtesting.
2. Watch the spread in live markets. Open your platform during a high-volatility period, like a CPI announcement or a major crypto news event. Watch the bid-ask spread in real time. See how wide it gets and how quickly it narrows. This is what your fills look like during news events. Understand it before it costs you.
3. Compare your live performance to your backtest across the first 2 weeks. The first 2 weeks of any live or challenge account are a calibration period. If your live results differ significantly from backtest expectations, the data feed discrepancy may be part of the explanation. Look at which trades underperformed and whether they were active during high-volatility moments.
4. Understand where your drawdown limit sits in tick terms. On a $50,000 account with a 5% daily loss limit, you have $2,500 of daily loss allowance. For BTC/USD at $65,000 trading 1 BTC, a 384-tick adverse move (roughly 0.6%) on a full position reaches that limit. Know the tick distance to your limit before entering.
5. Choose the right firm for your strategy. Avoid prop firms that use simulated ticks that don't match live market conditions. A simulated tick feed is designed to pass certain statistical tests while deviating from real market microstructure. It will make your backtest look cleaner than your live results deserve.
For more on the rule mechanics that affect how your drawdown is calculated and tracked, see crypto prop firm rules explained. For a comparison of how different firms approach data and execution, see best crypto prop firms 2026. Tick data discrepancies are also one of the main reasons traders fail challenges unexpectedly — see why traders fail prop challenges and the full guide to passing a 2-step crypto prop challenge for how to prepare.
Ready to trade with institutional-grade data? Start your challenge →
This article is for informational purposes only and does not constitute financial or investment advice.
Frequently Asked Questions
About the author
Vittorio De Angelis
Executive Chairman
Former equity-derivatives trader at JP Morgan, Dresdner Kleinwort and Bank of America in London. Later Head of Brokerage at a global broker in Hong Kong.
View author page
