Strange Errors with Brokerage Recommendation Price Target

bshapiro

I have been checking some of the price targets given by brokerages, and I have noticed a strange reoccuring error. I use the following code snippet to retrieve price targets:

# Retrieves:
# - Brokerage
# - Analyst Nam
# - Price target
# - Date of Price Target change
def get_pt_est_snapshot(symbol_part_list: list):
    fields = [
              'TR.TPEstValue.brokername', 'TR.TPEstValue.analystname',
              'TR.TPEstValue', 'TR.TPEstValue.date'
             ]
    data, err = ek.get_data(instruments=symbol_part_list, fields=fields)
    return data

I am able to hand check the price targets returned by comparing with the publications from the brokerages.

There is a strange error that appears to effect Jefferies price targets: Reuters will sometimes report incorrrectly that the price target is 52.

As of September 7th, you can check symbols UAL, GKOS, RETA, CINC, STT, and HQY.

It appears 52 is some sort of default value returned when Reuters does not know the correct price target.

raksina.samasiri

hi @bshapiro ,

regarding case number 11570774 you raised on this issue, the resolution from the specialist was posted as below

With regarding to query for the case number 11570774. I would like to inform you that we have now removed incorrect Target Price from Jefferies as of September 7th and 8th Sept for symbols UAL, GKOS, RETA, CINC, HQY, BCYC, GILD, and PHR.
The changes made will reflect on our products within 30 minutes.
Please note that we are closing this service ticket and kindly let us know if you have any follow-up question/s on this.
Please let me know if you have any questions.

Plus, I've checked the data and found that the incorrect value (52) was gone

Jirapongse

@bshapiro

I got the following data when using Eikon Excel.

The followings are data from Eikon Data API.

Some values from JEFFERIES are 52 and Eikon Data API gets the same data as Eikon Excel.

To verify the retrieved content, please contact the content or Eikon support team directly via MyRefinitiv. You can ask them to verify the content retrieved by Eikon Excel.

bshapiro

Yes, this is the issue, this data is incorrect (with the exception of STT, which must have been updated).