How to Set Volume Profile Level Alerts: POC, VAH and VAL
Monitor POC and value-area levels using documented Auto Key Levels alerts or explicit fixed prices, with clear profile-period and data limits.
Setup Steps
Choose the profile period and level
Decide whether you mean a completed prior session, the developing current period or a fixed range. Record the session, price-row settings and value-area percentage. POC is the highest-volume row; VAH and VAL bound the selected volume area. A visible-range profile changes with the viewed range.
Use the documented Auto Key Levels workflow
TradingView’s Auto Key Levels indicator documents POC, VAH and VAL alerts for current, previous and custom periods. Add it, enable the particular levels in its inputs, then open Create Alert and select Auto Key Levels. A disabled level can still appear in the dialog but will not calculate or trigger.
Choose a dynamic level or a fixed-price fallback
Select the enabled level and the desired price comparison. If you instead copy a profile value into a normal price alert, name it with the profile date: it is a fixed number and will not follow later recalculation. Do not assume every Volume Profile variant exposes identical alert plots or that a custom estimate matches the built-in profile.
Save the alert context
Choose the frequency, expiry and notification method in your account. For a rule defined on completed candles, select Once Per Bar Close where available. Record the symbol, timeframe and inputs. Recreate the alert after changing the script or its inputs; the running alert retains its saved configuration.
Verify delivery on new market data
Treat chart inspection and delivery as separate checks. Bar Replay can help inspect historical plots, but server alerts continue using live data. Check a new event against the alert log, then check the chosen notification channel. This is a test procedure, not a claim that delivery or investment performance has been tested here.
Alert Conditions Reference
Conditions to define and verify for the selected indicator.
| Condition | Signal | Notes |
|---|---|---|
| Price crosses a selected VAH | Price moves through the chosen upper value boundary | This is an interaction with a specified profile, not proof of acceptance above it. |
| Price crosses a selected VAL | Price moves through the chosen lower value boundary | Record whether the profile is complete or developing. |
| Price crosses a selected POC | Price revisits the selected highest-volume row | A crossing does not encode a bounce, rejection candle or low-risk entry. |
| Manual fixed-price level alert | Price reaches a number copied from a profile | Update it intentionally when the research reference changes; it is not a dynamic indicator link. |
Parameters to record and evaluate
Examples describe the configuration, not validated trading settings.
| Parameter | Starting value or requirement | Description |
|---|---|---|
| Profile period | Choose explicitly | Current, previous and custom periods answer different questions. |
| Value area | 70%, common convention | It selects a share of observed volume; it does not define intrinsic fair value. |
| Rows / price increments | Record the selected method | A row count does not imply a fixed number of futures points without the covered price range. |
| Level calculation | Enable the required input | Auto Key Levels needs the selected level enabled to calculate and alert on it. |
FAQ
Alert Setup FAQ
Do all Volume Profile variants support the same alerts?
Does a fixed-price alert follow the developing profile?
Is an approximate custom volume profile equivalent to exchange order flow?
Can a POC touch guarantee a profitable bounce?
Does scrolling change every server alert?
Need a custom alert rule?
Describe the condition in Pineify’s coding agent, then review the generated Pine Script and test its timing and delivery in TradingView.
Explore Pine Script coding