Skip to main content

Vote for ideas and share your own — that's how you shape the development of ATAS

We read every idea, and you can see what's already in progress on the roadmap.

Perhaps your idea has already been posted — find it and support it with your vote. One request with 50 votes moves faster than five identical ones with 10 each.

Didn't find it? Create a post. One post = one idea.

Doesn't belong here:

  1. Questions and issues with the platform — contact support@atas.net

  2. Several ideas in one post — such posts are rejected

Feature Request: Historical MBO Data Access for 7 Days or More, Similar to BookmapData

Title: Feature Request: Historical MBO Data Backfill (7–14+ Days) with Multi-Feed Compatibility Hi ATAS Team, I would really appreciate a feature that allows users to access historical Market-by-Order (MBO) data for at least 7–14 days, ideally even further back. Something similar to the historical data backfill functionality offered by Bookmap would be extremely useful. The main issue is that MBO analysis shouldn’t be limited to live data or data that was recorded locally while ATAS was running. For example, when price revisits an important liquidity zone that was formed one or two weeks ago, I want to be able to analyze the original MBO activity at that level, including historical icebergs, stops, sweeps, and order-level behavior. Without access to that historical data, valuable information is simply missing from the analysis. My suggestion would be: Server-side historical MBO backfill for at least 7–14 days, preferably longer. The ability to load historical MBO data on demand, even for periods when ATAS was not running. Accurate historical reconstruction of MBO events, including individual orders and relevant iceberg, stop, and sweep activity. Compatibility with existing connections such as Rithmic (including Apex Trader Funding accounts) and dxFeed, wherever MBO data is supported. The ability to use historical MBO data alongside existing live market data and trading connections without conflicts, connection instability, or interference with order execution. I understand that storing and providing historical MBO data requires significant infrastructure, and I would also be open to an optional paid historical data service. Is ATAS currently considering anything like this, or is there already a solution or workaround available? I believe this would be a major improvement for traders who rely on MBO analytics to study historical liquidity zones and market behavior. Thanks!

Flavio29 days ago

Trade count and win rate are wrong when a position has multiple fills

The trading journal counts every fill as its own trade instead of counting the whole position. If I enter 5 contracts and it fills as 2 + 2 + 1, or I scale in and out, ATAS shows 3 or more trades when it was really one. This throws off a lot of the stats. When I grouped my fills into actual positions (flat to flat), my real trade count was about half of what the journal shows, and my win rate was several points different. Average trades per day, average win, average loss and win rate are all affected, and those are the numbers I use to judge my strategy. Could you add an option to group fills into one trade from entry until the position is flat again? Ideally in the journal, the statistics page and the export. Right now I have to export everything and regroup it myself to get my real numbers.

Ahmed15 days ago
In Progress

Counting a scaled-in position as one trade for consecutive-loss limits

In ATAS X Risk Management, I can open a position, scale into it while it remains open, and then have the entire position stopped out. The risk management consecutive-loss calculation is currently counting this as being the number of losing trades equal to the number of times that I added to my running position before it was stopped out. I think that most traders would agree that this should instead be counted as a single losing trade. Can we please add an option to calculate the consecutive-loss limit by completed position: group all entries and exits from when the position opens until it returns to flat, then count the combined P&L as one win or loss. And this should also be able to account for when an exit order receives multiple partial fills. Thank you

Atlas2 months ago

Cross-Trading Dropdown not available in Replay Mode

In the new Replay Mode (after last Update) the Cross-Trading Drop-Down is deactivated when Replay is started. The executing contract can therefore not be changed during a replay Session. This was possible in the previous version, however you had to load the additional contract seperately (eg. ES and MES), which is not necessary in the new version. I have varying stop loss sizes and choose the contract depending on the stop size in order to meet my risk limit. This is now not possible anymore in Replay. It would be great if you reintroduce the possibility of switching the executing contract via the cross-trading dropdown in the trading panel, during replay playback.

Stefan1 month ago

Generelle Verbesserungen der plattform

