Feature/linkedin click uri updates

CHANGELOG.md

@@ -1,3 +1,24 @@
+# dbt_ad_reporting v1.10.0
+
+[PR #120](https://github.com/fivetran/dbt_ad_reporting/pull/120) includes the following updates:
+
+## Breaking Changes (within upstream dbt_linkedin_source and dbt_linkedin)
+- The dependency on dbt_linkedin has been bumped to the `[">=0.10.0", "<0.11.0"]` range and the dbt_linkedin_source dependency has been bumped to the `[">=0.10.0", "<0.11.0"]` range. These upstream version ranges include the following breaking changes. For more details regarding these changes, refer to the [dbt_linkedin_source v0.10.0](https://github.com/fivetran/dbt_linkedin_source/releases/tag/v0.10.0) and [dbt_linkedin v0.10.0](https://github.com/fivetran/dbt_linkedin/releases/tag/v0.10.0) release notes.
+  - The `click_uri_type` field has been added to the below mentioned models. This field allows users to differentiate which click uri type (`text_ad` or `spotlight`) is being used to populate the results of the `click_uri` field. 
+    - `stg_linkedin_ads__creative_history`
+    - `linkedin_ads__creative_report`
+    - `linkedin_ads__url_report`
+    - Please be aware this new field only supports `text_ad` or `spotlight` click uri types. If you are interested in this package supporting more click uri ad types, please let us know in this [Feature Request](https://github.com/fivetran/dbt_linkedin_source/issues/70).
+
+## Bug Fixes (upstream dbt_linkedin_source change)
+- The `click_uri` field has been adjusted to populate the results following a coalesce on the `text_ad_landing_page`, `spotlight_landing_page`, or `click_uri` fields. For more details refer to [dbt_linkedin_source v0.10.0](https://github.com/fivetran/dbt_linkedin_source/releases/tag/v0.10.0) release notes.
+  - This change is in response to a [LinkedIn Ads API](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/contentapi-migration-guide?view=li-lms-2024-05#adcreativesv2-api-creatives-api) and [Fivetran LinkedIn Ads connector update](https://fivetran.com/docs/connectors/applications/linkedin-ads/changelog#january2024) which moved `click_uri` data to either the `text_ad_landing_page` or `spotlight_landing_page` fields depending on the creative type.
+
+## Under the Hood
+- Addition of the following consistency validation tests for the below mentioned models to be used during integration tests (only used by Fivetran maintainers):
+  - `ad_reporting__ad_report` 
+  - `ad_reporting__url_report`
+
 # dbt_ad_reporting v1.9.0
 
 ## Under the Hood

README.md

@@ -80,7 +80,7 @@ Include the following github package version in your `packages.yml`
 ```yaml
 packages:
   - package: fivetran/ad_reporting
-    version: [">=1.9.0", "<1.10.0"] # we recommend using ranges to capture non-breaking changes automatically
+    version: [">=1.10.0", "<1.11.0"] # we recommend using ranges to capture non-breaking changes automatically
 ```
 
 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.
@@ -598,10 +598,10 @@ packages:
     version: [">=0.9.0", "<0.10.0"]
 
   - package: fivetran/linkedin
-    version: [">=0.9.0", "<0.10.0"]
+    version: [">=0.10.0", "<0.11.0"]
 
   - package: fivetran/linkedin_source
-    version: [">=0.9.0", "<0.10.0"]
+    version: [">=0.10.0", "<0.11.0"]
 
   - package: fivetran/reddit_ads
     version: [">=0.2.0", "<0.3.0"]

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'ad_reporting'
-version: '1.9.0'
+version: '1.10.0'
 
 config-version: 2
 

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'ad_reporting_integration_tests'
-version: '1.9.0'
+version: '1.10.0'
 profile: 'integration_tests'
 config-version: 2
 
@@ -10,8 +10,10 @@ dispatch:
   - macro_namespace: dbt_expectations
     search_order: ['google_ads_source', 'dbt_expectations']
 
-vars: 
-
+models:
+  +schema: "ad_reporting_{{ var('directed_schema','dev') }}"
+
+vars:
   apple_search_ads__using_search_terms: True
   twitter_ads__using_keywords: False
 
@@ -23,7 +25,7 @@ vars:
     apple_search_ads_ad_group_history_identifier: "apple_search_ad_group_history_data"
     apple_search_ads_ad_group_report_identifier: "apple_search_ad_group_report_data"
     apple_search_ads_ad_history_identifier: "apple_search_ad_history_data"
-    apple_search_ads_ad_report_identifier: "apple_search_ad_report_data"
+    apple_search_ads_ad_level_report_identifier: "apple_search_ad_report_data"
     apple_search_ads_keyword_history_identifier: "apple_search_keyword_history_data"
     apple_search_ads_keyword_report_identifier: "apple_search_keyword_report_data"
     apple_search_ads_search_term_report_identifier: "apple_search_search_term_report_data"
@@ -251,6 +253,10 @@ seeds:
       +column_types:
         created_time: timestamp
         last_modified_time: timestamp
+        status: "{{ 'string' if target.type in ['bigquery','spark','databricks'] else 'varchar' }}"
+        intended_status: "{{ 'string' if target.type in ['bigquery','spark','databricks'] else 'varchar' }}"
+        last_modified_at: timestamp
+        created_at: timestamp
     linkedin_ad_analytics_by_campaign_data:
       +column_types:
         day: timestamp

integration_tests/packages.yml

@@ -1,2 +1,2 @@
 packages:
-  - local: ../
+  - local: ../