Facebook Ads PRIVATE PREVIEWlink
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.
Featureslink
Feature Name | Supported | Notes |
---|---|---|
Capture Deletes | check | CAMPAIGN_HISTORY , AD_SET_HISTORY , AD_HISTORY and CREATIVE_HISTORY tables. |
Custom Data | check | ACCOUNT_ATTRIBUTION and AD_SET_ATTRIBUTION tables. All fields in these tables are custom fields except primary and foreign keys. |
Data Blocking | ||
Column Hashing | ||
Re-sync | check | Connector level, fetches only reporting data |
History | check | All fields. We capture the delta of changes between syncs. |
API Configurable | check | |
Priority-first sync | ||
dbt Package |
Setup guidelink
Follow our step-by-step Facebook Ads setup guide to connect Facebook Ads with your destination using Fivetran connectors.
Sync overviewlink
You can decide to sync all accounts or sync specific accounts to the destination.
We need the following permissions:
-
ads_read
permission to sync Ad Accounts, Ad Sets, and related entities. -
ads_management
permission to sync Ads, Campaigns, Ad Creatives, and related entities. -
business_management
permission to sync Business fields and related data.
We retrieve the following tables and their related data, during every update:
- all
AD_ACCOUNTS
ADS
CAMPAIGNS
AD_SETS
AD_CREATIVES
REPORT
Schema informationlink
This schema applies to all Facebook Ads connectors.
To zoom, open ERD in new window.
Schema noteslink
The *_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 v7.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:
date
for Day aggregationweek
for Week aggregationmonth
for Month aggregation
fivetran_id
is the primary key for the parent table. fivetran_id
and 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:
Ad
level: If you select thead_id
and/orad_name
fields, and/orproduct_id
breakdown, and/oraction_target_id
action breakdownAdset
level: If you select theadset_id
and/oradset_name
fieldsCampaign
level: If you select thecampaign_id
and/orcampaign_name
and/orobjective
fieldsAccount
level: 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
ad_id
andadset_id
fields, we query onAd
level.
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 with of the type list<AdsActionStats>
, list<AdsHistogramStats>
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.
Updating datalink
Updates occur as frequently as every 15 minutes.