This guide will cover the basic limitations and rate limits of the Supermetrics Twitter Premium connector. Unless specified in the section, all guidance within should apply to all Supermetrics products that support the Twitter Premium connector.
Historical data, 90 day limit
Twitter Premium sets a 90 day limit on impressions and engagements, and the derived rate metrics of those. This means that you can only get impression/engagement data 90 days back from today. All other metrics are available further back.
Engagement totals endpoint (currently the only one used by Supermetrics) sets these rate limits:
250 Tweet IDs per request
20 Requests per minute (connector wide total)
20 requests per minute makes Twitter Premium quite a rate limited connector. We have set up a query retry system that mitigates this issue successfully. The query is retried 10 times with an increasing interval - the six first tries 1, 2, 4, 8, 16 and 32 seconds in between, the last 4 with 60 seconds in between (total of 5 minutes 3 seconds) - and if all tries fail, then we return the “You are being rate limited” error.
To comply with Twitter legal requirements, Supermetrics uses API Points to control the amount of unique tweets any Supermetrics team can query for in under any 30 day period. The limit is 1 500 000 points, and each Tweet ID queried counts as 1 point used. If you hit the point limitation, you will get an error message "Error: Twitter Premium failure (You do not have enough API points left to complete this query)" and the query will fail.
API points refresh after 30 days. Any points used today replenish to the team after 30 days.
Supermetrics does not limit the accounts, but Twitter does impose a limitation to this. So called “agency accounts” (accounts that can access multiple other accounts) are limited so that data is only provided for the primary account (the one used for the login).
Several non-agency accounts (one account for the login) can be authenticated one by one, as long as their login emails are different (same login email on several accounts will cause token issues).
Additionally: after a change done in May 2020, you can now also pull data from several single accounts in one query/element.
If you want to help change this, please go upvote (by liking) this forum post by us on the Twitter developer forums (requires a sign-up): https://twittercommunity.com/t/supporting-agency-account-login-for-twitter-engagement-and-related-endpoints/137704