What Is a BTD Bot? Buying the Dip, Automated
Buy the dip, automated: a BTD bot layers buy orders as price falls and sells into the recovery. The mechanics, a worked example, and how it differs from DCA and QFL.
A BTD (Buy The Dip) bot buys into a price drop once it clears a set threshold below a reference point, and can layer in further buys if the price keeps falling, then sells into the recovery. It's long-only, spot, and threshold-triggered — built for markets that fall hard and bounce, not for picking the exact bottom.
A BTD bot buys into a price drop once it passes a set threshold below a reference price, and sells as the market recovers. It's long-only, spot, and threshold-triggered — it doesn't wait for a specific support level like a QFL bot, and it doesn't average in on a fixed schedule like a DCA bot. It reacts to the size of the drop itself, then acts.
A BTD (Buy The Dip) bot is a long-only spot trading bot that opens a position after price falls a defined amount below a reference point — a recent high, a moving average, or the bot's own prior entry — then adds further buy orders if the decline continues, each one deepening the position at a lower average price. It closes the cycle by selling into the recovery, typically before price fully retraces to where it started. "Buy the dip" has been crypto shorthand for opportunistic dip-buying since the market's earliest cycles; a BTD bot is the mechanical, rules-based version of that habit — a threshold and a plan for what happens if the dip keeps going, not a timing instinct.
TL;DR
- Threshold, not schedule or base — a BTD bot reacts to the size of a price drop, unlike DCA's interval-based averaging or QFL's support-level pattern
- Long-only, spot — no leverage, no short side
- Built for downtrends — repeated drops with real bounces, not one clean dip
- Entry — triggers once price falls a set amount below a reference point, and can layer further buys as the decline continues
- Exit — sells into the recovery, usually before price fully returns to where the drop started
How the drop-and-recover pattern works
The sequence a BTD bot follows:
- Reference point set. The bot tracks a recent high, a moving average, or its own last entry as the level a drop is measured from.
- Drop threshold crossed. Price falls a defined percentage below that reference, and the bot opens its first buy.
- Further layers, if the drop continues. Additional buy orders trigger at set intervals further down, each one lowering the average entry price — the deeper the fall, the more layers can fire.
- Recovery. Price reverses off the bottom of the decline.
- Exit. The bot sells into the bounce, closing the position at a target tied to its average entry rather than waiting for a full round-trip back to the original high.
A worked example
Say SOL is trading at $180 and drops to $162 — a 10% decline — on a broad market pullback. A BTD bot configured with a 10% drop threshold opens its first buy around $162.
The decline continues. At 20% below the reference ($144), a second layered order fires. At 30% below ($126), a third. Each layer lowers the bot's average entry price further.
Price then reverses and climbs back toward $150. The bot's exit target sits at a set gain above its average entry — not at the original $180 — so it sells into the recovery at $150 rather than waiting for a full retrace. The cycle closes, and the bot resets to watch for the next drop.
If price had kept falling instead of bouncing at $126 — down to $100, say, with no recovery — the bot would still be holding the position at whatever average price its configured layers reached. That scenario is exactly what the "fits — and doesn't" section below is about.
How a BTD bot differs from DCA and QFL
All three bot types buy into a falling price and sell into a recovery, which is where the similarity ends — each one decides when to buy differently.
| DCA | QFL | BTD | |
|---|---|---|---|
| Trigger | Schedule or fixed price interval | Base break below a repeatedly tested support level | Price drop past a set threshold below a reference point |
| Requires a "base"? | No | Yes — a level tested more than once | No — reacts to any qualifying drop |
| Best fit | Gradual entry into an asset view, in any market phase | Choppy markets with fear-driven dips at known support | Sustained downtrends with real bounces along the way |
A DCA bot doesn't need the drop to match any particular shape — it averages in on its own schedule regardless. A QFL bot needs a specific, previously-tested support level to break before it acts at all. A BTD bot needs neither: any drop past its threshold qualifies, which makes it more reactive than QFL and less scheduled than DCA — and also means it can trigger on a drop that turns out to have no real support underneath it. GRID vs DCA vs COMBO vs LOOP covers the wider bot lineup if you're weighing options beyond the dip-buying family; What Is a QFL Bot? covers the support-level version of this pattern in full.
When a BTD bot fits — and when it doesn't
A BTD bot fits sustained downtrends that still produce real bounces along the way — a market where price keeps making lower lows but also keeps snapping back hard enough to sell into. Bear-market conditions with periodic relief rallies are the setup this strategy was built around.
It fits less well in two specific situations. The first is a flat or calm market: no drops means no entries, and the bot simply sits idle. The second, more costly case is a structural decline with no real bounce — an asset that keeps falling because something about it has actually broken, not because the market overreacted. A BTD bot doesn't distinguish between a fear-driven dip and a fundamentals-driven collapse; it only sees a price that dropped past its threshold. That distinction is the trader's job, not the bot's.
Test your threshold against how the asset actually drops before running this live. Bitsgap's demo mode runs on real market data with virtual funds, so you can see how a BTD setup reacts to your pair's real volatility first.
Configuring a BTD bot
| Setting | What it controls |
|---|---|
| Drop threshold | How far below the reference point price has to fall before the first buy triggers |
| Reference point | What the drop is measured from — recent high, moving average, or last entry |
| Layered orders | How many staged buy orders the bot places as price falls further |
| Order spacing | The price distance between each layered order |
| Exit target | The gain above average entry price the bot sells into |
| Max exposure | The total capital committed if every layered order fills |
As with any bot type, backtesting shows how a given threshold and spacing would have performed on a specific asset's history, and demo mode shows how it behaves on current price action before any capital is committed. Exact field names in the Bitsgap interface may differ from the descriptions above — check the setup screen for current labels.
Common mistakes
Setting the drop threshold too tight. A threshold set just below normal daily noise triggers on moves that were never really a "dip" in the pattern's sense, filling positions on ordinary volatility.
Sizing against the first layer only. Like a DCA or QFL bot, a BTD bot's real exposure is every layered order it could place before hitting its configured depth, not just the opening buy.
Running it on an asset in structural decline. A coin that keeps falling because something about it actually broke doesn't produce the bounces this strategy depends on — it produces a slowly deepening position with no real exit.
Ignoring how much capital the full layer stack requires. A bot that looks conservatively sized on its first buy can require several times that if the decline reaches its deepest configured layer.
Ready to see how a BTD bot handles your pair's actual drop-and-recover pattern? Start a 7-day free trial on Bitsgap — no credit card required — and run it in demo before committing real funds.
FAQ
What does BTD stand for? Buy The Dip — one of crypto's oldest trading phrases, implemented here as a rules-based, threshold-triggered bot rather than a manual habit.
Is a BTD bot the same as a DCA bot? No. A DCA bot averages in on a schedule or fixed interval regardless of whether a genuine drop has occurred. A BTD bot only buys once price crosses a defined drop threshold, and stays inactive otherwise.
Is a BTD bot the same as a QFL bot? No. A QFL bot requires a specific, previously-tested support level to break before it acts. A BTD bot reacts to any qualifying drop from its reference point, with no requirement that the level has ever acted as support before.
Can a BTD bot short the market? No. It's a long-only spot strategy by design, with no short-side logic.
What kind of market suits a BTD bot? Sustained downtrends that still produce real bounces along the way. It performs worse in flat markets, where it has nothing to react to, and worse still in a structural decline with no genuine recovery.
