Alerts separation by type
According to resource requirements, all alerts are divided into 3 types: Price and Technicals and Watchlist.
(detailed lists of alerts related to each category are given at the end of the article).
Each type has a separate limit on the number of active alerts, for example, with this limit:
Active price alerts | 400 |
Active technical alerts | 400 |
Active watchlist alerts | 5 |
You can run no more than 400 price alerts and no more than 400 technical + 5 watchlist ones (in this case, you can run 805 alerts in total).
![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/43536487339/original/pu6B3Pc9xaOnePzctj-6Uajs5VHVJYtl4Q.png?1737634855)
The current limits for each plan can be seen on the GoPro page in the alerts section:
https://www.tradingview.com/gopro/#compare
Price Alerts
An alert is considered Price when the following two conditions are met:
- only a symbol is used in the alert (for any type of chart: Bars, Renko, PnF, etc) and a price value
- one of the following is selected as the trigger condition:
- Crossing
- Crossing Up
- Crossing Down
- Greater Than
- Less Than
For example, an alert on a Renko chart would be considered Price:
![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/43536487553/original/haiaHTsR3Hcwm4pbA-HX4jlt9jsFdy6PWA.jpg?1737634902)
as well as an alert on the spread symbol:
![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/43536488728/original/bJpreuUj_lVPz1pBWNOqMHXkjSjq6ALEMQ.jpg?1737635187)
Technical alerts
An alert is considered Technical if any of the following conditions are met:
- the alert uses an overlay symbol, indicator, drawing or strategy
- one of the following is selected as the trigger condition:
- Entering Channel
- Exiting Channel
- Inside Channel
- Outside Channel
- Moving Up
- Moving Down
- Moving Up %
- Moving Down %
for example, such an alert will be considered technical, because it is based on the script:
![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/43536504358/original/5jL0nYlJfklcQHcDfFsdm7rYX0LL2_3aFg.jpg?1737638930)
![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/43394862229/original/8D3WxYKNv6Xu6EtPzphJ11nmIMKt9e1L9A.png?1677681741)
as well as such an alert, because it is created on the Moving-condition:
![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/43536488807/original/LZYS69yYG1nH2gAPKWOl8uuG4zOLsrgGGg.jpg?1737635199)