Is TradingView Ghost Feed a live data feed?

No. Its candles are a drawing of a hypothetical scenario. Read actual prices from the market series and keep those observations separate in your review.

Can I backtest the candles I draw with Ghost Feed?

Ghost Feed does not replace chart OHLC data for Strategy Tester or Bar Replay. To test a rule, define its conditions explicitly and evaluate them on the relevant market history.

Can Pine Script read my Ghost Feed drawing?

No. TradingView documents manual chart drawings and Pine drawing objects as separate entities. A script needs explicit inputs or its own calculation rather than access to your manual drawing.

Can I create an alert on Ghost Feed candles?

Ghost Feed is not listed among TradingView supported drawing alerts. Define a separate market-price or script condition, and check whether it evaluates intrabar or only on a completed bar.

What if the final price reaches the target after invalidation?

Retain the invalidation when your original rule makes failure terminal. In the worked example, the 98.50 close invalidates version A even though the following close reaches 103.50. Any revised scenario needs a new timestamp.

TradingView workflows

TradingView Ghost Feed: scenario sketches without fake backtests

TradingView Ghost Feed draws hypothetical candles along a direction you choose. It does not supply future market data. Use it to illustrate a written scenario, save the original chart and timestamp, then compare later market observations with that unchanged record. A convincing sketch is not a backtest or evidence of forecast accuracy.

See the decision guide

Create and identify the drawing

On the left drawing toolbar, open Forecasting and measurements tools and select Ghost Feed. Choose a starting point and map the intended direction. Double-click the ghost candles to open settings. TradingView recommends standard candles for this tool.

Use a visibly different drawing color and add a separate text annotation: HYPOTHETICAL, scenario ID, creation time and expiry. Do not rely on color alone.
Save a screenshot before any later bars arrive. Lock is an editing aid, not an immutable audit record.
For illustration, 80 minimum ticks × an assumed 0.01 price unit per tick = 0.80 price units. Record the actual instrument tick size; this setting supplies no probability or confidence interval.

Control	What to record
Inputs	Avg HL in minticks and Variance: candle range and spacing controls.
Coordinates	Starting price and bar position.
Style	Body, border and wick colors, plus transparency.
Visibility	The intervals where the drawing appears.
Right-click menu	Lock prevents accidental dragging; Object Tree groups drawings.

Freeze a baseline that another person can locate

Use the most recent completed bar as t0, then separately record when you created the sketch. A chart bar timestamp and your decision timestamp are different fields. If a new bar has already begun, the record must say what information was visible when you made the decision.

Count future completed bars on the frozen interval. Three bars does not always mean three calendar periods because sessions and gaps matter.
Use the written checkpoint prices as the comparison values. A pixel position or a wick that looks close is not a numeric observation.
If the feed is delayed, preserve that fact. Do not label the sketch as preceding a market event merely because that event was not yet visible in your feed.

Baseline field	Required entry
Chart identity	Exchange-qualified symbol, interval, standard candles, session and adjustment settings.
Information cutoff	t0 bar timestamp, timezone, completed close and data delay status.
Decision time	Creation timestamp with timezone; note any partially formed bar already visible.
Sketch definition	Starting coordinate, path checkpoints, drawing inputs and original screenshot reference.
Evaluation rule	Price source, close versus intrabar test, horizon, failure precedence and missing-data policy.

Worked scenario: the rebound does not erase the failure

This invented exercise uses a t0 close of 100.00 and three future completed bars. The sketch has close checkpoints of 101.00, 102.00 and 103.00. Define completion as a close at or above 103.00 by t+3, provided no earlier close is below 99.00. A close exactly at 99.00 does not fail this rule. Once invalidated, the scenario stays invalidated.

Original schematic, not a TradingView screenshot. All prices are invented. Hollow candles show the frozen hypothesis; the separate filled candles illustrate later observations. View original source

