Facebook Public Data data source

Learn how to set up a Facebook Public Data data source and then move your data to one of the data destinations supported by Coupler.io. 

Two steps to complete the setup

  1. Set up your data source
  2. Set up your data destination

1. Set up your data source

1.1. Select an application: Facebook Public Data

1.2. Connect a Facebook account

  • Click "Connect".
  • Log in to your Facebook account and authorize Coupler.io to import the data on your behalf.
  • Note: in case you've already connected your Facebook account to other Facebook data sources in Coupler.io (Facebook Ads or Facebook Page Insights) - you can use existing connection. 

1.3. Setup Basic settings

  • 'Public pages statistics' report type is selected by default. Allows to see basic Facebook statistics of any account.

Enter a list of page Ids or public aliases you need to fetch data. For specifying one Id in each line.
See example below:

  • 'My pages statistics' report type. 

Specify pages from where you want to extract data.
In the following Wizard settings enter period that should be covered in your report and select needed metrics from the dropdown.

Note: in case some of the needed pages are missing in the dropdown or there's an error when selecting them - permissions for that page should be checked in your Facebook account. Please use following articles to troubleshoot permission issues:

  • Troubleshooting: fix missing Facebook Pages or Instagram Profiles
  • Troubleshooting: User does not have sufficient permissions for this action on this page
    • 'My pages post statistics' report type. 

    Specify pages from where you want to extract data.
    In the following Wizard settings select needed metrics from the dropdown.

    2. Set up your data destination

    Continue the integration setup depending on the destination you want to import data to. Select your tool from the list of supported data destinations and follow the relevant setup guide.

    Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.