ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Connector Facebook

Facebook serves as a central hub for online interactions. In the context of data utilization, businesses can leverage the Facebook Connector, a feature built on the Facebook Graph API, to extract valuable information from their Facebook business accounts and get data out of the Facebook platform.

By utilizing the Facebook Connector, businesses can efficiently export relevant data, such as user engagement metrics, ad performance, and demographic insights, from their Facebook accounts to integrate into their broader customer data strategy within a CDP. This integration enhances the ability to analyze and understand customer behavior across multiple channels, contributing to more informed decision-making and targeted marketing efforts.

Requirements

To set up the Facebook connector, you will need admin/ editor access to the business account you want to obtain data from.

Learn more: Graph API Explorer

Data In/Data Out

Data In N/A
Data Out CSV files in the out/tables folder.

Learn more: about the folder structure please go to this article.

Parameters

yRmCDphY75ODzpgh-Facebook-connectors-Parameters.png

Account/ ID (required)

The ID of the business account you want to download data from. It is possible to add more than one account.

Learn more: about Facebook ID here.

API

Знімок екрана 2024-03-15 о 14.36.57.png

API version you prefer to use.  In case of failure, use v16.0.

Warning: Please update the API version to the newest available, otherwise, the component will return an error. 

 

Facebook-Query.png

Name (required)

The chosen name of the query. 

 

For the name of the query that differs from the Path, a folder with the name QueryName_PathName will be created in the out/tables folder.

 

For the name of the query same as the Path (it is recommended), the name of the created folder will be PathName*. Alphanumeric characters[a-zA-Z0-9_].

Type (required)

In the Facebook Graph API every endpoint represents a node in a graph.

An example of a node could be:

/me - ie user info, 

me/posts - ie posts of the current user.

 

Learn more: about the Graph API Explorer tool. 

 

In the Facebook connector, only the nested-query type is supported. Nested query allows extracting the whole subtree of the node connected to the chosen endpoint. 

For example, the call me?fields=posts, accounts, id, name will return all posts, accounts, id, and the name of the current user.

Path (optional)

Typically it is endpoint feed. The absolute URL is like graph.facebook.com/version/path

 

Remember: It can be an empty string if we want to start extracting from the "root" node that is the page itself.

Fields (required) Fields parameter of the graph API nested-query.

IDS (optional)

A comma-separated list of IDs (typically page-ids) will be prepended with the path. It is also a parameter of the Graph API.

 

Remember: If empty, then all IDs from the accounts object will be used.  

Limit (optional)

The size of one response. The default value is 25, maximum 100.

 

Remember: Useful when Facebook API returns an error that the request is "too big" - in such case use a smaller limit.

 

This parameter also affects the total number of requests made to Facebook API. 

Since (optional)

Relates to the created_time of path parameter i.e., if the path is "posts" then it takes all posts with created_time since the specified date in since parameter. If the path is empty then it does not have any effect. Can be specified relatively, e.g. 10 days ago.

 

Until (optional) Same as since above but specifies a date until data with created_time date.