Quickstart · Source connector
Facebook Pages ELT Connector
Extract brings Facebook Pages quickstart data into data warehouses and databases for analysis with the rest of your business data. Teams use it to build recurring reporting and compare business activity across systems. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Business performance reporting
Use Facebook Pages data to monitor recurring activity and investigate meaningful changes over time.
Cross-system analysis
Combine Facebook Pages data with customer, finance, and operational metrics for consistent reporting.
Data quality monitoring
Compare Facebook Pages record totals and reporting periods to identify incomplete or unexpected data.
Flexible reporting cadence
Refresh Facebook Pages reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.
Warehouse and database analysis
Use Extract to make Facebook Pages quickstart data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
daily_page_engagement | Fields include page_id, date, _singular_extract_timestamp, page_daily_follows. | Incremental |
daily_page_follows_city | Fields include page_id, city, date, _singular_extract_timestamp. | Incremental |
daily_page_follows_country | Fields include page_id, country, date, _singular_extract_timestamp. | Incremental |
daily_page_follows_stats | Fields include page_id, date, _singular_extract_timestamp, page_follows. | Incremental |
daily_page_media_view | Fields include page_id, date, _singular_extract_timestamp, page_media_view. | Incremental |
daily_page_reactions | Fields include page_id, date, _singular_extract_timestamp, page_actions_post_reactions_anger_total. | Incremental |
daily_page_video_views | Fields include page_id, date, _singular_extract_timestamp, page_video_complete_views_30s. | Incremental |
lifetime_page_post_media_view | Fields include page_id, post_id, _singular_extract_timestamp, post_media_view. | Full refresh |
lifetime_page_post_video_views | Fields include page_id, post_id, _singular_extract_timestamp, post_video_complete_views_30s_autoplayed. | Full refresh |
lifetime_page_video_posts | Fields include page_id, post_id, _singular_extract_timestamp, post_video_avg_time_watched. | Full refresh |
page | Fields include id, _singular_extract_timestamp, about, affiliation. | Full refresh |
page_post | Fields include page_id, id, _singular_extract_timestamp, actions. | Incremental |
page_video | Fields include page_id, _singular_extract_timestamp, ad_breaks, audio_story_wave_animation_handle. | Full refresh |
video_metrics | Fields include page_id, video_id, _singular_extract_timestamp, total_video_10s_views. | Full refresh |
video_reels | Fields include page_id, id, _singular_extract_timestamp, description. | Full refresh |
video_reels_metrics | Fields include video_id, _singular_extract_timestamp, blue_reels_play_count, fb_reels_replay_count. | Full refresh |
Schema
Data model at a glance
daily_page_engagement
page_idstringdatestring_singular_extract_timestampstringpage_daily_followsintegerpage_daily_follows_uniqueintegerpage_daily_unfollows_uniqueintegerpage_fan_adds_by_paid_non_paid_uniquestringpage_followsinteger
daily_page_follows_city
page_idstringcitystringdatestring_singular_extract_timestampstringvalueinteger
daily_page_follows_country
page_idstringcountrystringdatestring_singular_extract_timestampstringvalueinteger
daily_page_follows_stats
page_idstringdatestring_singular_extract_timestampstringpage_followsinteger
daily_page_media_view
page_idstringdatestring_singular_extract_timestampstringpage_media_viewintegerpage_views_totalinteger
daily_page_reactions
page_idstringdatestring_singular_extract_timestampstringpage_actions_post_reactions_anger_totalintegerpage_actions_post_reactions_haha_totalintegerpage_actions_post_reactions_like_totalintegerpage_actions_post_reactions_love_totalintegerpage_actions_post_reactions_sorry_totalinteger
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Facebook Pages in Extract workflows.
Why Extract
Why Extract for Facebook Pages
- Rust-native performanceUse Rust-native data movement to refresh Facebook Pages reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Facebook Pages API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Facebook Pages data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.
FAQ
Frequently asked questions
How does Extract handle incremental and full Facebook Pages syncs?
An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define full refresh, incremental changes, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical Facebook Pages data with Extract?
Historical coverage for Facebook Pages: Backfill (Days) (backfill): The backfill setting revisits and updates data from the past X days, ensuring the most current and accurate information replaces any previously pulled data. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor Facebook Pages data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Facebook Pages API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.
How often can Extract sync data from Facebook Pages?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the Facebook Pages data model look like in the destination?
The Available streams table describes the datasets Extract can read from Facebook Pages. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.