Ein Ai das trading analysiert im journal und genauere daten liefern kann. Zb kann es genau analysieren in welchen märkten man zu wie viel % bessere ergebniss bekommt oder um welche uhrzeit oder an welchen tagen. Wenn man genau sehen kann wann man eine erhöhte wr oder profitfaktor hat und wann sich etwas verschlechtert oder nach wie vielen trades die wr nachlässt. Nicht nur die profite an tagen zb um wie viel % man profitabler ist an bestimmten tagen,stunden usw. Etwa so in der richtung Gex aber mit richtigen gex daten und nicht einer schätzung. Die meisten gex daten basieren auf addieren von beiden seiten der optionen, deepcharts hingegen hat gex daten die von richtigen Providern kommen, was deren System hervorhebt und sehr viel professioneler macht als alle anderen Konkurrenten grade auf den Markt. Ein system was ticks statt pnl anzeigt wenn man in einem trade ist. Dadurch kann man besser profit unabhängig traden und eher nach marktstruktur und sich nicht beeinflussen lassen vom geld. Ein sprachgesteuertes ai system wie ein persönlicher Assistent der verbunden ist mit den journal das man mit einer taste aktivieren kann so das es einen antworten, kommands oder tradig regeln die man ihm sagen kann zb die trading regeln an die er einen erinnert bei regel verstößen oder hinweißt wenn man in unprofitabelen trading stunden ist laut journal Ai und einem direkt auch pnl vom tag sagen kann oder die markt nachrichten mit 3 sterne vorlesen kann wann sie sind oder einen erinnern kann wenn sie gleich sind. Außerdem dier erwartung und ergebnisse der marktnachrichten sagt und ob es wahrscheinlich eher bullisch oder bärisch gewertet wird vom markt. Mit so einem Ai system im journal und beim trading würde es das komplette trading System revolutionieren und damit auch wieder klarvorteile gegenüber Konkurrenz wie Deepcharts haben. Außerdem ist das heute auch alles ziemlich einfach integrierbar mit chat gpt oder claude.

Timur2 months ago

Group executions by order ID in the Journal / Trading Statistics

When trading Binance futures, a single order is often filled by the exchange in several executions at different price levels. Each fill arrives with its own exchange ID but they all share the same order ID. ATAS logs each execution as a separate line in Trading Statistics. A single close therefore appears as several trades with fractional sizes. Total PnL and the equity curve remain correct, but trade count, win rate and average PnL per trade are distorted, which makes the statistics hard to use. This is especially problematic when assigning playbook strategies to trades, since the same setup has to be tagged across many fragments and the per-strategy statistics end up falsified. Suggestion: add an option to group executions sharing the same order ID into a single trade, using a size-weighted average fill price. A simple checkbox such as "Aggregate partial fills" in the Journal / Statistics settings would be enough, leaving the current execution-level view available for users who need it.

Simon2 months ago

Profit target tracker

Add a function within the trading journal to input a profit target for the day and a progress bar telling you if you hit it, with the option to add an alert when the target is hit

Callum3 months ago

Strategy backtesting module for ATAS indicators and MBO level3 historical data

A module specifically for strategy development and automated trading would be really next level. Strategy backtesting and trading system analysis and optimisation is something that all high level platforms are now developing. Something similar to Multicharts or Tradstation functions would be great. Easy language or C# for developers/Traders to take advantage of ATAS full features.

Craig4 months ago
1

Extend "Ticks and the DOM (Level 2)" replay period

Dear ATAS Team, In market replay, the "Ticks and the DOM (Level 2)" mode is currently limited to a single day per run, while "Ticks + best prices" allows much longer periods. Would it be possible to extend the DOM mode to multi-day periods (e.g. a full week) ? Thank you for considering it. Best regards

Alexis4 months ago
1

Multi-edit support for trade journal entries

Hello, I would like to suggest a new feature for the journal section. It would be very helpful if it were possible to apply settings or updates to multiple trades at once using a "multi-edit" function. Currently, I have to edit each trade individually, which is quite time-consuming. Having the ability to select multiple trades and update their properties in a single action would significantly improve the workflow. Please see the attached video for a demonstration of how I envision this functionality.

Viktor4 months ago
In Progress

Automatically attach screenshot to trading journal entry

Hi, it would be quite nice if there was a way to attach an ATAS screenshot to a Trading Journal Entry, when for example entering a comment. Currently I would have to take a screenshot with an external tool like ShareX, upload it to an external host and paste the link into the comment box, which is rather annoying. A better way would be to use the ATAS screenshot function (maybe even automatically) in order to add a screenshot via “+”-symbol.

Domenico5 months ago
2

Statistics / Trading Journal: display correct currency per account (multi-currency accounts)

