diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index 17c2c545..c496ccd9 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -1,7 +1,7 @@ name: 🐞 Bug description: Report a bug or an issue you've found within the dbt package title: "[Bug] " -labels: ["bug", "triage"] +labels: ["type:bug"] body: - type: markdown attributes: @@ -35,6 +35,12 @@ body: description: A concise description of what you expected to happen. validations: required: true + - type: textarea + attributes: + label: Possible solution + description: Were you able to investigate and/or discover a potential fix to this bug in your investigation? If so, it would be much appreciated if you could submit code samples to show us how your fix resolved this issue. + validations: + required: false - type: textarea attributes: label: dbt Project configurations @@ -61,6 +67,19 @@ body: - other (mention it in "Additional Context") validations: required: true + - type: dropdown + id: orchestration_type + attributes: + label: How are you running this dbt package? + multiple: true + options: + - Fivetran Quickstart Data Model + - Fivetran Transformations + - dbt Core™ + - dbt Cloud™ + - other (mention it in "Additional Context") + validations: + required: true - type: textarea attributes: label: dbt Version @@ -83,6 +102,6 @@ body: description: Our team will assess this issue and let you know if we will add it to a future sprint. However, if you would like to expedite the solution, we encourage you to contribute to the package via a PR. Our team will then work with you to approve and merge your contributions as soon as possible. options: - label: Yes. - - label: Yes, but I will need assistance and will schedule time during our [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance + - label: Yes, but I will need assistance. - label: No. - required: false \ No newline at end of file + required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 6fa36f86..496b3bd6 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,5 +1,5 @@ contact_links: - - name: Provide feedback or request a new package to our dbt package team + - name: Provide feedback to our dbt package team url: https://www.surveymonkey.com/r/DQ7K7WW about: Fill out our survey form to provide valuable feedback to the Fivetran team developing and maintaining the dbt packages. - name: Fivetran connector question diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml index a1d28bbb..529e9bc5 100644 --- a/.github/ISSUE_TEMPLATE/feature-request.yml +++ b/.github/ISSUE_TEMPLATE/feature-request.yml @@ -1,7 +1,7 @@ name: 🎉 Feature description: Suggest a new feature for the Fivetran dbt package title: "[Feature] <title>" -labels: ["enhancement"] +labels: ["type:enhancement"] body: - type: markdown attributes: @@ -20,6 +20,13 @@ body: description: A clear and concise description of what you want to happen and why you want the new feature. validations: required: true + - type: textarea + attributes: + label: How would you implement this feature? + description: | + How would you build out this feature with your existing data? Any code examples you can provide to help accelerate development on this issue? + validations: + required: true - type: textarea attributes: label: Describe alternatives you've considered @@ -34,7 +41,7 @@ body: description: Our team will assess this feature and let you know if we will add it to a future sprint. However, if you would like to expedite the feature, we encourage you to contribute to the package via a PR. Our team will then work with you to approve and merge your contributions as soon as possible. options: - label: Yes. - - label: Yes, but I will need assistance and will schedule time during your [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance. + - label: Yes, but I will need assistance. - label: No. required: false - type: textarea diff --git a/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md b/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md index a75d5093..32b0fb8e 100644 --- a/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md +++ b/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md @@ -16,7 +16,6 @@ Please acknowledge that you have successfully performed the following commands l Before marking this PR as "ready for review" the following have been applied: - [ ] The appropriate issue has been linked, tagged, and properly assigned - [ ] All necessary documentation and version upgrades have been applied - <!--- Be sure to update the package version in the dbt_project.yml, integration_tests/dbt_project.yml, and README if necessary. --> - [ ] docs were regenerated (unless this PR does not include any code or yml updates) - [ ] BuildKite integration tests are passing - [ ] Detailed validation steps have been provided below @@ -33,4 +32,4 @@ Please share any and all of your validation steps: ### If you had to summarize this PR in an emoji, which would it be? <!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908) --> -:dancer: \ No newline at end of file +:dancer: diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index b4e7e8e0..30849fd0 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -19,7 +19,13 @@ <!--- To select a checkbox you simply need to add an "x" with no spaces between the brackets (eg. [x] Yes). --> - [ ] Yes -**Provide an emoji that best describes your current mood** +**Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?** +<!--- If you select Yes this will help expedite your PR in case there are small changes required before approval. We encourage you not to use this branch in a production environment as we may make additional updates. --> +<!--- If you select No, we will not make any changes directly to your branch and will either communicate any planned changes via the PR thread or will merge your PR into a separate branch so we may make changes without modifying your branch.. --> +- [ ] Yes +- [ ] No + +**If you had to summarize this PR in an emoji, which would it be?** <!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908) --> :dancer: diff --git a/.quickstart/quickstart.yml b/.quickstart/quickstart.yml new file mode 100644 index 00000000..06a7d0e8 --- /dev/null +++ b/.quickstart/quickstart.yml @@ -0,0 +1,76 @@ +dbt_versions: '>=1.3.0 <2.0.0' + +multi_connector_config: + amazon_ads: + database_key: amazon_ads_database + union_schema_key: amazon_ads_union_schemas + model_variable: ad_reporting__amazon_ads_enabled + apple_search_ads: + database_key: apple_search_ads_database + union_schema_key: apple_search_ads_union_schemas + model_variable: ad_reporting__apple_search_ads_enabled + facebook_ads: + database_key: facebook_ads_database + union_schema_key: facebook_ads_union_schemas + model_variable: ad_reporting__facebook_ads_enabled + google_ads: + database_key: google_ads_database + union_schema_key: google_ads_union_schemas + model_variable: ad_reporting__google_ads_enabled + linkedin_ads: + database_key: linkedin_ads_database + union_schema_key: linkedin_ads_union_schemas + model_variable: ad_reporting__linkedin_ads_enabled + bingads: + database_key: microsoft_ads_database + union_schema_key: microsoft_ads_union_schemas + model_variable: ad_reporting__microsoft_ads_enabled + pinterest_ads: + database_key: pinterest_database + union_schema_key: pinterest_ads_union_schemas + model_variable: ad_reporting__pinterest_ads_enabled + reddit_ads: + database_key: reddit_ads_database + union_schema_key: reddit_ads_union_schemas + model_variable: ad_reporting__reddit_ads_enabled + snapchat_ads: + database_key: snapchat_database + union_schema_key: snapchat_ads_union_schemas + model_variable: ad_reporting__snapchat_ads_enabled + tiktok_ads: + database_key: tiktok_ads_database + union_schema_key: tiktok_ads_union_schemas + model_variable: ad_reporting__tiktok_ads_enabled + twitter_ads: + database_key: twitter_ads_database + union_schema_key: twitter_ads_union_schemas + model_variable: ad_reporting__twitter_ads_enabled + +table_variables: + amazon_ads__portfolio_history_enabled: + - portfolio_history + apple_search_ads__using_search_terms: + - search_term_report + pinterest__using_keywords: + - keyword_history + - keyword_report + twitter_ads__using_keywords: + - line_item_keywords_report + +destination_configurations: + databricks: + dispatch: + - macro_namespace: dbt_utils + search_order: + - spark_utils + - dbt_utils + +public_models: [ + "ad_reporting__account_report", + "ad_reporting__campaign_report", + "ad_reporting__ad_group_report", + "ad_reporting__ad_report", + "ad_reporting__keyword_report", + "ad_reporting__search_report", + "ad_reporting__url_report" +] \ No newline at end of file diff --git a/README.md b/README.md index f91a6758..20640fef 100644 --- a/README.md +++ b/README.md @@ -11,8 +11,8 @@ </p> # Ad Reporting dbt Package ([Docs](https://fivetran.github.io/dbt_ad_reporting/)) -# 📣 What does this dbt package do? -- Standardizes schemas from various ad platform connectors and creates reporting models for clicks, spend and impressions aggregated to the account, campaign, ad group, ad, keyword and search levels. +## What does this dbt package do? +- Standardizes schemas from various ad platform connectors and creates reporting models for clicks, spend and impressions aggregated to the account, campaign, ad group, ad, keyword and search levels. - Currently supports the following Fivetran ad platform connectors: - [Amazon Ads](https://github.com/fivetran/dbt_amazon_ads) - [Apple Search Ads](https://github.com/fivetran/dbt_apple_search_ads) @@ -29,9 +29,9 @@ - Generates a comprehensive data dictionary of your source and modeled Ad Reporting data via the [dbt docs site](https://fivetran.github.io/dbt_ad_reporting/) <!--section="ad_reporting_transformation_model"--> -Refer to the table below for a detailed view of final models materialized by default within this package. Additionally, check out our [Docs site](https://fivetran.github.io/dbt_ad_reporting/#!/overview) for more details about these models. +Refer to the table below for a detailed view of final tables materialized by default within this package. Additionally, check out our [Docs site](https://fivetran.github.io/dbt_ad_reporting/#!/overview) for more details about these models. -| **model** | **description** | +| **Table** | **Description** | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [ad_reporting__account_report](https://fivetran.github.io/dbt_ad_reporting/#!/model/model.ad_reporting.ad_reporting__account_report) | Each record represents daily metrics by account | | [ad_reporting__campaign_report](https://fivetran.github.io/dbt_ad_reporting/#!/model/model.ad_reporting.ad_reporting__campaign_report) | Each record represents daily metrics by campaign and account. | @@ -45,8 +45,8 @@ Refer to the table below for a detailed view of final models materialized by def <!--section-end--> -# 🎯 How do I use the dbt package? -## Step 1: Pre-Requisites +## How do I use the dbt package? +### Step 1: Pre-Requisites **Connector**: Have at least one of the below supported Fivetran ad platform connectors syncing data into your warehouse. This package currently supports: - [Amazon Ads](https://fivetran.com/docs/applications/amazon-ads) - [Apple Search Ads](https://fivetran.com/docs/applications/apple-search-ads) @@ -63,7 +63,7 @@ Refer to the table below for a detailed view of final models materialized by def - **Database support**: This package has been tested on **BigQuery**, **Snowflake**, **Redshift**, **Postgres** and **Databricks**. Ensure you are using one of these supported databases. -### Databricks Dispatch Configuration +#### 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` as well as the `calogica/dbt_expectations` then the `google_ads_source` packages respectively. ```yml dispatch: @@ -74,7 +74,7 @@ dispatch: search_order: ['google_ads_source', 'dbt_expectations'] ``` -## Step 2: Installing the Package +### Step 2: Installing the Package Include the following github package version in your `packages.yml` > Check [dbt Hub](https://hub.getdbt.com/) for the latest installation instructions, or [read the dbt docs](https://docs.getdbt.com/docs/package-management) for more information on installing packages. ```yaml @@ -86,7 +86,7 @@ packages: Do NOT include the individual ad platform packages in this file. The ad reporting package itself has dependencies on these packages and will install them as well. -## Step 3: Configure Database and Schema Variables +### Step 3: Configure Database and Schema Variables By default, this package looks for your ad platform data in your target database. If this is not where your app platform data is stored, add the relevant `<connector>_database` variables to your `dbt_project.yml` file (see below). ```yml @@ -125,11 +125,11 @@ vars: twitter_ads_database: your_database_name ``` -## Step 4: Enabling/Disabling Models -This package takes into consideration that not every account will have every feature enabled per platform. If your syncs exclude certain tables, it is because you either don't use that functionality in your respective ad platforms or have actively excluded some tables from your syncs. +### Step 4: Enabling/Disabling Models +This package takes into consideration that not every account will have every feature enabled per platform. If your syncs exclude certain tables, it is because you either don't use that functionality in your respective ad platforms or have actively excluded some tables from your syncs. -### Disable Platform Specific Reporting -If you would like to disable all reporting for any specific platform, please include the respective variable(s) in your `dbt_project.yml`. +#### Disable Platform Specific Reporting +If you would like to disable all reporting for any specific platform, please include the respective variable(s) in your `dbt_project.yml`. ```yml vars: @@ -145,7 +145,7 @@ vars: ad_reporting__tiktok_ads_enabled: False # by default this is assumed to be True ad_reporting__twitter_ads_enabled: False # by default this is assumed to be True ``` -### Enable/Disable Specific Reports within Platforms +#### Enable/Disable Specific Reports within Platforms For **Apple Search Ads**, if you are not utilizing the search functionality, you may choose to update the respective variable below. For **Pinterest Ads**, if you are not tracking keyword performance, you may choose to update the corresponding variable below. @@ -161,7 +161,7 @@ vars: twitter_ads__using_keywords: False # by default this is assumed to be True ``` -## (Recommended) Step 5: Change the Build Schema +### (Recommended) Step 5: Change the Build Schema By default this package will build all models in your `<target_schema>` with the respective package suffixes (see below). This behavior can be tailored to your preference by making use of custom schemas. If you would like to override the current naming conventions, please add the following configuration to your `dbt_project.yml` file and rename `+schema` configs: ```yml @@ -227,8 +227,8 @@ models: > Provide a blank `+schema: ` to write to the `target_schema` without any suffix. -## (Optional) Step 6: Additional configurations -### Union multiple connectors +### (Optional) Step 6: Additional configurations +#### Union multiple connectors If you have multiple ad reporting 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 `<package_name>_union_schemas` OR `<package_name>_union_databases` variables (cannot do both) in your root `dbt_project.yml` file. Below are the variables and examples for each connector: ```yml @@ -266,11 +266,11 @@ vars: twitter_ads_union_schemas: ['twitter_usa','twitter_canada'] twitter_ads_union_databases: ['twitter_usa','twitter_canada'] ``` -Please be aware that 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`. +> 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](https://github.com/fivetran/dbt_fivetran_utils/tree/releases/v0.4.latest#union_data-source) 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. -## Adding custom metrics to final reports +### Adding custom metrics to final reports By default, this package selects `clicks`, `impressions`, and `cost` metrics from the upstream Ad platform reports. Additionally, each specific upstream Ad platform package allows for custom passthrough metrics to be included in the individual platform's final reports. You can find a complete list of available passthrough metric variables for each platform by referring to the relevant links below and inspecting the additional configurations for each platform: - [Amazon Ads](https://github.com/fivetran/dbt_amazon_ads#optional-step-5-additional-configurations) @@ -474,7 +474,7 @@ vars: - name: local_spend_amount ``` -## Disabling null URL filtering from URL reports +### Disabling null URL filtering from URL reports The default behavior for the `ad_reporting__url_report` end model is to filter out records having null URL fields, however, you are able to turn off this filter if needed. To turn off the filter, include the below in your `dbt_project.yml` file. This variable will affect ALL Fivetran platform packages enabled in Ad Reporting, therefore either all URL reports will have null URLs filtered, or all URL reports will have null URLs included. ```yml @@ -482,7 +482,7 @@ vars: ad_reporting__url_report__using_null_filter: False # Default is True. ``` -### Change the source table references +#### 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. This is not available for sources in which you are unioning together multiple connectors. > IMPORTANT: See the Apple Store [`dbt_project.yml`](https://github.com/fivetran/dbt_apple_store_source/blob/main/dbt_project.yml) and Google Play [`dbt_project.yml`](https://github.com/fivetran/dbt_google_play_source/blob/main/dbt_project.yml) variable declarations to see the expected names. @@ -493,7 +493,7 @@ vars: <br> -## (Optional) Step 7: Orchestrate your models with Fivetran Transformations for dbt Core™ +### (Optional) Step 7: Orchestrate your models with Fivetran Transformations for dbt Core™ <details><summary>Expand for details</summary> <br> @@ -502,7 +502,7 @@ Fivetran offers the ability for you to orchestrate your dbt project through [Fiv </details> <br> -## (Optional) Step 8: Use predefined Metrics and the dbt Semantic Layer +### (Optional) Step 8: Use predefined Metrics and the dbt Semantic Layer <details><summary>Expand for details</summary> On top of the `ad_reporting__ad_report` final model, the Ad Reporting dbt package defines common [Metrics](https://docs.getdbt.com/docs/build/build-metrics-intro) using [MetricFlow](https://docs.getdbt.com/docs/build/about-metricflow) that can be queried with the [dbt Semantic Layer](https://docs.getdbt.com/docs/use-dbt-semantic-layer/dbt-sl). These metrics include: @@ -528,7 +528,7 @@ This package includes a model called `metricflow_time_spine.sql` that MetricFlow vars: ad_reporting__metricflow_time_spine_enabled: false ## true by default ``` -Additionally, the `dbt_date.get_base_dates` macro is used in the generation of the `metricsflow_time_spine.sql` model. This macro requires the `dbt_date:time_zone` variable to be defined in the project to generate a time spine based on the defined time zone. The default value in this package is `America/Los_Angeles`. However, you may override this variable in your own project if you wish. +Additionally, the `dbt_date.get_base_dates` macro is used in the generation of the `metricsflow_time_spine.sql` model. This macro requires the `dbt_date:time_zone` variable to be defined in the project to generate a time spine based on the defined time zone. The default value in this package is `America/Los_Angeles`. However, you may override this variable in your own project if you wish. >**Note**: This variable is defined under the `ad_reporting` hierarchy within this package and should not adjust any local global variable values in your project if you already have this variable defined. For more information on why this variable is needed and the different value options, refer to the [dbt-date package documentation](https://github.com/calogica/dbt-date#variables). @@ -546,7 +546,7 @@ You may notice a new run artifact called `semantic_manifest.json`. This file ser </details> <br> -# 🔍 Does this package have dependencies? +## Does this package have dependencies? This dbt package is dependent on the following dbt packages. For more information on the below packages, refer to the [dbt hub](https://hub.getdbt.com/) site. > **If you have any of these dependent packages in your own `packages.yml` I highly recommend you remove them to ensure there are no package version conflicts.** @@ -627,18 +627,18 @@ packages: - package: fivetran/twitter_ads_source version: [">=0.7.0", "<0.8.0"] ``` -# 🙌 How is this package maintained and can I contribute? -## Package Maintenance +## 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](https://hub.getdbt.com/fivetran/github/latest/) of the package and refer to the [CHANGELOG](https://github.com/fivetran/dbt_ad_reporting/blob/main/CHANGELOG.md) and release notes for more information on changes across versions. -## Opinionated Decisions +### 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](https://github.com/fivetran/dbt_ad_reporting/blob/main/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 -These dbt packages are developed by a small team of analytics engineers at Fivetran. However, the packages are made better by community contributions! +### Contributions +These dbt packages are developed by a small team of analytics engineers at Fivetran. However, the packages are made better by community contributions. -We highly encourage and welcome contributions to this package. Check out [this post](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657) on the best workflow for contributing to a package! +We highly encourage and welcome contributions to this package. Check out [this post](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657) on the best workflow for contributing to a package. -# 🏪 Are there any resources available? -- If you encounter any questions or want to reach out for help, please refer to the [GitHub Issue](https://github.com/fivetran/dbt_ad_reporting/issues/new/choose) section to find the right avenue of support for you. +## Are there any resources available? +- If you encounter any questions or want to reach out for help, see the [GitHub Issue](https://github.com/fivetran/dbt_ad_reporting/issues/new/choose) 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 future dbt package to be developed, then feel free to fill out our [Feedback Form](https://www.surveymonkey.com/r/DQ7K7WW). diff --git a/integration_tests/ci/sample.profiles.yml b/integration_tests/ci/sample.profiles.yml index 7d19dbec..4717f311 100644 --- a/integration_tests/ci/sample.profiles.yml +++ b/integration_tests/ci/sample.profiles.yml @@ -16,13 +16,13 @@ integration_tests: pass: "{{ env_var('CI_REDSHIFT_DBT_PASS') }}" dbname: "{{ env_var('CI_REDSHIFT_DBT_DBNAME') }}" port: 5439 - schema: ad_reporting_integration_tests_6 + schema: ad_reporting_integration_tests_7 threads: 8 bigquery: type: bigquery method: service-account-json project: 'dbt-package-testing' - schema: ad_reporting_integration_tests_6 + schema: ad_reporting_integration_tests_7 threads: 8 keyfile_json: "{{ env_var('GCLOUD_SERVICE_KEY') | as_native }}" snowflake: @@ -33,7 +33,7 @@ integration_tests: role: "{{ env_var('CI_SNOWFLAKE_DBT_ROLE') }}" database: "{{ env_var('CI_SNOWFLAKE_DBT_DATABASE') }}" warehouse: "{{ env_var('CI_SNOWFLAKE_DBT_WAREHOUSE') }}" - schema: ad_reporting_integration_tests_6 + schema: ad_reporting_integration_tests_7 threads: 8 postgres: type: postgres @@ -42,13 +42,13 @@ integration_tests: pass: "{{ env_var('CI_POSTGRES_DBT_PASS') }}" dbname: "{{ env_var('CI_POSTGRES_DBT_DBNAME') }}" port: 5432 - schema: ad_reporting_integration_tests_6 + schema: ad_reporting_integration_tests_7 threads: 8 databricks: catalog: "{{ env_var('CI_DATABRICKS_DBT_CATALOG') }}" host: "{{ env_var('CI_DATABRICKS_DBT_HOST') }}" http_path: "{{ env_var('CI_DATABRICKS_DBT_HTTP_PATH') }}" - schema: ad_reporting_integration_tests_6 + schema: ad_reporting_integration_tests_7 threads: 8 token: "{{ env_var('CI_DATABRICKS_DBT_TOKEN') }}" type: databricks \ No newline at end of file diff --git a/integration_tests/dbt_project.yml b/integration_tests/dbt_project.yml index b8549994..3d4df4a5 100644 --- a/integration_tests/dbt_project.yml +++ b/integration_tests/dbt_project.yml @@ -16,7 +16,7 @@ vars: twitter_ads__using_keywords: False apple_search_ads_source: - apple_search_ads_schema: ad_reporting_integration_tests_6 + apple_search_ads_schema: ad_reporting_integration_tests_7 apple_search_ads_organization_identifier: "apple_search_organization_data" apple_search_ads_campaign_history_identifier: "apple_search_campaign_history_data" apple_search_ads_campaign_report_identifier: "apple_search_campaign_report_data" @@ -30,7 +30,7 @@ vars: apple_search_ads__using_search_terms: True google_ads_source: - google_ads_schema: ad_reporting_integration_tests_6 + google_ads_schema: ad_reporting_integration_tests_7 google_ads_ad_stats_identifier: "google_ads_ad_stats_data" google_ads_ad_history_identifier: "google_ads_ad_history_data" google_ads_ad_group_history_identifier: "google_ads_ad_group_history_data" @@ -43,7 +43,7 @@ vars: google_ads_ad_group_criterion_history_identifier: "google_ads_ad_group_criterion_history_data" microsoft_ads_source: - microsoft_ads_schema: ad_reporting_integration_tests_6 + microsoft_ads_schema: ad_reporting_integration_tests_7 microsoft_ads_account_history_identifier: "microsoft_ads_account_history_data" microsoft_ads_account_performance_daily_report_identifier: "microsoft_ads_account_performance_daily_report_data" microsoft_ads_ad_group_history_identifier: "microsoft_ads_ad_group_history_data" @@ -57,7 +57,7 @@ vars: microsoft_ads_search_query_performance_daily_report_identifier: "microsoft_ads_search_performance_daily_report_data" linkedin_source: - linkedin_ads_schema: ad_reporting_integration_tests_6 + linkedin_ads_schema: ad_reporting_integration_tests_7 linkedin_ads_account_history_identifier: "linkedin_ad_account_history_data" linkedin_ads_ad_analytics_by_creative_identifier: "linkedin_ad_analytics_by_creative_data" linkedin_ads_campaign_group_history_identifier: "linkedin_ad_campaign_group_history_data" @@ -66,7 +66,7 @@ vars: linkedin_ads_ad_analytics_by_campaign_identifier: "linkedin_ad_analytics_by_campaign_data" twitter_ads_source: - twitter_ads_schema: ad_reporting_integration_tests_6 + twitter_ads_schema: ad_reporting_integration_tests_7 twitter_ads_account_history_identifier: "twitter_account_history_data" twitter_ads_campaign_history_identifier: "twitter_campaign_history_data" twitter_ads_line_item_history_identifier: "twitter_line_item_history_data" @@ -80,7 +80,7 @@ vars: twitter_ads_line_item_keywords_report_identifier: "twitter_line_item_keywords_report_data" pinterest_source: - pinterest_schema: ad_reporting_integration_tests_6 + pinterest_schema: ad_reporting_integration_tests_7 pinterest_ads_ad_group_history_identifier: "pinterest_ad_group_history_data" pinterest_ads_campaign_history_identifier: "pinterest_campaign_history_data" pinterest_ads_pin_promotion_history_identifier: "pinterest_pin_promotion_history_data" @@ -93,7 +93,7 @@ vars: pinterest_ads_advertiser_report_identifier: "pinterest_advertiser_report_data" facebook_ads_source: - facebook_ads_schema: ad_reporting_integration_tests_6 + facebook_ads_schema: ad_reporting_integration_tests_7 facebook_ads_account_history_identifier: "facebook_ads_account_history_data" facebook_ads_ad_history_identifier: "facebook_ads_ad_history_data" facebook_ads_ad_set_history_identifier: "facebook_ads_ad_set_history_data" @@ -102,7 +102,7 @@ vars: facebook_ads_creative_history_identifier: "facebook_ads_creative_history_data" snapchat_ads_source: - snapchat_ads_schema: ad_reporting_integration_tests_6 + snapchat_ads_schema: ad_reporting_integration_tests_7 snapchat_ads_ad_account_history_identifier: "snapchat_ad_account_history_data" snapchat_ads_ad_history_identifier: "snapchat_ad_history_data" snapchat_ads_ad_hourly_report_identifier: "snapchat_ad_hourly_report_data" @@ -114,7 +114,7 @@ vars: snapchat_ads_creative_url_tag_history_identifier: "snapchat_creative_url_tag_history_data" tiktok_ads_source: - tiktok_ads_schema: ad_reporting_integration_tests_6 + tiktok_ads_schema: ad_reporting_integration_tests_7 tiktok_ads_adgroup_history_identifier: "tiktok_adgroup_history_data" tiktok_ads_ad_history_identifier: "tiktok_ad_history_data" tiktok_ads_advertiser_identifier: "tiktok_advertiser_data" @@ -124,7 +124,7 @@ vars: tiktok_ads_campaign_report_hourly_identifier: "tiktok_campaign_report_hourly_data" amazon_ads_source: - amazon_ads_schema: ad_reporting_integration_tests_6 + amazon_ads_schema: ad_reporting_integration_tests_7 amazon_ads_ad_group_history_identifier: "amazon_ads_ad_group_history_data" amazon_ads_ad_group_level_report_identifier: "amazon_ads_ad_group_level_report_data" amazon_ads_advertised_product_report_identifier: "amazon_ads_advertised_product_report_data" @@ -138,7 +138,7 @@ vars: amazon_ads_search_term_ad_keyword_report_identifier: "amazon_ads_search_term_ad_keyword_report_data" reddit_ads_source: - reddit_ads_schema: ad_reporting_integration_tests_6 + reddit_ads_schema: ad_reporting_integration_tests_7 reddit_ads_account_identifier: "reddit_ads_account_data" reddit_ads_account_report_identifier: "reddit_ads_account_report_data" reddit_ads_ad_identifier: "reddit_ads_ad_data"