How a signal becomes an order

The path an alert takes, and the two places it can stop.

1
The alert arrives
TradingView posts to your strategy's webhook. The passphrase in the body is checked first.
2
It is normalised
Ticker, direction and quantity are read out of the payload and the signal is recorded — whether or not anything trades.
3
Each subscription decides
Every account following the strategy applies its own size, its own trading window and its own risk gates.
4
The order is routed
Or parked for confirmation first, if that subscription is on manual.

A strategy with no subscribers trades nothing

Signals arrive at the webhook and are recorded, and the strategy looks alive. Nothing trades until an account follows it. This is the single most common reason for "my alert fired and nothing happened".

The second place it stops is the risk gate: an account can be locked, outside its trading window, or sized down to zero contracts. Each of those is written into the event log with its reason.

Open in Tradeus

Strategies — requires an account.

Step-by-step

Turn a TradingView strategy into real orders

A Pine strategy on a chart cannot place an order. TradingView can only fire an alert, and an alert is an HTTP request to a URL — it carries no broker, no account and no authentication. Everything between that request and a fill is what this page is about, including the five places the path can stop and what each one says when it does.

Also in Strategies and signals

Creating a strategyWhat you choose, and the passphrase you only see once.
The TradingView alertThe exact message body, field by field.
Position sizeFour methods, set per account and not per strategy.
Automatic and manualThe confirmation queue, and the number on the Strategies tab.
When a signal does not tradeRead the event log first — it names the reason.

A broker login belongs to one Tradeus account Creating a strategy