Current behavior: With two live CQG accounts (one USD for CME, one EUR for Eurex) under the same login, the Trading Journal displays all PnL and commission values with a "$" symbol, including trades on EUR-denominated instruments. Example — FDXM (Mini-DAX, EUR-denominated) trade: Positions tab: Closed PnL = 825 (no symbol) Trading Journal: Net P&L = $xxx+ Commission $ = $825 The raw number is identical in both tabs, so no EUR→USD conversion appears to be applied — the "$" is a hardcoded/default label. The per-trade values are numerically correct in the instrument's currency, but the displayed currency is wrong for EUR accounts. Problems: Misleading display: EUR amounts shown with a $ symbol. When multiple accounts in different currencies are selected, aggregates (Total PnL, equity curve) apparently sum EUR and USD raw values together, producing meaningless totals. Requested: Display each trade's PnL/commission in the actual currency of the account/instrument (the platform already knows Portfolio currency — it is shown correctly in the Accounts tab). Either block or explicitly convert (with a documented rate source) cross-currency aggregation in Statistics when accounts in different currencies are selected together. Platform: ATAS (Windows).

Franck4 months ago
In Progress

Upload Screenshot in Trading Journal

It would be great if upload screenshot is provided in trading journal to recall how our executed trades performed in the past. It is not a luxury. It is a necessity.

WEE6 months ago

Custom Tags for Trading Journal

I'd like to suggest adding custom tags that are independent from Playbooks. Currently, the only way to create a custom tag is by creating a Playbook. However, Playbooks and tags serve different purposes. A Playbook defines a trading setup or process. Tags are metadata used for journaling, filtering, and analysis. For example, I may have a Playbook called "ORB Long," but want to tag the trade as: A+ Setup B Setup Delta Flip Absorption Trend Day Late Entry These are trade characteristics, not separate Playbooks. Allowing standalone custom tags would make journaling and post-trade analysis much more powerful while keeping Playbooks focused on actual setups.

marlon6 months ago

MBO data for Replay

Request: give ATAS the ability to include MBO data in Replay mode. Reason: This capability is necessary for back-testing and practicing with the ATAS MBO tools.

Dennis6 months ago

ATAS X: Missing cross-platform order synchronization (incorrect journal data)

ATAS X does not correctly display trade history when orders are executed on another platform (e.g., TradingView on mobile). As a result: trades are missing or incomplete trading journal statistics become inaccurate Other platforms (TradingView, CQG Desktop, Quantower) correctly synchronize orders across platforms, regardless of where the trade is placed. Request: Enable full cross-platform order synchronization so that trade history and journal statistics remain accurate and consistent.

MV7 months ago

Replay mode: Portfolio.ClosedPnL always returns 0

TradingManager.Portfolio.ClosedPnL always returns 0 during Market Replay — OnPortfolioChanged never fires at all in replay mode. The only workaround is to regex-parse position.ToString() to extract the closed P&L string, which is fragile and undocumented. Request: make Portfolio.ClosedPnL (and OnPortfolioChanged) work correctly in replay mode, the same as in live/paper trading. Strategy developers rely on closed P&L to enforce daily loss limits, profit goals, and session resets — none of these work in replay without this fix, making replay useless for strategy validation.

Robert7 months ago
2

True Real-Time Replay Mode

The current Replay mode offers a speed slider, but even at 1x the playback does not reflect the actual speed at which ticks were originally recorded. It appears that the replay engine streams ticks sequentially without preserving the real time intervals between them, which means the market moves noticeably faster during playback than it did live. It is also unclear whether the relative timestamps of incoming ticks are respected at all. For scalpers and order-flow traders, this is a critical limitation. Effective training requires practicing entries, exits, and tape reading under conditions that are identical to live trading - including the real-world delays between ticks, the pauses during slow periods, and the bursts of activity during fast markets. Any deviation from the original timing distorts reaction times and undermines the training value of Replay. Request: Please add a dedicated "Real-Time" (1:1) playback option that replays ticks using their original recorded timestamps, so that the Replay speed exactly matches the live market conditions at the time of recording; no acceleration, no compression, no artificial delays. The existing speed slider (0.1x–50x) could remain as an additional multiplier on top of this baseline for users who want to deviate from real time. This would make ATAS Replay significantly more valuable for scalpers and anyone training execution skills under realistic conditions.

Paul7 months ago

Fix window size issue in Daily Note screen

As you enter lines in the Daily Note view of the journal it expands the text box but the window remains a fixed size that can’t be resized. You end up unable to see or press the the cancel / Save buttons as a result, making it unusable. The Trade Notes screen handles this by adding a scroll bar to the text box, which would be ok here.

David7 months ago

Import statistics

I would like to suggest an improvement regarding the Replay Mode functionality. When performing backtesting in Replay Mode, I typically load only a single trading day or session (e.g., the New York session). As a result, my statistics are reset each time I load a new day, which makes it difficult to track overall performance across multiple sessions. It would be highly beneficial to have the ability to preserve or import statistics between sessions, allowing for more comprehensive and continuous performance analysis.

Mateo8 months ago