Most triggers in Brokerpilot respond to what happens. Account State Events responds to what the account has become. It is not about catching an action — it is about catching a condition. And conditions are often more dangerous than actions, because they build up quietly until they matter.
This is why the team calls it a super-trigger. The settings don't ask you to define an event. They ask you to define a state — and then tell you when that state has been reached.
What kind of conditions can you track
Margin level dropped below a threshold. Floating profit exceeded a certain amount. A single trade produced more profit than it should. The account has been inactive for a defined period. These are four very different situations — and all of them can be set up as separate rules within the same trigger.
The list of trackable conditions is extensive. If there is a state you want to monitor on a specific account or group of accounts, the trigger almost certainly supports it.
Rules that stack
One account can appear in multiple rules at the same time. An account flagged for low margin can simultaneously be tracked for unusual profit on a single trade. A group of accounts can share one rule while individual accounts within that group have their own additional conditions.
This is what makes Account State Events different from a standard alert. It is not a single check — it is a layered monitoring framework that the dealer configures around the specific situations that matter for their dealing environment. The more precisely the rules are defined, the less noise the dealer has to manage.
Book a presentation → to see Account State Events configured on a live dealing environment.
