PR #36 includes the following updates:
- Incorporates the
basic_ad_actions
andbasic_ad_action_values
pre-built reports in order to grab conversion data. They are both child tables of the already-requiredbasic_ad
report, broken down byaction_type
.- Addition of the new
stg_facebook_ads__basic_ad_actions
andstg_facebook_ads__basic_ad_action_values
(and their_tmp
counterparts) staging models. Given that this is a schema change for the package, this is a breaking change.
- Addition of the new
- With the inclusion of the
basic_ad_actions
andbasic_ad_action_values
source tables, we have added thefacebook_ads__basic_ad_actions_passthrough_metrics
andfacebook_ads__basic_ad_action_values_passthrough_metrics
variables to pass through additional conversion value metrics to downstream models. - Adds the
optimization_goal
field tostg_facebook_ads__ad_set_history
model. This is defined as the optimization goal this ad set is using, possible values of which are defined here. - Adds the
conversion_domain
field tostg_facebook_ads__ad_history
model. This is defined as the domain you've configured the ad to convert to.
- Documents the ability to transform metrics provided to the new
facebook_ads__basic_ad_passthrough_metrics
andfacebook_ads__basic_ad_action_values_passthrough_metrics
variables. See README for details.
- Creates
facebook_ads_fill_pass_through_columns
macro to make passthrough column logic in the new staging models DRYer.
PR #37 includes the following update:
- Updated partition logic in
*_history
staging models to account for null tables, which could causeconstant expressions are not supported in partition by clauses
errors in Redshift.
PR #35 includes the following updates:
- Resolved the "duplicate column" error that would arise when the
facebook_ads__basic_ad_passthrough_metrics
variable includedreach
orfrequency
.Reach
andfrequency
were included by default in thestg_facebook_ads__basic_ad
model but will now only persist to downstream transform models if specified in thefacebook_ads__basic_ad_passthrough_metrics
variable.- This error is now avoided by first checking if
reach
andfrequency
are included infacebook_ads__basic_ad_passthrough_metrics
and only selecting the columns once if so.
- This error is now avoided by first checking if
- Updated the maintainer PR template to our most up-to-date standards.
- Removed the now defunct 2nd-reviewer workflow bot.
PR #33 includes the following updates:
- Updated
stg_facebook_ads__creative_history
test instg_facebook_ads.yml
to test uniqueness on identifier_fivetran_id
, since there are rare cases where_fivetran_synced
andcreative_id
could hold the same value.
PR #31 includes the following updates:
- The prerequisite steps in the README for generating the
basic_ad
pre-built report have been modified to reflect the current state of the Facebook Ads connector. - Adds the DECISIONLOG to clarify why there exist differences among aggregations across different grains.
PR #28 includes the following updates:
- Unioning capability! This adds the ability to union source data from multiple facebook_ads connectors. Refer to the Union Multiple Connectors README section for more details.
- Updated tmp models to union source data using the
fivetran_utils.union_data
macro. - To distinguish which source each field comes from, added
source_relation
column in each staging model and applied thefivetran_utils.source_relation
macro. - Updated tests to account for the new
source_relation
column. - Incorporated the new
fivetran_utils.drop_schemas_automation
macro into the end of each Buildkite integration test job. - Updated the pull request templates.
PR #23 includes the following breaking changes:
- Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically
{{ dbt_utils.<macro> }}
have been updated to{{ dbt.<macro> }}
for the below macros:any_value
bool_or
cast_bool_to_text
concat
date_trunc
dateadd
datediff
escape_single_quotes
except
hash
intersect
last_day
length
listagg
position
replace
right
safe_cast
split_part
string_literal
type_bigint
type_float
type_int
type_numeric
type_string
type_timestamp
array_append
array_concat
array_construct
- For
current_timestamp
andcurrent_timestamp_in_utc
macros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompat
dbt.current_timestamp_in_utc_backcompat
packages.yml
has been updated to reflect new defaultfivetran/fivetran_utils
version, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.
PR (#25)[#22] includes the following changes:
- Updates source models to include more potentially useful columns and respective definitions within
src.yml
andstg.yml
. - Added passthrough functionality for
BASIC_AD
pre-built report usingfacebook_ads__basic_ad_metrics
variable.facebook_ads__basic_ad_metrics
example.
vars:
facebook_ads__basic_ad_metrics:
- name: "my_field_to_include" # Required: Name of the field within the source.
alias: "field_alias" # Optional: If you wish to alias the field within the staging model.
- Updates
is_most_recent_record
logic to take inupdated_time
rather than_fivetran_synced
for the following models:stg_facebook_ads__campaign_history
stg_facebook_ads__ad_set_history
stg_facebook_ads__ad_history
- Model grain tests were added for better data integrity.
- Addition of identifier variables for each of the source tables to allow for further flexibility in source table direction within the dbt project.
README
updates for easier navigation and use of the package.
🎉 dbt v1.0.0 Compatibility 🎉
- Adjusts the
require-dbt-version
to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.- For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
- For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
- Upgrades the package dependency to refer to the latest
dbt_fivetran_utils
. The latestdbt_fivetran_utils
package also has a dependency ondbt_utils
[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utils
in yourpackages.yml
that is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
Refer to the relevant release notes on the Github repository for specific details for the previous releases. Thank you!