> ## 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.

# FAQs

> Common questions, expected behaviors, and troubleshooting for the X (Twitter) Public data source.

## Why is my monitored handle returning no data?

X (Twitter) Public reads only what X exposes publicly through its official API, so a handle can come back empty for a few reasons.

<AccordionGroup>
  <Accordion title="The account is protected (private)">
    Protected accounts cannot be monitored. X's API does not expose a protected account's tweets or engagement even to an authenticated caller, so no new data arrives while the account stays private. If a handle is switched to protected after it was added, new data stops, but any history already cached before the switch remains queryable.
  </Accordion>

  <Accordion title="The handle changed its username">
    A monitored data source is tied to the exact username it was created with. If the handle changes its X username, the existing data source can no longer resolve it. Create a new X (Twitter) Public data source pointing at the new username to resume collection.
  </Accordion>

  <Accordion title="The username doesn't match an existing account">
    A typo, a suspended account, or a handle that no longer exists all return nothing. Confirm the handle resolves on x.com, then retry.
  </Accordion>
</AccordionGroup>

## Why don't I see impressions on my tweets?

Impressions (view counts) are gated behind paid X API access. When the underlying X API does not return an impression value for a tweet, the metric comes back empty. Like, repost, reply, quote, and bookmark counts are not gated the same way and are available for monitored public tweets. For the full list of what the connector exposes, see the [X (Twitter) Public data reference](/data-sources/o-z/x-twitter-public/data-reference).

## Why is my data stale or partial?

X's API enforces low per-window request quotas. Monitoring many handles at once, or refreshing frequently, can bump against those quotas, which can surface as data that looks stale or incomplete for a given refresh. It usually resolves on the next scheduled refresh once the quota window resets. Reducing the number of handles tracked on a single data source lowers the pressure. For the refresh schedule itself, see the [X (Twitter) Public data reference](/data-sources/o-z/x-twitter-public/data-reference).

## Why can I only refresh the data source once a day?

Manual refresh is capped at one per data source per day. The cap exists to stay within X's API quotas, which are shared across the monitoring that Adriel performs. Scheduled refreshes continue to run on their own regardless of whether the manual refresh has been used. See the [X (Twitter) Public data reference](/data-sources/o-z/x-twitter-public/data-reference) for the schedule.

## How far back does the data go?

When a data source is first connected, Adriel imports up to about one year of public tweet history for each monitored handle. Because Adriel caches the data, the longer the data source stays connected, the more history accumulates. Two limits are worth knowing:

* Metrics are available for up to 500 tweets per monitored handle, so very high-volume accounts are capped at their most recent tweets.
* Profile counts such as followers, following, and listed count are captured as daily snapshots from the day the handle was added. There is no snapshot history for dates before that.

## How is X (Twitter) Public different from Organic and Ads?

X (Twitter) Public reads publicly visible profile and tweet metrics for handles a workspace chooses to monitor, without administering those accounts. It suits competitor tracking, brand-mention monitoring, and influencer analytics. For accounts the workspace administers directly, use [X (Twitter) Organic](/data-sources/o-z/x-twitter-organic/data-reference). For paid campaign reporting, use [X (Twitter) Ads](/data-sources/o-z/x-twitter-ads/data-reference). The three are separate data sources and are not merged.

## Related

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

  <Card title="Connect X (Twitter) Public" href="/data-sources/o-z/x-twitter-public/how-to-connect">
    Set up monitoring for public X handles.
  </Card>

  <Card title="X (Twitter) Organic data reference" href="/data-sources/o-z/x-twitter-organic/data-reference">
    For accounts the workspace administers directly.
  </Card>

  <Card title="X (Twitter) Ads data reference" href="/data-sources/o-z/x-twitter-ads/data-reference">
    For paid X campaign reporting.
  </Card>
</CardGroup>