August 2025

Connector SDK

Fivetran Connector SDK

Connector SDK now supports private links as a connection option. See our Connector SDK Connection Options documentation for more information.

fivetran-connector-sdk PyPI package

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

• Minor improvements and enhancements.

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

• Operations like op.upsert() no longer require the use of yield in your connector code.

  Previously, operations had to be yielded like this:

      yield op.upsert(table="table_name", data=data)
  

  Now, you can call them directly without yield:

      op.upsert( table="table_name", data=data)
  

  This simplifies connector logic and improves code readability. See our Migration Guide to learn how to remove yield usages from your connector code.

• Performance improvements and internal design enhancements.

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

• Minor improvements and enhancements.

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

• Internal design and performance improvements.
• Updated tester.

fivetran-api-playground PyPI package

We have released version 1.1.1 of the fivetran-api-playground PyPI package. This release adds the following:

• Added two new cursor endpoints for retrieving user data for multiple sync strategies:
  • /incremental/timestamp - Get a list of user data which was updated since the timestamp in params.
  • /incremental/step - Get a list of users within a start and end parameter.

We have released version 1.1.0 of the fivetran-api-playground PyPI package. This release adds the following:

• Added two new cursor endpoints for retrieving company and department data:
  • /cursors/companies - Get a list of companies with filtering options.
  • /cursors/<company_id>/departments - Get department details for a specific company with filtering options.

Fivetran AWS Seoul Servers

We have added new servers in the AWS Asia Pacific (Seoul) region.

If you're on a Business Critical plan, you can now select this region in your destination setup form. Connectors configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in Asia Pacific (Seoul), your data does not leave this region during processing.

For more information, see our data residency documentation.

Lite Connectors

Lite connectors are now available for the following sources:

• Ascend by Partnerize
• Asset Panda
• Consensus Demo Automation Platform
• Crunchbase
• Validio

Transformations for dbt Core

Auto-pause failing dbt Core transformations

We’ve introduced an auto-pause feature for dbt Core transformations that encounter repeated failures. This helps prevent resource waste and reduces unnecessary alerts from ongoing issues.

How it works

If a dbt Core transformation run fails consecutively due to factors outside of Fivetran’s control (such as issues with your data, configuration, or environment), the system will automatically pause the transformation if both of the following conditions are met:

• The transformation has failed more than 10 times in a row (i.e., on the 11th consecutive failure)
• At least 24 hours have passed since the first failure in the sequence

Key details

• Only failures caused by factors external to Fivetran (such as your data, configuration, or environment) will trigger the auto-pause mechanism
• System-level or transient errors don’t count toward the consecutive failure threshold
• When a transformation is auto-paused, you’ll see an alert on your dashboard
• If you’ve subscribed to transformation notifications, you’ll also receive an email
• The failure counters reset after the transformation is paused

Feature availability

This feature is being rolled out gradually to all users over the next few days.

You can manually resume paused transformations through the Fivetran dashboard once you’ve resolved the underlying issues.

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

• Amazon Ads to version 1.0.0.
• Asana to version 1.0.0.
• Facebook Pages to version 1.0.0.
• Fivetran Platform to version 2.3.0.
• GitHub to version 1.0.0.
• Greenhouse to version 1.0.0.
• Instagram Business to version 1.0.0.
• Intercom to version 1.0.0.
• Iterable to version 1.0.0.
• Jira to version 1.0.0.
• Klaviyo to version 1.0.0.
• Lever to version 1.0.0.
• LinkedIn Ad Analytics to version 1.0.0.
• LinkedIn Company Pages to version 1.0.0.
• Mailchimp to version 1.0.0.
• Marketo to version 1.0.0.
• Microsoft Advertising to version 1.0.0.
• Mixpanel to version 0.14.0.
• NetSuite SuiteAnalytics to version 1.0.0.
• Pardot to version 1.0.0.
• Pendo to version 1.0.0.
• Pinterest Ads to version 1.0.0.
• Qualtrics to version 1.0.0.
• QuickBooks to version 0.21.0.
• Recharge to version 1.0.0.
• Recurly to version 1.0.0.
• Reddit Ads to version 1.0.0.
• Sage Intacct to version 1.0.0.
• Salesforce Marketing Cloud to version 0.3.0.
• ServiceNow to version 0.5.0.
• Shopify to version 0.21.0.

