Anchored volume profile: event choice, endpoints and drift
Anchored volume profile groups volume by price from a chosen starting point through the available bars. It describes participation since that event. As the endpoint advances, the busiest price row can change even when the anchor stays in place.
Short answer
Choose an event using information available at the time, record when that choice became knowable, and keep its anchor fixed. Use an expanding endpoint to follow the developing distribution. Use a fixed endpoint to preserve a completed observation before testing later reactions. Record both settings and timestamps so a later profile cannot replace earlier evidence.
Start
One documented event coordinate
Native AVP endpoint
End of available bars
Comparison control
Fixed endpoint and row settings
Main bias
Choosing an anchor after the outcome
One event, two endpoint policies
Keep the event and calculation settings the same. The endpoint determines which observations enter the measurement and when its levels may be used.
| Policy | What it measures | Rule for later evaluation |
|---|---|---|
| Expanding endpoint: anchored volume profile | Volume from the event through the latest available bar | Save each observation at its timestamp; evaluate later bars against the level actually recorded then. |
| Fixed endpoint: completed event window | Volume between the same event and a chosen cutoff, using fixed range with Extend Right disabled | Keep both coordinates unchanged; begin evaluating reactions only after the cutoff is complete. |
| Fixed range with Extend Right enabled | A range whose calculation continues beyond its original second coordinate | Treat it as developing. Extending the calculation differs from merely displaying an old level farther right. |
A repeatable chart workflow
- 1
Record the event and its availability
Write the anchor timestamp, timezone, event rule, and the first time the rule was satisfied. A swing point confirmed two bars later cannot supply a live signal on the swing bar.
- 2
Choose the endpoint policy
Select Anchored Volume Profile in the drawing toolbar and place the start. For a completed comparison, use fixed range with the same start, a stated cutoff, and Extend Right disabled.
- 3
Keep a comparable measurement
Record symbol and venue, chart timeframe, session coverage, row layout, ticks per row or row count, value-area percentage, and the earliest covered bar. Save a screenshot before changing a setting.
- 4
Save observations before reviewing reactions
At each planned close, record POC, VAH, VAL, and the current endpoint. Define the next observation time and the condition that ends the study. Preserve unsuccessful anchors in the same log.
Notes from chart review
- Separate the timestamp of the event from the timestamp when it became identifiable. A retrospective label belongs in a review, not in the original decision record.
- Keep the first screenshot when an anchor is revised. Record the new reason and treat the revised anchor as a separate study.
- When a level moves, first check whether the endpoint, row grid, session coverage, or data resolution also changed.
Choose an anchor that could have been named then
An anchor is a sampling decision. A scheduled release, an opening gap, and a confirmed breakout answer different questions. Write the rule before comparing their profiles; choosing whichever start produces the neatest later bounce selects the result you hoped to find.
Hypothetical five-minute example: a candidate low is on the 10:00 bar. Your pivot rule requires two completed bars to its right, so confirmation arrives at the close of the 10:10 bar, at 10:15. You may then study volume beginning at 10:00, but the decision record starts at 10:15. A reaction at 10:05 was unavailable to that confirmed-pivot rule.
A session low is also provisional until the session ends. For an intraday study, specify a running-low rule and log every replacement, or wait for the close. Do not label the final low as an event known at the open.
Recalculate POC drift without changing the anchor
This invented example isolates added volume: three unchanged $1 price bins, complete coverage, and no rebinning. At cutoff A, the bins $100 to below $101, $101 to below $102, and $102 to below $103 contain 200, 500, and 300 volume units. Total volume is 1,000; the middle bin is POC. Use bin centers consistently, so its reported reference is $101.50.
Between cutoffs A and B, the bins receive 50, 100, and 600 more units. The expanding profile now contains 250, 600, and 900 units, totaling 1,750. Its POC is the upper bin at $102.50: a $1.00 upward change, or one row. The profile frozen at A still has POC at $101.50. Both are correct for their own endpoints.
The added volume totals 750, and 600 / 750 = 80% of it entered the upper bin. That explains the change in this example. It does not demonstrate buying pressure or establish a trade. A reaction between A and B must be assessed using the snapshot available before that reaction, not the final $102.50 level.
- Snapshot A: endpoint A; total 1,000; POC row $101 to below $102; reference $101.50.
- Snapshot B: endpoint B; total 1,750; POC row $102 to below $103; reference $102.50.
- Fixed comparison at B: endpoint still A; total 1,000; reference still $101.50.
Row size and data coverage can change the comparison
With Number of Rows, an expanding price span can change the ticks grouped into each row. With Ticks Per Row, row height is fixed while row count can grow. For example, a $0.25 tick and four ticks per row give a $1 price height. Record the actual row boundaries too; the same height alone does not prove that two grids align.
The horizontal width of the histogram controls its appearance; the vertical price height controls which prices share a row. Do not record only a screenshot width percentage when documenting the calculation.
TradingView selects a calculation timeframe for AVP based on the length of its range. When lower-timeframe history is unavailable, it can fall back to chart-resolution data. A longer range can therefore change both the included volume and its resolution. Mark the calculation resolution as unknown when it cannot be verified; a finer-looking histogram does not restore missing data.
Matching endpoints do not guarantee identical AVP and fixed-range histograms: their resolution-selection rules can differ. Record the tool type as well as its settings, and use snapshots of the same tool when isolating endpoint drift.
Keep the venue, trading session, and volume unit consistent. Stocks use trade volume; some markets use tick counts, and crypto can use base or quote volume. Non-standard charts can distort price and volume. An empty feed is missing evidence, not proof that nobody traded.
Keep a record that survives the next chart reload
Use one record per observation: event reason, anchor time, known-at time, endpoint, timezone, symbol and venue, session coverage, chart timeframe, calculation resolution if known, row method, actual price height, value-area percentage, POC, VAH, VAL, and screenshot. Add the next review time and a stop condition, such as the next scheduled event or a predetermined number of sessions.
Record the change in each level as current value minus prior recorded value, but compare only compatible settings. If a data correction or a changed grid prevents that comparison, mark it separately rather than calling it market migration. Saving only the final chart loses the sequence needed to judge the original rule.
Use Pineify for a helper and a review record
Pine Script AI Coding Agent can help write an overlay or alert rule from explicit inputs. For a frozen-profile study, supply the recorded POC, VAH, VAL, and their availability time. Pine scripts cannot read a manually drawn TradingView profile, so those values need manual inputs or a separately implemented calculation whose assumptions you can inspect.
Use Trading Journal notes and screenshots to preserve the event hypothesis, the settings, and the later review alongside a trade. Save the original observation before adding the outcome. Neither code generation nor a journal can recover unavailable volume history or turn a hindsight-selected anchor into a live signal.
Describe a frozen-level chart helper
This is a specification to review with the coding agent, not a ready-made profile calculation or a tested trading strategy.
Create a Pine Script v6 overlay with manual inputs for recorded POC, VAH, VAL, and the timestamp when those values became available. Require VAL <= POC <= VAH. Plot the levels only from that timestamp onward. After a previous close at or below VAH, alert on a later confirmed close above VAH. Do not evaluate earlier history using these inputs. Label this as a manual frozen-profile helper; do not attempt to read chart drawings or claim to reconstruct the native volume profile. Explain alert setup and how changing inputs affects historical displays.Build a chart helper with Pineify
Continue the volume analysis
Tools for the next check
Volume Profile Analyzer
Estimate POC and value-area levels by distributing uploaded OHLCV volume across each bar’s range. Compare the approximation with TradingView profile methods.
Volume Profile Calculator
Group entered volume-at-price rows and calculate POC and value-area reference levels. Inspect rounding, tie rules and the achieved volume percentage.
Fixed Range Volume Profile
Set reproducible range anchors, read POC and value-area levels, and turn a fixed range volume profile observation into a testable rule.
Order Flow Volume Profile
Separate historical volume-at-price structure from live order-flow evidence, data proxies, and bid/ask confirmation.
Pine Script Indicator Generator
Explore Pine Script indicator generation and review the resulting code for your TradingView chart.
Sources and calculation notes
Frequently asked questions
This educational workflow is not investment advice. The numeric example is invented to explain changing endpoints. Profile levels describe the selected data and do not guarantee support, resistance, or profitable trades.