--- title: "Good to know about X Ads (Twitter)" slug: "good-to-know-about-x-ads-twitter" description: "Learn more about request limits, historical range, and things to consider when using the X Ads (Twitter) data source in Supermetrics." updated: 2026-09-16T08:32:10Z published: 2026-09-16T08:32:10Z canonical: "docs.supermetrics.com/good-to-know-about-x-ads-twitter" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt > Use this file to discover all available pages before exploring further. # Good to know about X Ads (Twitter) This article outlines recommendations and notes certain limitations imposed by the data source API, which you may need to consider when building your queries. If you’re connecting to X Ads (Twitter), follow the instructions in our [connection guide](/v1/docs/x-ads-twitter-connection-guide). See [X Ads (Twitter) metrics and dimensions](/v1/docs/x-ads-twitter-fields) for the fields available in this data source. ## Request limits and recommended refresh rate **Request limit**: 250 requests per 15 minutes **Recommended refresh window**: Set to the maximum of your attribution windows on the platform. **API delay**: 2 days ## Historical range There are no known limitations to the historical range of data you can pull with the X Ads (Twitter) data source connector. However, 30-day fetches are recommended. ## Accounts in X Ads (Twitter) In the X Ads (Twitter) connector, each Ad account is considered a separate account within the connection. Your Supermetrics subscription determines the number of [data source accounts](https://docs.supermetrics.com/docs/about-data-source-accounts) you can use simultaneously. ## Things to consider ### Segmentation Segmentation not supported for MEDIA_CREATIVE or ORGANIC_TWEET entities. Promoted tweet entity doesn't support segmentation when WEB/MOBILE conversion metrics are selected. ### Missing data for text-only tweets Tweet media type None (text-only) means that there is no card for tweet and no related media entities so `promoted_tweet_destination_url` and `promoted_tweet_card_destination_url` are expected to be empty. ### Spend data All analytics metrics are locked and will not change after 24 hours, with the exception of `billed_charge_local_micro`. The `billed_charge_local_micro` metric is an estimate for up to 5 days after the data is returned. After 24 hours, this metric can decrease due to credits for overspend (ads served after the given end_time) and for billable events that are determined to be junk. This metric changes minimally after 24 hours. [See X Ads documentation](https://docs.x.com/x-ads-api/analytics#best-practices). ### Tweet cards Tweet cards for "single Image", "Animated GIF", and "Summary" media types aren’t supported. ### Time zone issues The X Ads API reach report endpoint doesn't allow requests with an end date later than the current date-time, nor date ranges shorter than 1 hour. This means that we can't fetch data for the current day (in account's timezone) if we're requesting it between 00:00:00 and 00:59:59 in the X Ads' account time zone. There is now this error that occurs when less-than-one-hour condition is met: `Twitter only allows to retrieve data for a range of at least 1 hour. For accounts in timezone <name of timezone>, for date <YYYY-MM-DD>, there is still no data available` If there are other valid queries for reach (for other accounts, for older dates), those will pass through and be shown. This is so that data warehouse transfers don’t stop due to the above error. ### Pre-roll campaign data missing Pre-rolls are considered to be account media (media entity) and not a tweet (promoted tweet entity). These types of data are not compatible. If you include tweet dimensions in the query, that means that media items, including pre-rolls, won’t be in the data by design. You would need to build another query that doesn’t contain promoted tweet dimensions, and then the pre-roll objects should appear. ### Total audience reach not compatible with ad group or ads Total audience reach isn’t compatible with the ad group or ads due to an API limitation. The reach and frequency data is only available at the campaign level and the funding instruments level. Errors saying the field is incompatible with the ad group and ad level dimensions are correct and expected behavior. Unfortunately, the UI does show cases where the Total audience reach is also displayed with the ad preview, but this isn’t currently possible with the API. ### Total audience reach not compatible with future dates There’s some error mishandling that leads to using Total audience reach with a future end-date that shows `Date range invalid, start date cant be bigger than end date`. This isn’t the right error, but the issue is that X doesn’t like processing future dates. The fix is to set the date range to today or earlier. ### Promoted accounts Users may want to track data from a Promoted account (also known as the “Account” ad type). Promoted accounts don’t use promoted tweets, so the standard ad-level breakdowns don’t apply. To resolve this, you need to get data at the ad group level. To filter the data to find these specifically, you can use the `line_item_product_type` field and filter for: `WHERE Line_item_product_type = 'PROMOTED_ACCOUNT'` Don’t include promoted tweet fields as that level of reporting can’t show these. The data returned then should be for promoted accounts. ## More resources - [X Ads (Twitter) connection guide](/v1/docs/x-ads-twitter-connection-guide) - [X Ads (Twitter) report building guide](/v1/docs/x-ads-twitter-report-building-guide) - [X Ads (Twitter) metrics and dimensions](/v1/docs/x-ads-twitter-fields)