May 2024

Fivetran Azure Germany West Central Servers

We have added new servers in the Azure Germany West Central (Frankfurt) 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 Germany West Central, your data does not leave Germany West Central during processing.

For more information, see our data residency documentation.

Lite Connectors

Lite connectors are now available for the following sources:

Proxy Agent

The Fivetran Proxy Agent connection method in beta is now available for the Azure germanywestcentral (Frankfurt) region. The Proxy Agent allows you to connect Fivetran to your database securely. Installed behind your firewall, it initiates communication with Fivetran, eliminating the need for other complicated networking options.

Save for Later Option in Connector Setup Forms

In your connector setup form, once you have entered the Destination schema or Destination schema prefix that defines the name of your connector, you can now save an incomplete configuration at any moment by clicking Save for later. We save that connector in an incomplete configuration state.

Save incomplete connector configuration for later

Saving an incomplete connector configuration can be useful when you don't have all the information or permissions required to configure the connector at the moment. Later, you can find the connector by sorting or searching the connector list by connector name, then complete the configuration.

Find connector with incomplete configuration by name

Transformation Improvements

Bulk Actions for Transformations

You can now use bulk actions for Transformations, which allow you to perform any of the following actions on multiple transformations at once:

Pause selected transformations
Resume selected transformations
Edit schedule of selected transformations
Remove selected transformations

Transformations for dbt Core

dbt Core version 1.7.14 support

We now support dbt Core* version 1.7.14. You can use this version to run your projects.

NOTE: For dbt Core versions later than 1.1.5, we don't support MySQL destinations. These destinations are not currently supported by custom dbt Core adapters.

* 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.

dbt Job Retries for Scheduled in Code Transformations.

We now support the dbt job retry mechanism for scheduled in code transformations. By default, a failed job is retried up to 4 times.

You can change this by setting the value of the retryOnFailure parameter to false in the job configuration:

- name: daily
  schedule: 0 12 * * *
  retryOnFailure: false

Schema changes

15Five

Effective May 28, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes because the source schema has been updated.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`GROUPS`
column	New Column	`mention_name`	We've added a new column to reflect the changes made in the source schema.
`USERS`
column	New Column	`mention_name`	We've added a new column to reflect the changes made in the source schema.

Close

Effective May 6, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to a null primary key issue. We are also deprecating the CONTACT_INTEGRATION_LINK and LEAD_INTEGRATION_LINK tables.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

6 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CONTACT`
column	New Column		`integration_links`
`CONTACT_INTEGRATION_LINK`
table	Deprecated Table	`CONTACT_INTEGRATION_LINK`		Data available in the `INTEGRATION_LINK` table.
`LEAD`
column	New Column		`integration_links`
`LEAD_INTEGRATION_LINK`
table	Deprecated Table	`LEAD_INTEGRATION_LINK`		Data available in the `INTEGRATION_LINK` table.
`SMS_ATTACHMENT`
column	Primary Key Change	`media_id` 🔑	`media_id`	No longer primary key due to a `null` primary key issue.
column	Primary Key Change		`index` 🔑	New primary key.

Delighted

We have renamed the primary key column tag of the RESPONSE_TAG table to tags for connectors created on or after April 26, 2024.

Dropbox Sign

Effective May 27, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We require this schema change because we have deprecated the ACCOUNT table and added two new tables, TEAM and TEAM_ACCOUNT. Failing to do so may cause missing and/or incomplete data in your pipelines.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

9 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ACCOUNT`
table	Deprecated Table	`ACCOUNT`		The data is available in the `TEAM` table.
`SIGNATURE`
column	Deprecated Column	`signature_request_id` 🔑		No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`TEAM`
column	Deprecated Column	`id` 🔑		No longer a primary key
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
column	New Column		`invited_account`	Since the `ACCOUNT` table is deprecated, data is available in the `invited_account` column of the `TEAM` table.
column	New Column		`name`	No longer a primary key.
`TEAM_ACCOUNT`
column	Deprecated Column	`invited`		Data of `invited_accounts` is available in the `TEAM` table.
column	New Column		`_fivetran_id`	Child of `TEAM` table.

Facebook Pages

We have added a new field, unshimmed_url, to the POST_ATTACHMENT_HISTORY table.