Schema changes

Ada

Apple App Store

We have added a new table, SALES_SUBSCRIPTION_OFFER_CODE_REDEMPTION. We are gradually rolling out these changes to all existing connections.

Auth0

BigCommerce

We have made the following changes for connections set up before July 21, 2024:

• Added two new columns, id and type, to the PAYMENT_METHOD table

• Added two new tables, PAYMENT_METHOD_STORED_INSTRUMENT and PAYMENT_METHOD_SUPPORTED_INSTRUMENT

• Removed the CATEGORY table and its data is now available in the CATEGORY_TREE table

• Replaced the BILLING_ADDRESS_CUSTOM_FIELD table with two new tables, CHECKOUT_BILLING_ADDRESS_CUSTOM_FIELD and CONSIGNMENT_BILLING_ADDRESS_CUSTOM_FIELD

• Renamed the timestamp column of the ORDER_SHIPPING_ADDRESS_QUOTE table to timestamps

• Renamed the option_id column of the PRODUCT_VARIANT_OPTIONS_VALUE table to product_variant_option_id

• Renamed the offline column of the ORDER_REFUND_PAYMENT table to offlines

• Renamed the primary key, tag, of the STORE_BLOG_TAG table to tags

• Changed the primary key from index to _fivetran_id for the following tables:

  • CATEGORY_SETTING
  • CUSTOMER_SETTING_PER_CHANNEL
  • EMAIL_SETTING
  • LOCALE_SETTING
  • PRICE_LIST_RECORD
  • ROBOT_SETTING
  • SEARCH_SETTING
  • SECURITY_SETTING
  • SEO_SETTING
  • STATUS_SETTING
  • STORE_PROFILE_SETTING
  • STOREFRONT_PRODUCT_SETTING

Brex

Centra

ChartMogul

Delighted

For connections created before April 26, 2024, we have renamed the primary key, tag, of the RESPONSE_TAG table to tags.

Drata

Eloqua

We now sync the new activity type, ExternalActivity, to the CONTACT_ACTIVITY table. As part of this update, we’ve introduced the following columns:

• external_asset_name
• external_asset_type
• external_type

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

Factbird

Fivetran Platform Connector

Float

Gong

We have made the following schema changes for connections created before August 29, 2025:

• Added four new columns, call_outcome_name, call_outcome_category, call_outcome_id, and brief, to the CALL table.
• Added a new column, count, to the CALL_TRACKER table.
• Added five new tables, CALL_OUTLINE, CALL_OUTLINE_ITEM, CALL_HIGHLIGHT, CALL_HIGHLIGHT_ITEM, and CALL_KEY_POINT.

Google Business Profile

Google Campaign Manager 360

Our Google Campaign Manager 360 connector now supports syncing metadata. For a full list of metadata tables the connector syncs, see the Google Campaign Manager 360 ERD. Only connections created on and after August 11, 2025 support syncing metadata tables.

Google Search Ads 360

We now support custom columns. When you select custom columns in any report, you'll see the following additional tables in your schema:

• The CUSTOM_COLUMNS_METADATA table with the following columns:

  • id
  • customer.id
  • name

• The CUSTOM_COLUMNS table with the following columns:

  • id
  • value

We are gradually rolling out these changes to all connections.

We've added support for the following fields for the CUSTOMER table:

- customer.account_level - customer.associate_manager_descriptive_name - customer.associate_manager_id - customer.manager_descriptive_name - customer.manager_id - customer.sub_manager_descriptive_name - customer.sub_manager_id

Greenhouse

We have made the following changes for connections set up before July 18, 2024:

• Changed the primary key of the EDUCATION table from id to index
• Added the primary_email_address column to the USERS table
• Added the response_status column to the SCHEDULED_INTERVIEWER table
• Removed the is_primary column from the USER_EMAIL table
• Renamed the TAG table to TAGS
• Renamed the USER table to USERS
• Renamed the demographic_question column of the DEMOGRAPHIC_ANSWER_OPTION table to demographic_question_id
• Renamed the following columns of the EMAIL table:
  • from to from_email
  • to to to_email in the
