Analyst Ratings

One of our most popular dataset is the sell side analyst ratings feed. This is a feed of recommendations / ratings issued by sell side analysts in prominent investment banks such as Goldman Sachs, J.P. Morgan, Wedbush, Needham and many more (~850 research firms)

The Analyst Ratings data is uploaded to Snowflake or FTP in hourly files, each hourly file contains the following fields:

• DetectionTimestamp – the timestamp on which the rating was analyzed by our engine.
• RatingDate – the date on which the rating was issued.
• FirmID – the ID of the firm for which the analyst works
• AnalystID – the ID of the individual analyst, or -1 if we do not know the specific analyst that issued the rating.
• Action – the action taken by the analyst, could be one of the following values:
o Initiated Coverage – analyst began covering the stock.
o Resumed Coverage – analyst resumed his coverage of this stock.
o Upgraded – analyst has upgraded his previous rating.
o Downgraded – analyst has downgraded his previous rating.
o Maintained – analyst maintained the same rating (typically with a price target change)
• Rating – the rating issued by the analyst, can have one of the following values:
o Buy
o Hold
o Sell
• PrevPriceTarget – the previous price targets the analyst had for this stock.
• NewPriceTarget – the current price targets the analyst forecasts.
• Ticker – the ticker symbol of the equity.
• ISIN, FIGI, GlobalFIGI, CompanyName – various identifiers of the security
• ISOMIC – The ISOMIC of the exchange in which the security is traded.
• PrimaryExchange – whether this is the primary market in which the stock is traded (1) or a secondary market (0).
• Country – the country in which the security is traded.
• RatingID – the internal identifier of this rating.
• ArticleID – the internal identifier of the article ID in which the rating was detected, or -1 if it was not detected on an article (e.g., a report sent directly to TipRanks by the analyst).
• SourceID – the identifier on the site on which the article was detected.
• DaysFromRatingDate – denotes the day difference between the RatingDate and the DetectionTimestamp. This enables skipping records where the delta is significant.

While we strive to have all the ratings on the day they were issued, there are many cases where we add ratings retrospectively. These cases can include:
• Articles published about historical ratings being analyzed by our system.
• Reports being sent to TipRanks with a delay.
• Adding a new source and back scanning previous ratings on this source.
The field DaysFromRatingDate enables skipping some ratings with very large delays for backtesting simulations.