- Updated
stripe__balance_transactionsto correctly handle multiple disputes on the same transaction:- Adjusted
customer_facing_amountto reflect thedispute_amountof the latest dispute (if the transaction is not a charge or refund and is associated with any disputes) (PR #92). - Added the following the dispute-related columns (PR #92):
latest_dispute_amount_won: Latest disputed amount that was won in favor of the merchant.latest_dispute_amount_lost: Latest disputed amount that was lost and returned to the customer.latest_dispute_amount_under_review: Latest disputed amount that is currently under review by the bank.latest_dispute_amount_needs_response: Latest disputed amount that currently needs a response (the dispute has been filed but the merchant has not yet responded with evidence).latest_dispute_amount_warning_closed: Latest disputed amount that is currently of statuswarning_under_closed(early fraud warning being closed due to no formal dispute).latest_dispute_amount_warning_under_review: Latest disputed amount that is currently of statuswarning_under_review(card issuer suspects possible fraud but hasn't yet escalated the situation to a full dispute).latest_dispute_amount_warning_needs_response: Latest disputed amount that is currently of statuswarning_needs_response(early fraud warning has been escalated into formal dispute and/or card issuer has requested more information).dispute_count: Count of disputes raised against this transaction. If > 1, join indisputedata for additional information on each dispute.
- Adjusted the
dispute_idanddispute_reasonfields to aggregate together data from multiple disputes if present. They have been renamed todispute_idsanddispute_reasonsin the following models (PR #88):stripe__balance_transactionsstripe__activity_itemized_2stripe__balance_change_from_activity_itemized_3stripe__ending_balance_reconciliation_itemized_4
- Adjusted
- Updated
disputeseed data to test the above changes (PR #92). - Added additional validation tests on the affected models from above (PR #92).
PR #89 includes the following updates:
- Addressed a potential
Divide by 0error in calculatingunit_amountin thestripe__line_item_enhancedmodel. Now, if the denominatorinvoice_line_item.quantityis 0,unit_amountwill also be 0.
- Expanded the
consistency_line_item_enhanced_counttest to also validate potential changes tounit_amountsums. - Adjusted the
invoice_line_itemseed data to include cases wherequantity= 0 in order to test the above bug fix.
PR #82 includes the following updates:
- Addition of the
stripe__line_item_enhancedmodel. This model constructs a comprehensive, denormalized analytical table that enables reporting on key revenue, subscription, customer, and product metrics from your billing platform. It’s designed to align with the schema of the*__line_item_enhancedmodel found in Stripe, Recharge, Recurly, Shopify, and Zuora, offering standardized reporting across various billing platforms. To see the kinds of insights this model can generate, explore example visualizations in the Fivetran Billing Model Streamlit App. Visit the app for more details.- This model is currently disabled by default. You may enable it by setting the
stripe__standardized_billing_model_enabledastruein yourdbt_project.yml.
- This model is currently disabled by default. You may enable it by setting the
Relevant Upstream Updates (dbt_stripe_source v0.12.0)
- Addition of the following new staging models and accompanying upstream references:
stg_stripe__discount(required for downstreamdbt_stripemodel transformations)stg_stripe__product(enabled by default, but can be disabled by setting thestripe__using_subscriptionsvariable tofalse)
- Added consistency test within integration_tests for the
stripe__line_item_enhancedmodel. - Updated the
quickstart.ymlto include theproductsource table as a requirement for thestripe__using_subscriptionsvariable.
PR #78 includes the following updates:
- Renamed folder
stripe_reportstostripe_financial_reportsto be more descriptive of the contents.⚠️ If you are using folder names to scope out configs, runs, etc., you will need to update the folder name.
- Updated model
int_stripe__date_spineto accommodate cases when modelstripe__balance_transactionshas no records.- Previously, the date spine relied on
stripe__balance_transactionsto set date bounds, which caused errors if empty. Now, the model defaults to a one-month range in such cases.
- Previously, the date spine relied on
- Updated structure of model
int_stripe__date_spinefor improved performance and maintainability.
PR #75 includes the following updates:
- No longer filters out deleted customers in
stripe__customer_overview.- Persists
is_deletedfield to differentiate between deleted and active customers. - Note that this is a 🚨 breaking change 🚨, as previously filtered-out records will appear in
stripe__customer_overview.
- Persists
- Adds the
phonecolumn tostripe__customer_overview.
- Included auto-releaser GitHub Actions workflow to automate future releases.
- Updated the maintainer PR template to resemble the most up to date format.
PR #69 contains the following updates:
- Prefixed the following fields based on their corresponding upstream source to maintain clarity:
| Previous Name | New Name |
|---|---|
| created_at | balance_transaction_created_at |
| available_on | balance_transaction_available_on |
| currency | balance_transaction_currency |
| amount | balance_transaction_amount |
| fee | balance_transaction_fee |
| net | balance_transaction_net |
| type | balance_transaction_type |
| source | balance_transaction_source_id |
| reporting_category | balance_transaction_reporting_category |
| description | balance_transaction_description |
-
Introduced the following new models, named after the Stripe reports that they follow. These models help reproduce reports available in the Stripe Reporting API. The reports introduced in this update include:
- stripe__activity_itemized_2
- stripe__balance_change_from_activity_itemized_3
- stripe__ending_balance_reconciliation_itemized_4
- stripe__payout_itemized_3
-
Updated the
stripe__balance_transactionswith the following changes:reporting_categoryhas been updated to pull directly from the titular column. If noreporting_categoryexists, it then falls to sort based on balance transactiontypein accordance to the Stripe documentation.- Added the following fields:
- dispute fields
- transfer fields
- additional payout fields
- additional customer fields
- additional card fields
- additional charge fields
- additional invoice fields
- Updated
customer_facing_amountto include for refunds and disputes as well - Updated
charge_idto charge, refund, then dispute objects consecutively
- Incorporated the new
fivetran_utils.drop_schemas_automationmacro into the end of each Buildkite integration test job. - Updated the pull request templates.
PR #61 contains the following changes:
- Updated the Metadata pivot documentation to be more clear that these variables only affect the
dbt_stripe_sourcestaging models. - Added reference to the new
stripe__card_metadataandstripe__invoice_line_item_metadatametadata variables that are available in the latest source package update.
- Updated the
cardandinvoice_line_itemseed files to be consistent with the source package versions. Specifically to include the metadata fields. - Added a new BuildKite run statement to test a few of the metadata variables.
- See the source package CHANGELOG for updates made to the staging layer in dbt_stripe_source
v0.9.1.
#60 includes the following changes:
- Unwrapped
total_*fields from the for loop instripe__daily_overviewto reduce compute required for previous for-loops - Add
account_idinint_stripe__account_rolling_totalsfor use as part of the join in the case where more than 1account_idexists.
- Intermediate model materializations have changed from ephemeral to table to reduce the compute required for the complexity of calculations.
#56 includes the following changes:
stripe__subscription_line_itemshas been removed. To recreate it, simply filterstripe__invoice_line_itemsfor wheresubscription_idis not null.- The
stripe__weekly_overview,stripe__quarterly_overview, andstripe__monthly_overviewmodels have been removed as they can be recreated directly from thestripe__daily_overviewby rolling up the date grain. - The
stripe__invoice_line_itemandstripe__subscription_line_itemshave been renamed tostripe__invoice_line_item_detailsandstripe__subscription_details. - Following the addition of the new
pricingsource table which may replace theplantable depending on whether you migrated to the Price API (Stripe doc here.), the following columns instripe__invoice_line_itemshave been updated. This package will draw the respective columns from thepriceobject by default if it exists. However, if you still have and wish to keep usingplan, you can setstripe__using_priceto False. For more please see the README
| Previous Name | New Name |
|---|---|
| plan_is_active | price_plan_is_active |
| plan_amount | price_plan_amount |
| plan_interval | price_plan_interval |
| plan_interval_count | price_plan_interval_count |
| plan_nickname | price_plan_nickname |
| plan_product_id | price_plan_product_id |
-
In addition,
stripe__plan_metadatavariable has been renamed tostripe__price_plan_metadata -
Stripe connectors set up after February 09, 2022 will use the subscription_history table, as they will no longer be syncing the subscription table. This package uses
subscription_historyby default if it exists. However, if you still have thesubscriptiontable and wish to use it instead, then set thestripe__using_subscription_historyto False. -
Variables have been prefixed with
stripe__so they can be used globally.
| Previous Name | New Name |
|---|---|
| using_invoices | stripe__using_invoices |
| using_credit_notes | stripe__using_credit_notes |
| using_payment_method | stripe__using_payment_method |
| using_livemode | stripe__using_livemode |
| using_invoice_line_sub_filter | stripe__using_invoice_line_sub_filter |
| using_subscriptions | stripe__using_subscriptions |
| using_subscription_history | stripe__using_subscription_history |
| using_price | stripe__using_price |
- In the
stripe__subscription_detailsmodel,start_datehas been updated tostart_date_atto follow our standard naming practices.
- Introducing the new model
stripe__invoice_details. - Updated the models
stripe__daily_overviewwith additional daily and rolling metrics. subscription_item_idhas been added to thestripe__invoice_line_itemsmodel.- Added the ability to union datasets across different schemas or databases. A new column populating each model called
source_relationwill specify the source of each record.
For more information please refer to the README and stripe.yml
PR #48 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_valuebool_orcast_bool_to_textconcatdate_truncdateadddatediffescape_single_quotesexcepthashintersectlast_daylengthlistaggpositionreplacerightsafe_castsplit_partstring_literaltype_biginttype_floattype_inttype_numerictype_stringtype_timestamparray_appendarray_concatarray_construct
- For
current_timestampandcurrent_timestamp_in_utcmacros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompatdbt.current_timestamp_in_utc_backcompat
- Dependencies on
fivetran/fivetran_utilshave been upgraded, previously[">=0.3.0", "<0.4.0"]now[">=0.4.0", "<0.5.0"]. - Updated README to include instructions on how to use metadata variable in cases of dictionary arguments. (#51)
- Included the
subscription_item_idfield within thestripe__invoice_line_itemsmodel. (#50) - BuildKite testing has been added. (#52)
- Included the
currencyfield within thestripe__invoice_line_itemsmodel. (#44)
- Databricks compatibility 🧱 (#44)
- README updates for easier package navigation and understanding. (#41)
- Updating the package dependency to reference the proper [">=0.7.0", "<0.8.0"] version range of
dbt_stripe_source. (#41)
- Stripe connectors set up after February 09, 2022 no longer sync the
subscriptiontable; however, a newersubscription_historytable is synced. To account for this change a variablestripe__subscription_historyhas been added to the package project to allow for users to define if their source contains thesubscription_historytable. (#37)- By default this variable is set to
false. If you still have thesubscriptiontable, then there is no adjustment needed on your end. If you do have thesubscription_historytable then you will want to set the variable totrue. - Similarly, if you have both tables, then I highly encourage you start leveraging the
subscription_historysource table in your package. - This package now points to the latest
dbt_stripe_sourcepackage version which accounts for the above update. (#33 and #34)
- By default this variable is set to
- #35: Fix issue with timezone conversion in postgres by updating the
date_timezonemacro with postgres functionality. @johnf - Added Postgres support for the Stripe package.
- See PR #37
- #24: Updating docs to add
dbt_stripedocumentation in addition todbt_stripe_sourcedocumentation. - #27: Updating
models/stripe__customer_overview.sqlto usemaxinstead ofminfor calculatingmost_recent_sale_date. - #28: Updating
models/stripe__customer_overview.sqlto include "No Associated Customer" records.- This PR accounts for when a transaction may be tied to a customer_id that has not yet synced into the customers table due primarily due to a sync lapse between the tables; in which case, the customer_description field will be "No Associated Customer".
- Each "No Associated Customers" record will be an individual row, since we can not predictably do any group bys due to the
stripe__customer_metadatavariable variability in both datatype and number of metadata fields.
🎉 dbt v1.0.0 Compatibility 🎉
- Adjusts the
require-dbt-versionto 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_stripe_source. Additionally, the latestdbt_stripe_sourcepackage has a dependency on the latestdbt_fivetran_utils. Further, the latestdbt_fivetran_utilspackage also has a dependency ondbt_utils[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utilsin yourpackages.ymlthat is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
- Add functionality to include customer metadata in
stripe__customer_overview. (#21) The customer metadata is passed in from thestg_stripe__customermodel in the Stripe source package.- For more information refer to the Stripe source package CHANGELOG
- Refer to the relevant release notes on the Github repository for specific details for the previous releases. Thank you!