• Renamed the following columns of the EMAIL_TEMPLATE table:
  • default to is_default
  • from to from_email
• Renamed the end column of the SCHEDULED_INTERVIEW table to ends

Help Scout

We have made the following changes for connections set up before June 26, 2024:

• Renamed the order column of the MAILBOX_WORKFLOW_HISTORY table to orders
• Renamed the rating_comments column of the HAPPINESS_RATING table to rating_comment

Hubspot

We now capture deletes for the CUSTOM_OBJECTS table.

Intercom

We have made the following schema changes:

• Added a new table, TICKET_STATE.
• Added a new column, enabled_push_messaging, to the CONTACT_HISTORY table.
• Added a new column, app_package_code, to the TICKET_PART_HISTORY table.

Iterable

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

We will discontinue the email_list_ids column from the USER_HISTORY table on October 13, 2025, because the LIST_USER table contains the same data.

Lever

We have made the following changes for connections set up before July 27, 2024:

• Added the following new tables:

  • FEEDBACK_FORM_SCORE_CARD_SUB_FIELD
  • FEEDBACK_FORM_TEMPLATE_FIELD
  • POSTING_FORM_SCORE_CARD_SUB_FIELD
  • POSTING_FORM_TEMPLATE_FIELD
  • PROFILE_FORM_SCORE_CARD_SUB_FIELD
  • PROFILE_FORM_TEMPLATE_FIELD
  • REFERRAL_FORM_SCORE_CARD_SUB_FIELD
  • REFERRAL_FORM_TEMPLATE_FIELD

• Removed the SCORE_CARD_SUB_FIELD and TEMPLATE_FIELD tables

• Renamed the USER table to USERS

• Renamed the end column of the PANEL table to ends

• Renamed the custom_field_* column of the REQUISITION table to custom_fields_*

• Renamed the primary key, tag, of the OPPORTUNITY_TAG and POSTING_TAG tables to tags

• Changed the primary key of the OFFER table to a composite key consisting of the id and opportunity_id columns

• Changed the primary key of the FILE table to a composite key consisting of the id and contact_id columns

Mandrill

We have made the following changes for connections set up before June 19, 2024:

• Renamed the timestamp column of the following tables to timestamps:

  • EVENT
  • MESSAGE
  • MESSAGE_SMTP_EVENT

• Renamed the tag column of the MESSAGE_TAG table to tags

PayPal

We have made the following changes for connections set up before June 21, 2024:

• Renamed the following columns of the DISPUTE table:

  • return_shipping_address_line_1 to return_shipping_address_address_line_1
  • return_shipping_address_line_2 to return_shipping_address_address_line_2
  • return_shipping_address_line_3 to return_shipping_address_address_line_3

• Renamed the following columns of the TRANSACTION table:

  • auctionitem_site to auction_item_site
  • available_balance_amount to available_balance_value
  • shipping_address_* to shipping_info_address_*
  • shipping_method to shipping_info_method
  • shipping_name to shipping_info_name
  • shipping_secondary_address_* to shipping_info_secondary_address_*

• Renamed the following columns of the TRANSACTION_ITEM_DETAIL table:

  • insurance_amount_amount to insurance_amount
  • insurance_amount_currency_code to insurance_currency_code

Pipedrive

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

We have added a new child table, INSTALLMENT, to the DEAL_HISTORY table. We are gradually rolling out this change to all connections.

Pylon Support Platform

Recharge

We have made the following changes for connections set up before June 18, 2024:

• Replaced the UTM_TAG table with the following new tables:

  • CHARGE_UTM_TAG
  • CHECKOUT_UTM_TAG
  • CUSTOMER_UTM_TAG
  • SUBSCRIPTION_UTM_TAG

• Renamed the ORDER table to ORDERS

• Renamed the subscription_id column of the SUBSCRIPTION_HISTORY table to id

• Added a new column, buyer_accepts_marketing, to the CHECKOUT table

• Stopped syncing data into the is_deleted column for the following tables, as this information is already available in the _fivetran_deleted column:

  • ONE_TIME_PRODUCT
  • ORDERS
  • CHARGE
  • CUSTOMER

