ALERTS / DESKTOP, MOBILE & AUTOMATION
Setting Up Alerts
Keep One Million and Swim & Pool within reach. Choose the iETsg0 events you want to follow, receive them on your computer and phone, and learn how to pass selected events to an automated trading service.
Choose how your alerts reach you
An alert starts with a named iETsg0 event. You decide which event to watch and where its message should go. Installing an indicator does not automatically create its alerts.
TradingView runs created alerts on its servers, so they can continue while your computer is off. Your phone still needs connectivity to receive a notification; a bot or bridge must remain available to receive automation messages.
| Destination | What it does |
|---|---|
| Computer | Show a notification and play a sound while you work. |
| Phone | Send a TradingView app notification when you are away from the chart. |
| Automation | Send an event to a webhook receiver that validates it and handles orders through your broker or exchange. |
Before creating your first alert
- Load the correct iETsg0 indicator and confirm your access is active. Finish its settings before creating alerts. Some events depend on enabled features and access.
- Choose the exact exchange, symbol, chart interval, and indicator instance. Two charts with similar symbol names can use different feeds.
- Check the alert allowance, delivery options, and expiration available in your TradingView account. An iETsg0 subscription and a TradingView subscription are separate.
- Start with the events you actually follow. Money, Cloud, Matrix, Rada, Pool, and other chart elements do not each have a dedicated named alert in the supplied versions.
- The catalogs below cover 16 One Million conditions and 10 Swim & Pool conditions in the supplied versions. Compare them with your installed version’s Condition menu; availability can change between releases.
Create an alert step by step
Create a separate alert for each named condition and chart setup you want to monitor. These versions provide individually named conditions; there is no bundled option that automatically subscribes you to all 26 events.
| Step | What to select |
|---|---|
| 1 · Open Create alert | Use the alert control on your TradingView chart. |
| 2 · Choose the indicator | Under Condition, select One Million or Swim & Pool, then the exact event from the catalogs below. |
| 3 · Set the frequency | For a first setup, use Once Per Bar Close when available. Review the timing section below. |
| 4 · Set the expiration | Choose a suitable expiry and keep track of when the alert will stop. |
| 5 · Name the alert | Include the indicator, event, symbol, and interval so you can identify it later. |
| 6 · Choose delivery | Enable Notify on App, Show Pop-up, Play Sound, or Send Email as needed. Add Webhook URL only after preparing a receiver. |
| 7 · Create and verify | Save the alert and check that it is active in the Alerts manager. |
One Million · primary and #2 alerts
Use the exact condition names below. The primary group and the #2 group have separate entry and exit events. An event describes the indicator’s state; it does not confirm that a broker has opened or closed a position.
| Condition | How to use the notification |
|---|---|
| ✈️ iETsg0 LONG | A primary LONG event. Review the primary group on the chart. |
| 🚗 iETsg0 SHORT | A primary SHORT event. Keep its routing separate from LONG #2 and SHORT #2. |
| ❌ iETsg0 TRADE EXIT | An exit event for the primary group. The message does not identify the side; an executor must know its existing primary position. |
| 🛫 iETsg0 LONG #2 | A LONG event for the separate #2 group. |
| 🏎️ iETsg0 SHORT #2 | A SHORT event for the separate #2 group. |
| ⛔ iETsg0 EXIT #2 | An exit event for the #2 group. It must not accidentally close the primary group. |
| 🧯 iETsg0 DrawDown Stop | A condition that depends on the DrawDown feature. This feature is disabled in the supplied version; creating this alert alone does not activate it or place a protective broker order. |
One Million · additional events
These nine conditions provide additional notifications. Similar words or matching colors do not make them interchangeable with the primary or #2 group. Use them to bring your attention back to the chart unless you have explicitly designed and tested another action.
| Condition | What to review |
|---|---|
| ▲ Long | The separate Long event; this is a different condition from ✈️ iETsg0 LONG. |
| ▼ Short | The separate Short event; this is a different condition from 🚗 iETsg0 SHORT. |
| 🚀 Rocket UP | The start of a Rocket UP event and its surrounding chart context. |
| 🔥 Fire DOWN | The start of a Fire DOWN event and the current One Million picture. |
| ⤒ Power Spike UP | The named upward Power event. Check Power alongside Matrix and the other visible elements. |
| ⤓ Power Spike DOWN | The named downward Power event. Review it in context. |
| 🔋 iETsg0 Trust UP | A Trust UP event; review the current Trust reading. |
| 🪫 iETsg0 Trust DOWN | A Trust DOWN event; review how the wider picture has changed. |
| 🛒 iETsg0 Buy | A separate Buy event. Do not treat it as an alias for the primary LONG or LONG #2 condition. |
Swim & Pool · all available events
The four named phase alerts report a change into that phase; they do not repeat simply because the background remains the same. Pilot alerts describe a passage through the middle guide, not every turn or star on Pilot.
The supplied version starts with both entry features switched off. Enable the relevant entry feature in indicator settings before creating its alert. If your installed version uses different labels, confirm the setting with iETsg0 support.
Swim & Pool does not provide a dedicated EXIT condition in this version. An automated setup needs its own explicit exit rules. An opposite Entry message must not silently become a close-and-reverse instruction.
| Condition | What to review |
|---|---|
| Bull | A Bull event in Swim & Pool. Read the current Pool picture alongside it. |
| Bear | A Bear event in Swim & Pool. This alone does not mean all five Pool readings match. |
| 🍀 MARKET UP | A change into MARKET UP. |
| 🚗 MARKET DOWN | A change into MARKET DOWN. |
| 🍌 ACCUMULATION | A change into ACCUMULATION. |
| 🐻 DISTRIBUTION | A change into DISTRIBUTION. |
| Pilot Cross Up Mid | Pilot moves upward through its middle guide. |
| Pilot Cross Down Mid | Pilot moves downward through its middle guide. |
| 🟢 Entry LONG | A named Entry LONG event, dependent on the corresponding entry feature and access being enabled. |
| 🔴 Entry SHORT | A named Entry SHORT event, dependent on the corresponding entry feature and access being enabled. |
Receive alerts on your computer
- Enable Show Pop-up and allow TradingView notifications in your browser and computer settings.
- Enable Play Sound, choose a sound, and check speaker volume, muted tabs, and system notification settings.
- Keep the receiving browser or desktop app available when you want a local notification. A powered-off computer cannot play a sound.
- Use the Alerts log to distinguish an event that triggered from a notification your device did not display. Optionally enable Send Email as another delivery channel.
Receive alerts on your phone
- Install or update the official TradingView app and sign in to the same TradingView account used to create the alert.
- Enable Notify on App on each alert you want delivered to the phone.
- Allow TradingView notifications in your phone settings and check the app’s notification settings, especially on Android.
- If the alert appears in the log but your phone stays silent, check connectivity, Focus or Do Not Disturb, sound settings, and battery restrictions.
- Test with the phone locked as well as unlocked. Desktop delivery alone does not prove that mobile delivery is configured.
Choose when an alert can trigger
Available choices depend on the selected condition. Choosing an earlier frequency does not force an iETsg0 event to occur earlier if that event already waits for the candle to finish. Bar-close delivery is not a promise of an unchanged historical chart or instantaneous delivery.
Alerts watch new live events after creation. A symbol already visible on an older candle is not a test notification and will not be sent retroactively.
| Frequency | Practical meaning |
|---|---|
| Once Per Bar Close | Checks for the condition at the candle’s close. A useful starting choice when you want to review a completed candle. |
| Once Per Bar | Can notify during a developing candle. A condition seen earlier may no longer be present at the close. |
| Only Once | Stops after the first trigger. Use it when you intentionally want a single notification. |
Write messages you can recognize
For a personal notification, include the product, selected event, symbol, and interval. Example alert name: One Million | Primary LONG | BTCUSDT | 15m. Use your actual market and interval.
Example message for the primary LONG condition: iETsg0 | One Million | MAIN_LONG | {{exchange}}:{{ticker}} | Interval {{interval}} | Price {{close}} | Sent {{timenow}}.
TradingView replaces these placeholders when the alert fires. {{time}} identifies the candle’s opening time; {{timenow}} identifies the alert firing time, both in UTC. {{close}} is the chart value at the event, not a broker fill price. Check interval values on nonstandard charts.
Default messages can differ from condition titles and may include emoji. For a bot, define an explicit event name for each condition and use the receiver’s required message format. Do not use a loose search for the word LONG to route all iETsg0 events.
How automated trading connects
Both indicators can supply named events to a webhook workflow. Order placement requires a compatible external bot or bridge, configured for your broker or exchange. Enabling Webhook URL alone does not create that integration.
| Stage | Responsibility |
|---|---|
| 1 · iETsg0 event | The selected One Million or Swim & Pool condition occurs. |
| 2 · TradingView alert | The active alert sends its configured message to your webhook URL. |
| 3 · Bot or bridge | The receiver validates the message, checks its age and identity, and maps it to an approved action. |
| 4 · Broker or exchange | The connected account accepts or rejects the order and reports its actual status. |
| 5 · Monitoring | The executor records the result and checks the real position. A received webhook does not prove an order filled. |
- Obtain the endpoint and message template from your chosen service. Confirm that it supports TradingView indicator alerts and your intended market.
- Enable two-factor authentication on TradingView to use webhooks. Use a secure HTTPS endpoint with the receiver’s supported authentication.
- TradingView sends the alert message by HTTP POST. Valid JSON is sent as application/json; other messages use text/plain.
- The receiver must respond within three seconds. TradingView supports ports 80 and 443; webhook delivery can fail, so inspect Webhook status in the alert log.
- Keep account passwords and exchange API secrets out of the alert message. Store trading credentials securely in the execution service.
Map each event before connecting orders
The following names are example receiver labels, not built-in iETsg0 commands or a universal bot format. Your receiver must explicitly implement them. Use its documentation for the actual payload.
| Selected condition | Example receiver label | Scope |
|---|---|---|
| ✈️ iETsg0 LONG | MAIN_LONG | Primary group only |
| 🚗 iETsg0 SHORT | MAIN_SHORT | Primary group only |
| ❌ iETsg0 TRADE EXIT | MAIN_EXIT | Close only the tracked primary position |
| 🛫 iETsg0 LONG #2 | SECOND_LONG | #2 group only |
| 🏎️ iETsg0 SHORT #2 | SECOND_SHORT | #2 group only |
| ⛔ iETsg0 EXIT #2 | SECOND_EXIT | Close only the tracked #2 position |
| 🟢 Entry LONG / 🔴 Entry SHORT | SWIM_LONG / SWIM_SHORT | Separate Swim & Pool workflow with defined exit rules |
- Record the product, event, group, exchange, symbol, interval, and event time in the receiver. Map chart symbols to the broker’s exact instruments.
- Define position sizing, allowed directions, exit behavior, and what to do when a position already exists. Keep primary and #2 ownership explicit, especially if the account combines positions on one symbol.
- Reject duplicate and stale events. For bar-close alerts, an identity can include the alert setup, event, symbol, interval, and candle time; adapt this if your workflow intentionally accepts multiple events within a candle.
- A directionless EXIT must use the receiver’s tracked position and actual account state. It should not open a new position when no matching position exists.
- Keep Rocket, Fire, Trust, Power, phase, and Pilot notifications informational unless you deliberately assign a tested execution rule.
- Set protective order handling in the execution service or broker. The DrawDown alert listed above does not provide active protection in the supplied version.
Test the complete journey
Only move a workflow out of test mode after its complete entry and exit behavior is verified. Keep a way to pause new automated entries and inspect open positions. Turning off an alert does not close an existing broker position.
| Test | Evidence to check |
|---|---|
| Notification delivery | Use a temporary simple TradingView price alert to check desktop and phone delivery independently, then remove it when finished. |
| Actual iETsg0 event | Wait for a new selected event. Match the alert log to the correct indicator, symbol, interval, and configured frequency. |
| Webhook delivery | Use a receiver in test mode. Check delivery status and the exact message received, including replaced placeholders. |
| Demo execution | Verify the intended instrument, side, size, and order result in a demo environment. Check an exit as well as an entry. |
| Failure handling | Send duplicate, stale, and unmatched exit examples to the test receiver. Verify they do not create unintended orders. |
| Primary and #2 separation | Verify that exiting one group does not close or reverse the other group’s position. |
Troubleshoot a missing or unexpected alert
| What you notice | What to check first |
|---|---|
| No event in the alert log | Active status, expiration, selected condition, symbol, interval, access, and required feature settings. The live condition may not have occurred. |
| Entry alerts never fire | In Swim & Pool, confirm the relevant entry feature is enabled. Both start disabled in the supplied version. |
| DrawDown Stop stays silent | The DrawDown feature is disabled in the supplied One Million version. Alert creation does not enable it. |
| Event logged, phone silent | Notify on App, same account, phone permissions, connectivity, and notification filters. |
| Event logged, computer silent | Pop-up permission, Play Sound, muted tabs, system volume, and desktop notification settings. |
| Webhook failed | Webhook status, public endpoint availability, authentication, supported port, and response time. |
| Webhook received, no order | Receiver validation, message format, symbol mapping, account permissions, and broker rejection logs. |
| Wrong or duplicate orders | Overlapping active alerts, ambiguous event routing, primary/#2 mapping, and duplicate handling. |
| Alert differs from the chart | The saved alert setup may differ from the current chart; also compare frequency and whether the candle was still developing. |
Keep your alerts current
TradingView saves a snapshot of the indicator and its settings when an alert is created. Changing chart inputs, symbol, interval, or the indicator version does not update that saved setup. Recreate affected alerts after those changes, and disable the old copies to avoid overlap.
Review active alerts and expiration dates regularly. Keep a small record of each alert’s indicator version, settings, destination, and test result. Review the bot’s real position separately from the indicator’s displayed state.
This guide covers the two supplied iETsg0 versions and TradingView documentation reviewed on 13 September 2026. If a condition or setting differs in your installed release, confirm that release before relying on its alerts.
Need help? Contact support.