September 2025

Connector SDK

fivetran-connector-sdk PyPI package

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

• Two new environment variables, FIVETRAN_CONNECTION_ID and FIVETRAN_DEPLOYMENT_MODEL, which can be referenced from connector code.
• Minor improvements and enhancements.
• Updated testers.

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

• Fix in inference for boolean data type, to identify as boolean and not int.
• Minor improvements and enhancements.

We have released version 2.1.1 of the fivetran-connector-sdk PyPI package. This release adds support for Python version 3.13. All new connections default to Python 3.13 unless the version is specified with the --python-version or --python argument at the deploy time.

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

• Support for using pipreqs-fivetran to generate requirements.txt
• Minor fixes and improvements

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

• Improved logging
• Updated tester performance
• Minor fixes and improvements

Lite Connectors

Lite connectors are now available for the following sources:

• Apollo
• AppLovin
• Brightflag
• GoFundMe Pro
• Listen360
• Uptempo
• Yahoo Display Ads on Yahoo Japan
• YouGov BrandIndex

Improvements to re-sync strategy

We have changed our connection re-sync strategy. During a re-import, we no longer delete historical records for tables with a retention period at the source because we won't be able to retrieve the older records. We are gradually rolling out this improvement to all connections.

This change applies to the following tables of the connectors below:

Transformations for dbt Core

dbt Core versions 1.9.10 and 1.10.11 support

We now support dbt Core* versions 1.9.10 and 1.10.11. You can use these versions to run your projects.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Teradata Vantage dbt adapter support

We now support the Teradata Vantage destination for the following versions of dbt Core* transformations: 1.7.19, 1.8.9, 1.9.10, and 1.10.11.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

• Amazon Selling Partner to version 0.2.1. We are gradually rolling out this change. All Quickstart transformations will be updated by October 18, 2025.
• Qualtrics to version 1.0.1. We are gradually rolling out this change. All Quickstart transformations will be updated by October 18, 2025.
• QuickBooks to version 0.21.1. We are gradually rolling out this change. All Quickstart transformations will be updated by October 22, 2025.
• Recharge to version 1.1.0. We are gradually rolling out this change. All Quickstart transformations will be updated by October 20, 2025.
• Reddit Ads to version 1.0.1. We are gradually rolling out this change. All Quickstart transformations will be updated by October 12, 2025.
• SAP ERP on HANA to version 0.3.1. We are gradually rolling out this change. All Quickstart transformations will be updated by October 13, 2025.
• Shopify to version 0.22.0. We are gradually rolling out this change. All Quickstart transformations will be updated by October 22, 2025.
• Zendesk Support to version 1.0.1. We are gradually rolling out this change. All Quickstart transformations will be updated by October 13, 2025.

Schema changes

Adobe Workfront

ADP Workforce Now

We have added the following child tables to the WORKER_TIME_CARD table:

• WORKER_TIME_CARD_DAY_ENTRY
• WORKER_TIME_CARD_TIME_ENTRY
• WORKER_TIME_CARD_LABOR_ALLOCATION
• WORKER_TIME_CARD_ENTRY_TOTAL

We are gradually rolling out this change to all connections.

Akeneo

Amazon Selling Partner

We now capture deletes for ITEM_RELATIONSHIP table in CATALOG module using _fivetran_deleted column. This boolean column flags rows marked as deleted.

We are gradually rolling out this change to all existing connections.

Appcues

Apple App Store

We have added the following new tables:

• SALES_WIN_BACK_ELIGIBILITY to store the win-back offer eligibility data for churned subscription customers.

• SALES_PRE_ORDER_SUMMARY contains pre-order sales data from Apple's App Store Connect, allowing you to track and analyze pre-order performance across different time frequencies.

• APP_STORE_BROWSER_CHOICE_SCREEN_ENGAGEMENT_REPORT contains browser choice screen engagement analytics data for iOS apps, tracking user interactions with browser selection screens as required by regulatory compliance in certain regions.

• APP_STORE_APP_VERSION contains App Store version information for each app including version strings, platform, release dates, and approval states.

• APP_STORE_APP_VERSION_REVIEW contains customer reviews associated with specific app versions, linking review data to both the app and the specific version being reviewed.

• SALES_FIRST_ANNUAL_DETAILED contains data that tracks first annual installs for apps in the EU, helping developers measure their install base for the Digital Markets Act compliance. The SALES_FIRST_ANNUAL_DETAILED table provides daily granular data by country and device.

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

Ascend by Partnerize

Braze

We have added two new columns, is_suspected_bot_click and suspected_bot_click_reason, to the SMS_EVENT table. These columns sync data that helps identify potential bot activity in SMS link clicks, improving data quality for fraud detection and analytics.

We have added two new columns, is_suspected_bot_click and suspected_bot_click_reason, to the EMAIL_EVENT table.

Brivo

CallRail

Coupa

We have added a new column, rejected, to the EASY_FORM_DATA table.

We have added the tax_code_id column to the INVOICE_HEADER table and the code column to the TAX_CODE table.

Criteo

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

Cvent

Deposco

Drata

Flywheel Digital

Gladly

Google Display & Video 360

Our Google Display & Video 360 connector can now sync the following metadata:

• ad_group_assigned_targeting_option
• assigned_first_party_and_partner_audience
• contact_info
• first_party_and_partner_audience
• hashed_email
• hashed_phone_number
• zip_code

