Import Binance Trades into TradesViz to Find Which Type of Trades Is Losing Money

Binance

27 October 2026

After importing your Binance trade records into TradesViz, the key to finding which type of trades is losing money is not the "import" step itself, but what dimensions you use to slice the data afterward. TradesViz gives you the ability to filter and analyze by symbol, long/short direction, and time. But to answer "which type of trades is losing money," you first need to define what a "type" is — by coin, by long/short, by holding period, or by your own custom tags. Importing only turns raw trade records into analyzable data. The real insight comes from the grouping dimension you choose.

Binance Exchange
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!

First decide which import method to use

There are two paths from Binance to TradesViz: manual CSV upload and automatic API sync. They are not interchangeable; each fits different situations.

If you only want to analyze historical data, such as futures trades from the past six months, manual export is faster. After exporting your Binance futures trade history, TradesViz requires the file to include these columns: Date(UTC), Symbol, Side, Price, Quantity, Amount, Fee, Fee Coin, and Quote Asset. If the exported format is .xls or .xlsx, you need to save it as .csv in Excel. Simply changing the file extension to .csv will not work. The upload entry is on TradesViz's Import page. Select your trading account and Binance, then choose Upload File.

If you want future trades to automatically enter TradesViz, you should use API auto-sync. But there is one important condition to know in advance: auto-sync only pulls new trades after the connection is set up. It will not backfill history. So the correct order is to first manually import your historical trades, then set up the API connection. TradesViz's official documentation clearly states this: missing old trades happen because auto-sync only fetches recent records, so you need to manually import historical files first and then enable auto-sync. API permissions only need to be read-only. TradesViz states that it does not request trading or transfer permissions. TradesViz supports Binance USDT-M and COIN-M futures, including leverage and position tracking.

My take is this: if you are only doing a one-time review to find the source of losses, manual import is enough. No need to bother with API. If you plan to keep an ongoing journal, manually import history first, then enable auto-sync. Do not reverse the order.

After importing, first confirm data completeness, then look at losses

After the import is done, do not jump straight to loss analysis. Do two things first.

First, confirm that the number of imported trades matches your expected time range. TradesViz's common import failure reasons include missing required columns, changed export format, and manually edited files. If the number is clearly too low, go back to Binance and export again. Check whether the time range covers the full period you want to analyze. Some brokers' export files do not include all history at once, so you may need to export in batches by year or month and import them one by one.

Second, understand TradesViz's PnL definitions. TradesViz separates PnL into different concepts: Closed PnL is the profit and loss of all fully closed trades. Total Realized PnL includes both fully closed and partially closed trades. Unrealized PnL is the floating profit and loss of open positions calculated at the last closing price. When looking for "which type of trades is losing money," you should look at Closed PnL or Total Realized PnL, not include floating losses from open positions. If the numbers you see in TradesViz do not match the Binance App, first check whether this definition difference is the cause, or whether you have toggled between Net P&L (after fees) and Gross P&L.

Which dimension to slice by in order to find the source of losses

TradesViz's statistics page provides aggregated data by Symbol: best and worst performing symbols, symbols sorted by total PnL, symbols with the highest volume and the most trades. Each symbol is a clickable tag. Clicking it filters all trades for that symbol. This is the most direct path to "finding losses by coin."

But "which type of trades is losing money" does not necessarily equal "which coin is losing money." A common mistake is seeing that BTCUSDT has the largest total loss and concluding that BTC is the problem. In reality, a large total loss may simply be because of more trades or larger position size. The average loss per trade may not be high. What is more worth looking at is the split by long/short direction. TradesViz's dashboard widgets include long/short ratio and corresponding win rate statistics. If you find that your long win rate is clearly lower than your short win rate, or that the average loss in one direction is significantly higher, the source of losses is more likely pointing to directional judgment rather than symbol selection.

Another easily overlooked dimension is time. TradesViz's calendar view can show profit and loss distribution by day, week, or month. If your losses are concentrated on certain days or during certain periods, the problem may be trades made under specific market conditions, not a specific symbol or direction. For example, if you find that Wednesday accounts for most of the week's losses, and on Wednesday you happened to trade a particular coin or used larger position sizes, then what you need to investigate is the decision-making in that scenario, not a vague "trade less of a certain coin."

If you used custom tags or notes when placing orders on Binance, the official documentation does not clearly state whether TradesViz can preserve that information after import. This cannot be confirmed, so do not assume that tags will carry over with the CSV. If there are no tags, manually tagging trades in TradesViz after import is possible, but for large historical datasets the workload is significant. A more practical approach is to first slice by Symbol, direction, and time. Once you find a suspicious range, then go back and review those specific trades in detail.

A practical judgment sequence

My suggestion is to follow this order. Each step answers only one question:

Step 1: Look at the distribution of Closed PnL by Symbol. Which symbol or symbols contributed the largest losses? If losses are highly concentrated in 1-2 symbols, the problem may be symbol selection or your market read on that symbol. If losses are spread across many symbols, the problem is more likely in trade frequency, position sizing, or directional judgment.

Step 2: For the symbol with the largest losses, switch to the long/short split. Are the losses concentrated on the long side or the short side? Or are both sides losing? If only one side is losing, it means your directional judgment has a systematic bias, not just bad luck.

Step 3: Click into that symbol's trade list and sort by time. Are the losses evenly distributed across every trade, or concentrated in a few large losing trades? If the latter, the problem is in stop-loss execution or position control. If the former, the problem is in win rate or risk-reward ratio itself.

Completion standard: You can describe the source of losses in one sentence, and that sentence includes symbol, direction (or time period), and the degree of concentration. For example: "BTCUSDT long trades over the past month contributed the main losses, and the losses are concentrated in three trades where stop-losses were not executed in time." If you can only say "I'm losing money" without naming specific dimensions, the slicing is not detailed enough yet.

TradesViz's free plan only supports stock trade imports. Non-stock trades require a Pro or Platinum plan to import and analyze. If your account is on the free plan, you may see nothing after importing Binance futures data. This needs to be confirmed before you start, otherwise you may mistake it for an import failure.