ATAS displays executed volume by price and trade category when the connected feed supports it. This does not identify the individual people behind every trade or show all global liquidity. Decide what data your analysis needs before comparing platform and feed costs.

What ATAS actually does

ATAS is a specialist terminal for order flow and volume analysis. A footprint can separate executed contracts by price and Bid/Ask category when its feed supports that information. Each trade still has a buyer and seller: the categories describe execution activity, not the identities or net positions of all participants. Compare the dataset and calculation before interpreting a coloured cell.

A cluster chart displays activity inside a candle. Volume Profile groups executed volume by price over a selected interval; POC is the highest-volume level under that grouping. Session boundaries, price bins and Value Area settings matter. DOM and a heatmap instead describe available orders and their changes; visible liquidity can be cancelled. Icebergs Tracker requires MBO data and order IDs, and distinguishes native-refresh confirmation from detection by indirect signs. It cannot reveal every hidden intention from an unsupported feed.

A mean percentage is not total-volume delta

Similar percentages can hide very different contract volumes. Preserve each numerator and denominator before combining two candles.

Scroll sideways to see the full diagram

A mean percentage is not total-volume deltaTwo fictional candles of the same contract and feed, with no time overlap. A: Ask 90, Bid 10, delta +80 out of 100 contracts, or +80%. B: Ask 100, Bid 900, delta -800 out of 1,000, or -80%. Stacked horizontal bars share a volume scale: 1,000 contracts takes ten times the space of 100. The mean percentage is zero, but total delta -720 out of 1,100 is about -65.45%. This does not measure trader counts or forecast price direction. Purple means Ask; ochre means Bid.PERCENTAGES NEED WEIGHTSTwo fictional candles; one contract and feed.A: Ask 90 / Bid 10 contractsDelta +80; share +80%B: Ask 100 / Bid 900 contractsDelta -800; share -80%05001,000Contract volume: common scaleMean share: (+80 - 80) / 2 = 0%Total: -720 / 1,100 = -65.45%Purple: Ask / Ochre: Bid

Assumptions: Two separate fictional candles of one contract; units are contracts. A has executed Ask volume 90 and Bid 10; B has 100 and 900. Each execution belongs to exactly one category; there are no unclassified volumes, missing data or duplicates. Ask/Bid are executed-trade categories, not resting DOM quotes.

Our share is (Ask - Bid) / (Ask + Bid) x 100%. A has +80%, B has -80%. Their mean is zero because each candle receives equal weight. Summing contracts instead gives Ask = 190, Bid = 910, volume = 1,100 and delta = -720. The whole-sample share is approximately -65.45%.

Both calculations are mathematically correct but answer different questions: the mean indicator value per candle and delta's share of total executed volume. ATAS Cluster Statistics distinguishes delta, Delta/Volume and session equivalents. Our counterexample does not reproduce the program's session configuration or filters.

Export delta and volume separately, not just the percentage. A negative share here does not imply more individual sellers, their final positions or a price-decline forecast.

Opposite percentages do not cancel total delta when volumes differ.

What data feed you need for ATAS to make sense

Check the exact provider, venue, instrument, data entitlement and execution permission. A chart connection is not automatically permission to trade. The documented ATAS–MT5 route supports selected brokers and needs a running MT5 terminal, its OFT component and the required settings. It processes the completed previous second of ticks, requesting them about 200 ms into the next second. OCO through this connector is simulated locally: after disconnection, execution of one linked order does not automatically cancel the other. This is a connector-specific limitation.

For a broker feed, establish whether the displayed measure is executed volume or quote activity. An A-book/B-book label does not make local data a global OTC transaction tape. A separately identified exchange contract can provide a different observation, but its venue, expiry, units and price basis must remain distinct from spot or CFDs. The guide to tick volume explains that distinction; it does not make one dataset a substitute for every other market.

Pricing and what you really get

