> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to connect

> How to connect the X (Twitter) Public data source to Adriel: track publicly visible profile and tweet metrics for X handles the workspace does not own.

X (Twitter) Public surfaces publicly visible profile and tweet metrics for X (formerly Twitter) accounts designated as monitoring targets. It is intended for competitive monitoring, brand-mention tracking, and influencer analytics on handles the workspace does not own, bringing profile snapshots and per-tweet engagement into Adriel dashboards.

## Before you connect

The following are required:

* An X account with API access at an appropriate X API v2 tier.
* One or more public X handles to monitor. Protected (private) accounts cannot be tracked.
* Workspace permission to add a new data source.

## Connect X (Twitter) Public

<Steps>
  <Step title="Find X (Twitter) Public">
    On the **Data Sources** page, search for **X (Twitter) Public** and select it.
  </Step>

  <Step title="Authorize through X">
    Sign in to X and approve the requested read scopes for public profile and tweet data. The connecting account does not need to own the handles being tracked — its credentials authorize the underlying X API v2 calls. Authorization returns to the data source setup screen on completion.
  </Step>

  <Step title="Enter the handles to monitor">
    Provide one or more public X handles, without the leading **@**. Multiple handles can be tracked per data source.
  </Step>

  <Step title="Save">
    Select **Save** to create the data source. The first sync runs a one-year backfill of public tweet history, subject to the limits of the connected X API tier.
  </Step>
</Steps>

## What gets imported

Public profile snapshots — follower count, following count, tweet count, listed count — are captured for each monitored handle, alongside per-tweet engagement such as likes, reposts, replies, quotes, bookmarks, and (on paid tiers) impressions. Daily refreshes use a rolling date-range window to keep recent activity current. A compatibility mapper preserves the legacy field shape from the connector's prior Apify-backed implementation, so widgets built before the migration continue to render without changes.

For the complete list of metrics, breakdowns, and limits, see the [X (Twitter) Public data reference](/data-sources/o-z/x-twitter-public/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Some metrics return blank values">
    Several engagement metrics, including impressions, are tier-gated by X API v2. Lower tiers omit them. Upgrading the connected X account's API tier unlocks the full metric set.
  </Accordion>

  <Accordion title="A monitored handle returns no data">
    Protected (private) X accounts cannot be monitored — X's API does not expose their data even to authenticated callers. Confirm the handle is public. If a handle was recently switched to protected, new data stops arriving while cached history remains queryable.
  </Accordion>

  <Accordion title="Refreshes appear stale or partial">
    X API v2 enforces low per-window request quotas on lower tiers. High-volume monitoring across many handles can hit these limits. Manual refresh is capped at one per day per data source. Reduce the monitored handle count or upgrade the API tier if throttling persists.
  </Accordion>

  <Accordion title="Existing dashboards built on the legacy connector">
    The X API v2 response passes through a compatibility mapper that emits the legacy Apify field names, so widgets and dashboards built before the migration continue to render without changes.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="X (Twitter) Public data reference" href="/data-sources/o-z/x-twitter-public/data-reference">
    Metrics, breakdowns, and limits for X (Twitter) Public.
  </Card>

  <Card title="X (Twitter) Public FAQs" href="/data-sources/o-z/x-twitter-public/faqs">
    Common questions and expected behaviors for the X (Twitter) Public data source.
  </Card>

  <Card title="How to connect X (Twitter) Organic" href="/data-sources/o-z/x-twitter-organic/how-to-connect">
    Connect owned-account X analytics.
  </Card>

  <Card title="How to connect X (Twitter) Ads" href="/data-sources/o-z/x-twitter-ads/how-to-connect">
    Connect paid X advertising campaigns.
  </Card>
</CardGroup>