X (Twitter) walkthrough

Connection

To connect X with your destination, refer to X connection topic. After you create the connection, choose a Source connection.

Predefined reports

Data Integration provides a convenient entry point and recommended approach for accessing a range of predefined reports. Each report has a concise data description, a list of customizable fields (if applicable), and the schema mapping.

Since these reports follow a standardized format, Data Integration restricts specific fields. You can access those fields only through Custom Reports.

Custom reports

To build your X Data Flow, choose your preferred report type: Statistics or Entity.

Statistics report

1. Navigate to the Data Integration Console.
2. Select the connection that you created.
3. Select the Accounts for the report.
4. Choose the Entity to pull, metric group, and placements. The available entities are:
   • Ad Groups
   • Campaigns
   • Funding Instruments
   • Organic Tweets
   • Promoted Tweets
5. Define report filters based on the selected entity.
6. Specify the time period of the report.

note

• The End date can be left empty to pull data until the current time.
• The Start and End dates automatically update after each run, which handles continuous data extraction.
• The Start Date does not advance if a Data Flow run is unsuccessful. Optionally, click More Options to advance the start date even if the Data Flow run is unsuccessful (Not recommended).
• Set the time zone offset if the end date is empty.
• Use Days back to pull data from a specified number of days before the start date.

7. Choose the breakdown granularity to group data either by Hour or Day.
8. If dealing with a large amount of data, consider dividing the loading process into intervals using an Interval chunk size (optional).
9. Optionally, enable the Include deleted results checkbox to identify deleted results in a separate column.
10. To bypass errors for specific accounts, select the Ignore errors for accounts checkbox and list the relevant accounts.
11. Save your Data Flow configuration.
12. Execute the Data Flow to fetch data from X based on the specified parameters.

info

• The maximum time range for non-segmented queries is 90 days, and 45 days for segmented queries.
• Statistics and Campaigns rows do not appear if there is no data on the chosen day.

Entity report

1. Choose the Entity for retrieval. Available entities are:
   • Accounts
   • Ad Groups
   • Campaigns
   • Cards
   • Funding Instruments
   • Media Library
   • Promoted Tweets
   • Tweets
2. Select the accounts associated with the chosen entity.
3. Specify whether to trim users:
   • When set to True, each Tweet returned contains only the author's numerical ID in the user object.
   • When set to False, X returns the complete user object.
4. Enable the Normalize option to standardize result structures, which handles table import.
5. Select the Extract Method.
6. For Incremental Extraction, define the time period.
   • The End date can be left empty to pull data until the current time.
   • The Start and End dates automatically update after each run, which handles continuous data extraction.
   • The Start Date does not advance if a Data Flow run is unsuccessful.
   • Optionally, click More Options to advance the start date even if the Data Flow run is unsuccessful (Not recommended).
   • Set the time zone offset if the end date is empty.
   • Use Days back to pull data from a specified number of days before the start date.
7. Optionally, include a column to flag deleted results by checking the Include deleted results checkbox.
8. If you want to bypass errors for specific accounts, select the Ignore errors for accounts checkbox and specify the relevant accounts.
9. Save your Data Flow configuration.
10. Execute the Data Flow to retrieve data from X based on the specified parameters.

Rate limitation

If an endpoint has a rate limit of 900 requests per 15 minutes, you can make up to 900 requests within any 15-minute window.

The rate limits depend on the authentication method you use. For instance, OAuth 1.0a User Context grants one limit per time frame for each set of users' Access Tokens, whereas OAuth 2.0 Bearer Token assigns a distinct limit per time frame for your app's requests.