GithubHelp home page GithubHelp logo

fivetran / dbt_snapchat_ads Goto Github PK

View Code? Open in Web Editor NEW
1.0 38.0 6.0 1.72 MB

Fivetran data models for Snapchat Ads built using dbt.

Home Page: https://fivetran.github.io/dbt_snapchat_ads

License: Apache License 2.0

Shell 100.00%
dbt fivetran dbt-packages snapchat-ads

dbt_snapchat_ads's Introduction

Snapchat Ads Transformation dbt Package (Docs)

What does this dbt package do?

  • Produces modeled tables that leverage Snapchat Ads data from Fivetran's connector in the format described by this ERD and builds off the output of our Snapchat Ads source package.
  • Generates a comprehensive data dictionary of your source and modeled Snapchat Ads data through the dbt docs site.
  • Enables you to better understand your marketing performance based on different levels of granularity:

The following table provides a detailed list of all tables materialized within this package by default.

TIP: See more details about these tables in the package's dbt docs site.

Table Description
snapchat_ads__account_report Each record represents the daily ad performance of each account.
snapchat_ads__campaign_report Each record represents the daily ad performance of each campaign.
snapchat_ads__ad_report Each record represents the daily ad performance of each ad.
snapchat_ads__url_report Each record represents the daily ad performance of each ad url.
snapchat_ads__ad_squad_report Each record represents the daily ad performance of each ad squad.

How do I use the dbt package?

Step 1: Prerequisites

To use this dbt package, you must have the following:

  • At least one Fivetran Snapchat Ads connector syncing data into your destination.
  • A BigQuery, Snowflake, Redshift, Databricks, or PostgreSQL destination.

Databricks Dispatch Configuration

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']

Step 2: Install the package

Include the following snapchat_ads_source package version in your packages.yml file:

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

packages:
  - package: fivetran/snapchat_ads
    version: [">=0.6.0", "<0.7.0"] # we recommend using ranges to capture non-breaking changes automatically

Do NOT include the snapchat_ads_source package in this file. The transformation package itself has a dependency on it and will install the source package as well.

Step 3: Configure your variables

Define database and schema variables

By default, this package runs using your destination and the snapchat_ads_source schema. If this is not where your Snapchat Ads data is (for example, if your Snapchat Ads schema is named snapchat_ads_fivetran), you would add the following configuration to your root dbt_project.yml file with your custom database and schema names:

vars:
    snapchat_ads_database: your_destination_name
    snapchat_ads_schema: your_schema_name 

(Optional) Step 4: Additional configurations

Union multiple connectors

If you have multiple snapchat_ads connectors in Fivetran and would like to use this package on all of them simultaneously, we have provided functionality to do so. The package will union all of the data together and pass the unioned table into the transformations. You will be able to see which source it came from in the source_relation column of each model. To use this functionality, you will need to set either the snapchat_ads_union_schemas OR snapchat_ads_union_databases variables (cannot do both) in your root dbt_project.yml file:

vars:
    snapchat_ads_union_schemas: ['snapchat_ads_usa','snapchat_ads_canada'] # use this if the data is in different schemas/datasets of the same database/project
    snapchat_ads_union_databases: ['snapchat_ads_usa','snapchat_ads_canada'] # use this if the data is in different databases/projects but uses the same schema name

NOTE: The native source.yml connection set up in the package will not function when the union schema/database feature is utilized. Although the data will be correctly combined, you will not observe the sources linked to the package models in the Directed Acyclic Graph (DAG). This happens because the package includes only one defined source.yml.

To connect your multiple schema/database sources to the package models, follow the steps outlined in the Union Data Defined Sources Configuration section of the Fivetran Utils documentation for the union_data macro. This will ensure a proper configuration and correct visualization of connections in the DAG.

Passing Through Additional Metrics

By default, this package will select clicks, impressions, and cost from the source reporting tables to store into the staging models. If you would like to pass through additional metrics to the staging models, add the below configurations to your dbt_project.yml file. These variables allow for the pass-through fields to be aliased (alias) if desired, but not required. Use the below format for declaring the respective pass-through variables:

IMPORTANT: Make sure to exercise due diligence when adding metrics to these models. The metrics added by default (taps, impressions, and spend) have been vetted by the Fivetran team, maintaining this package for accuracy. There are metrics included within the source reports, such as metric averages, which may be inaccurately represented at the grain for reports created in this package. You must ensure that whichever metrics you pass through are appropriate to aggregate at the respective reporting levels in this package.

vars:
    snapchat_ads__ad_hourly_passthrough_metrics: 
      - name: "new_custom_field"
        alias: "custom_field"
    snapchat_ads__ad_squad_hourly_passthrough_metrics:
      - name: "this_field"
    snapchat_ads__campaign_hourly_report_passthrough_metrics:
      - name: "unique_string_field"
        alias: "field_id"

Change the source table references

If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:

IMPORTANT: See this project's dbt_project.yml variable declarations to see the expected names.

vars:
    snapchat_ads_<default_source_table_name>_identifier: your_table_name 

Change the build schema

By default, this package builds the Snapchat Ads staging models within a schema titled (<target_schema> + _stg_snapchat_ads) and your Snapchat Ads modeling models within a schema titled (<target_schema> + _snapchat_ads) in your destination. If this is not where you would like your Snapchat Ads data to be written to, add the following configuration to your root dbt_project.yml file:

models:
    snapchat_ads_source:
      +schema: my_new_schema_name # leave blank for just the target_schema
    snapchat_ads:
      +schema: my_new_schema_name # leave blank for just the target_schema

(Optional) Step 5: Orchestrate your models with Fivetran Transformations for dbt Core™

