Feature: Add Quickstart Model Counts to README

CHANGELOG.md

@@ -1,3 +1,9 @@
+# dbt_google_ads version.version
+
+## Documentation
+- Added Quickstart model counts to README. ([#73](https://github.com/fivetran/dbt_google_ads/pull/73))
+- Corrected references to connectors and connections in the README. ([#73](https://github.com/fivetran/dbt_google_ads/pull/73))
+
 # dbt_google_ads v0.11.0
 
 [PR #66](https://github.com/fivetran/dbt_google_ads/pull/66) includes the following updates:

README.md

@@ -31,14 +31,16 @@ The following table provides a detailed list of all tables materialized within t
 | [google_ads__ad_report](https://fivetran.github.io/dbt_google_ads/#!/model/model.google_ads.google_ads__ad_report)            | Each record in this table represents the daily performance at the ad level. |
 | [google_ads__url_report](https://fivetran.github.io/dbt_google_ads/#!/model/model.google_ads.google_ads__url_report)            | Each record in this table represents the daily performance of URLs at the ad level. |
 
+### Materialized Models
+Each Quickstart transformation job run materializes 26 models if all components of this data model are enabled. This count includes all staging, intermediate, and final models materialized as `view`, `table`, or `incremental`.
 <!--section-end-->
 
 ## How do I use the dbt package?
 
 ### Step 1: Prerequisites
 To use this dbt package, you must have the following:
 
-- At least one Fivetran Google Ads connector syncing data into your destination.
+- At least one Fivetran Google Ads connection syncing data into your destination.
 - A **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL**, or **Databricks** destination.
 
 #### Databricks Dispatch Configuration
@@ -70,8 +72,8 @@ vars:
 
 ### (Optional) Step 4: Additional configurations
 
-#### Union multiple connectors
-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:
+#### Union multiple connections
+If you have multiple google_ads connections 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:
 
 ```yml
 vars:
@@ -122,7 +124,7 @@ models:
 ```
 
 #### 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 when running the package on multiple unioned connectors.
+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 when running the package on multiple unioned connections.
 
 > IMPORTANT: See this project's [`dbt_project.yml`](https://github.com/fivetran/dbt_google_ads/blob/main/dbt_project.yml) variable declarations to see the expected names.