Skip to main content

X Organic Analytics

Overview​

The X Organic Analytics source connector (x_organic_analytics) syncs organic performance metrics and tweet metadata from X (Twitter). It is designed for reporting use cases such as tracking impressions, engagements, and other organic KPIs over time.

Requirements​

  • An X (Twitter) account with access to the relevant analytics endpoints.
  • Credentials for authenticating to the X API (see Authentication).

Authentication​

This connector authenticates to X (Twitter) using API credentials.

Provide the required credentials in the connector configuration (exact fields may vary by deployment). Typical options include:

  • OAuth 2.0 (recommended)
  • OAuth 1.0a (if required by your X app configuration)

If you are unsure which method your workspace uses, follow your platform’s standard X/Twitter connector setup flow and paste the generated credentials into the configuration form.

Setup​

  1. In your workspace, create a new source and select X Organic Analytics.
  2. Enter your X API credentials (see Authentication).
  3. Configure sync options (for example, date range/backfill if available in your UI).
  4. Choose a destination and run the initial sync.

Configuration reference​

Configuration fields are provided in the connector UI. Commonly required values include:

  • Credentials: OAuth credentials for X (Twitter).
  • Account / User identifiers: The X account(s) to pull data for (if applicable).
  • Start date: The earliest date to begin syncing analytics (if applicable).

Streams​

The connector outputs the following streams:

accounts​

Account-level metadata for the authenticated X account(s).

Primary use cases

  • Join account metadata to tweet and analytics data.
  • Identify which account produced a given tweet or report row.

tweets​

Tweet-level metadata.

Primary use cases

  • Build a tweet dimension table (text, created time, IDs, etc.).
  • Join tweet metadata to organic performance metrics.

organic_report​

Organic analytics metrics for tweets over time (reporting output).

Primary use cases

  • Track organic performance KPIs (impressions, engagements, etc.).
  • Build time-series reporting and dashboards.

scheduled_tweets​

Information about tweets scheduled for publishing.

Primary use cases

  • Monitor scheduled content.
  • Compare scheduled vs. published content (when joined with tweets).

Notes​

  • Stream availability and metric coverage depend on your X API access level and the permissions granted to your app.
  • If a stream returns no records, verify that the authenticated account has access to the corresponding endpoint and that the required permissions/scopes are granted.