January 11, 2021 16:49

Facebook Ads Integration

In this article, we’ll integrate a Facebook Ads data source with Y42.

Facebook Ads provides the set up history of your Ad Account, Campaigns, Ad Sets, Ads, and Ad Creatives. Facebook Ads also fetches Ad Insights data.

A guide on how to best understand and use the data from the API is available here on the Facebook Ads Raw Data Guide.

Overview

Authentication: OAuth

Settings: Historical Date selection, Account selection

Schema type: Fixed

Update Type: Full import and incremental

Authentication

OAuth doesn’t share password data but instead uses authorization tokens to prove an identity between you and the service provider. OAuth is an authentication protocol that allows you to approve one application interacting with another on your behalf without giving away your password. For instance, when you tell Facebook that it’s OK for another application or website to access your profile. To sum up, you only need to have an existing account to authorize the access.

Import Settings

By default, the historical date will be set to one year ago. Refer to your own datasource to decide from which exact date you would want to retrieve data.

Account pre-requisites

You will need an active Facebook account with permission to access data from accounts you'd like to sync. If the user account used to connect to the integration has restricted permissions - meaning the user doesn’t have access to all campaigns or ads - there might be issues when replicating data. Even if you only intend to sync partial data after completing the integration, the user's Facebook account should still have full access.

Schema

You can find the full list of API endpoints for the Facebook Marketing APIs and the description for each item on Facebook's API documentation, as well as the breakdowns and fields you'd like to sync.

Updating your data

You have the option of scheduling imports or Incremental Imports by the month, weeks, days, and even by the hour. With the incremental import, you will only add the new rows to that table, while a full import will actually re-import the entire table completely.

Incremental imports significantly increase the import speed, we import your table incrementally based on the last imported state e.g. id - If the table does not have a state, a full import will be triggered - This is done automatically.

We recommend therefore to schedule an incremental import regularly, but also schedule a full import with a certain frequency -- this is because only the full import will guarantee that old rows that have been updated on the data source will also get updated on your Y42 integration destination.

Facebook Ads Setup Guide:

Note: In order to connect Facebook Ads with Y42, you will need to have a Facebook Account.

On Integrate, click on "Add..." to search for Facebook Ads and select it.
Name your integration.
Click Authorize and log into your Facebook account.
After authentication, you are good to go and start importing your tables.
Choose from which point onwards in time to import your data. PLEASE NOTE: Facebook Ads are limited to a maximum 37-month reporting window. You can not import historical data older than 37 months from the initial import date.
Add in your Facebook Ads Account and press Select.
Select the tables you need and click import. You can start accessing the tables once the status is “Ready”.

Note: You can always import and reimport other tables as well, or delete them.

Tips

Creating two Facebook Ads integrations is recommended: one for the base tables (ads, adcreative, adsets, campaigns, etc.) and one for the insights tables (ads_insights). This is due to the 37 month limit on the insights tables. By separating the tables, you can select an older historical synchronization date for the base tables while keeping the 37-month limit for insights tables.

Additional information:

In case you expect to lose access permission to one of your Facebook Ads accounts, you have the option when adding the Facebook Ads integration, to decide to ignore lost access permissions or not.

By setting "Skip Invalid Accounts" = "Yes", the integration will ignore accounts where you have might lost access permissions and will continue to import data from accounts where access permissions are still granted. In case the setting is "Skip Invalid Accounts" = "No", the integration would show a failed import job.

Was this article helpful?

0 out of 0 found this helpful