Expand for more details

Fivetran offers the ability for you to orchestrate your dbt project through Fivetran Transformations for dbt Core™. Learn how to set up your project for orchestration through Fivetran in our Transformations for dbt Core setup guides.

Does this package have dependencies?

This dbt package is dependent on the following dbt packages. These dependencies are installed by default within this package. For more information on the following packages, refer to the dbt hub site.

IMPORTANT: If you have any of these dependent packages in your own packages.yml file, we highly recommend that you remove them from your root packages.yml to avoid package version conflicts.

packages:
    - package: fivetran/snapchat_ads_source
      version: [">=0.6.0", "<0.7.0"]

    - package: fivetran/fivetran_utils
      version: [">=0.4.0", "<0.5.0"]

    - package: dbt-labs/dbt_utils
      version: [">=1.0.0", "<2.0.0"]

    - package: dbt-labs/spark_utils
      version: [">=0.3.0", "<0.4.0"]

How is this package maintained and can I contribute?

Package Maintenance

The Fivetran team maintaining this package only maintains the latest version of the package. We highly recommend you stay consistent with the latest version of the package and refer to the CHANGELOG and release notes for more information on changes across versions.

Opinionated Decisions

In creating this package, which is meant for a wide range of use cases, we had to take opinionated stances on a few different questions we came across during development. We've consolidated significant choices we made in the DECISIONLOG.md, and will continue to update as the package evolves. We are always open to and encourage feedback on these choices, and the package in general.

Contributions

A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.

We highly encourage and welcome contributions to this package. Check out this dbt Discourse article on the best workflow for contributing to a package.

Are there any resources available?

  • If you have questions or want to reach out for help, see the GitHub Issue section to find the right avenue of support for you.
  • If you would like to provide feedback to the dbt package team at Fivetran or would like to request a new dbt package, fill out our Feedback Form.

dbt_snapchat_ads's People

Contributors

5tran-alexil avatar alex-ilyichov avatar dylanbaker avatar fivetran-catfritz avatar fivetran-jamie avatar fivetran-joemarkiewicz avatar fivetran-reneeli avatar fivetran-sheringuyen avatar kristin-bagnall avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dbt_snapchat_ads's Issues

Null records introduced

I was running into an error with the dbt_snapchat_ads utility.
For some reason, an extra 6 records for only six days out of 3 years of data was being created with a NULL in the ad_account_id. There are no NULLs in the AD_ACCOUNT_ID fields in the account nor campaign CTE.
While i am not sure why the NULLS were introduced.
These NULLS were tripping up the not-null tests.
My quick fix for this issue was to append
"WHERE AD_ACCOUNT_ID IS NOT NULL"
at the bottom of
snapchat_ads_account_report.sql
I'd love to learn why the extra records are happening, but hopefully I help address an issue before others struggle with it.
Thanks
-Chris
Records before
image
Code change
image
Records after
image

[Feature] Add union schema capability

Copied from fivetran/dbt_facebook_ads_source #29.

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

Issue for adding the union schema capability.

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

No response

[Feature] Update to use `fivetran_utils.extract_url_parameter` instead of `dbt_utils.get_url_parameter`

Copied from fivetran/dbt_facebook_ads #37.

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

An issue with dbt_utils.get_url_parameter was discovered in fivetran/dbt_linkedin_source#55 for Databricks SQL. Macro fivetran_utils.extract_url_parameter was added to solve this issue for Databricks targets (see fivetran/dbt_fivetran_utils#130 more info).

For this package, references to dbt_utils.get_url_parameter need to be updated to fivetran_utils.extract_url_parameter.

[Feature] Add documentation on differences among aggregations across different grains

Copied from fivetran/dbt_ad_reporting #92.

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

Some customers have brought up concerns on why sums are different across different grains, for example why spend is not the same summed up across the ad level versus the campaign level.

Example from Joe regarding a recent customer inquiry:

"The reason for this discrepancy is due to not all ads being served at the ad level. There are some ads that are only served at the ad group/campaign/etc. levels. This means that you can have ads sent at the campaign level and that counts towards your total spend. However, since the ad was never sent at an individual ad level, it will not be included.
This was a large reason for us breaking the ad reporting package into separate hierarchical end models. Because we found when we only used the ad level, we were missing data as some ads were not served at an ad level, but were served at a campaign level."

We should add more context like above to our ad packages READMEs as a proactive measure.

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

No response

BUG - [Snapchat Ads creative id ad adapter model]

Are you a current Fivetran customer?

Fivetran created issue

Describe the bug

Data for snapchat follows this hierarchy: campaign < ad group < ad < creative. We only have impression data down to the ad level (ref: ad_hourly_report).

Currently, in our snapchat__ad_adapter model, we are joining the ad table with creatives, and using the ad_history table to map ad_ids to creative_ids. This table does not always have a 1:1 relationship between ad_ids and creative_ids. Customers can potentially have multiple unique creatives per ad. The creative_id and creative_name should be removed from the snapchat__ad_adapter table as it potentially creates row duplicates for spend & impressions. Creative UTM fields should be OK.

Steps to reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Metric calculations should only be down to the ad id level.

Project variables configuration

copy dbt_project.yml here

Package Version

copy packages.yml here

Warehouse

  • BigQuery
  • Redshift
  • Snowflake
  • Postgres
  • Databricks
  • Other (provide details below)

Additional context

Screenshots

Please indicate the level of urgency

Are you interested in contributing to this package?

  • Yes, I can do this and open a PR for your review.
  • Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this fixed.
  • No, I'd prefer if someone else fixed this. I don't have the time and/or don't know what the root cause of the problem is.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.