← THE CHARTSPOD LEDGEROPEN TERMINAL →
AGGR.TRADE GUIDE · SETTINGS

Aggr.trade Bitcoin Settings: Reduce Noise Without Hiding Relevant Trades

A BTC tape with every fill is unreadable; a tape filtered too hard hides the trades that matter. Set thresholds by venue and market, then check what you are no longer seeing.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

To reduce noise in Aggr.trade on Bitcoin without hiding relevant trades: enable trade aggregation so split fills appear as one order, set your minimum display threshold from the market's own typical trade size, use exchange multipliers so smaller venues are not drowned out, keep liquidations on a separate threshold, and periodically lower the filter to check what you removed. Settings should differ for spot and perpetual markets.

A step-by-step setup

Noise reduction without blind spotsNoise reduction without blind spots. Steps: 1. Aggregate fills — One order, one row; 2. Set base threshold — From typical trade size; 3. Scale by venue — Exchange multiplier; 4. Separate liquidations — Own threshold; 5. Audit weekly — Lower filter, compare1Aggregate fillsOne order, one row2Set basethresholdFrom typical tradesize3Scale by venueExchange multiplier4SeparateliquidationsOwn threshold5Audit weeklyLower filter,compare
Each step is reversible; record the values you choose. Original ChartsPod editorial graphic.
  • Aggregation: merges same-timestamp fills; the changelog notes liquidations are also aggregated when trade aggregation is on (3.0.6).
  • Base threshold: watch the unfiltered tape for 15 minutes and note the size above which prints are rare.
  • Venue multiplier: the exchange threshold uses threshold × multiplier (2.5.6), so smaller venues can use a lower effective size.
  • Liquidations: a dedicated liquidation threshold exists (3.0).

Illustrative starting values

MarketDisplay minimumHighlight tier 1Highlight tier 2
Large venue BTC perpetualHigherMedium-largeVery large
Large venue BTC spotMediumMediumLarge
Smaller venue BTC perpetualLower (via multiplier)MediumLarge

Deliberately qualitative: typical trade sizes change with volatility and price. Derive numbers from your own observation window and record the date.

Illustrative: rows shown per minute at different minimumsIllustrative: rows shown per minute at different minimums: No filter 600 rows; Low minimum 120 rows; Medium minimum 25 rows; High minimum 3 rows.ILLUSTRATIVE: ROWS SHOWN PER MINUTE AT DIFFERENT MINIMUMSNo filter600 rowsLow minimum120 rowsMedium minimum25 rowsHigh minimum3 rowsIllustrative counts to show the trade-off; measure your own.
Aim for a tape you can read in real time without losing mid-size clusters. Original ChartsPod editorial graphic.

Spot and perpetual need different settings

Perpetual markets usually print larger and more frequent trades than spot for the same asset, because leverage lets participants trade larger notional with the same capital. A threshold tuned on a perpetual will hide nearly all spot activity; one tuned on spot will make the perpetual tape a wall of highlights.

Set separate thresholds or multipliers for each, and label the panes clearly. If you combine spot and perpetual in one feed, consider using the venue multiplier so a large spot print can still be highlighted at a lower absolute size.

Revisit thresholds after large volatility changes. In a high-volatility week, typical trade size rises and a previously rare threshold becomes routine; in quiet weeks the reverse happens. A note of the date and the reason for each change keeps your history of settings understandable.

Check what you are hiding

  1. Once a week, drop the minimum to the lowest tier for 10 minutes during an active period.
  2. Note clusters of mid-size prints that never reached your threshold.
  3. If clusters preceded moves you cared about, lower the threshold or add a tier.
  4. Record the new values and date.

Cross-check a filtered tape with a footprint, where every print is counted.

Open the live chart in ChartsPod

Filter by market-specific thresholds, separate liquidations, and audit what the filter removes.

Related: How to Read Aggr.trade: Large Trades, Side Filters and Rolling Volume, Aggr.trade Trade Aggregation: Why Several Prints Become One Row, Aggr.trade Audio Thresholds: Match Alerts to Trade Size and Market.

Compare Aggr.trade Bitcoin Settings across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

Questions readers ask

What threshold should I use for BTC on Aggr?

Derive it from the market's typical trade size in your own observation window; it varies by venue, spot vs perp and volatility.

Does aggregation hide trades?

No, it merges same-timestamp fills; thresholds are what hide smaller rows.

Should liquidations use the same threshold?

No. Aggr supports a separate liquidation threshold.

Sources and methodology

Aggr.trade behaviour is taken from its public README and CHANGELOG (version numbers cited) as read on 17 October 2026; the interface changes over time, so confirm settings in your build. Numbers in examples are illustrative.

  1. Aggr repository README — exchanges, aggregation, audio, history via aggr-server.
  2. Aggr changelog — workspaces, audio thresholds, liquidations, alerts.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.