fivetran-data-model-bot
released this
05 Nov 17:46
·
1 commit
to main
since this release
PR #51 includes the following updates:
Breaking Changes (--full-refresh
required after upgrading)
- Added a field called
first_open_or_click_event_at
in theiterable__user_campaign
model. This timestamp shows the first time a user interacted with a campaign, recording the earliest occurring event out of 'emailOpen', 'emailClick', and 'pushOpen'. (PR #50) - Corrected the incremental filter in
iterable__events
model to now use thecreated_on
date field instead of thecreated_at
timestamp.- Previously, this would potentially exclude late-arriving new records from populating in the end models if they had an older
created_at
value than what was present in the model. Switching tocreated_on
widens the criteria.
- Previously, this would potentially exclude late-arriving new records from populating in the end models if they had an older
- Updated upstream
stg_iterable__user_history
model from materializing as a table to a view in order to improve performance. - In order to ensure no issues, a
--full-refresh
is required after upgrading.
Under the Hood
- In addition to using
created_on
in the incremental logic initerable__events
, we introduced aiterable_lookback_window
variable to increase the window for accommodating potential late-arriving records. The default is 7 days prior to the maximumcreated_on
value present in theiterable__events
model, but you may customize this by setting the variterable_lookback_window
in your dbt_project.yml. See the Lookback Window section of the README for more details. - Added a section in the README about the
iterable__event_metrics
variable and how to use it to specify which event metrics to pivot out. (PR #49) - Removes
created_on
from the uniqueness test initerable__events
. Uniqueness is now tested solely onunique_event_id
, a surrogate key made up ofevent_id
(_fivetran_id
in the raw table, which is a Fivetran-created unique identifier derived from hashing campaign_id, created_at, and event_name) and_fivetran_user_id
(a Fivetran-created column derived from a hash ofuser_id
and/oremail
). - Modified the
event
seed data to more accurately represent real-life data, with a unique_fivetran_id
for eachcampaign_id
,created_at
, andevent_name
.
Documentation Update
- Updates the descriptions of timestamp-based fields. Previously they were described as milliseconds since epoch time, but they should be standard timestamps.
Contributors
Full Changelog: v0.12.0...v0.13.0