We have added a new field, full_picture, to the POST_HISTORY table.

Flexport

Effective May 27, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making this schema change to avoid potential data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`BOOKING_DESCRIPTION`
column	Primary Key Change	`code` 🔑	`code`	No longer primary key.
column	Primary Key Change	`description_type` 🔑	`description_type`	No longer primary key.
column	Primary Key Change	`parent_id` 🔑	`parent_id`	No longer primary key.
column	New Column		`_fivetran_id` 🔑	Added to primary key.

GRIN

Effective May 13, 2024 we use a new May 2024 Schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have changed the primary key column for multiple tables.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

10 total changes • 9 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CONTACT_CUSTOM_PROPERTY`
column	Primary Key Change	`contact_id`	`contact_id` 🔑	Added to primary key
`CONTACT_TAG`
column	Primary Key Change	`contact_id`	`contact_id` 🔑	Added to primary key
`CUSTOM_PROPERTY_OPTION`
column	Primary Key Change	`custom_property_id`	`custom_property_id` 🔑	Added to primary key
`MEDIA_LIBRARY_CONTENT`
column	New Column		`owner_reached`
`MEDIA_LIBRARY_CONTENT_TAG`
column	Primary Key Change	`media_library_content_id`	`media_library_content_id` 🔑	Added to primary key
`PARTNERSHIP_JOB`
column	Primary Key Change	`partnership_id`	`partnership_id` 🔑	Added to primary key
`PARTNERSHIP_PROPOSAL`
column	Primary Key Change	`partnership_id`	`partnership_id` 🔑	Added to primary key
`PARTNERSHIP_TASK`
column	Primary Key Change	`partnership_id`	`partnership_id` 🔑	Added to primary key
`PAYMENT_ITEM`
column	Primary Key Change	`payment_id`	`payment_id` 🔑	Added to primary key
`PRODUCT_IMAGE`
column	Primary Key Change	`product_id`	`product_id` 🔑	Added to primary key

Instagram Business

We have added a new table MEDIA_COMMENT with the following fields:

id
media_id
owner_id
owner_username
hidden
like_count
parent_id
text
created_time

For more information, see the Instagram Business ERD.

Jira

We now support Remote Issue Links. We are gradually rolling out this feature to all connectors.

When it's available for your connector, you will see an additional ISSUE_REMOTE_LINK table in your destination.

To learn more, see Jira's Remote Issue Links documentation.

Kantata

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

Klaviyo

We have added the following new tables and their associated child tables:

COUPON
- COUPON_CODE
TAG_GROUP
TAGS
- CAMPAIGN_TAG
- FLOW_TAG
- LIST_TAG
- SEGMENT_TAG

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

FLOW_ACTIONS
FLOW_ACTION_UTM_PARAMS
FLOW_MESSAGE

We re-import these tables in every sync. We are gradually rolling out these changes to all connectors.

LearnUpon

Effective May 14, 2024 we use a new 2024 May schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to renaming of some columns as per the standard naming convention.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

6 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`LEARNING_PATH_ENROLLMENT`
column	Deprecated Column	`date_lastaccessed`		Updated to adhere to standard naming conventions.
column	New Column		`date_last_accessed`	Updated to adhere to standard naming conventions.
`MODULE`
column	Deprecated Column	`tag`		Updated to adhere to standard naming conventions.
column	New Column		`tags`	Updated to adhere to standard naming conventions.
`USERS`
column	Deprecated Column	`language`		Updated to adhere to standard naming conventions.
column	New Column		`languages`	Updated to adhere to standard naming conventions.

Microsoft Entra ID

Effective May 20, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making this schema change because the source API added new a column. You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`USERS`
column	New Column			`employee_leave_date_time`	Added New Column

Pardot

We have added a new table, EMAIL_TEMPLATE with the following child tables:

REPLY_TO_OPTION
SENDER_OPTION

Pipedrive

We have changed the data type of the progress column in the GOAL table from INT to DOUBLE.

PostreSQL

Starting on June 15, 2024, newly created connections only display the root partitioned table in the Fivetran dashboard because we sync data from partitioned tables into the base table. Previously, we displayed both the root partitioned table and its child tables.

PowerReviews Enterprise

Effective May 10, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to avoid potential data integrity issues due to misuse of the index column.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

21 total changes • 21 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`QUESTION`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`QUESTION_ANSWER`
column	Primary Key Change	`question_id` 🔑	`question_id`	No longer primary key.
column	Deprecated Column	`question_index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`REVIEW`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`REVIEW_BADGE`
column	Deprecated Column	`review_id` 🔑		No longer primary key.
column	Deprecated Column	`review_product_page_id` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`REVIEW_CUSTOM_QUESTION_NAME`
column	Deprecated Column	`review_id` 🔑		No longer primary key.
column	Deprecated Column	`review_index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`REVIEW_MEDIA`
column	Primary Key Change	`review_id` 🔑	`review_id`	No longer primary key.
column	Deprecated Column	`review_index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`REVIEW_MERCHANT_RESPONSE`
column	Primary Key Change	`review_id` 🔑	`review_id`	No longer primary key.
column	Deprecated Column	`review_index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Productboard

Effective May 8, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to null primary key and paging cursor expiration issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`NOTE_COMMENT`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`NOTE_FEATURE`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.

Effective May 9, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to null primary key and paging cursor expiration issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`NOTE_FOLLOWER`
column	Primary Key Change	`member_id` 🔑	`member_id`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`TEMP_NOTE`
table	Deprecated Table	`TEMP_NOTE`		Data available in the `NOTE` table.

Qualtrics

We have added a new column, label, to the QUESTION_RESPONSE table. We are gradually rolling out this change to all existing connectors.

SAP Concur

We have added a new table, ENTRY_ATTENDEE_ASSOCIATION.

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

Sharetribe

Effective May 15, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to primary key issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`TRANSACTION_LINE_ITEM`
column	Primary Key Change	`transaction_id`	`transaction_id` 🔑	Added to primary key because `index` alone cannot serve as a strong primary key. We have modified it to have a composite key (CK) consisting of `index` and `transaction_id`.
`TRANSACTION_LINE_ITEM_INCLUDE`
column	Primary Key Change	`transaction_id`	`transaction_id` 🔑	Added to primary key because `index` alone cannot serve as a strong primary key. We have modified it to have a composite key (CK) consisting of `index` and `transaction_id`.

Shortcut

We have added two new tables, EPIC_STORY_CUSTOM_FIELD and STORY_CUSTOM_FIELD.

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

SonarQube

Effective May 21, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is necessary because the source API has deprecated certain columns and primary keys, resulting in the need for updates in our schema.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

16 total changes • 11 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPONENT_TAG`
column	Deprecated Column	`tag` 🔑		No longer primary key.
column	Primary Key Change		`tags` 🔑	New primary key.
`GROUP_MEMBERSHIP`
table	Deprecated Table	`GROUP_MEMBERSHIP`		Data now available in the `user_group` table.
`GROUPS`
column	Rename Column	`default`	`defaults`	Renamed to `defaults`.
column	Deprecated Column	`id` 🔑		No longer primary key.
column	Primary Key Change	`name`	`name` 🔑	Added to primary key.
column	New Column		`managed`	New column added.
`ISSUE_TAG`
column	Deprecated Column	`tag` 🔑		No longer primary key.
column	Primary Key Change		`tags` 🔑	New primary key.
`RULE_PARAM`
column	Rename Column	`desc`	`description`	Renamed to `description`.
`RULE_TAG`
column	Deprecated Column	`tag` 🔑		No longer primary key.
column	Primary Key Change		`tags` 🔑	New primary key.
`USERS`
column	New Column		`avatar`	New column added.
column	New Column		`email`	New column added.
column	New Column		`managed`	New column added.
column	New Column		`sonar_lint_last_connection_date`	New column added.

