This guide covers the basic functionality of the Supermetrics Facebook Public Data connector for Sheets and Data Studio, and gives examples of how to set up a query in both products.
The Facebook Public Data connector does not work like the other Facebook connectors in that you do not need to log in! It allows you to then collect publicly available data about pages and page posts, though the data and fields available are much more limited than having permissions to the page to use Facebook Insights directly. It uses a query selection system for the type of data you would like to collect, which limits which metrics can be used, but prevents user errors from combining invalid field combinations.
The Facebook Public Data connector supports 3 type of queries:
- Facebook page data - gathers data about the page itself, like Likes, About, Website Link, etc.
- Facebook posts by a page - gathers data about posts made to the page, such as Post Link, Reaction counts, Comment counts, etc.
- Facebook shares for URLs - gathers data about specific URLs shared, such as URL, Share count, Comment count, etc.
Query type selection in Google Sheets:
Query type selection in Data Studio:
Example Query Setup in Google Sheets
Here is a walk-through for setting up a 'Facebook posts by a page' query using the Google Sheets Add-on. (The example for Data Studio is below this section.)
- With an empty cell selected, launch the sidebar in Google Sheets.
- In the Data Source section, scroll down to the Simple Connectors part of the list and then select the connector "Facebook Public Data (beta)"
- This connector does not require you to log on. It should immediately open the Query Type section.
- In the Select query type drop-down, select "Facebook posts by a page".
- In the Facebook page alias/ID box, add the page name you wish to search for. You can add expand the box and add more than one name, one each on a new line.
- In the # of rows per item drop-down, select "10". This will pull the most recent 10 items for each page name you added. For better performance, avoid higher row values.
- Open the Select fields section. By default all fields should be selected, but you can add/remove fields to your liking. Note that as this is a simple connector, it's field options are more limited than the full Facebook Insights connector.
- You can also apply filters to some fields under Filter, or set "no headers" in the advanced settings under the Options. These are optional though, and not required to make the query work.
- At the top of the sidebar, click Get Data to Table to run the query and see the results. In this example, this is the most recent 10 posts made to the Supermetrics page.
If further adjustments need to be made, click Modify. Note that due to the nature of the "Query type" system, you cannot combine page data with post data in a single query. If you get errors, see the "Common Issues" section in this article at the bottom.
Example Query Setup in Data Studio
Here is a walk-through for setting up a 'Facebook posts by a page' query using the Data Studio connector.
- In Data Studio, add a new data source and search for "Facebook Public Data" in the Partner Connectors section. Click SELECT to add it.
- Click AUTHORIZE to start the authorization process for Data Studio. In the resulting pop-up, click your Google account you are using for Data Studio access. Click Allow to continue (else the connector won't function).
- Click AUTHORIZE for Facebook Public Data. You do not need to log in to use this connector, it will open a pop-up that closes automatically, and then should go to the next part of the configuration.
- In the Query type drop-down, select "Facebook posts by a page".
- Go down to the ***************** SETTINGS FOR QUERY TYPE: Facebook posts by a page ***************** section.
- In the Facebook page aliases/IDs box, add one or more page names, comma separated.
- In the # of posts per page drop-down, select "10". This will pull the most recent 10 items for each page name you added. Data Studio is hard-coded to a 250 row maximum by design. For better performance, avoid higher row values.
- You do not need to fill out any other query section as it will not be used. Note that you can only set one query type at a time with this connector. If you need other query types, repeat this process to create a new data source with the different query type selected.
- Give the Data Source a meaningful name.
- Click CONNECT in the upper right-hand corner to create the data source.
- It will take you to a page with all the connector's fields that are available for the "Facebook posts by a page" query type. Click ADD TO REPORT to continue.
- Create a report element on the report page, selecting your new source as the Data Source. Add the metrics and dimensions available to create your query. In this example, a table is used to show the last 10 posts made to the Supermetrics page.
- If you need to modify the query, you can do so from the Data bar in the Data Studio UI and it will update automatically to reflect your changes.
"No account objects selected" Errors
More often affects Data Studio. Check that you filled out the proper query section and that there's a valid page name given.
Query Runs Very Slowly
More commonly affects Sheets, as it allows for a larger row limit. The API being used is not that efficient, so the more pages you try pull or the more rows, the slower it gets. Try reducing the number of rows to something below 300 or limit the number of pages listed.
No Data over Time is Available/I Can't Report Over Time?
Sadly, this version of the API only shows lifetime totals for most metrics and you won't be able to report changes over time unless you use the "Combine new with old" feature in Sheets and run this every day to collect your own historical data (this feature is not available at all in Data Studio). If you need time breaks-downs, consider using the Facebook Insights connector instead.
Page Name is Correct, but Still Getting 'No Data'
Pages that are set to be region-specific or are for adult consumption (re: Alcohol products) cannot be found with the public API (as it cannot tell the region or age of the "user"). You can fix the region-specific pages by disabling their regions so that all users can see them, but the ones marked for adult users cannot be used with this connector at all.