Skip to main content

​
Introduction

X (Twitter) Organic surfaces account-level and post-level organic performance for a connected X account. It covers published posts, post engagement, video performance, and audience signals such as follower and following counts — the unpaid activity on an account, separate from any paid campaigns.
This data source uses the v2 X Organic connector. The earlier v1 connector is deprecated: existing v1 widgets keep working, but the v1 connector is hidden from new-connection flows.
As an organic-social connector, engagement metrics and post-level breakdowns are standardized so widgets can aggregate alongside other sources without additional configuration. To connect this data source, see How to connect X (Twitter) Organic to Adriel.

​
Data refresh strategy

​
Architecture data

Architecture covers the X account and its posts. It refreshes daily at 6:30 PM UTC. On first connection, posts created within the last 180 days are retrieved, but only lifetime totals are available for them — there are no historical daily values for posts published before the connection. Metrics accumulate in the cache from the connection date forward, and new posts appear after the next daily refresh.

​
Reports data

Reports include daily performance for the account and its posts. This connector is cache-based: dashboards read from the daily cache that these scheduled refreshes maintain.
  • Lifetime account and post data refreshes daily at 6:30 PM UTC.
  • Daily page data is initially backfilled for the last 180 days; each cycle then refreshes the most recent 3 days at 6:00 PM UTC.
Follower-type metrics have no historical backfill — only daily snapshots are cached, starting from the connection date.

​
Architecture levels

X account → Post

​
Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like impressions is the literal X field name. Italic text describes how a value is produced when it does not map cleanly to a single API field.
Lifetime and delta values X returns a snapshot of each post’s totals at the moment of retrieval. Adriel caches those snapshots once per day so it can report both lifetime values (the running total) and delta values (the day-over-day change, useful for trend charts). For posts published before the connection date, the first delta is 0 because no earlier snapshot exists, so the sum of deltas will not match the lifetime total for those posts.

​
Profile and followers

​
Impressions

​
Engagement

​
Video

​
Post metadata

​
Breakdowns

​
Account and post

​
Date

​
Time grouping

These groupings are Adriel-side aggregations of the same underlying daily data.

​
Overview

These are Adriel-provided grouping labels used for cross-connector reporting rather than values returned by X.

​
Limitations

  • 180-day first-time fetch — on first connection, only posts created within the last 180 days are retrieved, and those pre-connection posts arrive with lifetime totals only, no historical daily values.
  • No follower history before connection — follower-type metrics have no historical backfill; daily snapshots begin accumulating from the connection date.
  • Delta baseline — posts published before the connection date start with a delta of 0, so the sum of deltas will not equal the lifetime total for older posts. When a daily delta cannot be calculated (for example, during API downtime), the value is linearly estimated from the last available snapshot.
  • Page data derived from posts — account-level metrics are summed from the cached per-post rows rather than fetched from a dedicated account endpoint, so page totals depend on how completely posts synced for the day.
  • Media expiry — media associated with a post may become unavailable if the post is no longer retrievable through the API.
  • Older or removed posts — delta values for very old posts (3+ years) or posts that became unretrievable (deleted or restricted) are not recorded.
  • Temporary content — short-lived content is not fully implemented and may contain missing or inaccurate data.
  • Rate limits — X enforces strict rate limits on organic analytics endpoints (X Ads API — Analytics); for high-volume accounts a refresh cycle can be partial or delayed. This is a platform constraint rather than a connector behavior.
  • Historical reach — the Adriel connector makes roughly two years of history available for querying; this is a connector-set limit.

​
API references

​
See also