January 2026

Connector SDK

Fivetran Connector SDK

You can now create and manage Connector SDK connections programmatically using the new Connector SDK Package Management API along with the fivetran package command. The fivetran package command creates a ZIP archive of your connector code. The Connector SDK Package Management API allows you to do the following:

• Upload connector code packages
• Update existing packages
• List, retrieve, and delete packages
• Download package files

For more information, see the Connector SDK API documentation.

fivetran-connector-sdk PyPI package

We have released version 2.6.0 of the fivetran-connector-sdk PyPI package. This release adds the following:

• Security fixes for vulnerabilities in grpcio and pipreqs-fivetran
• Improved PyPI package logging
• Enhanced package management.
• Minor enhancements and improvements.

We have released version 2.5.1 of the fivetran-connector-sdk PyPI package. This release adds the following:

• New deployment strategy for Connector SDK connections.
• Minor enhancements and improvements.

We have released version 2.5.0 of the fivetran-connector-sdk PyPI package. This release adds the following:

• Updated testers to use DuckDB version 1.4.2
• Minor enhancements and improvements.

Fivetran Proxy Agent

Version 1.1.6

We released Fivetran Proxy Agent 1.1.6, which is bundled with High-Volume Agent version 6.1.0/93.

This release also includes:

• Security updates: Upgraded dependencies to address several CVEs in third-party libraries.
• Bug fix: the agent now properly retries connecting to the data source after initial connection failures.

You can download the updated package from the Downloads page.

Lite Connectors

Lite connectors are now available for the following sources:

• Fireflies
• HighLevel
• NetSuite SuiteProjects Pro
• OneTrust
• PeopleForce
• SAP SuccessFactors
• ServiceTrade
• Stackadapt

Partner SDK

Partner SDK Tester

We added testing tools for source and destination Partner SDK connectors.

We have released version 2.26.0508.001 of the Partner SDK Tester. This release includes the following improvements:

• Minor improvements and bug fixes to enhance the testing experience for Partner SDK connectors.

We have released version 2.26.0127.001 of the Partner SDK Tester. This release includes the following improvements:

• Updated the tester to throw an unsupported operation exception for LIVE mode schema migrations, aligning its behavior with production since PSDK does not yet support LIVE mode operations.

We have released version 2.26.0121.001 of the Partner SDK Tester. This release includes the following improvements:

• Updated column adjustment logic to match production behavior, ensuring consistency between testing and production environments

We have released version 2.26.0113.001 of the Partner SDK Tester. This release includes the following improvements:

• Fixed handling of the _fivetran_deleted column for soft_delete mode tables by default

We have released version 2.26.0105.001 of the Partner SDK Tester. This release includes the following improvements:

• Fixed default behavior for _fivetran_deleted column in soft delete mode

Convex connector for Fivetran

You can now exclude Convex components, tables, and columns from your syncs on the Schema tab of your connection details page in the Fivetran dashboard.

For more information, see our Data Blocking documentation and the Convex connector documentation.

SurrealDB destination is in beta

The SurrealDB destination is now in beta. For more information, see the SurrealDB destination documentation.

Quickstart Package Updates

Quickstart data model package updates

v0.3.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v0.6.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v2.5.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.3.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v0.4.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v0.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.1.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

v1.2.0

Features

• Increases the required dbt version upper limit to v3.0.0.

v0.15.0

Features

• Increases the required dbt version upper limit to v3.0.0

v0.1.0-b4

Features

• Increases the required dbt version upper limit to v3.0.0.

v1.3.1

Bug Fix

• Restores pass-through column functionality in the iterable__users model.

v0.16.1

Under the Hood

• Removes the date_range_start variable from the quickstart.yml.

v0.8.1

Test Fixes

• Removes duplicate column definitions in YAML schema files to avoid dbt parse warnings.

v1.1.1

Bug fix

• Increases required DBT version upper limit to v3.0.0 in the project.yml, correcting an earlier error.

v1.4.1

Under the Hood

