Feature/linkedin click uri updates

[fivetran-joemarkiewicz]

PR Overview

This PR will address the following Issue/Feature: dbt_linkedin Issue #35

This PR will result in the following new package version: v1.10.0

This will be a breaking change as a result of the upstream dbt_linkedin and dbt_linkedin_source updates.

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

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 and dbt_linkedin 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.

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 release notes.
  • This change is in response to a LinkedIn Ads API and Fivetran LinkedIn Ads connector update 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

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

• dbt run –full-refresh && dbt test
• [n/a] dbt run (if incremental models are present) && dbt test

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
• 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

❗ Special Updates for Ad Reporting ❗

To reduce integration testing time, not all models should be enabled in the run_models.sh vars. Update the variables after dbt run and dbt test to set:

• this PR's package to true
• Google Ads and Facebook Ads to true (if not already)
• All other packages to false

Detailed Validation

Please share any and all of your validation steps:

Please see the upstream PRs for relevant validations:

• Feature/click uri deprecation dbt_linkedin_source#69
• feature/click-uri-updates dbt_linkedin#38

Additionally, please see the passing validation tests below:

If you had to summarize this PR in an emoji, which would it be?

🔗

[fivetran-joemarkiewicz]

Will update before merge and release

[fivetran-reneeli]

Looks good!

[fivetran-avinash]

lgtm