Signed checkpoint error is observed close minus sketch close: -0.50, -3.50 and +0.50 price units. These are path errors, not trading profits or losses.
If every close stays at or above 99.00 but none reaches 103.00 by t+3, record expired, target not reached. A missing required observation produces an incomplete record, not a success.
The hypothetical endpoints and candle shapes are study inputs. They do not estimate the likelihood of this path or specify an executable entry, exit, size or fill.

Checkpoint	Frozen sketch close	Illustrative observed close	Record after bar closes
t0	100.00 baseline	100.00	Archive version A; no future observations yet.
t+1	101.00	100.50	Below sketch by 0.50; still active.
t+2	102.00	98.50	Below sketch by 3.50; first invalidation.
t+3	103.00	103.50	Above sketch by 0.50; version A remains invalidated.

Review actual candles without rewriting the forecast

Keep version A and its original screenshot unchanged. At each checkpoint, capture a new image and append the observed value and classification. The table above can be copied into notes with its observation cells left blank at creation. Label the values as actual only when they come from the market series you recorded.

Temporarily hide the drawing when reading market OHLC values, then restore it for a separate comparison screenshot. Preserve both images with their timestamps.
If the symbol, interval, session or adjustment basis changes, reconcile the data before comparing. Do not quietly substitute a more favorable series.
A revised outlook gets version B, a new creation time and a reason for the revision. Keep the failed version in the review sample.
A drawing positioned over known history is a retrospective illustration unless you have a record proving when the hypothesis was made. Moving it backward does not turn it into an earlier forecast.
If a provider later corrects a bar, retain the originally observed value and append the corrected value with its retrieval time.

Ghost Feed, alerts and backtests use different inputs

Pine Script cannot interact with manual chart drawing tools. A script therefore cannot read Ghost Feed candles as OHLC, obtain its anchor automatically, or treat its path as a strategy input. Encoding the written rule with explicit numbers is a separate implementation that must be tested on market bars.

An intrabar price alert below 99.00 is not the close-below-99.00 rule in this exercise. Review the completed close or use a separately coded confirmed-bar condition.
Do not interpret a notification as an order or a verified fill. This scenario review does not configure trade execution.

Task	Supported input and boundary
Visual scenario	Ghost Feed supplies a drawing. No executions or return series follow from the sketch.
Historical practice	Bar Replay reveals recorded market history. A Ghost Feed overlay does not replace those bars.
Strategy Tester	A Pine strategy and broker emulator simulate trades on chart data. Manually drawn candles do not become the dataset.
Alert notification	Use a separately defined price or script condition. Ghost Feed is absent from the official list of supported drawing alerts.

Save the plan and review notes in Pineify

Trading Journal supports written plans and diary notes. Save the scenario ID, baseline, rules and original screenshot reference in the plan, then append observations in diary notes. Store image files separately and include their file references or share links; this workflow does not assume automatic drawing import or market synchronization.

AI Chart Analysis accepts chart images. For a review, supply an image whose hypothetical area is visibly labeled, or hide the sketch and submit the market-only view.
Use screenshot analysis to discuss visible features, then check quoted prices against the chart. An image alone cannot establish when a prediction was made, recover an unseen price history or verify a fill.
Keep scenario review separate from trade performance. Neither a journal entry nor AI commentary establishes profitability, and this workflow does not place trades.

Where Pineify fits

Trading Journal

Keep the original scenario in a written plan and add later observations in diary notes, including failures, revisions and missing data.

Also useful: AI Chart Analysis. Review a chart image with the hypothetical area clearly labeled. Check the interpretation against your recorded market observations.

Explore Trading Journal

Related resources

TradingView workflows Historical Bar Replay practice TradingView trade journal workflow AI Chart Analysis

Frequently asked questions

Educational information, not investment advice. All example prices and candle shapes are invented. Scenario sketches, screenshot analysis and journal records do not establish forecast accuracy, executable fills or future returns.

Sources and verification

Last verified: 2026-10-18

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.