Once Meta is connected to Fostr, it becomes a central link between customer interactions, marketing performance, and operational workflows inside the platform. This page explains what types of data are ingested, how synchronization is handled, and how Fostr uses Meta messaging, insights, and ads data to enrich Actions, Records, and collaborative processes with real‑time context.

Sync Timing and Update Behavior

Fostr keeps Meta data current using a combination of scheduled refreshes and workflow‑based fetches. This ensures that connected conversations, advertising metrics, and account insights are always relevant to workflows.

Key aspects of sync:

• Scheduled polling at configurable intervals that can be adjusted by tenant or workspace.
• On‑demand fetches initiated when workflows or Actions reference Meta data for near real‑time freshness.
• Credential monitoring that automatically checks token health and alerts admins if a System User token expires or permissions change.
• Balanced performance, as syncs are designed to remain efficient and avoid exceeding Meta API limits.

Note: The current integration does not leverage Meta Webhooks. Fostr relies on polling plus workflow triggers to maintain both timeliness and stability.

Data Scope and Ingestion Rules

The Meta integration is designed to capture only the data needed for operations inside Fostr rather than ingesting every available field. This approach keeps Recordsets clean and performance‑friendly.

Data categories include:

• Always included: page and account identifiers, high‑level metadata, conversation threads from Messenger, Instagram DMs, and WhatsApp, as well as advertising metrics (impressions, spend, clicks, conversions).
• Optional depending on setup: engagement metrics tied to posts (likes, comments, shares) and Ads Manager breakdowns or audience insights.
• Excluded by default: media attachments from conversations, sensitive user profile information, and historical archives unless a selective backfill is specifically requested.

During initial configuration, admins may choose to enable selective backfill imports (such as the past 30 days of messages or ad data) to provide context for immediate use.

Data Handling and Security

Meta remains the system of record, and Fostr functions as a secure lens for surfacing that data within workflows. Information is ingested into encrypted Recordsets, which are protected at the environment level.

Important handling and visibility details:

• Integration access is read‑only. Campaign or content changes must be made directly in Meta.
• Fostr follows a two‑layer visibility model: Meta permissions define which assets the System User token can reach, and Fostr roles control which internal users can view or act on that data.
• Synced items can be linked and referenced directly within Fostr Actions, checklists, and workflow records.
• API quotas are fully respected. For high‑volume accounts, synchronization happens in smaller incremental requests to avoid disruptions.

This model ensures both security and clarity: only users with the right combination of Meta access and Fostr roles can view Meta‑linked information.