Spotify Ads

We've added a new field, canvasAssetId, to the AUDIO_ASSET table.

We've added a new field, display_name, to the ACCOUNT table.

We've added a new field, user_uploaded_image, to the AD table.

We now support the AD_ACCOUNT entity for custom aggregated reports.

We have added two new metrics to Get_Aggregate_Report for campaigns using the Video Views objective:

VIDEO_EXPANDS
VIDEO_EXPAND_RATE

Standard Metrics

Effective May 21, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes for more efficient data management and retrieval.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CUSTOM_COLUMN`
table	Deprecated Table	`CUSTOM_COLUMN`		Data available in the newly added tables below.
`CUSTOM_COLUMN_MULTI_SELECT`
table	New Table		`CUSTOM_COLUMN_MULTI_SELECT`
`CUSTOM_COLUMN_SELECT`
table	New Table		`CUSTOM_COLUMN_SELECT`
`CUSTOM_COLUMN_TEXT`
table	New Table		`CUSTOM_COLUMN_TEXT`

StarRez

We have added the following new tables:

CUSTOM_FIELD_DEFINITION
CUSTOM_FIELD_USAGE_TYPE_ENUM
ENROLLMENT_TYPE_ENUM
FIELD_DATA_TYPE_ENUM
GENERIC_TABLE_DATA
GENERIC_TABLE_DATA_FIELD
GENERIC_TABLE_DEFINITION
GENERIC_TABLE_DEFINITION_FIELD
GENDER_TYPE_ENUM
GL_POSTING_TYPE_ENUM
GROUPS
GROUP_STATUS_ENUM
LOG_ACTIVITY_DELETE
PROMO_CODE
PROMO_CODE_RECORD
PROMO_CODE_USAGE
RECORD_TYPE_ENUM
ROOM_RATE_DURATION_ENUM
ROOM_SPACE_TYPE_ENUM
TERM
TERM_SESSION

Stripe

We have added three new columns, cancellation_details_comment, cancellation_details_feedback, and cancellation_details_reason to the SUBSCRIPTION_HISTORY table. We will only sync new data from May 19, 2024 into these columns. We will not sync your historical data before May 19, 2024.

UKG Pro

Effective May 23, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making this schema change to avoid potential data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`EMPLOYMENT`
column	Primary Key Change		`company_id`	`company_id` 🔑	Added to primary key

VWO

Effective May 3, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to avoid potential data integrity issues due to the misuse of the `index` column.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CAMPAIGN_SHARE_LINK`
column	Primary Key Change	`campaign_id` 🔑	`campaign_id`	No longer primary key.
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change	`workspace_id` 🔑	`workspace_id`	No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Wrike

