0.9.0

What's Changed

This will be the final release of this package. It creates compatibility with dbt utils v1 for anyone who needs that, so that it will keep running for as long as possible.

⛔🏚️ This package is obsolete and no longer developed. Fivetran users should use fivetran/facebook_ads instead.

Full Changelog: 0.8.0...0.9.0

0.8.0

This release supports any version (minor and patch) of v1, which means far less need for compatibility releases in the future.

0.7.1

🚨 This is a compatibility release in preparation for dbt-core v1.0.0 (🎉). Projects using this version with dbt-core v1.0.x can expect to see a deprecation warning. This will be resolved in the next minor release.

dbt: facebook-ads v0.7.0

🚨 Breaking changes

• This package now requires dbt v0.20.0 and dbt-utils v0.7.0. dbt v0.20.0rc2 is currently available as a release candidate. If you are not ready to upgrade, consider using a previous version of this package.
• This package depends on dbt-labs/dbt_utils. If the latest version of another installed package depends on fishtown-analytics/dbt_utils, you'll need to wait to upgrade. See discourse for details.

Under the hood

• Use new adapter.dispatch syntax (#44)

facebook-ads v0.6.1

Incorporates #42, which fixes an issue with the macro call in stitch_fb_ads_adsets

facebook-ads v0.6.0

🚨 Breaking change — this package now requires dbt v0.18.0

Quality of life:

• Use 0.18.0 functionality, in particular the adapter.dispatch macro (#39)

facebook-ads 0.5.1

• Incorporates PR #38.

• 0.5.0 was intended to incorporate both #35 and #36 but an error in the base branch/ merge order of those PRs meant that we only incorporated #35. #38 incorporates the same changes as #36.

facebook-ads 0.5.0

🚨 Breaking change!

This package now requires dbt v0.17.x!

• Upgrades package to be compatible with dbt 0.17.0(PR #35 )
• Also specifies a frame clause for a first_value window function in fivetran_fb_url_tag , required by Redshift. (PR #36)

facebook ads v0.4.7

• this update includes significant changes to how urls are parsed and utm parameters are extracted from the urls

• incorporates the nested field macro inspired by this PR: #32

  • normalizes how nested fields are stored and then extracted across different databases

• some facebook ads have what are called 'child links'--meaning that one ad can contain multiple urls with utm parameters:

  • in Redshift, this is stored in a subtable: adcreative__object_story_spec__link_data_child_attachments
  • in Snowflake, this is a nested field within object_story_spec called child_attachments
  • a new model was built:fb_ad_creatives__child_links, which grabs these links and the utm parameters.
    • joins to fb_ad_creatives

facebook ads v0.4.6

fix snowflake base_url in creatives