You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,19 @@
1
-
# dbt_google_ads v0.x.x
2
-
3
-
[PR #58](https://github.com/fivetran/dbt_google_ads/pull/58) includes the following updates:
4
-
## Under the Hood:
5
-
- Updates the [DECISIONLOG](DECISIONLOG.md) to clarify why there exist differences among aggregations across different grains.
1
+
# dbt_google_ads v0.10.0
2
+
[PR #52](https://github.com/fivetran/dbt_google_ads/pull/52) includes the following updates:
3
+
## Feature update 🎉
4
+
- Unioning capability! This adds the ability to union source data from multiple google_ads connectors. Refer to the [Union Multiple Connectors README section](https://github.com/fivetran/dbt_google_ads/blob/main/README.md#union-multiple-connectors) for more details.
5
+
6
+
## Under the Hood 🚘
7
+
- In the source package, updated tmp models to union source data using the `fivetran_utils.union_data` macro.
8
+
- To distinguish which source each field comes from, added `source_relation` column in each staging and downstream model and applied the `fivetran_utils.source_relation` macro.
9
+
- The `source_relation` column is included in all joins in the transform package.
10
+
- Updated tests to account for the new `source_relation` column.
11
+
12
+
[PR #60](https://github.com/fivetran/dbt_google_ads/pull/60) includes the following update:
13
+
## Dependency Updates
14
+
- Removes the dependency on `dbt-expectations`. Upstream we specifically removed the `dbt_expectations.expect_column_values_to_not_match_regex_list` test.
15
+
## Under the Hood
16
+
- Updates the [DECISIONLOG](DECISIONLOG.md) to clarify why there exist differences among aggregations across different grains.
6
17
7
18
# dbt_google_ads v0.9.3
8
19
[PR #57](https://github.com/fivetran/dbt_google_ads/pull/57) includes the following updates:
Copy file name to clipboardExpand all lines: README.md
+14-15Lines changed: 14 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,14 +39,11 @@ To use this dbt package, you must have the following:
39
39
- A **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL**, or **Databricks** destination.
40
40
41
41
### Databricks Dispatch Configuration
42
-
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.
42
+
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`.
@@ -55,7 +52,7 @@ Include the following google_ads package version in your `packages.yml` file:
55
52
```yaml
56
53
packages:
57
54
- package: fivetran/google_ads
58
-
version: [">=0.9.0", "<0.10.0"] # we recommend using ranges to capture non-breaking changes automatically
55
+
version: [">=0.10.0", "<0.11.0"] # we recommend using ranges to capture non-breaking changes automatically
59
56
```
60
57
Do **NOT** include the `google_ads_source` package in this file. The transformation package itself has a dependency on it and will install the source package as well.
61
58
@@ -70,7 +67,17 @@ vars:
70
67
71
68
## (Optional) Step 4: Additional configurations
72
69
73
-
<details><summary>Expand for configurations</summary>
70
+
### Union multiple connectors
71
+
If you have multiple google_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 `google_ads_union_schemas` OR `google_ads_union_databases` variables (cannot do both) in your root `dbt_project.yml` file:
72
+
73
+
```yml
74
+
vars:
75
+
google_ads_union_schemas: ['google_ads_usa','google_ads_canada'] # use this if the data is in different schemas/datasets of the same database/project
76
+
google_ads_union_databases: ['google_ads_usa','google_ads_canada'] # use this if the data is in different databases/projects but uses the same schema name
77
+
```
78
+
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`.
79
+
80
+
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.
74
81
75
82
### Adding passthrough metrics
76
83
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:
0 commit comments