• Removes the recharge_first_date and recharge_last_date variables from the quickstart.yml.

v0.3.1

Under the Hood

• Adjusts the data type of aws_cloud_cost_start_date in the quickstart.yml from string to date.

v1.5.1

Under the Hood

• Adjusts the data type of shopify__calendar_start_date in the quickstart.yml from string to date.

v1.6.1

Test Fixes

• Removes duplicate column definitions in YAML schema files to avoid dbt parse warnings.
• Corrects descriptions for several fields.

v0.2.0

Features

• Increases the required dbt version upper limit to v3.0.0

Under the Hood

• Updates the README and integration tests architecture to align with other packages

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v0.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.6.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v2.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v0.16.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.3.1

Under the Hood

• Removes the amplitude__date_range_end variable from the quickstart.yml.
• Adjusts the data type of amplitude__date_range_start in the quickstart.yml from string to date.

v1.3.1

PR #194 includes the following updates:

Under the Hood (Quickstart Update)

• Removes duplicative variables defined within the quickstart.yml.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v0.5.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v0.8.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v0.8.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting

Under the Hood

Upstream Dependency Changes

• Increases the required Linkedin Pages package to version 1.2.0

v1.2.1

PR #27 introduces the following update:

Bug Fix

• Limits column introspection in pardot__campaigns (via the int__opportunity_tmp model) to execution time (i.e. during the dbt run and dbt build) to avoid errors during dbt compile.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v0.4.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.6.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.5.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v2.3.0

Upstream Breaking Changes

• Increases the required facebook_ads package to version 1.3.0
• Increases the required reddit_ads package to version 1.3.0.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
  • Adds supported_vars for Quickstart UI customization.

v1.1.0

Documentation

• Updates README with standardized Fivetran formatting.

Upstream Dependency Changes

• Increases the required Shopify package to version 1.5.0.
• Increases the required Klaviyo package to version 1.3.0.

v1.2.0

Documentation

• Updates README with standardized Fivetran formatting

Upstream Dependency Changes

• Increases the required Google Play package to version 1.2.0
• Increases the required Apple Store package to version 1.2.0

v1.3.1

Bug Fix

• Fixes double-counting of Instagram impressions in social_media_reporting__instagram_posts_reporting. Fivetran's Instagram Connector populates multiple fields with the same value for certain media types (CAROUSEL_ALBUM and VIDEO/Reels). Previously, the model summed all view metrics, which counted impressions twice. The fix takes video_photo_views or video_photo_impressions, which is the basis for both carousel_album and reel impressions/views.

v1.2.1

Feature Update

• Introduces the max_ticket_length_weeks variable. This variable defines the maximum length of time, in weeks, that the package expects a ticket to be open for business hour calculations and SLA policy computations.
  • The default value is 52 weeks (one year)
  • If your organization has tickets that are open for more than a year, apply the following configuration in your root dbt_project.yml file:

### dbt_project.yml
vars:
  zendesk:
    max_ticket_length_weeks: 208 # Integer value: Ensure this is >= the longest period a ticket was open (in weeks)

v1.5.0

Schema/Data Changes

3 total changes • 1 possible breaking changes

Under the Hood

• Updates seeds and macros to support the schema changes.

v1.1.1

Schema/Data Change

1 total change • 0 breaking changes

Bug Fixes

