Blog Post

Release Notes
2 MIN READ

[Experiences] Twitter Sourcing Changes

SFBlogger's avatar
SFBlogger
Khoros Alumni (Retired)
6 years ago

This week we will be making a few small changes to Twitter sourcing in Experiences in the interest of improving content quality and user experience. 

Why are we doing this?
We have a number of different ways that we allow our users to source content from Twitter. When we reviewed the usage data, we saw a handful of sourcing options getting little-to-no usage. On top of that, these are also the sourcing options that generate the most user confusion and undesirable / unwanted content. In order to optimize our customers' Twitter sourcing experience, we're going to clean this up.

What are we changing?
We will be removing the ability to source Tweets by profile keyword, by client / app, and by geo-location. We will also be removing the ability to backfill a stream. 

Based on customer usage data, it's likely the removing geo-location is the only one that may concern you. There's no need to be concerned - we will still be able to support all of your geo-location use cases.  The geo data will still be available to us with the Tweet and customers will still be able to use the geo-based rules. The only component that we're eliminating is asking Twitter for all Tweets in a 5 mile radius of New York City. Instead, you'll need to tell us what you're looking for (Tweets containing #nyfw) and then use rules to reject content that isn't in New York City. 
 
What is the impact?
We will be removing these sourcing options this week. Once we remove them, no new streams will be able to be created using these sourcing mechanisms. For previously created streams that are using these sources, we will stop sourcing based on these criteria.
Updated 5 months ago
Version 3.0
No CommentsBe the first to comment