Facebook Pages (Edge)

Configure Facebook Pages as a Source in your Pipeline

Perform the following steps to configure your Facebook Pages Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Facebook Pages.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing Facebook Pages Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Facebook Pages Source.

   • System User Access Token: Specify the system user access token generated in Meta Business Manager.

   • Page Selection: From the drop-down, select whether to sync all Pages accessible through your authentication method or only specific pages. Default value: Sync All Pages.

     • Sync All Pages: Hevo syncs data for all Facebook Pages accessible through your authorized account, including any Pages added later.

     • Sync Specific Pages: Select the Pages you want to sync from the Pages to sync drop-down.

       

7. Click Test & Continue to test the connection to your Facebook Pages Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For the following objects, Hevo ingests only the incremental data in subsequent Pipeline runs:

• Daily Page Metrics by City
• Daily Page Metrics by Country
• Daily Page Metrics by Paid Non Paid
• Daily Page Metrics by Paid Organic
• Daily Page Metrics
• Daily Page Metrics by Crosspost Status
• Daily Page Metrics by Earning Source
• Daily Page Metrics by Monetization Tool
• Daily Page Monetization Metrics
• Daily Post Metrics by Locale
• Daily Post Metrics
• Daily Post Metrics by Monetization Tool
• Daily Post Monetization Metrics
• Unique Daily Page Metrics by Paid Non Paid
• Unique Daily Page Metrics
• Unique Daily Post Metrics

Hevo also re-fetches data for the last 5 days for these objects every 24 hours. This captures any updates made to previously ingested data and keeps your Destination up to date.

For all other objects, Hevo ingests the entire data during each Pipeline run.

Facebook enforces a rate limit on the number of calls that can be made to its API in a given time period. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to replicate the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following tables (objects) are created at the Destination when you run the Pipeline:

---