From Release 2.25, Hevo has upgraded to v19.0 of the Marketing API. You may need to reauthorize Hevo for existing Pipelines. Refer to section, Configuring Facebook Pages as a Source for the authorization steps.
The new API version has removed the following Page Insights metrics:
Page Insights Category |
Page Insights Metrics |
Page Video Views |
- page_video_views_10s - page_video_views_10s_paid - page_video_views_10s_organic - page_video_views_10s_autoplayed - page_video_views_10s_click_to_play - page_video_views_10s_unique - page_video_views_10s_repeat |
Page Video Posts |
- post_video_views_10s - post_video_views_10s_unique - post_video_views_10s_autoplayed - post_video_views_10s_clicked_to_play - post_video_views_10s_organic - post_video_views_10s_paid - post_video_views_10s_sound_on |
Note: Hevo does not ingest any new data for the metrics listed in the table above, so the corresponding Destination tables are also not updated.
Facebook Pages uses Facebook’s Marketing API to fetch insights data for a Facebook page as a whole (such as followers and impressions), and for page posts (such as likes, shares, comments, and video plays). You can replicate the data of one or multiple Facebook pages, including details such as posting and activity history, page insights including page views, post impressions, and insights on posted stories or Ads to a Destination database or data warehouse using Hevo Pipelines.
The Facebook Pages admin user must authorize Hevo to access the Facebook Pages APIs for reading the page and posts-related insights data for the selected pages.
Note: The data is ingested only for posts made by the page owner.
Prerequisites
Configuring Facebook Pages as a Source
Perform the following steps to configure Facebook Pages as the Source in your Pipeline:
-
Click PIPELINES in the Navigation Bar.
-
Click + CREATE PIPELINE in the Pipelines List View.
-
On the Select Source Type page, select Facebook Pages.
-
On the Configure your Facebook Pages account page, do one of the following:
Note: If you enable Advanced Protection, such as two-factor authentication or password changes, you will need to reauthorize Hevo; otherwise, the Pipeline will be marked as failed.
-
On the Configure your Facebook Pages Source page, specify the following:
-
Pipeline Name: A unique name for your Pipeline, not exceeding 255 characters.
-
Pages: The pages whose data you want to replicate. Select one or more pages from the drop-down. Default selection: All.
-
Historical Sync Duration: The duration for which you want to ingest the existing data from the Source. Default duration: 1 Month.
Note: You can fetch data for daily_page
or unique_page
metrics for a period more than three months by changing the position of these objects to any past date up till two years from the current date, in the Pipeline Overview page. Any data ingested from the Source using the Change Position action is billable.
-
Click TEST & CONTINUE.
-
Proceed to configuring the data ingestion and setting up the Destination.
Data Replication
For Teams Created |
Default Ingestion Frequency |
Minimum Ingestion Frequency |
Maximum Ingestion Frequency |
Custom Frequency Range (in Hrs) |
Before Release 2.21 |
24 Hrs |
12 Hrs |
24 Hrs |
12-24 |
After Release 2.21 |
6 Hrs |
30 Mins |
24 Hrs |
1-24 |
Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.
-
Historical Data: The first run of the Pipeline ingests historical data for the selected objects on the basis of the historical sync duration specified at the time of creating the Pipeline and loads it to the Destination. Default duration: 1 Month.
Note: You can fetch data for Daily Page or Unique Page metrics for a period more than three months by changing the position of these objects to any past date up till two years from the current date, in the Pipeline Overview page.
-
Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency in Full Load or Incremental mode, as applicable.
-
Data Refresh: Data for the last 90 days is refreshed on a rolling basis for all data objects.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
Data Model
Hevo ingests the following data from your Facebook account:
Object |
Description & Update Frequency |
Daily Page Metrics |
Daily page metrics, grouped on the basis of the following categories: - Action Type - Age Gender - City - Consumption Type - Country - Frequency Distribution - Like Source - Paid Non-paid - Locale - Story Type - Time - Type - Unlike Source - Total - Profile Tab |
Lifetime Post Metrics |
All time post-level metrics grouped on the basis of the following categories: - Action Type - Age Gender - Country - Locale - Type - Total |
Page |
All page details such as bio, about, likes, creation date, page type, hours, products. Metrics such as likes and shares are subject to change daily. Other details such as bio and working hours are subject to a page owner’s preference. |
Post |
All posts-related activity and metrics such as likes, views, and shares, from the feed, fetched and updated for the past 14 days. |
Post Attachments |
Attachment details for posts, such as, description, type, and URLs. |
Post Tagged Object |
Details related to an entity tagged on any post, such as name, type, and related post details. |
Post Video Property |
All properties related to a video included in a post such as description, length, and source. |
Unique Page Metrics |
Individual page-level metrics grouped on the basis of the following categories: - Action Type - Age Gender - City - Consumption Type - Country - Frequency Distribution - Like Source - Paid Non-paid - Locale - Story Type - Time - Type - Unlike Source - Total - Profile Tab |
Unique Lifetime Post Metrics |
Individual post-level metrics grouped on the basis of the following categories: - Action Type - Age Gender - Country - Locale - Type - Total |
Read the detailed Hevo documentation for the following related topics:
Limitations
-
All page data is limited to the past two years due to Facebook Pages API limitations.
Note: To fetch data for daily_page
or unique_page
metrics for a period more than three months, change the position of the object to any past date up till two years from the current date, in the Pipeline Overview page.
Revision History
Refer to the following table for the list of key updates made to this page:
Date |
Release |
Description of Change |
Nov-05-2024 |
NA |
Added a note in the Configuring Facebook Pages as a Source section to indicate that enabling Advanced Protection requires reauthorizing Hevo for existing Pipelines. |
Aug-29-2024 |
NA |
Updated section, Limitations to remove the limitation on ingesting post data and metrics only from the last 90 days. |
Jul-01-2024 |
2.25 |
Updated the page overview to: - Add a warning container to inform about the upgrade to Marketing API v19.0, - Remove the note about the upgrade to Marketing API v18.0. |
Mar-05-2024 |
2.21 |
Updated the ingestion frequency table in the Data Replication section. |
Jan-29-2024 |
2.19.3 |
Added a note in the page overview about the Marketing API v18.0 update. |
Oct-03-2023 |
NA |
Updated the se |
Oct-03-2023 |
NA |
Updated the section, Configuring Facebook Pages as a Source as per the latest Facebook UI. |
Feb-20-2023 |
NA |
Updated section, Configuring Facebook Pages as a Source to update the information about historical sync duration. |
Sep-05-2022 |
NA |
Updated section, Data Replication to reorganize the content for better understanding and coherence. |
Dec-06-2021 |
1.77 |
Updated the Data Model section to correct the definitions of Lifetime Post Metrics and Unique Page Metrics. |
Oct-25-2021 |
NA |
Added the Pipeline frequency information in the Data Replication section. |
Jul-26-2021 |
NA |
Added a note in the Overview section about Hevo providing a fully-managed Google BigQuery Destination for Pipelines created with this Source. |