Effective May 31, 2024 we use a new May 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required to adhere to standard naming conventions.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`WORKFLOW_CUSTOM_STATUS`
column	Rename Column		`group`	`groups`	Updated to adhere to standard naming conventions.

Improvements

AppsFlyer

We now perform rollback syncs for the GEO_DAILY table to capture the latest Lifetime Value (LVT) records that change due to attribution. The default rollback window is 2 days. However, you can customize your rollback window within the range of 2 to 90 days. To support this enhancement, we have added a new field, Rollback Window, to the connector setup form. For more information, see our setup instructions.

Attentive

We have changed the connector type of our Attentive connector from Lite to Standard.

Azure Blob Storage

We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.

Azure Data Lake Storage

We now perform regular maintenance operations on the tables in your Azure Data Lake Storage destination. These maintenance operations do the following:

Delete the table snapshots that are older than 7 days
Clean up orphan and removed files

For more information, see our Azure Data Lake Storage documentation. We are gradually rolling out this enhancement to all existing destinations.

BigQuery

We support syncing data from tables and views from Analytics Hub linked datasets, which do not have the data egress restriction.

Care Quality Commission

We have made the following changes to our Care Quality Commission connector to support the recent Care Quality Commission API changes:

In the connector setup form, we replaced the Partner code field with the Primary key field. For more information, see our setup instructions.
In the API config parameters, we replaced the partner_code parameter with the primary_key parameter. For more information, see our REST API documentation.

Churnzero

We no longer capture deletes for the following tables and their child tables:

ACCOUNT
CONTACT
EVENT
JOURNEY
JOURNEY_INSTANCE
JOURNEY_MILESTONE
JOURNEY_MILESTONE_ACHIEVEMENT
JOURNEY_MILESTONE_PROGRESS
JOURNEY_MILESTONE_STEP_PROGRESS
JOURNEY_MILESTONE_TASK
JOURNEY_PROGRESS
SEGMENT
SEGMENT_COLUMN_SET
SURVEY_RESPONSE
TASK
USER_ACCOUNT

