Facebook Ads provides a history of the settings of your Ad Account, Campaigns, Ad Sets, Ads, and Ad Creatives. Facebook Ads also fetches Ad Insights data.
See Facebook documentation for more information.
|Data blocking||check||Column level|
|Re-sync||check||Connector level, fetches only reporting data|
|History||check||All fields. We capture the delta of changes between syncs.|
|Fivetran data models||check||Get the models: source / transform / creative history; Get the ad reporting model|
Follow our step-by-step Facebook Ads setup guide to connect Facebook Ads with your destination using Fivetran connectors.
You can decide to sync all accounts or sync specific accounts to the destination.
We need the following permissions:
ads_readpermission to sync Ads report information for Ad accounts that you own or Ad accounts that you have been granted access to through this permission.
ads_managementpermission to sync Ads accounts’ metadata. This permission is also used to request the
account_timezonefields of Ad accounts. The
account_timezonefield is required to save the correct report date in the destination.
business_managementpermission to sync Business fields. Every field that starts with the
businessprefix will be skipped if this permission isn’t granted.
We retrieve the following tables and their related data, during every update:
This schema applies to all Facebook Ads connectors.
*_HISTORY tables capture versions of the objects as they are updated. This isn’t a perfect record of every change, rather, it captures the delta of changes between syncs. To query them, use
SORT BY id and
ORDER BY updated_time.
Report schema informationlink
We support all the fields of the Facebook Marketing API v12.0. See Facebook’s documentation for more information.
We provide two types of reports:
- Prebuilt Report
- Custom Report
For either kind of report, we deliver a single main table named after the schema name of the connector. The table contains the fields you selected in the setup form.
Depending on the aggregation you select, we provide the corresponding column (the source field in the Facebook report is
datefor Day and Lifetime aggregation
weekfor Week aggregation
monthfor Month aggregation
fivetran_id is the primary key for the parent table.
index are the composite keys for the child tables.
Depending on the breakdowns, action breakdowns and fields you selected while configuring the connector, we query at different levels:
Adlevel: If you select the
Adsetlevel: If you select the
Campaignlevel: If you select the
Accountlevel: If you selected none of the fields listed above
NOTE: If you selected fields that correspond to more than one level, we query at the most granular level. For example, if you select both the
adset_idfields, we query on
If you select an action breakdown and field or fields, Fivetran creates a secondary table or tables. We name secondary tables with the main table name appended with the field names.
We create separate tables for fields of the
list<AdsHistogramStats> types listed in the Facebook’s field documentation.
The action breakdowns are columns in the table, and the field
value is the number of actions to occur.
NOTE: The action data is hierarchical: a simple sum of all actions will not equal the field
total_actions. See Actions you can measure in Facebook Ads Reporting for more information.
In the request used to query Facebook’s Insights endpoint we specify the report configuration defined during the connector setup. The report returned as a response may not contain all fields you selected. Certain data may be missing due to Facebook API limitations.
NOTE: When Facebook introduced changes related to Apple’s iOS 14 updates, some metrics became unavailable with certain breakdowns selected. For example, delivery and action breakdowns are not supported for offsite conversion events. This includes demographic breakdowns such as age, gender, and region. See Apple’s iOS 14 changes in Facebook API for more information.
Updates occur as frequently as every 15 minutes.