Sailthru

We have changed the primary key of the following tables from message_id to event_id:

• ES_CAMPAIGN_SENDS
• ES_CAMPAIGN_OPENS
• ES_CAMPAIGN_CLICKS
• ES_CAMPAIGN_BOUNCES
• ES_CAMPAIGN_UNSUBSCRIBES
• ES_TRIGGERED_SENDS
• ES_TRIGGERED_OPENS
• ES_TRIGGERED_CLICKS
• ES_TRIGGERED_BOUNCES
• ES_TRIGGERED_UNSUBSCRIBES

The new primary key field, the event_id field, is present for records from March 20th, 2025, onwards. The existing records in these tables will be moved to backup tables whose names contain the suffix _backup.

Salesforce Commerce Cloud

We have discontinued the ADDRESS table and will no longer sync it. Use the CUSTOMER_ADDRESS table.

Samsara

SAP Concur

We have added a new field, expense_id, to the EXPENSE_ENTRY table.

We have added a new table, EXPENSE_COMMENT.

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

Shopify

We've updated the Shopify connector schema. The new schema only applies to Fivetran accounts created on or after August 1, 2025.

We have added the following new tables:

• BUNDLE_COMPONENT
• BUNDLE_COMPONENT_OPTION_SELECTION
• BUNDLE_COMPONENT_VARIANT
• COMPANY_LOCATION
• COMPANY_LOCATION_CATALOG
• COMPANY_LOCATION_TAX_EXEMPTION
• MARKETING_EVENT
• SALE
• SALE_TAX
• SALES_AGREEMENT

We are gradually rolling out these changes to all connections. These new tables' MAR will be free until September 30, 2025.

Short.io

Sprout Social

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

Survicate

Tableau

TikTok Organic

Typeform

We have added a new table, RESPONSE_TAG.

Workday Financial Management

We have fixed a bug and rectified the values of the included_ledger_account_id and included_ledger_account_code columns of the ALL_INCLUDED_LEDGER_ACCOUNT table. We have also removed the incorrect records in the ALL_INCLUDED_LEDGER_ACCOUNT table in your destination.

Workday HCM

We no longer sync data for the time_calculation_tag_code column in the CALCULATED_TIME_BLOCK table. We now sync this data in the new CALCULATION_TAG table, which is a child table of CALCULATED_TIME_BLOCK.

Xero

We have added a new column, item_id, to the INVOICE_LINE_ITEM table.

Zendesk Chat

We have made the following changes for connections set up before July 23, 2024:

• Renamed the timestamp column of the following tables to timestamps:

  • CHAT
  • CHAT_HISTORY
  • ENGAGEMENT

• Renamed the primary key, tag, of the CHAT_TAG table to tags

Zoho Inventory

Improvements

Ada

We now use the Ada v2 API to retrieve data from the conversations endpoint. We now use the /api/v2/export/conversations endpoint to sync the CONVERSATION table. Previously, we used /data_api/v1.4/conversations. We are gradually rolling out this change to all connections.

BigCommerce

We have made the following changes to the Schema tab for connections set up before July 19, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables
• We no longer support table-level selection or deselection

Box

We now support syncing files to multiple destination tables and handling file patterns in Merge Mode. To support these features, we have made the following changes to the connection setup form:

• Added the Files field and sub-fields Table name and File pattern, that enable you to define destination tables and specify the file pattern names.
• Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

For more information, see our setup instructions and REST API configuration. We are gradually rolling out these enhancements to all existing connections.

Brex

We now support priority-first sync for the EXPENSE table. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use.

CockroachDB

We now support CockroachDB versions 24.1.0 - 25.3.0.

Databricks Lakebase for PostgreSQL

Our Databricks Lakebase for PostgreSQL destination is now generally available.

Read our Databricks Lakebase for PostgreSQL destination documentation.

Datadog

We now capture all the data of custom fields returned by the Datadog API’s Incidents endpoint in the INCIDENT_FIELD table.

Delighted

We have made the following changes to the Schema tab for connections set up before April 26, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables
• We no longer support table-level selection and deselection

Email

We have made the following changes to the connection setup form:

• Added support to configure archive patterns per table. This is useful when an archive folder contains files following different naming patterns, allowing you to route each pattern to a specific destination table based on its pattern.
• Renamed the Archive Folder Pattern field to Archive File Pattern.

For more information, see our setup instructions

Factbird

We have changed our sync strategy for Factbird connections:

• We now sync historical data for your connection starting from January 1, 2019.
• We now sync data for the OEE table daily.
• We now incrementally sync the BATCH table and its child tables to capture newly added and updated records.

File Connectors

We have added a new toggle, Manually provide cell reference, to the setup form of the following connectors:

• Amazon S3
• Box
• Dropbox
• Email
• SFTP
• SharePoint

You can now manually specify a cell reference for the file path instead of using the default automatic detection.

FTP

We have improved the setup experience for FTP connections.

• Added a new configuration option, Run connection test to perform an intermediate test during configuration
• Added a new configuration option, Preview Files to perform an intermediate test during configuration
• Added support for displaying fields based on the file type
• Added a new field, Quote character, to use an enclosing character
• Reorganised fields to make the setup form more intuitive
• Removed Infer as an option from the File Type field
• Removed the Enable Advanced Options toggle
• Changed the Null Sequence field to a toggle
• For the Delimiter character(s) field, we now use , as the default value
• For the Line Separator field, we now use \n as the default value

For more information, see our setup instructions and REST API configuration.

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

Google Ad Manager

Starting on August 11, 2025, new connections created in the dashboard become multi-reporting connections.

We have upgraded our Google Ad Manager connector from version 202411 to 202505 of the Google Ad Manager API and handled deprecations and updates. Learn more about the deprecations and changes in the Google Ad Manager API documentation.

Google Campaign Manager 360

You can now choose several Floodlight Configuration IDs in the Google Campaign Manager 360 FLOODLIGHT and PATH_TO_CONVERSION reports. We are gradually rolling out this change to all existing connections.

Starting from August 11, 2025, newly created connections will support adding multiple reports. For more information, see the Google Campaign Manager 360 setup guide.

Gorgias

We no longer capture deletes for the CUSTOMER table and its child tables.

Greenhouse

We have made the following changes to the Schema tab for connections set up before July 18, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables
• We no longer support table-level selection and deselection

Healthie

We have changed our sync strategy and now re-import all tables during every sync.

Help Scout

We have made the following changes to the Schema tab for connections set up before June 26, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables
• We no longer support table-level selection or deselection

Ironclad

We have updated our sync strategy. We now incrementally sync the RECORD table. Previously, we re-imported the RECORD table during every sync.

Lever

We have made the following changes to the Schema tab for connections set up before July 27, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables

We now store data only from the Lever API's Opportunity endpoint in the OPPORTUNITY table and its child tables. Previously, this table included data from both the Opportunity and Candidate endpoints.

Managed Data Lake Service

We have published Fivetran Iceberg REST Catalog Postman collection, which helps you get metadata from tables stored in your Fivetran Iceberg REST Catalog.

Mandrill

We have made the following changes to the Schema tab for connections set up before June 19, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables
• We no longer support table-level selection and deselection

We have removed the Use Template Labels toggle and Template labels field from the connection setup form.

Marketo

We have made changes to our Marketo connection setup form and REST API parameters to support the Marketo SOAP API deprecation. These changes won't impact how your connection syncs data to your destination.

We have removed the Provide SOAP API Credentials for BULK API Quota Estimation toggle and the following related fields from the connection setup form:

• SOAP API User Id
• SOAP API Encryption Key
• SOAP API Endpoint

Similarly, we have discontinued the following parameters from the REST API Configuration:

• user_id
• encryption_key
• soap_uri

MongoDB

We no longer support the _id fields of BSON_DB_POINTER, BSON_SYMBOL, and SYMBOL data types during historical or incremental syncs of a collection. Learn more in our MongoDB documentation.

MySQL

We have fixed a data inconsistency issue for MySQL and MariaDB connections that use Fivetran Teleport Sync, where during the initial sync, we converted the TIMESTAMP values to UTC in your destination, but in subsequent updates, we converted these values using the source's timezone configuration. We now always convert TIMESTAMP values to UTC in your destination. This change is consistent with how we handle these values for connections using the binary log update method.