Cin7 Core

We have renamed our DEAR connector to Cin7 Core. This name change applies to the Fivetran dashboard and our documentation.

Cvent

We have changed the sync strategy for the ATTENDEE_ACTIVITY table. We no longer re-import the ATTENDEE_ACTIVITY table to capture updates and deletes.

Delighted

We have made the following changes to the Schema tab for Delighted connectors created on or after April 26, 2024:

All table names now appear in lowercase.
We now display all tables in the schema, including the empty tables.
We no longer support table-level selection or deselection for new Delighted connectors.

Drip

We no longer re-import the following tables and their child tables to capture deletes:

CONVERSATION
EMAIL_SERIES_CAMPAIGN
EMAIL_SERIES_SUBSCRIBER_ACTIVE
EMAIL_SERIES_SUBSCRIBER_REMOVED
EMAIL_SERIES_SUBSCRIBER_UNSUBSCRIBED
PEOPLE
SINGLE_EMAIL_CAMPAIGN
WORKFLOW

Dropbox

Our Dropbox connector now supports syncing Microsoft Excel spreadsheets in Merge Mode. For more information, see our setup instructions.

Eventbrite

We have changed our sync strategy and no longer capture deletes for the following tables and their child tables:

ATTENDEE
ORDERS

Facebook Ads

We now support the new Engaged-view attribution window with a 1 day value. This window refers to engaged-view conversions that are counted when a skippable video ad is played for at least 10 seconds or at least 97% of its total length if it’s shorter than 10 seconds, then a person takes an action within one day.

Learn more in Facebook's Engaged-view documentation and Graph API parameters documentation.

Firebase

Support for non-default Firebase databases is now generally available for the Firebase connector. Previously, this feature was only available upon request.

Learn more about multiple databases (the default database + non-default databases) in Google's Firestore Multiple Databases is now generally available article.

Fivetran Platform Connector

The Fivetran Platform connector now syncs 7 days' worth of historical data instead of 5 days.

You now can select tables to be included in or excluded from syncs on the Schema tab of the Fivetran Platform Connector details page.

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

Google Analytics 4

Google Analytics 4 now supports aggregation by time unit dimensions.

Insightly

We now incrementally sync the following tables and their child tables:

CONTACT
CONTACT_FILE_ATTACHMENT
CUSTOM_OBJECT_RECORD
EMAIL
EMAIL_FILE_ATTACHMENT
EVENT
FORUM
FORUM_CATEGORY
FORUM_COMMENT
FORUM_POST
LEAD
LEAD_FILE_ATTACHMENT
NOTE
NOTE_COMMENT
NOTE_FILE_ATTACHMENT
MILESTONE
OPPORTUNITY
OPPORTUNITY_FILE_ATTACHMENT
OPPORTUNITY_ITEM
ORGANISATION
ORGANISATION_FILE_ATTACHMENT
PRICE_BOOK
PRICE_BOOK_ENTRY
PRODUCT
PROJECT
PROSPECT
QUOTE
QUOTE_ITEM
TASK
TICKET
USERS

Instagram Business

We have added data that represents comments on IG Media to our Instagram Business connector. For more information, see Graph API's IG Comment.

Klaviyo

We can now pack all the custom fields for the EVENT and PERSON tables into a single JSON file and upsert it into a single column. We have added a new field, Pack Mode, to the connector setup form. The field provides you the option to choose how Fivetran should handle your custom fields. For more information, see our Klaviyo connector documentation.

Mambu

We no longer re-import the CENTRE table and its child tables.

Maxio Chargify

We now incrementally sync the COMPONENT table and its child tables to capture new records.

We now also capture deletes for the COMPONENT table.

MySQL

Our GTID replication mode is now generally available.

NetSuite SuiteAnalytics

We have fixed a bug where we didn’t sync some records for the PREVIOUS_TRANSACTION_LINE_LINK table. We have added the _fivetran_index column as a primary key column to the PREVIOUS_TRANSACTION_LINE_LINK table.

OneLake

We now perform regular maintenance operations on the tables in your OneLake destination. These maintenance operations do the following:

