It would be very interesting to add a Twitter feed in Omniscope. The data that would be useful to have in it (but probably this will depend on what Twitter has to offer for their analytics?):
• Information on tweets (by day): a. Clicks on tweet b. Retweets of tweet c. Replies on tweet d. Total Reach (by tweet or by day) e. … • Information on followers: a. Number of followers (by day) b. Screen name / Name c. Description d. Location / Time zone e. Key words on followers (but I don’t think this will be possible) f. …
We already have a Twitter feed in Omniscope. This allows you to provide one or more search terms, and provides a list of tweets that mentioned your search.
For your first idea "Information on tweets (by day)", how would you envisage defining which tweets you wanted to collect information on?
For your second idea "Information on followers", again how would you supply which twitter pages you were interested in?
If anyone has any other ideas to enhancements to the twitter feed, please post them here.
For your first idea "Information on tweets (by day)", how would you envisage defining which tweets you wanted to collect information on?
It would be nice if we could login with our account and password to get information on tweets we send to our followers (same principle as the facebook feed). And if we prepare a particular Omniscope project for a client, we can propose to add some twitter statistics in it too, with the twitter feed of course. The only thing that the client has to give us, is his account and password of their twitter account.
Other possibility: Enter the twitter name of a twitter user in a field which is integrated in the twitter feed box. But I don’t know if it’s possible to get all information on a twitter account without giving up your twitter name and password?
For your second idea "Information on followers", again how would you supply which twitter pages you were interested in?
Same answer of course . But I don’t know if there’s already a lot of information available on your twitter followers via API ?
Ok, so you want to supply a twitter user (and maybe a password) and get statistics for all tweets from that twitter user (maybe filterable by date). So one row for each tweet and statistics such as "No clicks", "No reposts", "No replies".
For the second option, followers, again we would supply a twitter user, only this time each row in the resulting data would contain information about a follower of that person, and would show name, description, location etc.
We will investigate updating the Omniscope Twitter feed as part of the Omniscope 2.8 release. As part of that work we will try and incorporate as many of your ideas as possible.
In Omniscope 2.8 we have now updated the Twitter search block to use the new Twitter API. The old API will be discontinued at some point in the future, which means the twitter block will no longer work in Omniscope 2.7.
The new API requires you to log on to twitter in order to search the data. It also places restrictions on the number of times you can use the twitter search, see:
The restriction here is 180 searches per user per window. A window lasts approximately 15 minutes. It is also worth baring in mind that we can only obtain 100 results at a time, so if you specify the number of results to be 200, two searches will be undertaken.
We will soon be adding a "Twitter feed" block, which will allow you to obtain tweets, friends and followers for one or more users. Again there are restrictions on the number of API calls we can perform, so we will not be able to obtain results such as "friends-of-friends". I'll let you know when these are available.
We have now added the "Twitter feed" block. This currently provides two twitter reports:
- User timeline. Allows you to enter the name of the user and retrieve the most recent user tweets. This is currently limited to 200 results.
- Friends and followers. Allows you to enter the name of a user and retrieve the friends (the Twitter users that person is following), or the followers of that user. This is currently limited to 5000 results.
This functionality will be available in 2.8b706 onwards.
Please let us know how you get on, and whether you need any additional options or reports.