Between October 2025 and June 2026, TradingView added four alert types that watch something other than a simple price or indicator line. They are news alerts (20 October 2025), volume footprint alerts (20 November 2025), TPO alerts (2 February 2026) and valuation-metric alerts (29 June 2026). Each one comes with a caveat worth knowing before you consider it for any automated workflow, and for news alerts the caveat is that no message field or webhook is documented at all.
The short answer: TPO, footprint and valuation alerts are created through TradingView's normal alert system, but each comes with a data-stability caveat, and none of TradingView's pages says anything specific about webhooks for them. News alerts are notifications about stories, with no documented message field or webhook, so there is no documented route from them to PineConnector. This guide covers each type, then puts them side by side.
What changed
- News alerts, announced 20 October 2025 (post updated 22 June 2026), with multiple news alerts added on 11 May 2026. They watch for new stories that match a saved News Flow. One news alert can be active without a subscription; paid plans allow up to 10[7][8][12].
- Volume footprint alerts, announced 20 November 2025 (updated 13 January 2026). They watch imbalances, volume delta and total buy and sell volume. TradingView's pricing page listed volume footprint on its Premium and Ultimate plans when checked on 23 September 2026[3][10].
- TPO alerts, announced 2 February 2026 (updated 11 February 2026). They watch extended levels of completed market profiles. The sources used here do not state which plans include them[1].
- Valuation-metric alerts, announced 29 June 2026 (updated 9 July 2026). They watch 11 valuation metrics such as P/E and market capitalisation, for stocks only, and count toward the technical alert limit[5].
Plan features change, so check TradingView's pricing page for your own account.
TPO alerts: a snapshot of the profile settings
Time Price Opportunity (TPO) charts show how the market builds value over a session. TradingView offers six TPO alert conditions: price crossing an extended POC, VAH, VAL, poor high, poor low or single print[1]. POC is the point of control, and VAH and VAL are the value area high and low.
Three rules shape what these alerts can do:
- Completed profiles only. An alert fires when price crosses a level of a profile that has already formed; the profile still forming is ignored[1].
- Extended levels only. A level must be set to extend in the TPO settings, or it does not appear among the alert conditions[2].
- A snapshot, not a live link. The alert keeps a snapshot of the study's parameters from when it was created. Later merges or splits of profiles are not passed on to existing alerts, which can keep triggering on outdated levels and, in some cases, "may fire for levels that no longer exist on the chart"[2].
After changing a TPO chart's profile structure, recreate its alerts. TradingView says each TPO alert arrives with an automatic message naming the level and symbol[1]. Whether that message can be replaced with your own text, and whether these alerts can send a webhook, is not described in the sources used here.
Volume footprint alerts: repainting by design
Volume footprint charts break each bar into price rows with buying and selling volume. The alert conditions are new or stacked buy imbalances and new or stacked sell imbalances, plus standard operators on Volume Delta, Total Buy Volume and Total Sell Volume[3]. The Help Center lists a default message for each imbalance condition, for example "A new buy imbalance was found.", and says the alerts are "fully integrated into existing alert infrastructure"[4]. It does not describe webhook use for them specifically.
The caveat is explicit: the footprint study "is repainting by design". In real time it can calculate from one intrabar data source, and the same bar can later be recalculated from a coarser interval. The imbalances shown, and the alerts based on them, can therefore differ slightly between real time and later review[4]. The Help Center recommends setting Ticks per row manually and using manual row sizing for alerts, because an ATR-based row size changes with the current ATR value.
For anyone testing a footprint-based rule, that changes the method. Scrolling back through the chart to see where alerts should have fired is not a reliable check. Use the Alerts log timestamps from real-time operation instead. PineConnector's documentation makes the general point that a good-looking historical chart does not confirm that live signals arrive at the same points[11].
Related context for script authors: since January 2026, Pine Script has a request.footprint() function for reading footprint data inside a script, available to programmers on TradingView's Premium or Ultimate plans[9]. A script built on it faces the same real-time versus historical questions.
Valuation-metric alerts: data that can be corrected after it fires
Valuation-metric alerts watch 11 fundamentals: price to earnings, price to free cash flow, PEG, price to book, price to cash flow, price to sales, price to tangible book, buyback yield, earnings yield, dividend yield and market capitalisation. For now they are available for stocks only, each counts toward your technical alert limit, and each is tied to a single symbol[5]. TradingView says they work like alerts on any other indicator, including on watchlists and as presets, and that they trigger on the metric's own value; an alert on the metric crossing the price line is not supported[5]. Notifications are plain English, for example "Price to earnings ratio Less Than 32 on AAPL".
The Help Center adds the caveat that matters for automation: these alerts "may be triggered inaccurately" when price moves quickly after an earnings release, and corrected data appears within a few hours[6]. Anything done on an inaccurate value is not undone when the data is corrected. Treat a valuation alert as a prompt to research, not as an order trigger. If you trade share CFDs on MetaTrader, remember too that the alert is calculated on TradingView's stock data, not on your broker's CFD.
News alerts: notifications, not instructions
A news alert notifies you as soon as a story matching your saved News Flow filter is published[7]. You build the filter from tickers, watchlists, topics or providers, save it, and switch on the News alert toggle. Since 11 May 2026, paid plans can keep up to 10 news flows on alert at once[8]. The Help Center adds that users without a subscription can keep one news alert active, that pop-ups are suppressed for a flow already open on your screen, and that deleting a flow deletes its alert[12].
None of these pages mentions a message field, a webhook or placeholders for news alerts. Without a message PineConnector can read, there is no documented route to execution, and this guide does not suggest one. News alerts are useful for knowing when to look, for example before deciding whether to pause your own automation around an announcement.
Side by side: which of these can feed an automated workflow?
For PineConnector to act on any alert, the chain needs a message in PineConnector's format (LicenseID,Command,Symbol,Parameters) delivered to https://webhook.pineconnector.com[13]. The table checks each alert type against that requirement using only what TradingView documents for that type.
| Alert type | Own message and webhook | Main caveat |
|---|---|---|
| TPO | Not described | Snapshot; later profile changes ignored |
| Volume footprint | Not described | Repaints by design |
| Valuation metrics | Not described | Can be inaccurate after earnings |
| News | None documented | Notification only |
"Not described" means TradingView's pages do not say, not that the feature is missing. It also means the behaviour of one alert type cannot be borrowed from another type's documentation. None of these types was tested with PineConnector for this guide, so no route here is established and no setup recipe is given. How each fits a workflow today:
- TPO and footprint: check the documented caveat before relying on either for anything automated. Recreate TPO alerts after profile changes, and judge footprint alerts on real-time log entries.
- Valuation metrics: a research signal, calculated on TradingView's stock data rather than your broker's CFD.
- News: awareness only; there is no documented route to PineConnector.
If you decide to try one of the first three on demo, run it through PineConnector's demo test workflow first and inspect the actual message in the TradingView Alerts log.
Limitations and common mistakes
- Assuming every alert type behaves like a price alert. TPO alerts keep a snapshot, footprint alerts can disagree with later chart history, and valuation alerts can fire on data that is later corrected.
- Relying on a default message. A default such as "A new buy imbalance was found." is not an instruction PineConnector can read.
- Testing on history. For footprint alerts especially, historical review can show different imbalances from the ones that fired in real time.
- Treating news as a signal. A news alert says a story appeared. It does not say what the market will do, and it has no documented route to PineConnector.
What to check next
- Decide whether the alert is for your attention or for execution. For attention, any of these four types can help.
- For execution, prefer conditions whose behaviour you can verify in real time, and read the caveat for the type you are using.
- If you test one on demo, open the alert's notification settings and message, and confirm in the Alerts log what was actually sent.
- Check that the alert is not on a notification schedule that mutes webhooks outside certain hours (see notification schedules).
Reviewed 23 September 2026. Facts were checked against the linked sources on that date. No alert type in this guide was run against a trading account or tested with PineConnector.
Related reading
- TradingView updates for alert-based automation: a practical index
- TradingView notification schedules: why an alert can fire without sending its webhook
- I changed my Pine Script, but the alert still uses the old settings
- From a TradingView backtest to a verified demo trade
- TradingView webhook received, but no MT5 trade: a stage-by-stage diagnosis
Sources
- TradingView Blog – Stay ahead of market structure with new TPO alerts, published 2 February 2026, updated 11 February 2026, accessed 23 September 2026.
- TradingView Help Center – Time price opportunity charts explained, accessed 23 September 2026.
- TradingView Blog – Stay ahead of market shifts with alerts for volume footprint charts, published 20 November 2025, updated 13 January 2026, accessed 23 September 2026.
- TradingView Help Center – Volume footprint charts: a complete guide, accessed 23 September 2026.
- TradingView Blog – Introducing alerts for valuation metrics, published 29 June 2026, updated 9 July 2026, accessed 23 September 2026.
- TradingView Help Center – Alerts on fundamentals, accessed 23 September 2026.
- TradingView Blog – Real-time news alerts, published 20 October 2025, updated 22 June 2026, accessed 23 September 2026.
- TradingView Blog – Never miss a beat: multiple news alerts are here, published 11 May 2026, updated 13 June 2026, accessed 23 September 2026.
- TradingView – Pine Script release notes (January 2026: footprint requests), accessed 23 September 2026.
- TradingView – Pricing and plan comparison, accessed 23 September 2026.
- PineConnector Docs – Best Practices & Tips, accessed 23 September 2026.
- TradingView Help Center – News alerts, accessed 23 September 2026.
- PineConnector Docs – PineConnector Syntax, accessed 23 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
