Positions
Live exposure appears, changes, and closes.
Opened
Partially closed
Closed
Signalator Notify · Trade Monitoring
Know exactly what changed on your trading account.
Trade Monitoring turns live positions, pending orders, SL/TP changes, partial closes, and profit milestones into structured alerts you can understand immediately.
It is the module for account activity awareness: what happened, where it happened, and why it matters now.
Live trade event
XAUUSD
Position opened
Account activity detected, classified, and ready for routing.
What this module is for
Trade Monitoring answers one question: what exactly happened on the account?
The strength is separation. Health tells you whether a machine or terminal is reporting. Price Watch tells you whether a market level was reached. Trade Monitoring stays focused on account activity: openings, closes, partial closes, pending-order changes, protection updates, and profit milestones.
Health
Is the machine or terminal alive?
Trade Monitoring
What changed on the account?
Price Watch
Was a market condition reached?
What we monitor
The trade lifecycle, not just entry and exit.
Good monitoring does not stop at “position opened” and “position closed.” The real operational story is made from smaller lifecycle changes that often matter more than one final result.
Pending orders
Execution intent is visible before it becomes a trade.
Created
Modified
Cancelled
Protection and targets
SL and TP updates become visible as management events.
SL changed
TP changed
Protection reviewed
Profit and loss milestones
Rule-based progress can be surfaced before the position closes.
Profit reached
Loss reached
Next layer
Profit milestones expanded
Profit Rules surface trade progress before the trade is finished.
This is one of the strongest parts of Trade Monitoring. Instead of waiting only for open, modify, or close events, Notify can surface the next meaningful profit or loss layer while the trade is still alive.
- Several milestone layers on the same workflow
- Rules by symbol, account, terminal, or source
- Useful for progress visibility, discipline, and review
Example monitoring ladder
Illustrative only
01
EURUSD · 25 pips profit reached
Early progress becomes visible on a faster intraday workflow.
02
EURUSD · 50 pips profit reached
The next layer triggers only when the trade moves deeper into profit.
03
XAUUSD · account-specific milestone
A larger rule can be isolated to a specific account or terminal.
!
Loss threshold reached
Downside conditions can be surfaced as clearly as upside progress.
Why monitor this
Trade activity often goes wrong in the gap between execution and awareness.
The risk is not only the trade itself. The risk is that something happened and you found out too late, in the wrong place, or without enough context to interpret it quickly.
Unexpected activity needs immediate visibility
A copied trade, manual intervention, platform-side change, or operator action can create an event you did not expect.
Mixed alert streams become unreadable fast
When several accounts and terminals are active, flat notifications stop being operationally useful.
Lifecycle context matters more than raw messages
Opened, partially closed, cancelled, and SL updated are different operational events and should stay distinct.
Clean history supports discipline and review
Structured event history helps confirm what actually happened and compare expected versus actual behavior.
Privacy layers
Different routes can show different levels of trade detail.
Trade Monitoring should not force the same message everywhere. Some routes need full operator context. Others only need enough awareness to know that something changed.
Layer
Visible message style
Best use
Direct operators who need the full picture for fast review.
Broader operational routing where detail should be limited.
Privacy-sensitive routes where awareness matters more than public detail.
Privacy in Notify is practical and structural: visible message content, stored detail, retention choices, and route-specific exposure can be shaped separately.
When we send
Event-driven means Notify sends when the monitored trade event actually happens.
This is not a delayed digest model. Notify surfaces trade events at the point they matter, then applies the route and detail policy you selected.
1
Event happens
Position, order, protection, or milestone state changes.
2
Notify classifies it
The event is structured instead of being treated as raw terminal noise.
3
Policy is applied
Route and detail level decide how the message should appear.
4
You receive usable awareness
Dashboard, mobile push, Telegram, and history stay aligned.
Why Notify differs
Structured monitoring, not another loose stream of trade alerts.
The difference is not only that Notify can send a message. The difference is how the monitoring model keeps trade activity classified, routed, and reviewable when real operations become larger.
One operating layer for trade-event awareness.
Loose alert stream
Notify Trade Monitoring
—
Raw terminal messages
Messages arrive, but the operational meaning is not always structured.
Normalized trade events
Open, close, partial close, pending order, protection, and milestone events stay distinct.
—
Same detail everywhere
Every channel receives the same message, even when the audience needs less detail.
Route and detail policy
Dashboard, mobile push, and Telegram can show the level of detail selected for that route.
—
Mixed with other noise
Account activity, uptime status, and market-level checks can start to feel like one feed.
Separated event types
Trade Monitoring stays separate from Health and Price Watch, so each alert keeps its meaning.
—
Hard to review later
A pile of alert messages does not always explain the account sequence cleanly.
Structured history
The record shows what changed, when it changed, and how it was classified.
Next step
Add Trade Monitoring to your Notify setup.
Use Notify Pro when your setup needs terminal health, trade events, profit rules, price watch, and alert routing in one operational dashboard.