Example account A MT5
XAUUSD
| Per-tier settings | T | A selected | N |
|---|---|---|---|
| Lot size | 0.01 | 0.05 | 0.10 |
| Slippage pts | 100 | 300 | 600 |
| Take profit pts | 600 | 2000 | 3600 |
Stop loss 300 pts1 point = 0.01
Selected for execution checksBUY · 0.05 lots · A tier
ToxicTraders · Economic news automation
Automated news trading.
Your MT4 & MT5 accounts.
Choose the release. Define the signal rules. Prepare each account. ToxicTraders processes the published numbers and runs your configured execution and position management.
Membership by requestRequest access ↗
All MT4 and MT5 brokers supported.
01—02 · Before the release / At the release
Prepare the event.
See how your rules respond.
A CPI release can contain several indicators. Choose which components your strategy uses, how their deviations map to signals, and what should happen when they disagree. Then attach the strategy to the accounts and trading window you prepared.
01 / Prepare the event
A CPI task, with your rules and account settings.
Interactive example · settings are illustrative
- Release
- US CPI · monthly change
- Saved template
- CPI · two accounts
- Signal source
- My strategy
- Trading window
- −10 min to +1 min
AutoTrade loads the template at Start, waits for your strategy’s signal and requests closure at End. Times above are relative to the scheduled release.
02 / Read the release
Choose a scenario to see the decision change
ComponentPreviousForecastActualDeviation
Headline CPI m/mMain · produces the signal
Previous0.2%
Forecast0.3%
Actual0.1%
Deviation−0.2 pp
Core CPI m/mSecondary · checks for conflict
Previous0.3%
Forecast0.3%
Actual0.2%
Deviation−0.1 pp
Deviation = actual − forecast, in percentage points (pp).
Strategy verdictSellA
The Main signal passes the component check.
Headline CPI is 0.2 pp below forecast, reaching SellA. Core CPI also points lower. The A tier selects each account’s lot, slippage and take-profit settings below.
03 / Apply the account template
One signal. A separate execution setup for each account.
Reverse ON
Example account B MT4
USDJPY
| Per-tier settings | T | A selected | N |
|---|---|---|---|
| Lot size | 0.02 | 0.10 | 0.20 |
| Slippage pts | 30 | 60 | 100 |
| Take profit pts | 100 | 220 | 400 |
Stop loss 100 pts1 point = 0.001
Selected for execution checksSELL · 0.10 lots · A tier
Direction is configured. Reverse flips Buy ↔ Sell for that account and keeps the signal tier. Symbol, lot and point distances belong to that account’s template.
A signal is followed by execution. Slippage is an entry condition checked before submission, not a guaranteed fill-price cap. Execution checks and broker responses are recorded separately from NoTrade, Conflict or Timeout.
03 · From signal to position
Control what each account does next.
The signal is only the instruction. Your account settings determine the instrument and size, the conditions checked before submission and how the position is managed afterwards.
Manager / Account row
Give each account its own execution settings.
A strategy supplies the direction and signal tier. Each account row supplies the symbol, position size and execution parameters to use for that tier.
Point-based values use the instrument’s precision. Keep account and symbol settings together when saving a template.
- Symbol & Reverse
- Choose the broker instrument and whether that account follows or reverses the strategy direction.
- Lot T / A / N
- Set a separate position size for each signal tier. A zero lot skips that tier on that account.
- Slippage T / A / N
- Limit price movement from the previous minute’s close before submission. The recorded fill slippage remains a separate measurement.
- Profit T / A / N
- Set a target in broker points for each tier. The selected tier determines which target is used.
Follow both outcomes
NoTrade / Conflict / Timeout describes a strategy decision. Filled / blocked / rejected describes the subsequent execution attempt.
04 · A recorded July CPI execution
Now follow an actual order.
This published GOLD# trade connects the June CPI reading, released on 14 July 2026, with its stored broker prices and execution telemetry. Open the chart and compare the price move with the recorded entry and exit.
Recorded CPI execution
GOLD# · BUY
01
The release
US headline CPI · monthly
Reference period: Jun. 2026
- Previous
- 0.5 %
- Forecast
- -0.1 %
- Actual
- -0.4 %
- Actual − forecast
- -0.3 pp
02
The recorded order
BUY GOLD#- Open price
- 4,034.62 15:30:02
- Close price
- 4,057.68 15:30:03
Order timestamps: broker server time.
0.95 lots
Broker-reported net P&L+2,190.70 USD
GOLD#1-second bid / ask observations
Loading the recorded price window…
03
Review the execution
- Execution latency
- 153ms
- Broker ping
- 1ms
- Open slippage
- 96points
- Open spread
- 45points
Ping measures the network round trip; execution latency includes client processing and broker communication through fill confirmation. The one-second chart cannot resolve that latency interval.
The saved order clocks have whole-second precision. A confirmed exit reason is not recorded.
Beyond a single trade
Put that execution in context.
Inspect the recorded attempts and latency distribution for the disclosed production cohort. The snapshot keeps unsuccessful and unresolved attempts visible alongside confirmed fills.
Recorded execution outcomes
3 selected production users · news-source records
- Recorded attempts
- 5,691
- Filled
- 4,250
- Rejected / blocked / failed
- 1,183
- Other / pending
- 258
Execution latencyClient submission → fill confirmation
- Median
- 198.5 ms
- P90
- 784 ms
- P99
- 5,601.9 ms
Sample: 4,234 eligible filled records · includes client processing and broker communication.
Sample rules, exclusions and measurement limits
Counts cover recorded news attempts linked to the selected cohort. Unattributed records and users outside that cohort are excluded. Release-capture and platform-wide market-data totals are separate datasets.
Rejected / blocked / failed combines broker refusals, local guards such as slippage limits, and client or connection failures, including failures before submission. Other / pending contains 0 partial-labelled and 258 unknown / pending records. Legacy labels can classify some partial fills as filled.
Execution latency starts on the execution client when submission begins and ends when a fill is confirmed. It includes local preparation, broker communication and confirmation handling. Feed acquisition, parsing and signal generation are outside this interval.
Percentiles include filled records with positive latency up to 10,000 ms. The 10-second cutoff is a historical data-quality rule for earlier test and timing-code anomalies. It defines the admitted sample, not a guaranteed execution ceiling.
- Missing / previously discarded
- 16
- Non-positive
- 0
- Still stored above the limit
- 0
Previously discarded values can appear as missing; their original rejection reason cannot be recovered from the missing count.
Eligible population: 4,234. Percentile sample: 4,234. The sample cap is 100,000. Sample maximum: 9,979 ms. Percentiles use linear interpolation between adjacent ordered observations.
Execution timing is conditional on the eligible fills; it does not establish release-to-fill latency or profitability. Missing values appear as a dash. Methodology: news-software-stats-v3.
Read the evidence methodology →Private community
Membership by request.
Public registration is closed. We welcome requests from traders with a basic understanding of Forex.
You should understand lot size, leverage, margin, spread and trading risk. Tell us about your experience and the setup you want to trade.
How to join
- Introduce yourself
Complete the required fields in your native language, then send the prepared email. You can optionally choose Raw data feed or Full trading system.
- Discuss your setup
Support reviews your request and discusses access, account limits and terms with you.
- Receive your account access
After approval, we create your account and email the sign-in details.
Already a member? Sign in
All MT4 and MT5 brokers are supported. Additional platform and API connections can be added on request through support@toxictraders.com.
Use the workflow across releases
Inflation. Employment.
Rates. Energy.
Prepare different strategies and account templates for the release families you trade. The public report library contains a selection of the supported events.
CPI, PPI, employment and NFP, ISM, jobless claims, FOMC decisions, EIA inventories and WASDE.
Practical details
Before your first event.
Which brokers can I connect?
All MT4 and MT5 brokers are supported. Additional platform and API connections can be added on request through support@toxictraders.com.
Where does the software run?
Use the web workspace to prepare and review your trading. The execution client runs on your Windows VPS or dedicated host and needs a stable connection during the event. You arrange your own hosting and brokerage account.
Can accounts use different symbols and position sizes?
Yes. Each account row has its own instrument and execution settings, including separate lots and targets for the T, A and N signal tiers. Save those rows as a template for another event.
Why might an event finish without a trade?
The deviation may not meet a threshold, the configured component rules may produce a conflict, or required values may not arrive within the collection window. A trading signal can also encounter an execution guard or a broker rejection; these are separate outcomes.
Is the CPI setup above the historical trade configuration?
The interactive setup illustrates the available controls. The recorded July CPI case is loaded separately from its published broker-history snapshot. The example settings are not attributed to that historical trade.
How do I get access?
Public registration is closed. Email support@toxictraders.com with your Forex experience, broker, platform and intended use. Basic understanding of lot size, leverage, margin, spread and risk is required. Support reviews each request and discusses access and terms before creating an account.
Trading news involves rapid price changes, spread widening, slippage and possible execution failures. Recorded executions describe historical trades; their outcomes do not guarantee future results. Read our news trading risk case study with interactive gold tick charts to see two losing trades, their actual entry and exit prices, and the limits of low-latency execution.