Direct answer: what counts as “inputs” in Forex Signals
“Forex Signals” is an umbrella term for a system that produces trade-related outputs based on inputs. In most implementations, the inputs fall into three buckets: (1) data inputs (what information the system reads), (2) model/strategy inputs (parameters that control how that data is interpreted), and (3) execution inputs (rules that translate outputs into orders, including costs and constraints). The exact set is provider- and platform-specific, so the only accurate approach is to verify what your specific “Forex Signals” instance actually uses through its documentation and configuration.
Mechanism and definition: data, parameters, and dependencies
1) Data inputs (the information source)
Common data inputs include:
- Price and time series fields (e.g., bid/ask or derived mid-price, open/high/low/close, volume if available).
- Indicator source data (raw series that an internal algorithm uses to compute indicators).
- Account or environment context (often at least broker timezone/market session info).
Not all systems use the same fields. Some rely on higher-timeframe summaries; others use tick or bar data. If the provider uses a “signal” computed from historical patterns, the inputs during training and the inputs during live operation may still differ.
2) Model or strategy parameters (how data is interpreted)
Inputs also include fixed or configurable parameters such as:
- Timeframes used to compute signals (e.g., which bar sizes feed the logic).
- Thresholds and rules that govern when conditions are considered met.
- Risk-related parameters expressed as limits or constraints (for example, maximum exposure or whether multiple positions are allowed).
A helpful way to think about this layer is: parameters define the mapping from data to decisions.
3) Execution inputs (how decisions become orders)
Even if the “decision logic” is stable, execution depends on execution inputs such as:
- Order type and order timing rules (market vs. pending; when orders are placed relative to the data timestamp).
- Slippage and transaction costs handling (commissions, swaps/financing, and how costs affect effective outcomes).
- Broker/platform constraints (minimum stop distance, leverage settings, margin rules).
These dependencies matter because they can change realized results without changing the underlying decision logic.
Dependencies you should expect
Typical dependencies include:
- Data availability and update frequency (missing bars or delayed ticks can alter the computed conditions).
- Data feed consistency between the system and your broker/platform.
- Timezone alignment between signal timestamps and broker execution time.
Evidence and example: how inputs change outcomes without changing “the idea”
Assume a system uses a bar-based condition (example assumption: it checks a rule on every new bar close). The relevant inputs are then:
- The bar close time definition (timezone and session handling).
- The price fields used to compute that bar (bid/ask vs mid).
- The exact bar size.
If your broker produces bars with a different timezone cut-off, or if spreads widen such that bid/ask-based calculations shift, the condition may become true on a different bar, or at a different time. That changes the execution inputs (entry timing and order fill quality), which can materially change outcomes even though the “concept” is the same.
This is why the reader should separate: stable mechanics (data → parameters → decisions → execution) from variable provider and market conditions (fills, costs, feed differences).
Limitations and risks: common failure modes
Material limitations
- Data gaps or delays: if inputs arrive late or are incomplete, the system may act on stale or partial information.
- Feed mismatch: a strategy may assume one pricing definition while the broker provides another.
- Execution variance: even perfect decisions can produce different realized results due to slippage and cost changes.
- Regime shifts: historical relationships between inputs and outcomes do not ensure future behavior.
One material failure mode to check
A common failure mode is “condition timing drift”: the decision logic triggers based on an internal timeframe or timestamp, but execution occurs using the broker’s current prices and constraints. If those timelines are misaligned, the “same” condition can lead to different order timing.
Verification and next question: how to independently confirm the inputs
To verify which inputs are used in your specific Forex Signals setup, look for:
- A description of the data fields and timeframes the logic relies on. - A list of configurable parameters (thresholds, timeframes, limits) and their defaults.