Twitter trends appear broken

140dev · 2013-09-10T18:57:08.000Z

My testing makes me believe that the API is correct, while the Twitter.com is not. When I am collecting streaming data that shows a spike in a certain tag, the /trends/places API reflects this with that tag ranking very high. At the same time, the trends on the Twitter.com page have little to no relation to the data flow I am seeing.

episod · 2013-09-10T20:27:56.000Z

I’ve asked a member of my team to take another look at this issue.

If you’re experiencing discrepancies, it’d be very useful to know what part of the world your servers of applications are making requests. Thanks!

140dev · 2013-09-10T20:42:06.000Z

Thanks. This server is at a ServerBeach datacenter in San Antonio, TX.

jbo · 2013-09-10T21:37:22.000Z

Sure!

Orem, UT 84097

jbo · 2013-09-10T22:31:36.000Z

Thanks Taylor! It’s working.

140dev · 2013-09-11T20:16:55.000Z

Still not working for multiple accounts we are in contact with. Please let me know when any changes have been made and I will have people test again.

episod · 2013-09-11T20:46:15.000Z

Is it for the accounts or for the woeids? Do the same woeids give different results for different users?

140dev · 2013-09-11T22:09:53.000Z

This is all related to Twitter trends for the United States. That is all I have tested. I am tracking it through the API with the woeid of 23424977 and the /trends/place request. The results I see through the API seems to match what I collect through the streaming API. The results I and others see through the Twitter.com pages for the United States are different and do not seem to match streaming API data. I and others who see this do not have tailored trends set.

This is a very straight forward issue to test. Just run the API request and load Twitter.com. See if they match. If they don’t, then it is a general problem. If they do match for you, please let me know. It may mean that the problem is isolated to my app, server, IP, or something unique to the way I am querying the API.

Thanks for your help with this Taylor. I think you will agree that trending topics are taken seriously by people, and accuracy is worth trying for.

jbo · 2013-09-13T16:56:33.000Z

Taylor (@episod) FYI yesterday 12 starting at 9:40 a.m. GMT until 15:25 GMT the trends/place API call repeated the same set of trends for each woeid. Our server is located at Orem, UT 84097

jbo · 2013-09-13T18:20:00.000Z

Taylor (@episod):

I think that the situation is getting worse. As you can see on the following captures we received different set of trends for woeid 23424950 (Spain*) at the same time:

http://imgur.com/AFm9Qcx (Twitter.com / Madrid)
http://imgur.com/r1I2G1T (Utah)
http://imgur.com/Z4dD71S (Berlin)

Also, we detect until 5 sets of repeated trends for a lot of differents woeid.

How can we help? What other information do you need?

*Spain is just an example. We try with WW (1), Caracas (395269), and so on.

jbo · 2013-09-15T09:46:10.000Z

Hi!

As Adam (@140dev) says there are not relationship between the last available answer from the API and the trends at twitter.com.

As 9:30 GMT the API return a trends set for 23424950 (Spain) created_at 9:13 GMT, which repeated 3 times since the previous answer returned by 8:58 GMT.

When my app call the API at 9:15:03 GMT the set created_at 9:13 was already “created” but I received a set for 8:58 GMT.

I really need help to resolve this situation (if is a situation) and I don’t want to bother you. Please let me know any other information that can be useful.

anthonydb · 2013-10-02T18:46:21.000Z

Any update on this? We’ve noticed the staleness issue as well.

Beyond that, I’ve checked multiple WOEIDs for points across the U.S., and rarely do the terms seem to vary much from location to location. Would like to know more about how trends are elevated in this API.

jbo · 2013-10-03T06:59:07.000Z

Well, yesterday the trends/place API call repeated the same set of trends for each woeid during 8 hours

At 9:50 GMT began to repeat the 9:45 GMT set until 17:15 GMT.

jbo · 2013-12-03T18:27:27.000Z

Has anyone noticed that for the last 8 days, or so, the number of trending topics returned by the trends/place API has dropped drastically? /cc Taylor @episod

kainakos · 2017-08-01T14:09:27.921Z

I know this is very old but I am having the same issue with several locations worldwide. The data returned from the API do not match the data in the actual twitter website. Does anyone have any additional information about this? What should we trust the API or the website?

andypiper · 2017-08-01T16:31:02.990Z

The website may use different data sources than the API and surface user interest data that is not available in the API. That could account for some differences. If you want to use trends programmatically the API is the only data that you can currently consume.

andypiper · 2018-02-03T20:11:55.983Z

This is not a question related to the Developer platform so we are unable to assist on this forum.

dreamthatworks · 2018-02-04T07:04:16.211Z

Then who can help me in fixing this issue which is going on since last somany months ?

andypiper · 2018-02-04T07:05:33.880Z

Please use help.twitter.com for queries like this. This forum exists to help developers with API questions. This is nothing to do with the API and this is not an appropriate place to seek assistance, and is off-topic for the thread you’re asking on as well.

We cannot offer any assistance with issues related to accounts (suspension, verification, usernames etc), or usage of the twitter.com website, analytics or ads dashboards, and the iOS and Android mobile apps in this forum

Thanks.

Closing as off-topic.

andypiper · 2018-02-04T07:05:36.319Z