Version 1.3 API updates

[fivetran-avinash]

PR Overview

This PR will address the following Issue/Feature: [#8]

This PR will result in the following new package version: Version 0.4.0

We are updating old fields and renaming them to current fields based on the API updates, and we ensured backward compatibility by coalescing the two fields.

Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:

• In the July 2023 connector update for TikTok Ads, we upgraded the connector to the v1.3 API. As a result the dependent fields and field names from the downstream staging models have changed.
• In stg_tiktok_ads__ad_group_history, age has been renamed as age_groups.
• In stg_tiktok_ads__advertiser, phone_number has been renamed as cellphone_number, and telephone has been renamed as telephone_number.
• We coalesced the old API field names with these renamed fields to ensure backwards compatibility for these fields.

PR Checklist

Basic Validation

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

• dbt compile
• dbt run –full-refresh
• dbt run
• dbt test
• dbt run –vars (if applicable)

Before marking this PR as "ready for review" the following have been applied:

• The appropriate issue has been linked and tagged
• You are assigned to the corresponding issue and this PR
• BuildKite integration tests are passing

Detailed Validation

Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

• You have validated these changes and assure this PR will address the respective Issue/Feature.
• You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
• You have provided details below around the validation steps performed to gain confidence in these changes.

Renamed fields were appropriately showing from local and seed runs. Running the latest version of package should reflect the renamed fields from the above models.

Standard Updates

Please acknowledge that your PR contains the following standard updates:

• Package versioning has been appropriately indexed in the following locations:
  • indexed within dbt_project.yml
  • indexed within integration_tests/dbt_project.yml
• CHANGELOG has individual entries for each respective change in this PR
• README updates have been applied (if applicable)
• [NA] DECISIONLOG updates have been updated (if applicable)
• Appropriate yml documentation has been added (if applicable)

dbt Docs

Please acknowledge that after the above were all completed the below were applied to your branch:

• docs were regenerated (unless this PR does not include any code or yml updates)

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

🕐

[fivetran-joemarkiewicz]

@fivetran-avinash thanks for working through this API update! Your changes look good, I just have a few requests to update the code highlighted in my review below.

Additionally, one more change that needs to be applied before approving:

• Be sure to update the README version of the package as this is a breaking change. I noticed you marked that check as NA in the PR submission form. However, since this is a breaking change, we will want to make that update to reference the new version range.

[fivetran-avinash]

@fivetran-joemarkiewicz Thanks for noting the lack of a README update! Fixed that and applied all other changes now.

[fivetran-joemarkiewicz]

Changes look great! Thanks for working through these. Approved!