X (Twitter) Walkthrough

Introduction

In this document, we will focus on the procedure for pulling data from X, offering detailed instructions for configuring two distinct reports: the Statistics Report and the Entity Report.

Prerequisites

Before you begin pulling data from X using Rivery, ensure that you have an established X connection.

How to Pull Data from X using Rivery

Choose the previously created connection under Source Connection or create a new one. You have the option to pick either Predefined Reports or enter Custom Report River mode. If Custom Report River mode is selected, begin building your X River by choosing your preferred report type, either "Statistics" or "Entity."

Statistics Report

1. Select the Accounts for the report.

2. Choose the Entity to pull, metric group, and placements. The available entities are:

• Ad Groups
• Campaigns
• Funding Instruments
• Organic Tweets
• Promoted Tweets

3. Define report filters based on the selected entity.

4. Specify the time period of the report.

   Please 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 won't be advanced 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.

5. Choose the breakdown granularity to group data either by Hour or Day.

6. If dealing with a substantial amount of data, consider dividing the loading process into intervals using Interval chunks size (optional).

7. Optionally, enable a column to identify deleted results by checking the "Include deleted results" checkbox.

8. To bypass errors for specific accounts, check the "Ignore errors for accounts" checkbox and list the relevant accounts.

9. Save your River configuration.

10. Execute the River to fetch data from X based on the specified parameters.

Additional Notes:

• Maximum time range for non-segmented queries is 90 days, and for segmented queries, it is 45 days.

• 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. Indicate whether to trim users:

• When set to 'True,' each Tweet returned will include 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. Pick the Extract Method.

6. For Incremental Extraction, define the time period.

   Please 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 won't be advanced 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" checkbox.

8. If you want to bypass errors for specific accounts, check 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 you're using. 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. Continue reading for further insights and strategies to prevent hitting rate limits.