To fix existing values in your destination, contact our support team to re-sync the affected tables and understand the MAR impact.

We now support AWS IAM database authentication for our Amazon Aurora MySQL, RDS MySQL, and RDS MariaDB connectors.

PayPal

We have made the following changes to the Schema tab for connections set up before June 21, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables

PostgreSQL ctid improvement

We now support syncing tables without primary keys (PK-less) and tables with unsupported primary key types when using the Fivetran Teleport Sync method for the PostgreSQL connector. Previously we supported only tables with primary keys of following types for Fivetran Teleport Sync:

• character varying (with specified maximum length)
• text
• uuid
• smallint
• int
• bigint
• numeric (with specified precision)
• date

We can now sync tables with primary keys of all data types using a special PostgreSQL system column ctid. Previously, the Fivetran Teleport Sync method did not support syncing PK-less tables and tables that had strict type requirements on primary key as mentioned above.

Recharge

We have made the following changes to the Schema tab for connections set up before June 18, 2024:

• We display all table names in lowercase

• We display all the tables, including the empty tables

• We no longer support table-level selection and deselection

• We have removed the following tables:

  • META_FIELD_CHARGE
  • META_FIELD_CUSTOMER
  • META_FIELD_ORDER
  • META_FIELD_STORE
  • META_FIELD_SUBSCRIPTION

Sage Intacct

Now, when we encounter an API check failure during a sync, we temporarily exclude the complete endpoint, including the parent table and all the associated child tables, from the sync. We try to automatically retrieve the endpoints in subsequent syncs.

Salesforce

We have upgraded our Salesforce connector from version 63.0 to 64.0 of the Salesforce REST API. For more information, see Salesforce's changelog.

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

ServiceNow

You can now sync columns from parent tables to child tables by using the Inherited columns mode. We are gradually rolling out these changes to all existing connections.

See our Syncing columns from parent tables to child tables documentation to learn more.

Short.io

We have made the following changes to our sync strategy for the LINK table and its child tables:

• We no longer re-import these tables to capture updates and deletes.

• We now sync only the last 6 month's worth of data during historical syncs.

Square

We have changed the sync strategy for the following tables:

• GIFT_CARD_ACTIVITY
• REFUND
• ADDITIONAL_REFUND_RECIPIENT
• SHIFT
• SHIFT_BREAK

We now incrementally sync them to capture new records.

We also re-import these tables to capture updates and deletes. The re-import frequency depends on the duration of the last re-import for the table:

• If the last re-import took less than 2 hours, we re-import the table once a day.
• If the last re-import took more than 2 hours, we re-import the table once a week on Saturdays.

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

Swoogo

We have fixed a bug where the TRANSACTION table in your destination did not contain the payment_gateway_name and registrant_id columns, even though they were defined in the connection schema. The table now correctly includes these columns.

Workday Financial Management

We have removed the toggle button to choose between different OAuth authentication options in the setup form for all connections set up before February 25, 2025. For all connections, we now only support API client for integrations method if you use OAuth based authentication.

Workday HCM

We have removed the toggle button to choose between different OAuth authentication options in the setup form for all connections set up before February 25, 2025. For all connections, we now only support API client for integrations method if you use OAuth based authentication.

Xero

We have updated the CONTACT_ADDRESS table to correctly store multiple addresses per contact.

Zendesk Chat

We have made the following changes to the Schema tab for connections set up before July 23, 2024:

• We display all table names in lowercase
• We display all the tables, including the empty tables

REST API Improvements

Deprecated config parameters for Google Campaign Manager 360

As of August 11, 2025, the Fivetran REST API no longer supports the following configuration parameters for Google Campaign Manager 360 connections:

• conversion_dimensions
• custom_floodlight_variables
• dimensions
• enabble_all_dimension_combinations
• metrics
• per_interaction_dimensions
• report_configuration_ids
• report_type

We will fully sunset these parameters on November 11, 2025.

Google Search Ads 360

We've introduced the custom_column_ids API parameter for configuring your Google Search Ads 360 custom reports. We are gradually rolling out these changes to all customers.