Choose the instrument and data mode before choosing the plan. Start and Plus list a 15-minute futures delay and do not allow connecting futures in real time; Pro and Ultra allow real-time futures connections. Entitlement to connect is separate from the cost and terms of an exchange feed.

The free Start plan has limits on connections and analysis tools; paid plans alter those limits. The vendor offers several subscription periods and Lifetime access, with current conditions on the ATAS pricing page. Check the selected period, taxes, trial renewal and cancellation rather than treating an advertised monthly equivalent as a monthly invoice. ATAS X and some modules are marked beta; their availability and dependencies require separate checking.

Separate recurring software and market-data charges from trading commissions, account fees and capital posted as margin. A refundable deposit is not a monthly software expense. A free terminal also does not make brokerage trading cost zero or establish sufficient execution liquidity for every strategy.

ATAS versus TradingView and NinjaTrader

Compare the exact product version, plan and method. TradingView offers Volume Footprint, but its documentation classifies volume using intrabar price direction and can use coarser intervals deeper in history. Similar labels therefore do not establish identical Bid/Ask execution data. NinjaTrader also provides order-flow tools under its own access and account conditions. ATAS tools likewise depend on the connection and available data; software alone does not establish an execution edge.

Compare functions and data separately
TradingViewCheck footprint methodology, feed, chart access and broker integration
NinjaTraderCheck order-flow entitlements, replay data and execution connection
ATASCheck cluster data, session settings and connection permissions
Spot or CFDsIdentify what the broker feed actually measures
Exchange futuresCheck venue, contract month and data entitlement

Two illustrative examples

Hypothetical ES footprint check. At 09:35 New York time a one-minute sample has Bid 120 and Ask 80 at one price, then Bid 60 and Ask 240 at the next. Assume complete, mutually exclusive execution categories. Total volume is 500 contracts and delta is +140; the second level has volume 300 versus 200 at the first. It is the POC of this two-level sample, not automatically the previous session’s POC. Positive delta does not prove that price must rise or that a stop will fill at its trigger. Compare price behaviour, session definitions and the execution plan before deciding on a trade.

Hypothetical grouping check. A separately defined profile has volume 40, 35, 50 and 10 at prices 100, 101, 102 and 103. With individual levels, POC is 102. Grouping 100–101 and 102–103 gives 75 and 60; shifting the two-level boundaries gives 40 at 99–100, 85 at 101–102 and 10 at 103–104. Both use total volume 135. This is our aggregation model, not a claim that every ATAS version offers arbitrary grid shifts. A changed bin label alone does not show new trading activity.

Who ATAS pays off for and who should skip it

Evaluate whether the available dataset answers your question and whether the full cost fits your budget. The software alone does not establish an edge, nor is a several-hundred-dollar monthly expense universal. Simulation results should be distinguished from live executions.

Suitability depends on whether the available dataset answers a defined question and whether you can explain its limitations. Beginners, spot traders and longer-term analysts are not universally excluded by those labels. Start with a narrow exercise rather than interpreting every coloured cluster as a signal. The order flow mechanics guide explains the distinction between available orders and completed trades; the platforms section helps compare functions.

What to do tomorrow

  1. Use an available free or demo dataset for one short exercise. Record the venue, instrument, delay, units and classification; recompute one candle’s Bid, Ask, volume and delta before comparing layouts.
  2. Separate costs from posted capital. List current software entitlements, market-data subscriptions, per-side commissions and other fees, then record account margin or deposits separately. Compare matched plan, venue, instrument and activity assumptions.
  3. For an OTC feed, check what its volume field measures. The guide to tick volume is relevant even if you later inspect an exchange dataset; neither the platform name nor a colour establishes global executed volume.
  4. Write down the observation the extra data should help test. Compare it with the actual journal or replay record, keeping chart interpretation separate from execution cost and trade outcome.
  5. For a broker or prop account, verify the permitted platform, connector and instrument in its terms. Then test order creation, cancellation and disconnection behaviour; a successful chart connection does not prove that every linked order works on the server.