/dbt_facebook_ads

Fivetran data models for Facebook Ads built using dbt.

Apache License 2.0Apache-2.0

Apache License dbt logo and version

Facebook Ads

This package models Facebook Ads data from Fivetran's connector. It uses data in the format described by this ERD.

The main focus of the package is to transform the core ad object tables into analytics-ready models, including an 'ad adapter' model that can be easily unioned in to other ad platform packages to get a single view. This is especially easy using our Ad Reporting package.

Models

This package contains transformation models, designed to work simultaneously with our Facebook Ads source package and our multi-platform Ad Reporting package. A dependency on the source package is declared in this package's packages.yml file, so it will automatically download when you run dbt deps. The primary outputs of this package are described below.

model description
facebook_ads__ad_adapter Each record represents the daily ad performance of each creative, including information about the used UTM parameters.
facebook_ads__account_report Each record represents the daily ad performance of each account.
facebook_ads__campaign_report Each record represents the daily ad performance of each campaign.
facebook_ads__ad_set_report Each record represents the daily ad performance of each ad set.

Installation Instructions

Check dbt Hub for the latest installation instructions, or read the dbt docs for more information on installing packages.

Include in your packages.yml

packages:
  - package: fivetran/facebook_ads
    version: [">=0.3.0", "<0.4.0"]

Configuration

By default, this package will look for your Facebook Ads data in the facebook_ads schema of your target database. If this is not where your Facebook Ads data is, please add the following configuration to your dbt_project.yml file:

# dbt_project.yml

...
config-version: 2

vars:
    facebook_ads_schema: your_schema_name
    facebook_ads_database: your_database_name

For additional configurations for the source models, visit the Facebook Ads source package.

Changing the Build Schema

By default this package will build the Facebook Ads staging models within a schema titled (<target_schema> + _stg_facebook_ads), the Facebook Creative History models within a schema titled (<target_schema> + _facebook_ads_creative_history), and the final Facebook Ads models within a schema titled (<target_schema> + _facebook_ads) in your target database. If this is not where you would like your modeled Facebook data to be written to, add the following configuration to your dbt_project.yml file:

# dbt_project.yml

...
models:
    facebook_ads:
        +schema: my_new_schema_name # leave blank for just the target_schema
    facebook_ads_creative_history:
        +schema: my_new_schema_name # leave blank for just the target_schema
    facebook_ads_source:
        +schema: my_new_schema_name # leave blank for just the target_schema

Database Support

This package has been tested on BigQuery, Snowflake, Redshift, Postgres, and Databricks.

Databricks Dispatch Configuration

dbt v0.20.0 introduced a new project-level dispatch configuration that enables an "override" setting for all dispatched macros. If you are using a Databricks destination with this package you will need to add the below (or a variation of the below) dispatch configuration within your dbt_project.yml. This is required in order for the package to accurately search for macros within the dbt-labs/spark_utils then the dbt-labs/dbt_utils packages respectively.

# dbt_project.yml

dispatch:
  - macro_namespace: dbt_utils
    search_order: ['spark_utils', 'dbt_utils']

Contributions

Additional contributions to this package are very welcome! Please create issues or open PRs against main. Check out this post on the best workflow for contributing to a package.

Resources: