Describe the feature

The package needs to be updated to reflect the new tables and structures being extracted due to Stitch leveraging the newer version of Adwords API.

Additional context

Stitch deprecated their Adwords connector in favor of a new one, due to Google recently launching a new AdWords API.

Who will this benefit?

This will benefit current and future Stitch users that use the Adwords connector. It would prevent a lot of re-work related to creating new macros for the new API. Stitch fully deprecated the old connector.

Describe the feature

It seems advantageous to update the dbt_utils package version to support segment as these are commonly used together. See version mismatch in image below. It needs to be >=0.8.0.

Describe alternatives you've considered

We've gone through all dependencies and downgraded each to make this work as a workaround, but this is now throwing some warnings.

Who will this benefit?

Anyone using the newest versions of segment and adwords packages will be affected by this.

Repo checklist:

Urgent:

• A require-dbt-version parameter in the dbt_project.yml:

require-dbt-version: [">=0.17.0", "<0.18.0"]

• The dbt_project.yml is in version 2 format (upgrading docs)
• Any sample dbt_project.yml snippets in the README.md are in v2 syntax (especially for packages that use vars
• Release is of format major.minor.patch, e.g. 1.0.0
• A license (example)
• If this package relies on dbt-utils, make sure the range allows v0.4.x

packages:
  - package: fishtown-analytics/dbt_utils
    version: ["???", "<0.5.0"]

Integration tests

If this package has integration tests:

• The dbt_project.yml of the integration tests is in v2 format
• CircleCI uses python v3.6.3
• The dbt_project.yml does not have a require-dbt-version config (it should be inherited from the package)

This package is no longer compatible with dbt v0.19.0. Is this still being actively maintained?

Encountered an error:
Runtime Error
  Failed to read package: Runtime Error
    Invalid config version: 1, expected 2

With the recent update to use adwords_url_performance to feed into the adwords_ad_performance_adapter I think we should update the dbt_project.yml file to remove the disabled default on this model. If a use doesn't configure it true in their repository, it returns an error to run the package

This package is really helpful, thanks for building it. One issue we've run into is that Stitch is structuring our data slightly differently than what's expected by this package. Fields structured as arrays in the Adwords schema (e.g. the labels field in the ad_groups model) are being stored as separate tables rather than as fields containing nested data (we're using Redshift as our target database). Sorry if I'm missing something easy configuration-wise.

We could handle this problem on our end by writing some dbt models on top of the Stitch source data to put the data into the form this package expects, or by forking the repo and modifying the schema to match what Stitch is generating (found an example of someone else doing that as well).

I'm happy to go with one of those solutions if that's the best path forward. It this is something you think would be good to support within the package itself, I'd also be willing to try to put together a PR for that.