A number in a research note is only as defensible as the record behind it. When compliance, a client, or a portfolio committee asks where a price target came from and when, “the data vendor said so” is not an answer. Every figure needs a source and a date you can point to.
AnaChart’s analyst price target data carries that trail on every row: the issuing analyst, the firm, the exact date, the price at issue, and a source reference for the action, across 661,383 price targets and 759,654 ratings.
What “auditable” means here
- Who and when. Every target and rating ties to a named analyst, a firm, and the precise issue date.
- What it looked like then. The price at issue and the previous target are preserved, so you can show the state of the record on any past date.
- Where it came from. Each action carries a source reference, so a figure traces back to its origin rather than to an opaque aggregate.
Why aggregates fail the test
A blended consensus number is convenient and undefendable: it cannot tell you which analysts moved, when, or by how much. The moment someone needs the provenance, a single figure with no history behind it falls apart. A point-in-time, survivorship-free record does not, because the trail is the data. For how the same record scores each analyst’s accuracy, see the accuracy data.
Delivered where your controls live
The data arrives as a native Snowflake or BigQuery share, so the audit trail sits inside the same governed environment as the rest of your data, queryable and versioned. The queries that assemble a defensible view are on the use-cases page.
See the trail on one name
The free Apple sample shows the full per-analyst record with dates and price-at-issue for AAPL. Request the AAPL sample, or ask about the full dataset.
FAQ
Can I trace a single price target back to its source?
Yes. Each action carries the analyst, firm, exact date, price at issue, and a source reference, so an individual figure is traceable rather than blended away.
Does the record show prior values?
Yes. The previous target is kept, not overwritten, so you can show what the record looked like on any past date.
How is it delivered for a governed environment?
As a native Snowflake or BigQuery share inside your own account, or a custom one-time file, so it sits within your existing controls.