What-needs-to-be-done-to-display-AnalystScore

I'm a little confused. In order to backtest with the analyst rating, you need to have that rating given over time because it's constantly changing. Do you know of any datafeed API that provides this kind of event data over time?

If you don't care about backtesting with the analyst rating, you can probably simply use the broker's trading app to access the latest rating--for the moment--but I don't know any broker that provides this data over time (for backtesting).

Below is a screenshot of the watchlist for the Fidelity Trader+ app.

Re: Post #1. Of course it's "over time".

Re: title post. Quoting the Fundamental extension's description:

QUOTE:
Indicators

AnalystScore - Returns an average of individual firms' Analyst Ratings, with an optional N-year roll off period. Values range from 3 (strong buy) to -3 (strong sell). You must have an Event Provider such as Yahoo or MarketBeat enabled that delivers Analyst Rating Events.

The two pull the analyst ratings as historical series, powering the indicator.

At least for me MarketBeat looks broken (uncheck that one for now).
Instead, select Event Providers > Yahoo. Analyst Ratings are working there, which will be used by the AnalystScore indicator.

The only difference I can see is that you're using the wrong color theme!

Check for messages related to events in the Log Viewer.

I see Yahoo is returning a "content is currently unavailable" for our call to Analyst Ratings. Will monitor.

Re: Post #3. MarketBeat has improved their protection with a CF challenge and another layer. To overcome it, a headless browser is required, blowing the extension's footprint up by 100-200 MB.

There is nothing in the Log Viewer.

I haven't tested it altogether but Yahoo seems to be returning the data (raw HTML) for analyst up/downgrades as before - like nothing's broken.

@Glitch. As a cheap alternative to MarketBeat, Zacks could be explored - but its history depth clearly falls short of the failed provider's.

QUOTE:
There is nothing in the Log Viewer.

Well, maybe a feature could be added to let the WL user know in the Log Viewer if the event provider is no longer working. It's an interesting idea.