Myth, More Confluence Always Means a Better Trade
Many traders think that adding more conditions to a setup automatically improves quality. They stack indicators, zones, patterns, and timeframes until the checklist has twenty items. Then they take almost no trades, or they find ways to justify forced ones.
Problems with excessive confluence:
- Paralysis. Too many conditions rarely align, so you hesitate or skip good trades.
- Overfitting. Highly specific rules may fit past data but fail in the future.
- Duplication. Many indicators show the same information, so you're counting one reason several times.
- False confidence. A long list feels safe even when the underlying idea is weak.
A better approach:
1. Choose independent factors. For example, higher-timeframe bias, liquidity sweep, location in premium or discount, and a structure shift. Each adds different information.
2. Limit the list. Five to seven core items are plenty.
3. Test the effect. Compare results with and without each condition. Remove those that don't improve expectancy.
4. Keep it simple enough to execute under pressure.
Ask of each criterion: "What unique information does this give me, and what does my data say about it?"
Quality comes from relevant evidence, not from the quantity of boxes ticked.
Trim your checklist until every item earns its place.
Myth, More Confluence Always Means a Better Trade
Myth, More Confluence Always Means a Better Trade
It’s Fairman 
Re: Myth, More Confluence Always Means a Better Trade
Practical tip: try cutting your checklist down to the five items that show up in most of your best trades. Keep the rest as optional notes. You'll probably take more trades and the quality won't drop much, if at all. To find those five, go through your last thirty winners and list every condition that was present. Then do the same for thirty losers. The useful items are the ones common in winners and less common in losers. Anything that appears equally in both isn't helping you choose. Most people find that two or three of their favourite indicators fall into that last group and can be dropped without any loss.
It’s Fairman 
Re: Myth, More Confluence Always Means a Better Trade
There's also an overconfidence side to it. When a setup ticks fifteen boxes, people tend to size up and ignore the one warning sign that matters. Five solid conditions at normal size is usually the better trade. Many confluence factors are also measuring the same thing. An RSI divergence, a stochastic divergence and a MACD divergence on the same swing are one piece of information, not three. Test each condition separately in your journal by tracking whether it was present on each trade. You'll often find two or three conditions carry most of the edge and the rest add nothing.
It’s Fairman 
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Myth, More Confluence Always Means a Better Trade
The paralysis point has simple arithmetic behind it. If each of eight conditions is present on about 60 percent of candidate setups and they are truly independent, all eight line up only about 1.7 percent of the time.
Say a pair throws up 300 candidate setups a month, then that leaves about five trades. Five trades is too few to tell a good month from luck, so the checklist ends up untestable as well as slow.
When the conditions line up far more often than that, it usually means they are not independent. That is the duplication problem showing up in the numbers, and it is a quick way to spot indicators that measure the same thing.
One structure that works better for some traders is three required items for entry and the rest used only for size. A setup with just the core three takes half risk, and full risk needs two of the optional items as well.
That keeps trade count high enough to learn from, while the extra conditions still have to earn their place through results. Does anyone here scale size by confluence like that, or keep it fixed?
Say a pair throws up 300 candidate setups a month, then that leaves about five trades. Five trades is too few to tell a good month from luck, so the checklist ends up untestable as well as slow.
When the conditions line up far more often than that, it usually means they are not independent. That is the duplication problem showing up in the numbers, and it is a quick way to spot indicators that measure the same thing.
One structure that works better for some traders is three required items for entry and the rest used only for size. A setup with just the core three takes half risk, and full risk needs two of the optional items as well.
That keeps trade count high enough to learn from, while the extra conditions still have to earn their place through results. Does anyone here scale size by confluence like that, or keep it fixed?
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Myth, More Confluence Always Means a Better Trade
Fairman's thirty winners against thirty losers is a good start, but the sample is smaller than it looks. Say a condition shows up in 70 percent of winners and 55 percent of losers, then with thirty in each group the difference is only a little over one standard error, which chance produces easily.
It takes something like a 30 point gap, say 80 against 50 percent, before thirty and thirty start to say much. Smaller gaps need a hundred or more trades on each side.
There is also a selection problem in the method. Because every trade taken already passed most of the checklist, a condition can look useless simply because it was present on nearly all of them, winners and losers alike.
Keeping a record of skipped setups fixes part of that. A quick screenshot of each near miss, with the conditions it lacked, shows whether the trades filtered out by a condition would have done worse, which is the real job the condition is supposed to do.
On the RSI, stochastic and MACD point, the duplication is easy to measure. If two conditions agree on almost every swing, keeping the one that is simplest to read loses nothing and frees attention for something independent.
It takes something like a 30 point gap, say 80 against 50 percent, before thirty and thirty start to say much. Smaller gaps need a hundred or more trades on each side.
There is also a selection problem in the method. Because every trade taken already passed most of the checklist, a condition can look useless simply because it was present on nearly all of them, winners and losers alike.
Keeping a record of skipped setups fixes part of that. A quick screenshot of each near miss, with the conditions it lacked, shows whether the trades filtered out by a condition would have done worse, which is the real job the condition is supposed to do.
On the RSI, stochastic and MACD point, the duplication is easy to measure. If two conditions agree on almost every swing, keeping the one that is simplest to read loses nothing and frees attention for something independent.
-
FXS Prop Desk
- Posts: 1689
- Joined: Wed Oct 07, 2026 9:52 am
Re: Myth, More Confluence Always Means a Better Trade
A good test for a checklist is to look back at the last 50 trades and see which conditions actually made a difference. Often three or four items carry nearly all the value, and the rest just reduce the number of trades.
There is also a statistical problem. Each extra condition reduces the sample, so with twenty conditions you might end up with only a handful of trades a month. That makes it almost impossible to know whether the setup works. A simpler rule set with more trades gives clearer feedback.
There is also a statistical problem. Each extra condition reduces the sample, so with twenty conditions you might end up with only a handful of trades a month. That makes it almost impossible to know whether the setup works. A simpler rule set with more trades gives clearer feedback.
FXS Official Team | The Idea Lab & Strategy
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Myth, More Confluence Always Means a Better Trade
Two broker models handle the same problem in opposite ways. One says "the price has changed, do you still want this trade?" and the other says "filled, at whatever price was available."
The first is a requote. It's annoying, but it gives a choice. The second is market execution with slippage, which is faster, but the fill can land anywhere within the deviation setting.
Neither is automatically better. For a scalper, the requote model has a hidden cost: the delay. Between the first click and the second, the market keeps moving, and the retry usually happens at a worse price than the original one. Because the whole edge might be a single pip, losing the first quote is often the same as losing the trade.
Market execution has its own issue. The fill price depends on the broker's pool at that instant, and in fast conditions the gap between expected and actual can be large. The upside is that it is symmetric in theory. Positive slippage should occur as often as negative.
Whether that is true in practice is something only a fill log reveals.
A third variation exists: some brokers handle requotes with a short countdown, giving a couple of seconds to accept the new price. The countdown itself is a risk, since a scalper who accepts a new price after two seconds is taking a trade in a different market from the one that was meant.
Whatever the model, the number that counts is the total delay from the click to the final fill.
For most short-term trading, market execution with a tight deviation limit tends to fit better, but it depends on the broker. Which model has treated scalping entries better in your experience?
The first is a requote. It's annoying, but it gives a choice. The second is market execution with slippage, which is faster, but the fill can land anywhere within the deviation setting.
Neither is automatically better. For a scalper, the requote model has a hidden cost: the delay. Between the first click and the second, the market keeps moving, and the retry usually happens at a worse price than the original one. Because the whole edge might be a single pip, losing the first quote is often the same as losing the trade.
Market execution has its own issue. The fill price depends on the broker's pool at that instant, and in fast conditions the gap between expected and actual can be large. The upside is that it is symmetric in theory. Positive slippage should occur as often as negative.
Whether that is true in practice is something only a fill log reveals.
A third variation exists: some brokers handle requotes with a short countdown, giving a couple of seconds to accept the new price. The countdown itself is a risk, since a scalper who accepts a new price after two seconds is taking a trade in a different market from the one that was meant.
Whatever the model, the number that counts is the total delay from the click to the final fill.
For most short-term trading, market execution with a tight deviation limit tends to fit better, but it depends on the broker. Which model has treated scalping entries better in your experience?