• Fixed double-counting of net amounts in int_google_play__earnings. Previously, this intermediate calculation created duplicate net_order_amount values for each order line item, incorrectly summing total net amounts. The summation is now performed directly in the daily_country_metrics CTE in int_google_play__earnings. (PR #26)
• Added flags in int_google_play__earnings to fix dbt fusion compilation errors. (PR #28)

Under the Hood

• Syntactic fixes applied to consistency tests. (PR #26)

v1.4.0

Schema/Data Change

4 total changes • 1 possible breaking change

Under the Hood

• Updates int_quickbooks__general_ledger_date_spine date generation logic to prevent errors during compilation.
• Renames analysis/ directory to analyses/ for consistency with dbt naming conventions.
• Corrects misspelling of payed_to_account_id to paid_to_account_id within int_quickbooks__bill_double_entry model. Note this does not result in a schema change.

v0.4.1

Schema/Data Change

4 total changes • 2 possible breaking changes

Under the Hood

• Removes unused seed files.
• Creates consistency validation test for amazon_selling_partner__item_inventory.
• Adds identifier variables for seed files.

v0.7.0

Schema/Data Changes

2 total changes • 0 possible breaking changes

Documentation

• Adds a section to the DECISIONLOG.md with a recommendation for avoiding the manual creation of duplicate sys_choice values, per ServiceNow's advised best practices. (#24)
• Ensures column types are consistent and accurate in the hosted docs. (#25)

Under the Hood

• Sets explicit column_types for all seed files to ensure data type consistency across data warehouses. (#25)
• Streamlines integration test cmdb_ci_data and core_company_data seed files by removing unused columns to improve test maintainability. (#25)

v1.3.0

Schema Changes

2 total changes • 1 possible breaking change

Feature Update

• Introduces support for the newer, more flexible unioning framework. Previously, to run the package on multiple Xero sources at once, you could only use the union_schemas variable OR union_databases (mutually exclusive). While these setups are still supported for backwards compatibility, we recommend using xero_sources instead, which can be configured as such:

### dbt_project.yml

vars:
  xero:
    xero_sources:
      - database: connection_1_destination_name # Required
        schema: connection_1_schema_name # Required
        name: connection_1_source_name # Required only if following this step: https://github.com/fivetran/dbt_xero/blob/main/README.md#recommended-incorporate-unioned-sources-into-dag

      - database: connection_2_destination_name
        schema: connection_2_schema_name
        name: connection_2_source_name

• See the README for more details.

v2.4.0

Documentation

• Updates README with standardized Fivetran formatting

Upstream Dependency Changes

• Increases the required Amazon Ads package to version 1.2.0
• Increases the required Apple Search Ads package to version 1.2.0
• Increases the required Facebook Ads package to version 1.4.0
• Increases the required Google Ads package to version 1.2.0
• Increases the required LinkedIn Ads package to version 1.2.0
• Increases the required Microsoft Ads package to version 1.2.0
• Increases the required Pinterest Ads package to version 1.2.0
• Increases the required Reddit Ads package to version 1.4.0
• Increases the required Snapchat Ads package to version 1.2.0
• Increases the required TikTok Ads package to version 1.2.0
• Increases the required Twitter Ads package to version 1.2.0

v1.3.0

Schema/Data Change

2 total changes • 2 possible breaking changes

Feature Update

• When netsuite2__using_to_subsidiary is enabled, netsuite2__balance_sheet applies each transaction’s to_subsidiary fiscal calendar. If to_subsidiary is null, the model falls back to the fiscal calendar of the transaction’s subsidiary_id.
• Increases the required dbt version upper limit to v3.0.0

Under the Hood

• Adds full_name column to the get_accountingperiodfiscalcalendars_columns macro to support the new staging model field.
• Updates integration test seed data to include sample full_name values for testing the new functionality.
• In netsuite2__balance_sheet, combines variables netsuite2__using_to_subsidiary and netsuite2__using_exchange_rate into using_to_subsidiary_and_exchange_rate to simplify configuration.

v1.5.0

Schema/Data Change

3 total changes • 2 possible breaking change

Under the Hood

• Updated intercom__admin_metrics to filter conversations using is_assignee_admin boolean instead of the deprecated conversation_assignee_type = 'admin' string comparison
• Enhanced intercom__conversation_enhanced with a left join to the admin table to determine admin assignee status
• Updates to the integrity and consistency validation tests to ensure accurate testing of model changes between versions.

v1.4.0

Schema/Data Changes

11 total changes • 11 possible breaking changes

Feature Updates

• Introduces the shopify_max_metafields variable to configure the number of metafields pivoted into columns. Configure it as follows (see README for details):

vars:
  shopify_max_metafields: 200 # (Any positive integer) Default is 50

Bug Fixes

• Deduplicates metafields with identical slugs (for example, my-first-metafield and my_first_metafield) to prevent ambiguous column errors.
• Ensures the stg_shopify_gql__shop.enabled_presentment_currencies and stg_shopify_gql__transaction.receipt fields are strings.
• Applies the following warehouse-dependent limits on the number of metafields that are pivoted into columns, regardless of the value of shopify_max_metafields. Metafields are included based on their prevalence in your Shopify METAFIELD table:
  • BigQuery: 10,000
  • Redshift: 1,600
  • Postgres: 1,600
  • Databricks: 32,768
  • Snowflake: No limit

Under the Hood

• Adds data validation tests for metafield models.
• Adjusts metafield seed data to test for duplicate slugs/column names.
• Creates max_columns() and downstream_model_column_count() macros to support adherence to warehouse column limits when pivoting metafields.

v1.0.0

Breaking Changes (--full-refresh required after upgrading)

• Increases the upstream dbt_shopify dependency from [">=0.21.0", "<0.22.0"] → [">=1.4.0", "<1.5.0"]. Refer to the below Shopify releases to understand the full scope of changes:
  • dbt_shopify v0.22.0
  • dbt_shopify v1.0.0
  • dbt_shopify v1.1.0
  • dbt_shopify v1.2.0
  • dbt_shopify v1.3.0
  • dbt_shopify v1.3.1
  • dbt_shopify v1.4.0
• Increases the upstream dbt_klaviyo dependency from [">=1.0.0", "<1.1.0"] → [">=1.2.0", "<1.3.0"]. Refer to the below Klaviyo releases to understand the full scope of changes:
  • dbt_klaviyo v1.1.0
  • dbt_klaviyo v1.1.1
  • dbt_klaviyo v1.2.0
  • dbt_klaviyo v1.2.1

Feature Update

• Adds support for Shopify GraphQL API alongside existing REST API support. Models now dynamically reference the appropriate upstream tables based on the shopify_api variable, which is either rest (default) or graphql.

Under the Hood

• Increases the required dbt version upper limit to v3.0.0.
• Removes conditional compilation logic for shopify__using_order_line_refund, shopify__using_refund, and shopify__using_order_adjustment variables in int__daily_shopify_customer_orders. These columns are now always included in the aggregation.
• Adds missing Shopify variables to the quickstart.yml file.
• Updates Buildkite steps and seed files to adequately test the GraphQL schema.

v1.3.0

Schema/Data Change

12 total changes • 0 possible breaking changes

By default, the package includes conversion metrics for three event types: purchase, lead, and custom. You can configure alternative conversion events to be tracked by adjusting the reddit_ads__conversion_event_types variable in your dbt_project.yml. Each event type configured will generate four corresponding columns ({event_type}_conversions, {event_type}_view_through_conversions, {event_type}_value, and {event_type}_items) across all report models. See the README for how to configure conversion event types.

v1.4.0

Schema/Data Change

3 total change • 0 possible breaking changes

Feature Update

• Adds new analyses folder with advanced revenue reporting:
  • stripe__arr_snapshot_analysis: Generates a high-level ARR snapshot report for the entire business for revenue forecasting.
  • stripe__customer_mrr_analysis: Generates an MRR report at the customer level for retention reporting and cohort analysis.
  • These analysis files reference the stripe__subscription_item_mrr_report model and can be compiled using dbt compile and executed directly in your data warehouse.

Documentation

• Adds comprehensive column documentation for stripe__subscription_item_mrr_report in stripe.yml.
• Adds README in the analysis folder with instructions on how to compile and use the analysis SQL.

Under the Hood

• Adds consistency test for stripe__subscription_item_mrr_report model.
• Updates integration_tests/seeds/price_data.csv with additional test data.
• Adds stripe__subscription_item_mrr_report model to quickstart.yml public models list.

v1.3.0

Schema/Data Change

10 total changes • 0 possible breaking changes

The default action types included are onsite_conversion.purchase, onsite_conversion.lead_grouped, offsite_conversion.fb_pixel_purchase, offsite_conversion.fb_pixel_lead, and offsite_conversion.fb_pixel_custom. You can add additional custom action types by configuring the facebook_ads__conversion_action_types variable. See the README for details on how to configure custom action types.

Under the Hood

• Adds facebook_action_slug macro to generate slugified column names from action type configurations.

v0.6.0

Schema/Data Change

15 total changes • 0 breaking changes

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• Creates the following compatibility view intermediate models to handle complex transformations:
  • COEP: int_coep__acdoca_base, int_coep__acdoca_calculated, int_coep__acdoca_aggregated, int_coep__acdoca_final, int_coep__original
  • COSP: int_cosp__acdoca_base, int_cosp__acdoca_amounts, int_cosp__acdoca_timestamp, int_cosp__coep_derived, int_cosp__acdoca_derived
• Adds new enable/disable variables for all new staging tables: sap_using_t006, sap_using_cosp_bak, sap_using_bsad_bck, sap_using_coep, sap_using_prps
• Enhances remove_slashes_from_col_names macro to support database reserved words handling by adding reserved_word_list parameter, ensuring proper quoting for columns that are reserved keywords

v0.7.0

Schema and Data Changes

10 total changes • 0 possible breaking changes

Note: These staging models are ephemeral and will not be present in the warehouse, but we felt it important to document these updates to capture the full depth of changes.

Feature Updates

• Adds automatic table detection to support the newest version of the Workday API schema updates for new and existing Fivetran customers. Details in the Fivetran release notes:
  • stg_workday__military_service automatically detects and uses military_service_incoming table for existing customers if available, otherwise uses military_service table for new customers.
  • stg_workday__personal_information_ethnicity automatically detects and uses personal_information_ethnicity_incoming for existing customers table if available, otherwise uses personal_information_ethnicity table.
  • All models maintain backward compatibility by setting legacy fields to null.
• Added variables to enable table detection support. These variables are true by default to support existing customers, who will have the *_incoming tables available.
  • workday__using_military_service_incoming
  • workday__using_personal_information_ethnicity_incoming
• If you're a new customer who set up a Workday HCM Fivetran connection after January 5, you should set these variables to false. See the README for more details.
• Additionally, if customers need to leverage the old personal_information schema, they can set the below variable to false in the dbt_project.yml:
  • workday__using_personal_info_v2_schema

Documentation

• Updates DECISIONLOG with rationale for why we are not supporting the legacy schema.

Quickstart Updates

• Adds table variables to support the above automatic table switching feature. Note: These will be removed after the transition period when table switching is no longer needed.

Under the Hood

• Adds does_table_exist macro to dynamically detect table availability for automatic schema migration. Updates base models (stg_workday__military_service_base, stg_workday__personal_information_ethnicity_base) to use *_incoming table when available via automatic detection.
• Updates int_workday__personal_details to automatically detect and use new split personal information tables when both are available.
• Updates src_workday.yml with source definitions for new tables: personal_information_common_data, country_personal_information, plus _legacy variants for old schemas that will be deprecated after April.
• Adds 4 integration test seed files for the new Workday personal information schema; renames seed files to keep reference to old military_service and personal_information_ethnicity schema; will deprecate after full transition to new tables in April 2026: workday_military_service_legacy_data, workday_personal_information_ethnicity_legacy_data.
• Adds consistency tests for remaining Workday models.
• Updates seed files to ensure proper validation of data downstream in workday__employee_overview.

Sunset Connectors

Coheris

We sunset our Coheris connector. Effective January 29, 2026, we will no longer support the creation of new Coheris connections.

Schema changes

ActiveCampaign

Adobe Commerce

We have added the CART_SHIPPING_ADDRESS and ORDER_SHIPPING_ADDRESS tables.

We have added new columns to the CART table by flattening the billing_address fields.

We have added new columns to the ORDERS table by flattening the billing_address fields along with customer details columns for guest customers.

We are gradually rolling out these changes to all existing connections.

ADP Workforce Now

We have added the following new columns to the WORK_ASSIGNMENT_HISTORY table:

• job_function
• job_function_effective_date
• job_function_long_name
• job_function_short_name
• job_function_subdivisionType

Adyen

We have added the NON_TRANSACTIONAL_SCHEME_FEES_REPORT table to the Adyen connector.

Aha!

Alida

Auth0

Azure DevOps

Bizzabo

Brex

Buildkite

Cin7 Core

Clari

ClickUp

Cloudflare Analytics

Coupa

We have added the following new columns to the CONTRACT table:

• auto_extend_end_date_for_renewal
• contract_detail_commodity_id
• contract_detail_contract_type_custom_field_1
• contract_detail_contract_type_custom_field_2
• contract_detail_contract_type_custom_field_3
• contract_detail_contract_type_custom_field_4
• contract_detail_contract_type_custom_field_5
• contract_detail_contract_type_custom_field_6
• contract_detail_contract_type_custom_field_7
• contract_detail_contract_type_custom_field_8
• contract_detail_contract_type_custom_field_9
• contract_detail_contract_type_custom_field_10
• contract_detail_created_at
• contract_detail_external_object_name
• contract_detail_id
• contract_detail_notice_methods
• contract_detail_skip_archival
• contract_detail_updated_at
• external_contract_id
• fill_with_counterparty
• proxy_supplier_id
• stop_spend_based_on_max_value
• use_online_signing
• whose_paper

We have added a new table, CONTRACT_CURRENT_PARALLEL_APPROVAL_MAPPING, to capture the relationship between the CONTRACT and APPROVAL tables.

We have added the following columns to the EXPENSE_LINE table:

• audit_status_id
• audit_status_name
• audit_status_active
• audit_status_created_at
• audit_status_updated_at
• audit_status_updated_by_id

Datadog

dbt Cloud

Docebo

Eloqua

We have added the following new tables:

• EVENT_REGISTRATION
• EVENT_REGISTRATION_FIELD
• EVENT_REGISTRATION_REGISTRANT
• EVENT_REGISTRATION_REGISTRANT_FIELD_VALUE
• EVENT_REGISTRATION_SESSION
• EVENT_REGISTRATION_SESSION_FIELD
• EVENT_REGISTRATION_SESSION_FIELD_VALUE
• OPTION
• OPTION_LIST

By default, we select all the new tables for the sync. You can sync them for free until February 7, 2026. Be sure to exclude the tables that you don't want to count towards paid Monthly Active Rows (MAR) after this date. We are gradually rolling out these changes to all existing connections.

Everhour

Fortnox

Freshchat

Freshdesk

We have added a new table, TICKET_FIELD. We are gradually rolling out this change to all existing connections.

We have updated the connector to automatically handle survey ID format changes when Freshdesk accounts migrate from the Default CSAT module to the Advanced CSAT module.

When your Freshdesk account uses the Advanced CSAT module, the following columns will change from numeric to UUID string format:

• id column in the SURVEY table
• survey_id column in the SURVEY_QUESTION table
• survey_id column in the SATISFACTION_RATING table

The connector automatically detects which format your account uses and handles the data accordingly.

Friendbuy

Front

The is_spammer column in the CONTACT table now returns NULL for all records because Front has discontinued this field in their API.

We have added a new column, status_id, to the CONVERSATION table to store the unique identifier for conversation status categories. We populate this column only if you enable ticketing in Front.

Gem

GitHub

We have removed the following tables:

• PROJECT
• CARD
• COLUMN
• ISSUE_PROJECT_HISTORY

We have added a new table, REPOSITORY_LANGUAGE. This table contains programming language statistics for each repository, including which language it is and the number of bytes of code written in that language, as detected by the GitHub Linguist library.

We have added a new column, path, to the PULL_REQUEST_REVIEW_COMMENTS table.

Google Ad Manager

Our Google Ad Manager connector now supports syncing metadata. For a full list of metadata tables the connector syncs, see the Google Ad Manager ERD.

Only connections created on or after August 11, 2025 support syncing metadata tables.

Google Search Console

We have added the following new prebuilt reports:

• HOURLY_SITE_REPORT_BY_PAGE
• HOURLY_SITE_REPORT_BY_SITE
• HOURLY_PAGE_REPORT
• HOURLY_KEYWORD_SITE_REPORT_BY_PAGE
• HOURLY_KEYWORD_SITE_REPORT_BY_SITE
• HOURLY_KEYWORD_PAGE_REPORT

Additionally, we now support hour as a new dimension for custom reports.

Greenhouse

We have added a new column, credited_to_user_id, to the CANDIDATE table.

Healthie

Hex

Hilti On!Track

incident.io

Instagram Business

We have added the following new columns to the MEDIA_INSIGHTS table:

• story_follows
• video_photo_follows
• carousel_album_follows
• ig_reels_avg_watch_time
• ig_reels_video_view_total_time

Ironclad

Jira

We've added a new table, ISSUE_FORM.

We have added a new column, group_id, to the USER_GROUP table.

Kustomer

We have added the following new columns to the KOBJECT table:

• assigned_team
• assigned_user
• status

Linear

Lob

Microsoft Advertising

We have added a new column, _fivetran_deleted, to the following metadata history tables:

• ACCOUNT_HISTORY
• AD_ATTRIBUTE_HISTORY
• AD_CUSTOM_PARAMETER_HISTORY
• AD_GROUP_CUSTOM_PARAMETER_HISTORY
• AD_GROUP_HISTORY
• AD_GROUP_LABEL_HISTORY
• AD_HISTORY
• AD_LABEL_HISTORY
• AD_PUBLISHER_COUNTRY
• ASSET_GROUP_ATTRIBUTE_HISTORY
• ASSET_GROUP_HISTORY
• BUDGET_HISTORY
• CAMPAIGN_CUSTOM_PARAMETER_HISTORY
• CAMPAIGN_HISTORY
• CAMPAIGN_LABEL_HISTORY
• KEYWORD_CUSTOM_PARAMETER_HISTORY
• KEYWORD_HISTORY
• KEYWORD_LABEL_HISTORY
• KEYWORD_PUBLISHER_COUNTRY
• LABEL_HISTORY

Currently, this column is set to false for all records, preserving the existing sync behavior. When soft delete mode becomes available for your account, this column can be used as a convenient filter in queries to distinguish active records from those no longer in effect.

For example, to query only active campaigns:

SELECT * 
FROM campaign_history 
WHERE _fivetran_deleted = false

Microsoft Entra ID

Monday.com

NICE

OpenAI

Outbrain

We've added the following columns to the CAMPAIGN_REPORT, GEOLOCATION_REPORT, PROMOTED_LINK_REPORT, PUBLISHER_REPORT, and SECTION_REPORT tables:

• videoReachedFirstQ
• videoReachedSecondQ
• videoReachedThirdQ
• videoReachedCompletion
• videoAvgViewDuration
• clicksOnVideo
• videoActiveCompletions
• videoActiveCompletionsPercentage
• videoPlays

Pinterest Ads

We have added two new reporting tables, MMM_CAMPAIGN_TARGETING_DAILY_REPORT and MMM_AD_GROUP_TARGETING_DAILY_REPORT. We are gradually rolling out this change to all existing connections.

Pipedrive

We have discontinued the SUBSCRIPTION and SUBSCRIPTION_PAYMENT tables as Pipedrive has deprecated the associated API endpoints.

Procore

QuickBooks

We have added a new column, purchase_id, to the BILL_PAYMENT_LINE table.

Salesforce

We've added a new table, ENTITY_PARTICLE. This table provides granular metadata for compound Salesforce fields, such as address and geolocation fields, breaking them down into their individual components.

We now incrementally sync the LOGOUT_EVENT table instead of full re-syncs. We have also added EVENT_IDENTIFIER as an additional primary key.

ShipHero

Simplesat