Skip to main content
Documentation
Troubleshooting
Feature Requests Status

Pinterest Ads (Source)

Edit on GitHub
  • Updated
Fivetran System User Fivetranner

Apache License

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

This package enriches your Fivetran data by doing the following:

  • Adds descriptions to tables and columns that are synced using Fivetran
  • Adds column-level testing where applicable. For example, all primary keys are tested for uniqueness and non-null values.
  • Models staging tables, which will be used in our transform package

Modelslink

This package contains staging models, designed to work simultaneously with our Pinterest Ads transformation package and our multi-platform Ad Reporting package. The staging models:

  • Name columns consistently across all packages:
    • Boolean fields are prefixed with is_ or has_
    • Timestamps are appended with _at
    • ID primary keys are prefixed with the name of the table. For example, the campaign table’s ID column is renamed campaign_id.

Installation Instructionslink

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/pinterest_source
    version: [">=0.5.0", "<0.6.0"]

Configurationlink

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



...
config-version: 2

vars:
    pinterest_database: your_database_name
    pinterest_schema: your_schema_name

Passthrough Columnslink

This package allows for custom columns not defined within the stg_pinterest_ads__pin_promotion_report model to be passed through. These custom columns may be applied using the pin_promotion_report_pass_through_metric variable. To apply custom passthrough columns use the below format:



...
vars:
  pin_promotion_report_pass_through_metric:
    - 'cool_new_field'
    - 'my_other_column'
    - 'pass_this_through_too'

Changing the Build Schemalink

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



...
models:
    pinterest_source:
      +schema: my_new_schema_name # leave blank for just the target_schema

Database Supportlink

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

Databricks Dispatch Configurationlink

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.



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

Contributionslink

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:link

Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Didn’t find what you need?

Contact support