X (Twitter) walkthrough

Connection

1. To connect X with your destination, refer to X connection.
2. Choose a Source connection after creating the connection.

Predefined reports

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

Since these reports follow a standardized format, specific fields are restricted and can only be accessed through Custom Reports.

Custom reports

Start building your X River by choosing your preferred report type, either Statistics or Entity.

Statistics report

Procedure

1. Navigate to the Data Integration Account.
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 will be automatically updated after each run, facilitating continuous data extraction.
• The Start Date does not advance if a River run is unsuccessful. Optionally, click More Options to advance the start date even if the River 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 a column to identify deleted results by enabling the "Include deleted results" checkbox.
10. To bypass errors for specific accounts, check the "Ignore errors for accounts" checkbox and list the relevant accounts.
11. Save your River configuration.
12. Execute the River to fetch data from X based on the specified parameters.

info

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

Entity report

Procedure

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 includes only the author's numerical ID in the user object.
   • When set to False, the complete user object is returned.
4. Enable the Normalize option to standardize result structures for easy 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 will be automatically updated after each run, facilitating continuous data extraction.
   • The Start Date does not advance if a River run is unsuccessful.
   • Optionally, click More Options to advance the start date even if the River 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 check box.
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 River configuration.
10. Execute the River to retrieve data from X based on the specified parameters.

Rate limitation

If an endpoint enforces 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 used. 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. Going beyond these limits triggers an error response.