Facebook Posts

Facebook Posts

This document describes the Facebook Posts data source. Continue reading to learn more about:

  1. Collecting - what should you know about adding the data source.
  2. ERD - data relationships (such as parent-child table relationships).
  3. Data Dictionary - what data is available and how it is structured.

Collecting

WARNING: Facebook requires the logged in user to have permissions to the data. If the permissions are not in place, some of the data will not be available.

To configure this data source and collect Facebook Posts data:

  1. From the Data Sources menu, click Add Data Source.
  2. Search for Facebook Posts, then select it to continue to the next step.
  3. On the General tab:
    • Click Login and follow Facebook’s authorization process to allow Panoply to access Facebook Posts data.
    • Select the Facebook Pages from which to collect data.
      • The Facebook pages that appear in the list are those that your Facebook account has access to.
    • Select the Resources to collect.
    • Select a Date Range.
      • ‘Date Range’ determines how many days of historical data to collect.
      • If this is a first time collection, we recommend using the default selection. This will speed up the initial collection.
  4. (Optional) On the Advanced tab you can set the Advanced Options, however, we do not recommend changing advanced options unless you are an experienced Panoply user.
    • The Destination is the target table for the data. The default for the Facebook Posts data source is facebook_posts_{resource}, where resource is the table name from the schema for this data source, for example facebook_posts_insights.
  5. Click Save Changes then you can click Collect.
    • The data source appears grayed out while the collection runs.
    • You may add additional data sources while this collection runs.
    • You can monitor this collection from the Jobs page or the Data Sources page. 
    • After a successful collection, navigate to the Tables page to review the data results.

ERD

Data Dictionary

These are the resources available for the Facebook Posts data source, and along with them their table mappings. Depending on the resource, Panoply makes use of one or more tables for importing data. Here they are, grouped by resource:

Post Shares

Post Reactions

Comments

Insights

facebook_posts_shares

A table for storing posts and their share data.

Facebook Graph API Reference:

facebook_posts_reactions

A table for storing posts and the reaction of various users to it.

Facebook Graph API Reference:

facebook_posts_comments

A table for storing post comments and their comment replies.

Facebook Graph API Reference:

facebook_posts_comments_reactions

A table for storing the reactions of various users to either post comments or comment replies.

Facebook Graph API Reference:

facebook_posts_insights

A table for storing the insights of your Facebook Page’s posts, specifically, video posts. It contains fields that represent the video-related metrics of your video post, like how many times the video was played, the number of people who viewed it, etc. These fields are prefixed with the word posts in them.

Facebook Graph API Reference:

facebook_posts_insights_lifetime

A table for storing the insights of your Facebook Page’s posts, specifically preferring those metrics that can be aggregated for a lifetime.

Take note that other metrics of a post are aggregated differently, either for days, weeks, or months. Again, this table stores only the ones that can be aggregated for a lifetime.

Facebook Graph API Reference:

Flattened Fields

This table also contains numerous fields that were flattened by Panoply. Flattened fields are easy to recognize. They’re those fields with similar names but are differentiated by a suffix, which can either be a text or number value. The suffix is based on each property of the source nested object.

For example, the post_video_retention_graph_0 and post_video_retention_graph_1 fields are flattened fields based from the post_video_retention_graph object. The numbers 0, 1, and so on, are the suffixes that represent each property of the object.

Likewise, the fields post_video_view_time_by_country_id_israel and post_video_view_time_by_country_id_canada (and a list of other countries) were flattened from the post_video_view_time_by_country_id object. The respective country names also represent each property of the object.

Lastly, as a reference, here are the objects (metrics) from the Page Insights resource wherein the flattened fields are sourced from:

  • post_activity_by_action_type
  • post_activity_by_action_type_unique
  • post_clicks_by_type
  • post_clicks_by_type_unique
  • post_impressions_by_story_type
  • post_negative_feedback_by_type
  • post_negative_feedback_by_type_unique
  • post_reactions_by_type_total
  • post_video_retention_graph
  • post_video_retention_graph_autoplayed
  • post_video_retention_graph_clicked_to_play
  • post_video_view_time_by_age_bucket_and_gender
  • post_video_view_time_by_country_id
  • post_video_view_time_by_distribution_type
  • post_video_view_time_by_region_id
  • post_video_views_by_distribution_type
Getting started is easy! Get all your data in one place in minutes.
Try Free