> ## 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 Facebook Page Public data source.

## What is the difference between the Page and Posts data in this source?

Facebook Page Public reads two kinds of public data, and a single data source exposes both.

* **Page** data describes the Page's public profile: follower count, About text, website, Page link, cover image, and profile picture. It always returns a single row for the Page itself.
* **Posts** data describes the Page's recent public feed: one row per post, with per-reaction counts (like, love, haha, wow, sad, angry, care), total reactions, shares, comments, replies, and the post's published time.

Metrics and breakdowns differ by data type. Page-profile metrics are only available with the Page data, and post-engagement metrics are only available with the Posts data. A widget that mixes the two will leave one set of fields empty. For the full field list, see the [Facebook Page Public data reference](/data-sources/a-f/facebook-page-public/data-reference).

## Why does my Facebook Page Public source only show the most recent \~100 posts?

The Posts data returns at most the 100 most recent posts for a Page. The underlying feed can be paged further, but this source stops at 100 by design, so older posts are not retrieved and will not appear in a widget.

There is no setting to raise this cap. For a specific older post, reporting has to happen while it is still within the most recent 100 for that Page.

## Why can't I filter Facebook Page Public by date range?

This source does not use the dashboard date range. It has no date filtering: every report reads the current cached snapshot rather than a historical daily series. The Page data returns the current profile, and the Posts data returns the most recent posts (up to the 100-post cap), regardless of the date range set on the dashboard.

As a result, there is no historical daily breakdown to chart over time. Each engagement value reflects the latest cached total for a post, not what that total was on a past date. Facebook Page Public performs no historical back-fill on connection; instead, because the data is cached, coverage grows going forward — new posts are picked up as they are published and appear after the next scheduled refresh. For the refresh schedule itself, see the [Facebook Page Public data reference](/data-sources/a-f/facebook-page-public/data-reference).

## Why don't I see reach, impressions, or other insights?

Facebook Page Public reads only publicly visible data. Reach, impressions, and other owner-only Page insights are not part of the public Graph API surface, so they cannot be reported through this source no matter how the widget is configured.

Those metrics require owned-Page access. The [Facebook Page Organic data reference](/data-sources/a-f/facebook-page-organic/data-reference) covers the connection for a Page the account administers, which exposes reach, impressions, and audience insights. For paid Facebook and Instagram campaign performance, use Meta Ads instead.

## Why did a post's engagement stop updating, or an image stop loading?

Two expected behaviors explain most cases.

<AccordionGroup>
  <Accordion title="A post or profile field was deleted on Facebook">
    This source does not provide deleted elements. When a post or a profile field is removed on Facebook, its previously cached value stops updating and the current value becomes unavailable after the deletion. A row that was populated can therefore go blank on a later refresh.
  </Accordion>

  <Accordion title="A cover, profile-picture, or post image URL stopped loading">
    Image fields point to Facebook-hosted media. Those URLs can expire or change when the underlying content is removed or is no longer accessible through the Graph API, so an image that loaded before may later fail to load even though the metric row is otherwise intact.
  </Accordion>
</AccordionGroup>

## Why can't I combine Facebook Page Public with my other data sources?

Facebook Page Public is a generic data source. Its data can be viewed in a table on its own, but it cannot be natively combined with other connector types unless they share identical breakdowns. To report it alongside a different data source, set up a blended data source so the two can be joined on a shared breakdown.

## Related

<CardGroup cols={2}>
  <Card title="Facebook Page Public data reference" href="/data-sources/a-f/facebook-page-public/data-reference">
    Metrics, breakdowns, refresh schedule, and limits for this source.
  </Card>

  <Card title="Connect Facebook Page Public" href="/data-sources/a-f/facebook-page-public/how-to-connect">
    How to add a Facebook Page Public data source from a Page URL.
  </Card>

  <Card title="Facebook Page Organic data reference" href="/data-sources/a-f/facebook-page-organic/data-reference">
    Owned-Page analytics with reach, impressions, and audience insights.
  </Card>

  <Card title="Instagram Public data reference" href="/data-sources/g-n/instagram-public/data-reference">
    The equivalent public source for Instagram profiles and posts.
  </Card>
</CardGroup>