See the connector's updated ERD for more details.

At first, the new metadata will be available for connections created after September 21, 2025. We are gradually rolling this change out to all existing multi-reporting connections.

We've discontinued support for the following dimensions due to deprecations in the Google Display & Video 360 API:

We've also discontinued support for the following dimensions and metrics due to them being deprecated in the Google Display & Video 360 API:

The deprecated fields and dimensions shall be removed from your connections and relevant reports during a sync.

incident.io

Infobip

Intercom

We have added a new column, messenger_writable, to the DATA_ATTRIBUTE table.

Iterable

We have added a new table, JOURNEY. We are gradually rolling out this change to all existing connections starting September 17, 2025.

Jira

We've changed the data type of the id column in the ASSET_REFERENCE_TYPE table from INTEGER to STRING.

JustCall

Klaviyo

We have updated our connector and will start using the Klaviyo API Revision 2025-04-15 on October 15, 2025. We will be gradually rolling out the changes to all connections. As part of this upgrade, we have made the following schema changes:

CAMPAIGN table

The new API revision supports mobile push campaigns. We will sync these campaigns to the CAMPAIGN table.

• CAMPAIGN_TRACKING_UTM_PARAM table: We have added a new column, type.
• SEGMENT table: We have added a new column, definition.
• EVENT table: We have changed the structure of the property_attribution column. See the comparison between the old structure and the new structure, along with an example below:

{
  "$attributed_event_id": "string",
  "$send_ts": 0.0,
  "$message": "string",
  "$flow": "string",
  "$group_ids": []
}
        

{
  "type": "attribution",
  "id": "string",
  "relationships": {
    "event": {
      "data": {
        "type": "event",
        "id": "string"
      }
    },
    "attributed-event": {
      "data": {
        "type": "event",
        "id": "string"
      }
    },
    "campaign": {
      "data": {
        "type": "campaign",
        "id": "string"
      }
    },
    "campaign-message": {
      "data": {
        "type": "campaign-message",
        "id": "string"
      }
    },
    "flow": {
      "data": {
        "type": "flow",
        "id": "string"
      }
    },
    "flow-message": {
      "data": {
        "type": "flow-message",
        "id": "string"
      }
    },
    "flow-message-variation": {
      "data": {
        "type": "flow-message",
        "id": "string"
      }
    }
  }
}
        

NetSuite SuiteAnalytics

We now dynamically add _fivetran_index for incremental tables that have multiple primary keys but only one integer primary key column.

Proofpoint Security Awareness

Sage Intacct

We have resolved a data integrity issue in the Sage Intacct connector that impacts the GLACCOUNTBALANCE table. We have updated the primary key RECORDNO calculation for this table.

Earlier, we calculated the primary key as a hash of the following columns:

• accountno
• accountrec
• accounttitle
• bookid
• classdimkey
• classid
• classname
• contractdimkey
• contractid
• contractname
• createdby
• currency
• customerdimkey
• customerid
• customername
• departmentid
• employeedimkey
• employeeid
• employeename
• endbal
• forbal
• gldimcompensation_type
• gldimservice_line
• itemdimkey
• itemid
• itemname
• location_id
• locationno
• modifiedby
• openbal
• period
• projectdimkey
• projectid
• projectname
• recordno
• record_url
• taskdimkey
• taskid
• taskname
• totadjcredit
• totadjdebit
• totcredit
• totdebit
• vendordimkey
• vendorid
• vendorname
• whencreated

Now, we calculate the primary key as a hash of the following columns:

• accountno
• accountrec
• bookid
• classdimkey
• classid
• classname
• contractdimkey
• contractid
• createdby
• currency
• customerdimkey
• customerid
• departmentid
• employeedimkey
• employeeid
• gldimcompensation_type
• gldimservice_line
• itemdimkey
• itemid
• locationid
• locationdimkey
• locationno
• openbal
• period
• projectdimkey
• projectid
• recordno
• record_url
• taskdimkey
• taskid
• vendordimkey
• vendorid
• whencreated

To correct historical data in your destination:

• You can initiate a free re-sync for the GLACCOUNTBALANCE table until September 30, 2025, from Fivetran.
• If you choose not to re-sync, only incremental data from September 1, 2025, will reflect the updated RECORDNO calculation.

Salesforce Commerce Cloud

We now sync all additional fields for the onlineFlag field in the PRODUCTS table. You can now see the site-specific columns for the online status of products, such as online_flag_default@Site1 and online_flag_default@Site2.

Be sure to re-sync the PRODUCTS table to backfill the data for these new columns.

Shopify

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

• category_ancestor_ids
• category_children_ids
• category_full_name
• category_id
• category_is_archived
• category_is_leaf
• category_is_root
• category_level
• category_name
• category_parent_id

To ensure these new columns are backfilled with data, please perform a re-sync of the PRODUCT table.

Shortcut

Slack

We have removed the following tables for connections created on or after September 3, 2025:

• CHAT_PERMALINK
• MESSAGE
• MESSAGE_ATTACHMENT
• MESSAGE_BLOCK
• MESSAGE_BLOCK_ELEMENT
• MESSAGE_BLOCK_FIELD
• MESSAGE_FILE
• MESSAGE_REPLY_USER
• MESSAGE_REACTION

Teamwork