Skip to main content
Use the @bijection/connectors/meta entrypoint to declare Meta (Facebook and Instagram) resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Ad insights

​
daily: Daily ad insights re-read through Meta’s 28-day restatement window

The following example matches configuration campaigns.

​
Configuration: campaigns

Case: meta/insights/daily/campaigns. Connection and resource configuration are declared by this exact case. Credential kind: meta-marketing. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: insights
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
async: Daily ad insights read through asynchronous report runs, one run per pass

The following example matches configuration ads.

​
Configuration: ads

Case: meta/insights/async/ads. Connection and resource configuration are declared by this exact case. Credential kind: meta-marketing. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: insights
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Facebook Page insights

​
daily: Daily Page metrics, one request per metric

The following example matches configuration standard.

​
Configuration: standard

Case: meta/pageInsights/daily/standard. Connection and resource configuration are declared by this exact case. Credential kind: meta-organic. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: insights
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Instagram account insights

​
daily: Daily Instagram time-series metrics

The following example matches configuration standard.

​
Configuration: standard

Case: meta/instagramInsights/daily/standard. Connection and resource configuration are declared by this exact case. Credential kind: meta-organic. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: insights
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Read-only daily report observations over Graph API v26.0. Every mode shares the report window rules: a pass reads from its first day through the UTC day it began; each finished pass carries the day restatementDays before its last day, and the next pass re-reads from there. A row missing from a later read is not withdrawn, and nothing here is a ledger. insights.daily reads GET /act_{id}/insights one account day at a time at the declared level, with up to three breakdowns (publisher_platform separates Facebook from Instagram placements) and optional action_attribution_windows, which add actions and actionValues as Meta’s own text maps. Rows are keyed by (account, day, level object id, breakdown values). Metrics are Meta’s decimal text and are declared exact, so a metric sent as a JSON number fails the pass. Meta states that insights do not change after 28 days, the default restatementDays; settled is true only for a day at least that old when read. Pages follow paging.cursors.after, which Meta repeats on a last page, so each day ends with one empty request; a cursor that does not move is refused. Reports Meta finds too large for a synchronous request fail the pass; use insights.async for them. insights.async publishes the same rows, keys, exact metrics and settled through asynchronous report runs, one per pass: POST /act_{id}/insights over windowDays (default 31) from where the last pass left off, GET /{report_run_id} every pollSeconds (default 60) until async_status is Job Completed and async_percent_completion is 100, then the run’s rows at /{report_run_id}/insights, paged by the same cursor. Job Failed and Job Skipped end the pass with a typed gap. While history is being caught up the next pass begins after the run’s window; once a window reaches today it begins at the restatement window, so a long history takes one pass per window. settled is judged on the day a page is read. Meta keeps a run’s id for 30 days, limits asynchronous reach queries with breakdowns older than 13 months to ten a day per account, and counts both modes against one rate limit. pageInsights.daily and instagramInsights.daily read GET /{object}/insights?metric=…&period=day one metric per request over 30-day chunks. Each value is keyed by (metric, end_time), the end of a Pacific day, and is an exact integer. Only day-period integer metrics remaining after Meta’s 2025 deprecations are offered; Instagram views is answered only as a total_value and is not offered. restatementDays defaults to three days, a recipe choice: Meta states Instagram insights can be delayed up to 48 hours and states no restatement bound for either. Connections: meta-marketing (meta.credential, a system-user or user token with ads_read) for ad insights with setup adAccountId (digits, no act_ prefix); meta-organic (meta.organicCredential, a Page or Instagram token) with setup pageId or instagramAccountId. Throttling answers (400 with codes 17/80000 and the X-Business-Use-Case-Usage header) fail the page and are not modelled as a quota. Nothing here has run against Meta or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.