01
Your TradingView, TrendSpider, Python, Pine Script, or JavaScript alert arrives at your strategy URL.
Documentation
How orders route after your alert fires.
See what FirmGated checks between your strategy alert and your broker account, including Target-Lock protection, duplicate prevention, approvals, and the final trade record.
From alert to gated execution
FirmGated accepts common market, limit, and stop instructions. The gate checks the trade against your account rules before execution is released.
02
FirmGated reads the ticker, action, quantity, order type, and the account route you selected.
03
Target-Lock checks the account, prop rules, trading window, position size, and duplicate risk.
04
The signal is released, held for approval, or blocked before it reaches the broker.
05
Every step is recorded so you can review the gated signal and the final broker response.
| What happens | How it works |
|---|---|
| Duplicate protection | If the same alert arrives twice, the gate is designed to stop repeat execution. |
| Approval hold | When manual approval is enabled, the trade waits for your clearance before routing. |
| Target-Lock block | If your prop or account rules reject the signal, FirmGated labels the reason clearly. |
| Broker connection issues | If your broker credentials need refreshing, FirmGated tries once automatically before reporting an error. |