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 a results for an account that definitely has Tweets, but Supermetrics returns “No data,” 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 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, if 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 — the API can only serve the first 2,000 items for an account, no matter what type they are.
To fix this, adjust the date range to a longer period, and increase the number of rows per item. The query will take longer to process, but you’ll be more likely to see an accurate result.
You can also navigate to Report configuration (in the Supermetrics sidebar in Google Sheets and Excel, or in the data source’s configuration page in Data Studio) and adjust the Include retweets and Include replies settings. Removing these can cut down on the number of Tweets fetched.
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 accounts 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 because the Twitter API can’t serve more than around 2,000 objects for an account at once.
This means every query starts with that quota and then goes back through Tweets until it’s pulled a little over 2,000 of them. Then, it stops. The more active an account is, the smaller the historical window will be, as every Tweet, reply, and retweet that account made takes up one spot in the quota.