Delete the table snapshots that are older than 7 days
Clean up orphan and removed files

For more information, see our OneLake documentation. We are gradually rolling out this enhancement to all existing destinations.

Prive

We no longer capture deletes for the following tables:

BILLING_ATTEMPT
ORDER_LINE_ITEM
PRODUCT
SUBSCRIBER
SUBSCRIPTION_ACTIVITY

Qualtrics

The Qualtrics connector now supports OAuth 2.0 authentication. Qualtrics connectors created on or after May 21, 2024, use OAuth 2.0-based authentication. For more information, see our setup instructions.

You can migrate your existing connectors from API key-based authentication to OAuth authentication. For more information, see our migration instructions.

We are gradually rolling out this feature to all existing connectors.

Salesforce

We now translate formulas containing the / operator only for the following destinations:

BigQuery
Databricks
PostgreSQL
Redshift
Snowflake

Previously, we supported this operator for all destinations.

Salesforce Commerce Cloud

We now capture deletes for the following tables:

CATALOG
CATEGORY
SHARED_PRODUCT_OPTION
SHARED_PRODUCT_OPTION_VALUE
GIFT_CERTIFICATE
GIFT_CERTIFICATE_TRANSACTION
PROMOTION
COUPON
SOURCE_CODE_GROUP
CUSTOMER_GROUP
CUSTOM_OBJECT_ATTRIBUTE_DEFINITION
CUSTOM_OBJECT_ATTRIBUTE_GROUP
STORE
INVENTORY_LIST
INVENTORY_LIST_RECORD

Salesloft

We can now sync the email templates used in Salesloft Cadences into the EMAIL_TEMPLATES table. To backfill the historical data for this type of email templates, re-sync the EMAIL_TEMPLATES table.

SharePoint

Our SharePoint connector now supports syncing Microsoft Excel spreadsheets in Merge Mode. For more information, see our setup instructions.

Spotify Ads

We now support the Spotify Ads API v2 with all updates made to it through March 2024.

Sprout Social

Our Sprout Social connector is now generally available. Read our Sprout Social connector documentation.

Square

The Square connector now supports table blocking for all Square tables. You can choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables.

If you want to sync a child table, you must include its parent table for the sync.

Vitally

We have added a new field, Base URL, to the setup form. For more information, see our setup instructions.

Workday HCM

We now support OAuth authentication to connect to Workday HCM.

Wrike

We no longer perform a weekly re-import of the FOLDER_PROJECT and TASK tables.

Zoho CRM

You can now select the child tables (including subforms) to sync from the Schema tab on your connector details page. To backfill the historical data for a child table that you select, re-sync its parent table. We will backfill the historical data for the subforms during their weekly re-import.

We now create empty tables and columns in your destination for the child tables that do not have any data.

You can now track the history of your deal stages. To facilitate this enhancement, we have added the following new tables:

STAGE
A new child table, DEAL_STAGE_HISTORY, to the DEAL table

We are gradually rolling out this enhancement to all existing connectors.

REST API Improvements

Create a Connector Schema Config endpoint

Our Connector Management API now supports a new endpoint, Create a Connector Schema Config. The endpoint allows to configure the schema before the initial sync without reloading. The endpoint is not in beta.

Proxy Agent and Private Link Management-related changes in the REST API

To Create a Private Link using our Private Link Management API, you now must specify the service and region parameter values in the request instead of group_id. This enables you to use a single private link for all destinations with the same service and region.

To Create a Proxy Agent using our Proxy Agent Management API, you now must specify the group_region parameter value in the request instead of group_id. This enables you to use a single proxy agents for all connections in a specified region.

We have added the following parameters in the Connection Management API:

proxy_agent_id - defines the proxy ID
private_link_id - defines the private link ID.
networking_method - defines the connection method. Possible values are as follows:
- Directly - direct connection
- PrivateLink - connection via private link
- ProxyAgent - connection via proxy
- SshTunnel - connection via SSH Tunnel.

We have added the following parameters in the Destination Management API:

private_link_id - defines the private link ID.
networking_method - defines the connection method. Possible values are as follows:
- Directly - direct connection
- PrivateLink - connection via private link
- SshTunnel - connection via SSH Tunnel.