Export / storage of user handles

VonGocke · 2017-02-15T00:33:13.000Z

Hello, the proposed use case would involve surfacing tweets at an event using geo-tag coordinates, then providing additional analysis around the user handle(s) associated with those tweets. What are the restrictions on exporting those user handles into a CRM? Also, can those user handles be stored and then imported into Twitter Ads API for future retargeting? Thank you in advance!

IgorBrigadir · 2017-03-31T16:47:55.856Z

You’re better off working with IDs (id in a user json) - which never change for a user, as opposed to handles (screen_name) - As long as it’s just lists of IDs, there are no restrictions on exporting those.

For analysis, you can retrieve fresh user information with https://dev.twitter.com/rest/reference/get/users/lookup - This way any account that becomes private, or deleted, or any changes to profiles will be respected when you lookup a user.

I think Ads API handles lists of user ids, but i don’t know the API.

VonGocke · 2017-04-11T14:29:41.894Z

IgorBrigadir:

You’re better off working with IDs (id in a user json) - which never change for a user, as opposed to handles (screen_name) - As long as it’s just lists of IDs, there are no restrictions on exporting those.

For analysis, you can retrieve fresh user information with https://dev.twitter.com/rest/reference/get/users/lookup - This way any account that becomes private, or deleted, or any changes to profiles will be respected when you lookup a user.

Thanks, Igor!