Alerts
The Price Action Concepts™ can alert users for multiple conditions relevant to the existing features in the toolkit. To learn more about how to set alerts in general see:
In order for an alert to work in the toolkit make sure the related feature is enabled
Any Alert() Function Call
Users can create a single alert for multiple conditions using the any alert() function call alert condition. Conditions users want to be alerted for are grouped by the type of features they affect (structures, volumetric order blocks, imbalances…etc) and are located at the bottom of the toolkit settings.
Once conditions are toggled on users only need to set an alert using the any alert() function call as condition.
Any Alert() Function Call Message
Users can set a custom message that will be used when an any alert() function call condition is triggered in the message field below the list of conditions. Users can use placeholders to customize messages and return useful information, the following placeholders are supported:
Symbol Placeholders
| Placeholder | Description | Example |
|---|---|---|
{default} | Default message associated with the trigerred condition | "Mitigated Bullish Imbalance" |
{ticker} | Symbol ticker without the exchange prefix | "MSFT" |
{exchange} | Symbol exchange/data source | "COINBASE" |
{sector} | Sector of the symbol, na if the symbol has no sector | "Technology Services" |
{market} | Symbol market type | "Stocks" |
Time Placeholders
| Placeholder | Description | Example |
|---|---|---|
{tf} | Chart timeframe, includes “S” for seconds, “D” for days, “W” for weeks, “M” for months | "15" |
{time} | Unix time in milliseconds in exchange timezone | "1705331385158" |
{year} | Current year in exchange timezone | "2024" |
{month} | Current month in exchange timezone | "7" |
{day} | Current day of the month in exchange timezone | "21" |
Data Placeholders
| Placeholder | Description | Example |
|---|---|---|
{open} | Opening price | "1.2145" |
{high} | High price | "1.2357" |
{low} | Low price | "1.1983" |
{close} | Closing price | "1.0569" |
{volume} | Current volume | "45216" |
{ob_buy_volume} | Most recent order block internal buy volume | "560" |
{ob_sell_volume} | Most recent order block internal sell volume | "480" |
{ob_volume} | Most recent order block total internal volume | "1040" |
Format as JSON
Use the following message template to receive “any alert() function call” messages in the JSON format:
{
"alert": "{default}",
"ticker": "{ticker}",
"tf": "{tf}",
"ohlcv":{
"open": {open},
"high": {high},
"low": {low},
"close": {close},
"volume": {volume},
"order block buy volume": {ob_buy_volume},
"order block sell volume": {ob_sell_volume},
"order block total volume": {ob_volume}
},
"bartime": {time}
}
Custom Alert Creator
Users wishing to construct more complex alerts using features within the toolkit and/or external indicators can use the Custom Alert Creator.
The custom alert creator allows alerting when various user-set conditions are met or when a sequence of conditions is complete.
A user wishing to be alerted when any internal market structure occurs within 1AM and 5AM of the symbol timezone could do it as follows:
A custom alert can be triggered as an any alert() function call if the setting is selected or as a regular alert when selected in the Tradingview alert creator menu.
Steps
Steps allow creating a sequence of conditions, which when met trigger an alert. When a condition with a step equal to 1 is met the next condition associated with step 2 will be evaluated (if enabled) and so on for higher steps (if any).
Conditions with the same associated step will require both conditions to be true in order for the condition associated with a higher step (if any) to be evaluated. This allows certain conditions to act as filters.
A user wishing to be alerted when the price enters a bullish imbalance after any internal bullish market structure could do it as follows:
Make sure internal market structures and imbalances are enabled.
Make sure steps are set such that they form a linear sequence. For example, if the lowest step is 2 or if the set steps are only 1 and 3 an error will be returned.
OR Step Operator
The “OR” step operator can be used to get alerted for any additional condition using “OR” as a step, in addition to other set custom alert conditions.
Conditions using the “OR” step can be highlighted using a different color, which can be set from the Custom Alert Creator settings.
All Step Operator
The “All” step operator can be used to filter any set “Step” condition, including “OR” and “Invalidate”.
This step operator can be useful if all the steps in a sequence needs to obey a specific rule.
If a user has 2 steps set, and requires both of these to occur at a specific time interval such as 9am to 1pm, then we can use a “Session” condition using the “All” step, requiring our step 1 and step 2 to be occur between 9am and 1pm.
Invalidate Step
The “Invalidate” step allows to set a condition as an “invalidation condition”. When this condition is triggered while a sequence of conditions is incomplete, the sequence will restart at step 1.
If multiple steps are set as “Invalidate” any of the conditions being true will reset the sequence of conditions, as such not all of them are required to be true for the sequence of conditions to reset.
Example
Let’s take an example where we use 2 regular steps and one “Invalidate” step. The alert will trigger when step 2 trigger after step 1 has been triggered.
Step 1
Step 1 condition trigger, we will now evaluate step 2 from now on.
Invalidation Step
Invalidation step condition trigger, we reset the sequence and evaluate step 1 just after.
Invalidation Behaviors
Invalidation behaviors allows adding more restrictions to a sequence of conditions, users can use two different invalidation behaviors described below:
Invalidate On Step 1
The “Invalidate On Step 1” behavior allows to reset an incomplete sequence of conditions when the condition on step 1 trigger. This prevents the first step condition from happening in between other steps of the condition sequence.
This behavior is useful when the first step of our sequence of conditions needs to never be repeated during the sequence.
Example
Let’s take an example where we use 3 regular steps.
Step 1
Step 1 condition trigger, we will now evaluate step 2 from now on.
Step 2
Step 2 condition trigger, we will now evaluate step 3 from now on.
Step 1 Trigger
Step 1 condition trigger, we start evaluating step 2 from now.
Invalidate On Any Repeated Step
The “Invalidate On Any Repeated Step” behavior allows to reset an incomplete sequence of conditions when a step is triggered such that it does not respect the set order of conditions.
This behavior is useful when we want a perfectly ordered sequence of conditions to complete, without any step repeating itself.
Example
Let’s take an example where we use 3 regular steps.
Step 1
Step 1 condition trigger, we will now evaluate step 2 from now on.
Step 2
Step 2 condition trigger, we will now evaluate step 3 from now on.
Step 1 or 2 Trigger
Step 1 or 2 conditions trigger, we start evaluating step 1 from now.
Maximum Step Interval
Users can determine what is the maximum allowed horizontal distance (in bars) between two steps by enabling the “Maximum Step Interval” setting. This allows restricting steps separated by a large amount of bars.
If the amount of bars since a step exceed the set threshold, then the conditions sequence is reset, and we start evaluating from step 1 again.
Highlight Custom Alert Triggers
When a custom alert condition is set, a visual element is displayed at the bottom of the chart in order to more easily visualize when the custom alert condition occurs (displayed by default).
Was this page helpful?