Skip to main content

​
Introduction

Facebook Page Public retrieves publicly available data from any Facebook Page through the Meta Graph API (v23.0) — no page ownership, admin access, or ad account is required. It surfaces two kinds of data: the Page’s public profile (followers, About text, website, cover and profile imagery) and recent feed posts with their public engagement (per-reaction counts, shares, comments, and replies). This is a public connector, distinct from Facebook Page Organic (owned page analytics that require admin access) and Meta Ads (paid campaign data). Because it reads only public data, it authenticates with a server-side application token rather than a personal login, and the connection is created from a Facebook Page URL. To connect this data source, see How to connect Facebook Page Public to Adriel.

​
Data refresh strategy

​
Architecture data

Facebook Page Public is a simple-cache connector: for each connected Page, Adriel re-fetches the public data and refreshes the cache on a fixed daily schedule. There is no historical backfill — the cache holds the current snapshot of the Page profile and the most recent feed posts, and values accumulate from the connection date forward as each daily refresh runs. The Page profile and the feed are stored in two separate cache collections per data source (one for page-profile data, one for posts).

​
Reports data

The cache refreshes daily at 6:00 PM UTC for both the page profile and the posts collection (a single schedule covers both). This connector does not support date filtering. Reports always read the current cached snapshot: the page-profile view returns a single row, and the posts view returns up to the most recent 100 posts.

​
Architecture levels

Facebook Page Public operates in two data modes, and a data source exposes both:
  • Page mode — reads the Page’s public profile from GET /v23.0/{pageId}. Always returns exactly one row (the Page itself).
  • Posts mode — reads the Page’s public feed from GET /v23.0/{pageId}/feed. Returns one row per post, up to a cap of 100 of the most recent posts.
Metrics and breakdowns differ by mode: page-profile fields are only available in page mode, and post engagement fields are only available in posts mode.

​
Date range limits

Not applicable. Facebook Page Public has no date filtering — reports ignore the dashboard date range and always return the current cached snapshot (one page row; up to 100 recent posts).

​
Metrics

How to read the columnsData type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.API Key in code style such as followers_count is the literal Meta Graph API field (or constructed sub-query). Italic text describes how a value is produced when it does not map cleanly to a single API field.

​
Page profile

Available in page mode. Returns a single row describing the Page’s public profile.

​
Post engagement

Available in posts mode. Returns one row per post (up to 100 most recent). Reaction totals are fetched as per-type summary counts.

​
Breakdowns

​
Post

Available in posts mode. These group and identify individual posts.

​
Page

Available in page mode.

​
Limitations

  • No date filtering — reports always return the current cached snapshot; the dashboard date range has no effect. There is no historical daily data, only what accumulates from the connection date forward.
  • Posts are capped at ~100 — posts mode returns at most the 100 most recent posts, even though the underlying feed can be paginated further. Older posts are not retrieved.
  • Public data only — only publicly visible profile fields and public engagement are available. Reach, impressions, and other owner-only insights are not accessible; use Facebook Page Organic for those.
  • Generic data source — this connector cannot be natively combined with other connector types unless they share identical breakdowns. Cross-connector analysis requires a blended data source.
  • Deletions are not reflected — if an element (a post or a profile field) is deleted on Facebook, its previously cached value stops updating and the current value becomes unavailable after the deletion.
  • Media may expire — cover, profile-picture, and post image URLs point to Facebook-hosted media that can expire or change if the underlying content is removed or is no longer accessible through the API.

​
API references

​
See also