If you’re finding discrepancies between the User Tweets data you see in Twitter Public Data and in your Supermetrics reporting, it could be due to one of the issues below. This guide will walk you through the most common causes behind these discrepancies, and how to fix them.
Types of discrepancy
If you’ve requested results for an account that definitely has Tweets, but Supermetrics returns “No data,” it can be because of the “# of rows per item” value. This dictates what’ll be shown, and its counter is always looking from today into the past.
If this value is too low, the settings might not go far enough back into the past to find the account’s Tweets. With a value of 50, for example, it will fetch the first 50 Tweets from now, which does not extend far enough in time to capture older Tweets. These will return "No data".
To fix this, increase the "# of rows per item". This should enable you to pull older data.
In some cases, when you've selected a specific "# of rows per item" value, the number of Tweets returned is drastically lower than your selection. This can happen if an account is very active in posting Tweets, as the API can only serve the first 2,000 items for an account, no matter if they are Tweets, Retweets, or replies.
This limitation is set by the Twitter API.
If you’ve requested a date range for results but aren’t seeing Tweets from all points in that range, it could be because of the “# of rows per item” value. This dictates what’ll be shown, and its counter is always looking from today into the past.
If your “# of rows per item” is 10, for example, you’ll only see the account's 10 most recent Tweets within your date range.
To fix this, increase your “# of rows per item” value to accommodate the number of Tweets your account publishes in your date range.
If you're querying for older Tweets and not seeing results that match, it's likely caused by a limitation in the Twitter API. The Twitter API can't serve more than around 2,000 items (Tweets, Retweets, replies) for an account.
This means that every query starts with a quota of 2,000 items. The query goes back through the items until it’s pulled a little over 2,000 of them. Then, the query stops.
The more active the account is, the smaller the historical window will be, as every Tweet, Retweet, and reply made by the account takes up one spot in the quota.