June 2024

Databricks on Azure destinations with OAuth limitations

Databricks on Azure destinations with OAuth authentication don't support Transformations for dbt Core* and Quickstart models.

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

Hybrid Deployment

We have released the beta version of our Hybrid Deployment model. The Hybrid Deployment model enables organizations with strict security requirements to utilize the data integration capabilities of Fivetran within their on-premise or cloud environment. This deployment model allows organizations to process data locally within their network while leveraging Fivetran's cloud to orchestrate and configure all the data movement. For more information about this deployment model and the connectors and destinations supporting it, see our Hybrid Deployment documentation.

Lite Connectors

Lite connectors are now available for the following sources:

Sunset Connectors

Verizon Media

We sunset our Verizon Media connector. Effective June 1, 2024, we will no longer support the creation of new Verizon Media connectors.

Transformations for dbt Core

dbt job retries are disabled by default.

We now disable the dbt job retry mechanism for scheduled in code and scheduled in Fivetran transformations by default.

You can change this for scheduled in code transformations by setting the value of the retryOnFailure parameter to true in the job configuration:

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

Smart syncing option for custom scheduling

For scheduled in Fivetran transformations for dbt Core*, we have added a new option, Smart syncing, to the Custom Scheduling group of the Schedule tab.

With the Smart syncing option enabled, the models run on the set schedule. However, when their run schedule overlaps with the sync schedule of their upstream connectors, models wait until connectors have finished syncing before running.
With the Smart syncing option disabled, the models run on the set schedule regardless of the upstream connectors' sync schedule and state.

* 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 retry logic

Fivetran now provides the following retry logic:

If a connection fails with a task, for the first 24 hours following the first failure, it retries syncs as described in the Failed Sync Retries During the First 24 Hours section.
After 24 hours of failed sync retries since the first failure, the connection sync retry frequency is switched to the sync frequency you set for the connection until either a sync retry succeeds, or the time since the initial sync failure reaches 72 hours.
After 72 hours of failed sync retries since the first failure, the sync retry is run once a day until either a sync retry succeeds, or the time since the first failure reaches 14 days.
If the sync retry does not succeed after 14 days since the first failure, Fivetran automatically pauses the connection.
If you unpause the connection that was automatically paused after 14 days of failed retries, and the connection's sync still fails, Fivetran will retry syncing once a day for the next 14 days before automatically pausing it again.
Once a sync retry succeeds at any point within 14 days since the first failure, the connection reverts to the sync frequency you set for the connection.

New connectors

High-Volume Agent SAP ECC on SQL Server

SAP ECC on SQL Server is an enterprise resource planning and analytics platform built on top of SQL Server. Fivetran replicates data from your SQL Server source database and loads it into your destination using this High-Volume Agent connector.

Read our High-Volume Agent SAP ECC on SQL Server documentation.

Microsoft Dynamics 365 Finance and Operations

Microsoft Dynamics 365 Finance and Operations is an ERP solution for medium to large organizations.

Read our Microsoft Dynamics 365 Finance and Operations connector documentation.

Schema changes

Ada

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

We are implementing these schema changes to facilitate the addition of new columns for a feature enhancement.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`CONVERSATION`
column	New Column	`generated_topic_id`	We've added a new column.
column	New Column	`generated_topic_label`	We've added a new column.

Alchemer

Effective June 21, 2024 we use a new June 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 being made to ensure alignment with development framework best practices.

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 • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ANSWER_VALUE`
column	Primary Key Change	`answers_value`	`answers_value` 🔑	Added to primary key.
`CONTACT_LIST_CONTACT`
column	Rename Column	`group`	`groups`
`QUOTA`
column	Rename Column	`limit`	`limits`
`SURVEY_CAMPAIGN`
column	Rename Column	`language`	`languages`
`SURVEY_CONTACT`
column	Rename Column	`group`	`groups`
`SURVEY_RESPONSE`
column	Rename Column	`language`	`languages`

Assembled

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

We are implementing this schema change to facilitate the addition of a new column for a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`AGENT_STATE`
column	New Column			`platform`	We've added a new column.

Birdeye

Effective June 18, 2024 we use a new June 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 reserved keywords being used as column names.

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
`PAGE`
column	Rename Column	`order`	`orders`
`PAGE_QUESTION`
column	Rename Column	`order`	`orders`
`QUESTION_CHOICE`
column	Rename Column	`order`	`orders`

Bitly

Effective June 3, 2024 we use a new June 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 to align with the recent changes in the Bitly API.

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
`GROUP_OVERRIDE`
table	Deprecated Table		`GROUP_OVERRIDE`		Bitly deprecated this endpoint from their public API.

CallRail

Effective June 19, 2024 we use a new June 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 efficiently retrieve and manage data. 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
`CALL`
column	New Column			`gclid`

Campaign Monitor

Effective June 18, 2024 we use a new June 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 weak primary key and for the purposes of establishing a foreign key relationship between the CLIENT_SENT_CAMPAIGN table and its child entities.

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.

14 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CAMPAIGN_BOUNCE`
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_CLICK`
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_EMAIL_CLIENT`
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_LIST`
column	Primary Key Change		`client_id` 🔑	New primary key.
`CAMPAIGN_OPEN`
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_RECIPIENT`
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_SEGMENT`
column	Primary Key Change		`client_id` 🔑	New primary key.
`CAMPAIGN_SPAM_COMPLAINT`
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_SUMMARY`
column	Primary Key Change	`campaign_id` 🔑	`campaign_id`	No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
column	New Column		`client_id`	Added to foreign key.
`CAMPAIGN_UNSUBSCRIBE`
column	New Column		`client_id`	Added to foreign key.
`CLIENT_SENT_CAMPAIGN`
column	Primary Key Change		`client_id` 🔑	Added to primary key.
`SENT_CAMPAIGN_TAG`
column	Primary Key Change		`client_id` 🔑	Added to primary key.

Castor EDC

Effective June 7, 2024 we use a new June 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 primary key issue.

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
`REPEATING_DATA_INSTANCE_DATA_POINT`
column	Primary Key Change	`field_id`	`field_id` 🔑	Added to primary key.
`STUDY_DATA_ENTRY`
column	Primary Key Change	`field_id`	`field_id` 🔑	Added to primary key.

Chargebee Product Catalog 2.0

Effective June 28, 2024 we use a new June 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 necessary due to changes in the source API. We've also added new 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.

3 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`DIFFERENTIAL_PRICE_TIER`
table	New Table		`DIFFERENTIAL_PRICE_TIER`	Child table of the `DIFFERENTIAL_PRICE` parent table.
`ITEM_PRICE_TIER`
table	New Table		`ITEM_PRICE_TIER`	Child table of the `ITEM_PRICE` parent table.
`PRICE_TIER`
table	Deprecated Table	`PRICE_TIER`		Chargebee Product Catalog 2.0 no longer supports it.

ClickUp

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

We have made the following schema changes to avoid 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.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ACCESSIBLE_CUSTOM_FIELD`
column	Primary Key Change	`list_id`	`list_id` 🔑	Added to primary key
`GOAL_GR_0_UP_MEMBER (new table name: GOAL_GROUP_MEMBER)`
table	Rename Table	`GOAL_GR_0_UP_MEMBER`	`GOAL_GROUP_MEMBER`	Renamed a Table
`SUB_TASK`
column	Rename Column	`tag`	`tags`	Renamed a column

Concord

Effective June 14, 2024 we use a new June 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 index.

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.

15 total changes • 15 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`AGREEMENT_APPROVAL`
column	Primary Key Change	`agreement_uuid` 🔑	`agreement_uuid`	No longer primary key.
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change	`organization_id` 🔑	`organization_id`	No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`AGREEMENT_APPROVAL_RULE`
column	Primary Key Change	`agreement_approval_uuid` 🔑	`agreement_approval_uuid`	No longer primary key.
column	Primary Key Change	`agreement_organization_id` 🔑	`agreement_organization_id`	No longer primary key.
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`AGREEMENT_APPROVAL_VALIDATION`
column	Deprecated Column	`agreement_approval_index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`ORGANIZATION_MEMBER`
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change	`organization_id` 🔑	`organization_id`	No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`ORGANIZATION_MEMBER_GROUP`
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Coupa

We have added a new column, channel, to the INVOICE_HEADER table. Be sure to re-sync the INVOICE_HEADER table to backfill the historical data for this column or contact our support team to re-sync it for you.

Crossbeam

Effective June 20, 2024 we use a new June 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 a null primary key error in the REPORT_FILTER table.

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.

14 total changes • 14 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`REPORT_FILTER`
column	Deprecated Column	`id` 🔑		No longer primary key.
column	Primary Key Change	`report_id`	`report_id` 🔑	Added to primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`REPORT_FILTER_EXPRESSION`
column	Deprecated Column	`report_filter_id` 🔑		No longer primary key.
column	Primary Key Change		`report_filter_index` 🔑	New primary key.
column	Primary Key Change		`report_id` 🔑	New primary key.
`REPORT_FILTER_PART`
column	Deprecated Column	`report_filter_id` 🔑		No longer primary key.
column	Primary Key Change		`report_filter_index` 🔑	New primary key.
column	Primary Key Change		`report_id` 🔑	New primary key.
`REPORT_FILTER_PART_OPERAND`
column	Deprecated Column	`report_filter_id` 🔑		No longer primary key.
column	Primary Key Change		`report_filter_index` 🔑	New primary key.
column	Primary Key Change		`report_id` 🔑	New primary key.
`THREAD`
table	Deprecated Table	`THREAD`		No longer available.
`THREAD_TIMELINE`
table	Deprecated Table	`THREAD_TIMELINE`		No longer available.

Drift

Effective June 18, 2024 we use a new June 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 a reserved keyword being used.

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
`MESSAGE_BUTTON`
column	Primary Key Change	`conversation_id`	`conversation_id` 🔑	Added to primary key.
`USER (new table name: USERS)`
table	Rename Table	`USER`	`USERS`

Everhour

Effective June 18, 2024 we use a new June 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 reserved keywords being used as column names.

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
`EXPENSE`
column	Rename Column	`user`	`users`
`PROJECT`
column	Rename Column	`foreign`	`foreigns`

Fivetran Platform Connector

We have added the destination_type column to the DESTINATION table. While the existing type column has two possible values, Fivetran and HVR, destination_type will contain the exact destination type (for example, Snowflake, Kafka, BigQuery, etc.).

Fivetran Platform legacy transformations deprecation

We have removed the TRANSFORMATION and TABLE_TRIGGER tables, as well as the log.transformation_id field, that were related to the previously deprecated basic SQL transformations.

Google Analytics 4

The 'conversions' metrics and dimensions were replaced with 'key events' for Google Analytics 4. We have updated custom and prebuilt reports by replacing deprecated dimensions with the new ones in accordance to the Google Analytics Data API changelog.

Google Search Console

We have added a new dimension, SEARCH_APPEARANCE.

HiBob

Effective June 10, 2024 we use a new June 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 necessary because the source API was updated.

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.

75 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`EMPLOYEE`
column	Rename Column	`active_effective_date`	`work_active_effective_date`	We've renamed the column due to updates in the source.
column	New Column		`actual_working_pattern`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`address_1`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`address_2`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`adress_active_effective_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`age`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`age_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`at_risk_counter`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`avatar`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`birth_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`city`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`company_car_amount`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`contract`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`country`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`current_active_status_start_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`employment_active_effective_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`entitlement_lunch_voucher_amount`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`family_status`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`financial_bank_name`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`fte`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`full_address`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`honorific`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`hours_in_day_not_worked`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`is_manager_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`kids_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`legal_gender`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`lifecycle_status`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`line_1`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`line_2`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`low_risk_counter`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`manager_tenure_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`mobile_phone`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`monthly_payment`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`nationality`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`num_of_direct_reports_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`num_with_same_title_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`number_of_kid`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`pay_frequency`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`pay_period`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`payment_currency`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`post_code`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`postal_code`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`private_email`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`probation_end_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`recent_manager_change_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`salary_active_effective_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`season_ticket_loan_amount`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`short_birth_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`site_city`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`site_country`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`site_state`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`site_working_pattern`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`some_risk_counter`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`spouse_birth_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`spouse_first_name`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`spouse_gender`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`spouse_short_birth_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`spouse_surname`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`ssn`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`ssn_serial_number`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`status`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`team_recent_turnover_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`team_size_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`tenure_rank_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`time_off_frequency_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`time_since_last_salary_change`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`usa_state`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`veteran_status`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`weekly_hour`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`work_active_effective_date`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`work_mobile`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`work_phone`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`yearly_payment`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`years_with_current_title_risk_indicator`	We've added a new column to the `EMPLOYEE` table.
column	New Column		`years_with_recent_salary_risk_indicator`	We've added a new column to the `EMPLOYEE` table.

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

We have removed tables to avoid data redundancy.

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
`ONBOARDING_WIZARDS`
table	Deprecated Table	`ONBOARDING_WIZARDS`
`PUBLIC_PROFILE`
table	Deprecated Table	`PUBLIC_PROFILE`

Hopin

Effective June 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 misuse of index.

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
`DOWNLOAD_REPORT`
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change	`report_type_id` 🔑	`report_type_id`	No longer primary key.
column	Primary Key Change	`report_type_title` 🔑	`report_type_title`	No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Insightly

Effective June 6, 2024 we use a new June 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 minimize the occurrence of long syncs.

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.

97 total changes • 81 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CATEGORY`
table	Deprecated Table	`CATEGORY`		Data now available in the `OPPORTUNITY_CATEGORY`, `PROJECT_CATEGORY`, and `TASK_CATEGORY` tables.
`CONTACT_DATE`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`contact_id` 🔑	New primary key.
`CONTACT_EMAIL`
table	Deprecated Table	`CONTACT_EMAIL`		Data now available in the `CONTACT_LINK` table.
`CONTACT_EVENT`
table	Deprecated Table	`CONTACT_EVENT`		Data now available in the `CONTACT_LINK` table.
`CONTACT_FILE_ATTACHMENT`
column	Deprecated Column	`object_id`
column	Deprecated Column	`object_type`
column	New Column		`contact_id`
`CONTACT_NOTE`
table	Deprecated Table	`CONTACT_NOTE`		Data now available in the `CONTACT_LINK` table.
`CONTACT_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`contact_id` 🔑	New primary key.
`CONTACT_TASK`
table	Deprecated Table	`CONTACT_TASK`		Data now available in the `CONTACT_LINK` table.
`CUSTOM_OBJECT_RECORD`
column	Deprecated Column	`custom_object_name`
`DATES`
table	Deprecated Table	`DATES`		Data now available in the `CONTACT_DATE` and `ORGANISATION_DATE` tables.
`EMAIL_FILE_ATTACHMENT`
column	Deprecated Column	`object_id`
column	Deprecated Column	`object_type`
column	New Column		`email_id`
`EMAIL_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`email_id` 🔑	New primary key.
`FILE_ATTACHMENT`
table	Deprecated Table	`FILE_ATTACHMENT`		Data now available in the `ORGANISATION_FILE_ATTACHMENT`, `OPPORTUNITY_FILE_ATTACHMENT`, `LEAD_FILE_ATTACHMENT`, `CONTACT_FILE_ATTACHMENT`, `EMAIL_FILE_ATTACHMENT`, and `NOTE_FILE_ATTACHMENT` tables.
`LEAD_EMAIL`
table	Deprecated Table	`LEAD_EMAIL`		Data now available in the `LEAD_LINK` table.
`LEAD_EVENT`
table	Deprecated Table	`LEAD_EVENT`		Data now available in the `LEAD_LINK` table.
`LEAD_FILE_ATTACHMENT`
column	Deprecated Column	`object_id`
column	Deprecated Column	`object_type`
column	New Column		`lead_id`
`LEAD_NOTE`
table	Deprecated Table	`LEAD_NOTE`		Data now available in the `LEAD_LINK` table.
`LEAD_SOURCE`
column	Deprecated Column	`lead_source`
column	New Column		`name`
`LEAD_STATUS`
column	Deprecated Column	`lead_status`
column	New Column		`status`
`LEAD_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`lead_id` 🔑	New primary key.
`LEAD_TASK`
table	Deprecated Table	`LEAD_TASK`		Data now available in the `LEAD_LINK` table.
`LINK`
table	Deprecated Table	`LINK`		Data now available in the `ORGANISATION_LINK`, `EVENT_LINK`, `NOTE_LINK`, `PROJECT_LINK`, `TASK_LINK`, `OPPORTUNITY_LINK`, `EMAIL_LINK`, `LEAD_LINK`, and `CONTACT_LINK` tables.
`NOTE_COMMENT`
column	Deprecated Column	`id` 🔑		No longer primary key.
column	Primary Key Change	`owner_user_id`	`owner_user_id` 🔑	Added to primary key.
column	Primary Key Change		`comment_id` 🔑	New primary key.
`NOTE_FILE_ATTACHMENT`
column	Deprecated Column	`object_id`
column	Deprecated Column	`object_type`
column	New Column		`note_id`
`OPPORTUNITY_CATEGORY`
column	Deprecated Column	`category_name`
column	Deprecated Column	`object_name`
column	New Column		`name`
`OPPORTUNITY_EMAIL`
table	Deprecated Table	`OPPORTUNITY_EMAIL`		Data now available in the `OPPORTUNITY_LINK` table.
`OPPORTUNITY_EVENT`
table	Deprecated Table	`OPPORTUNITY_EVENT`		Data now available in the `OPPORTUNITY_LINK` table.
`OPPORTUNITY_FILE_ATTACHMENT`
column	Deprecated Column	`object_id`
column	Deprecated Column	`object_type`
column	New Column		`opportunity_id`
`OPPORTUNITY_NOTE`
table	Deprecated Table	`OPPORTUNITY_NOTE`		Data now available in the `OPPORTUNITY_LINK` table.
`OPPORTUNITY_PRODUCT_ITEM`
table	Deprecated Table	`OPPORTUNITY_PRODUCT_ITEM`		Data now available in the `OPPORTUNITY_ITEM` table.
`OPPORTUNITY_STATE_REASON`
table	Deprecated Table	`OPPORTUNITY_STATE_REASON`		Data now available in the `OPPORTUNITY_STATE_HISTORY` table.
`OPPORTUNITY_TAG`
column	Deprecated Column	`object_name`
`OPPORTUNITY_TASK`
table	Deprecated Table	`OPPORTUNITY_TASK`		Data now available in the `OPPORTUNITY_LINK` table.
`ORGANISATION_DATE`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`organisation_id` 🔑	New primary key.
`ORGANISATION_EVENT`
table	Deprecated Table	`ORGANISATION_EVENT`		Data now available in the `ORGANISATION_LINK` table.
`ORGANISATION_FILE_ATTACHMENT`
column	Deprecated Column	`object_id`
column	Deprecated Column	`object_type`
column	New Column		`organisation_id`
`ORGANISATION_NOTE`
table	Deprecated Table	`ORGANISATION_NOTE`		Data now available in the `ORGANISATION_LINK` table.
`ORGANISATION_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`organisation_id` 🔑	New primary key.
`ORGANISATION_TASK`
table	Deprecated Table	`ORGANISATION_TASK`		Data now available in the `ORGANISATION_LINK` table.
`PIPELINE_STAGE`
column	Primary Key Change	`pipeline_id` 🔑	`pipeline_id`	No longer primary key.
`PRODUCT`
column	Deprecated Column	`product_code`
column	Deprecated Column	`product_family`
column	Deprecated Column	`product_image_url`
column	Deprecated Column	`product_name`
column	Deprecated Column	`product_sku`
column	New Column		`code`
column	New Column		`family`
column	New Column		`image_url`
column	New Column		`name`
column	New Column		`sku`
`PRODUCT_PRICE_BOOK_ENTRY`
table	Deprecated Table	`PRODUCT_PRICE_BOOK_ENTRY`		Data now available in the `PRODUCT_LINK` table.
`PROJECT_CATEGORY`
column	Deprecated Column	`category_name`
column	Deprecated Column	`object_name`
column	New Column		`name`
`PROJECT_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`project_id` 🔑	New primary key.
`PROSPECT_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`prospect_id` 🔑	New primary key.
`TAGS`
table	Deprecated Table	`TAGS`		Data now available in the `ORGANISATION_TAG`, `PROJECT_TAG`, `OPPORTUNITY_TAG`, `EMAIL_TAG`, `LEAD_TAG`, `CONTACT_TAG`, `PROSPECT_TAG`, and `TICKET_TAG` tables.
`TASK_CATEGORY`
column	Deprecated Column	`category_name`
column	Deprecated Column	`object_name`
column	New Column		`name`
`TICKET_TAG`
column	Deprecated Column	`object_id` 🔑		No longer primary key.
column	Deprecated Column	`object_name`
column	Primary Key Change		`ticket_id` 🔑	New primary key.

Kantata

We have added a new table, STATUS_REPORT, for syncing Kantata status report data. For more information, see Kantata's developer docs.

We are gradually rolling out this change to all customers.

LaunchDarkly

Effective June 20, 2024 we use a new June 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.

7 total changes • 5 possible breaking changes

Table/column	Change type	Old name	New name
`ENVIRONMENT_TAG`
table	Deprecated Table	`ENVIRONMENT_TAG`
`FEATURE_FLAG_ENVIORNMENT_PRODUCTION_TARGET`
table	New Table		`FEATURE_FLAG_ENVIORNMENT_PRODUCTION_TARGET`
`FEATURE_FLAG_ENVIORNMENT_TEST_TARGET`
table	New Table		`FEATURE_FLAG_ENVIORNMENT_TEST_TARGET`
`REQUIRED_APPROVAL_TAG`
column	Deprecated Column	`tag_type`
`SEGMENT_CONTEXTS`
table	Deprecated Table	`SEGMENT_CONTEXTS`
`SEGMENT_EXCLUDED_CONTEXTS`
column	Deprecated Column	`object_type`
`SEGMENT_INCLUDED_CONTEXTS`
column	Deprecated Column	`object_type`

Mandrill

We have made the following schema changes for Mandrill connector created on or after June 19, 2024:

Renamed the timestamp column to timestamps in the following tables:
- EVENT
- MESSAGE
- MESSAGE_SMTP_EVENT
Renamed the tag column to tags in the following tables:
- MESSAGE_TAG

Maxio Chargify

Effective June 14, 2024 we use a new June 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 as part of a feature enhancement.

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`INVOICE_PAYMENT`
column	New Column	`payment_method_details`
column	New Column	`payment_method_kind`
column	New Column	`payment_method_memo`

Megaphone

Effective June 20, 2024 we use a new June 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 data integrity issues caused by a misuse of index in combined entities.

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 • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`GEO_NAME_ID_EXCLUSION`
table	New Table		`GEO_NAME_ID_EXCLUSION`
`GEO_NAME_ID_INCLUSION`
table	New Table		`GEO_NAME_ID_INCLUSION`
`ORDER_GEO_NAME`
table	Deprecated Table	`ORDER_GEO_NAME`		Removing table as it was causing data integrity issues.
`PODCAST_AD_FREE_FEED_URL`
table	New Table		`PODCAST_AD_FREE_FEED_URL`
`PODCAST_CATEGORY`
table	Deprecated Table	`PODCAST_CATEGORY`		Removing table as it was causing data integrity issues.
`PODCAST_CLONED_FEED_URL`
table	New Table		`PODCAST_CLONED_FEED_URL`
`PODCAST_EXCLUDED_CATEGORY`
table	New Table		`PODCAST_EXCLUDED_CATEGORY`
`PODCAST_FEED_URL`
table	Deprecated Table	`PODCAST_FEED_URL`		Removing table as it was causing data integrity issues.
`PODCAST_ITUNES_CATEGORY`
table	New Table		`PODCAST_ITUNES_CATEGORY`

Microsoft Advertising

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

budget_type
bid_strategy_id
bid_strategy_name
bid_strategy_target_roas
bid_strategy_target_ad_position
bid_strategy_target_impression_share

Navan

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

We have made the following schema changes to fix a bug where we didn't sync a few columns.

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 • 2 possible breaking changes

Table/column	Change type	Old name	New name
`BOOKING`
column	New Column		`max_price_policy`
`BOOKING_BOOKER`
column	Deprecated Column	`person_uuid`
column	New Column		`billable_entity`
column	New Column		`email`
column	New Column		`employeed_id`
column	New Column		`manager_email`
column	New Column		`manager_name`
column	New Column		`manager_uuid`
column	New Column		`passport`
`TRANSACTION`
column	Deprecated Column	`person_employeed_id`

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

We need this schema change to fix an issue with the primary key.

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
`TRANSACTION`
column	Primary Key Change		`item_id`	`item_id` 🔑	Added to primary key.

Open Data DC

Effective June 18, 2024 we use a new June 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 a reserved keyword being used as a column name.

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
`CRASH_IN_DC`
column	Rename Column		`offset`	`offsets`

Pendo

We have added the following columns to the GUIDE_HISTORY table:

audience
audienceUiHint
authored_language
current_first_eligible_to_be_seen_at
description
editor_type
is_module
is_top_level
kind
published_ever

If you'd like to sync historical data for these columns, contact our support team.

Pinterest Ads

We have added the following new metrics to report tables:

checkout_roas
pinterest_checkout_cost_per_action
pinterest_checkout_roas
total_checkout_conversion_rate
total_add_to_cart_conversion_rate
custom_roas
total_custom_conversion_rate
total_custom_value_in_micro_dollar

PostreSQL

Partitioned tables

Date	Event/Change	Details
June 27, 2024	Change in partitioned tables	The Fivetran dashboard displays only the partitioned table for existing connections. Data syncs do not change, unless your connection meets one of four scenarios*. Previously, the dashboard displayed both the partitioned table and child tables.
June 27, 2024	3-month buffer period starts	For connections that fall within the four scenarios*, we provide a three-month buffer period so you can make the recommended changes. (We have reached out to users whose connections fall within the four scenarios.)
September 27, 2024	3-month buffer period ends	For all connections with partitioned tables, the Fivetran dashboard displays only the partitioned table. We then sync data into the partitioned table in destination, unless you previously reached out to Fivetran requesting data to be synced into partitions. In that case, there will be no change in sync behavior or dashboard display.

* The four scenarios are as follows:

If your connection uses XMIN or Teleport and the Fivetran user does not have select access to all partitions of a partitioned table, we can no longer select and sync that partitioned table after the three-month buffer period ends. We recommend you grant select access to all partitions of the partitioned table you want to sync.
If your connection uses logical replication, your PostgreSQL version is below 13, and the Fivetran user did not include all partitions of the partitioned table in the publication, we can no longer select and sync that partitioned table after the three-month buffer period ends. We recommend you include all partitions of the partitioned table in your publication.
If the partitioned table or some of its partitions are not selected in the Fivetran dashboard, we can no longer select and sync that partitioned table after the three-month buffer period ends. We recommend you select the partitioned table in the Fivetran dashboard.
If your connection uses logical replication, the partitioned table is selected in the Fivetran dashboard, and none of the partitions is selected in the Fivetran dashboard, we do not currently sync data into the partitioned table. However, we can now sync into the partitioned table after the three-month buffer period ends. If you do not want data to be synced into the partitioned table, deselect the partitioned table in the Fivetran dashboard.

If you want to only select partial partitions of a partitioned table in the Fivetran dashboard and have data sync into the partitions, reach out to Fivetran Support and ask that the data be synced into partitions.

Inherited tables

Date	Event/Change	Details
June 27, 2024	3-month buffer period starts	For all existing connections with inherited tables, we provide a three-month buffer period so you can make the recommended changes. Until the buffer period ends, the base table still shows the result of `SELECT * FROM base_table` for inherited tables. Learn more in our Partitioning using inheritance documentation. (We have reached out to users whose connections have inherited tables.)
July 27, 2024	Change in inherited tables for newly created connections	For newly created connections, we treat inherited tables as separate entities. The base table only shows data that physically lives in the table (`SELECT * FROM ONLY base_table`). Learn how we sync child table data and base table data in our Partitioning using inheritance documentation.
September 27, 2024	3-month buffer period ends	Fivetran supports syncing inherited tables and treats them as separate entities. For all connections with inherited tables, the base table only shows data that physically lives in the table (`SELECT * FROM ONLY base_table`). Learn how we sync child table data and base table data in our Partitioning using inheritance documentation.

If you have any questions or concerns, please reach out to Fivetran Support.

Recharge

We have made the following schema changes for connectors created on or after June 18, 2024:

Renamed the ORDER table to ORDERS
Replaced the UTM_TAG table with the following new tables:
- CHARGE_UTM_TAG
- CHECKOUT_UTM_TAG
- CUSTOMER_UTM_TAG
- SUBSCRIPTION_UTM_TAG

REVIEWS.io

Effective June 5, 2024 we use a new June 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 a data integrity issue.

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.

11 total changes • 11 possible breaking changes

Table/column	Change type	Old name
`REVIEW_AND_QUESTION`
column	Deprecated Column	`average_rating`
column	Deprecated Column	`results_count`
column	Deprecated Column	`review_count`
column	Deprecated Column	`stats_company_average_rating`
column	Deprecated Column	`stats_company_review_count`
column	Deprecated Column	`stats_rating_1`
column	Deprecated Column	`stats_rating_2`
column	Deprecated Column	`stats_rating_3`
column	Deprecated Column	`stats_rating_4`
column	Deprecated Column	`stats_rating_5`
`REVIEW_AND_QUESTION_STATS_ATTRIBUTE`
table	Deprecated Table	`REVIEW_AND_QUESTION_STATS_ATTRIBUTE`

Salesloft

We have added a new column, task_id, to following tables:

CALL
ACTION
EMAIL

We have removed the status column from the CALL table. You can find related status columns for calls and their recordings in its child table, CALL_RECORDING.

Salsify

Effective June 5, 2024 we use a new June 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 a primary key issue.

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
`RECORD_DIGITAL_ASSET`
column	Primary Key Change		`digital_asset_id`	`digital_asset_id` 🔑	Added to primary key.

Slack

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

We are implementing this schema change to facilitate the addition of a new column for a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`USERS`
column	New Column			`start_date`	The data in this column denotes the user creation date.

StackAdapt

Effective June 28, 2024 we use a new June 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 more efficiently retrieve and manage data.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`STATS_DELIVERY`
column	New Column			`conv_rev`

Stripe

We have changed the data type of the livemode column in the TRANSFER table from STRING to BOOLEAN.

To apply this change, you need to drop the livemode column in your connector's schema. The next sync will update the datatype. If you need historical data for this column, a re-sync is required.

Taboola

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

create_time
description
learning_display_status
old_item_version_id

The Trade Desk

We have added the category_id property to the ADVERTISER table.

We have added a new table, ADVERTISER_CATEGORY, with the following fields:

id
name
taxonomy_id
taxonomy_name
taxonomy_version

We have added a new table, CATEGORY_MAPPING, with the following fields:

category_id
index
taxonomy_id
external_id

For more information, see our The Trade Desk ERD.

TikTok Ads

We have added the total_landing_page_view, cost_per_landing_page_view, landing_page_view_rate, total_pageview, cost_per_pageview, pageview_rate, avg_value_per_pageview, and total_value_per_pageview fields to the following reports:

CAMPAIGN_REPORT_DAILY
CAMPAIGN_REPORT_HOURLY
CAMPAIGN_REPORT_LIFETIME
ADGROUP_REPORT_DAILY
ADGROUP_REPORT_HOURLY
ADGROUP_REPORT_LIFETIME
AD_REPORT_DAILY
AD_REPORT_HOURLY
AD_REPORT_LIFETIM

We have added the total_landing_page_view, cost_per_landing_page_view, and landing_page_view_rate fields to the following reports:

CAMPAIGN_AGE_GENDER_REPORT
CAMPAIGN_COUNTRY_REPORT
CAMPAIGN_LANGUAGE_REPORT
CAMPAIGN_PLATFORM_REPORT
AD_AGE_GENDER_REPORT
AD_COUNTRY_REPORT
AD_LANGUAGE_REPORT
AD_PLATFORM_REPORT

Typeform

We have added two new tables, FORM_FIELD_INSIGHT and FORM_INSIGHT. These tables can only be synced if you have a Typeform account on the business or enterprise plan.

WorkRamp

Effective June 10, 2024 we use a new June 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 to fix the validation errors in the code.

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
`ACADEMY_USER`
column	Deprecated Column		`type`

Zendesk Support

We have added the following new tables:

CATEGORY
SECTION
USER_SEGMENT
USER_SEGMENT_ADDED_USER
USER_SEGMENT_GROUP
USER_SEGMENT_ORGANIZATION
USER_SEGMENT_TAG

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

Zoom

Effective June 4, 2024 we use a new June 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 resolve a table joining issue.

3 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`WEBINAR_ABSENTEE`
column	New Column	`email`	The new column is a foreign key relation to the `USERS` table.
`WEBINAR_PARTICIPANT`
column	New Column	`user_email`	The new column is a foreign key relation to the `USERS` table.
`WEBINAR_REGISTRANT`
column	New Column	`email`	The new column is a foreign key relation to the `USERS` table.

Improvements

Aircall

We now sync only the last 3 months' worth of data for the CALL table. Previously, we synced the last 6 months' worth of data.

Amazon Selling Partner

To ensure data accuracy, we now sync the past two days' worth of SALES_AND_TRAFFIC_BUSINESS_REPORT_DAILY reports. Previously, we synced one day's worth of these reports due to source side limitations. It may take up to two days to reflect for the destination to reflect correct data. Learn more in our Amazon Selling Partner reports documentation.

Azure Data Lake Storage

You can now specify how long you want us to retain your table snapshots before deleting them through table maintenance operations. To facilitate this enhancement, we have added a new drop-down menu, Snapshot Retention Period, to the destination setup form. For more information, see our setup instructions.

BallotReady

We no longer capture deletes for the MEASURE and OFFICE_HOLDER tables.

Braintree

We have changed our sync strategy for the DISPUTE table. To avoid data discrepancy, we now sync the past 3 days' data for this table daily. Previously, we only synced data for the past 2 days.

Brex

We have changed the sync strategy for our Brex connector. We no longer capture deletes for the CASH_ACCOUNT_TRANSACTION and PRIMARY_CARD_ACCOUNT_TRANSACTION tables and their child tables.

Chameleon

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

DOMAIN
ENVIRONMENT
LAUNCHER
TAGS
TOOLTIP
TOUR_INTERACTION

Column

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

ACH_RETURN
CHECK_RETURN
CHECK_TRANSFER
EVENT
INTERNATIONAL_WIRE
PAYMENT
TRANSFER
WIRE_DRAW_DOWN
WIRE_TRANSFER

crowd.dev

We no longer capture deletes for CONVERSATION table.

Deputy

We now incrementally sync the EMPLOYEE_HISTORY table and its child tables also.

Drata

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

PERSONNEL
USER_IDENTITIES_INFRASTRUTURE
USER_IDENTITIES_VERSION_CONTROL

FireHydrant

We have removed the weekly re-import for the INCIDENT and INCIDENT_METRIC_BUCKET tables.

Friendbuy

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

CLICK
DISTRIBUTED_ADVOCATE_REWARD
DISTRIBUTED_FRIEND_INCENTIVE
EMAIL_CAPTURE
PURCHASE
SHARE
SIGNUP
WIDGET_VIEW

GetFeedback

We no longer incrementally sync the RESPONSE table and its child tables.

GlobalMeet

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

Google Ads

We have added the segments.week and segments.month timeline segments and now provide a finer timeline granularity for custom reports. All new connectors created after June 7, 2024 support this functionality.

We've added the option to skip empty account reports to improve connector performance. This feature is enabled by default for all connectors created after June 20, 2024. You can also manually toggle it On or Off on the connector setup form. See our Skip Empty Reports documentation for further details.

Google Search Ads 360

Our Google Search Ads 360 connector is now generally available.

Read our Google Search Ads 360 documentation for more information.

Height

We started using webhooks to track the deletion of records in the TASK and ACTIVITY tables.

Read our Height documentation for more information.

KeyPay

We no longer re-import the INVOICE tables and its child tables once a week to capture deletes.

Lob

We have made the following changes to the sync strategy:

We now incrementally sync the following tables to capture new records:
- ADDRESS
- BANK_ACCOUNT
- CHECKS
- LETTER
- POSTCARD
- SELF_MAILER
- TEMPLATE
- TEMPLATE_VERSION
We now re-import the following tables once a week to capture updates and deletes:
- BANK_ACCOUNT
- CHECKS
- LETTER
- POSTCARD
- SELF_MAILER
- TEMPLATE
We no longer capture deletes for the ADDRESS table.

Mandrill

We have made the following changes to the Schema tab for Mandrill connectors created on or after June 19, 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 Mandrill connectors.

Maxio Chargify

We now incrementally sync the SUBSCRIPTION_COMPONENT table.

Namely

We now incrementally sync the PROFILE table and its child tables.

OneLake

PagerDuty

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

PartnerStack Vendor

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

REWARD

PayPal

We have made the following changes to the Schema tab for connectors created on or after June 21, 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 for syncing

Qualtrics

The Qualtrics connector now supports table-level re-syncs.

Recharge

We have made the following changes to the Schema tab for connectors created on or after June 18, 2024:

Table names now appear in lowercase
We display all the tables, including the empty tables
We no longer support table-level selection and deselection for syncing

S3 Data Lake

We have significantly reduced the time taken to query your data from the non-primary key columns of your destination tables. To facilitate this enhancement, our connectors created on or after June 20, 2024 now update two statistics, minimum value and maximum value, for all the columns in the tables that contain up to 200 columns.

We now support the Delta Lake format for your destination tables. For more information, see our S3 Data Lake documentation.

You can now integrate Databricks Unity Catalog with your S3 Data Lake destination and create external tables for the data stored in your destination's Delta Lake tables. For more information, see our Unity Catalog setup instructions.

Sailthru

We can now pack all the custom fields of the LIST_STAT and USER 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. This feature is useful when the number of columns in a table exceeded 9,900 columns. If Unpacked Mode is selected and the number of columns of your table exceeds 9,900 then we will truncate the columns to 9,900. For more information, see our Sailthru connector documentation.

Salesforce

We now support AWS Private Link for Salesforce. This feature is in BETA and available only for Business Critical accounts.

Samsara

We have made the following changes to the sync strategy:

We now re-import only the DOCUMENT and ROUTE tables once a week to capture updates and deletes.
We no longer capture deletes for the following tables:
- DEFECT
- DRIVER
- DRIVER_HOS_VIOLATION
- DVIR
- HOS_DAILY_LOG
- SAFETY_EVENT
- VEHICLE
- VEHICLE_TRIP

SAP ERP on HANA

A new version of the Fivetran NetWeaver API is now available for download: v1900230. This API version enables the following two features:

For more information, see our SAP ERP on HANA documentation and SAP ERP on HANA setup guide.

ServiceTitan

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

APPOINTMENT
APPOINTMENT_ASSIGNMENT
BOOKING_PROVIDER_TAG
BUSINESS_UNIT
CALL
CAMPAIGN
CUSTOMER
EMPLOYEE
EXPORT_INVOICE_ITEM
INVENTORY_BILL
INVOICE
JOB
JOB_HOLD_REASON
JOB_SPLIT
JOB_TYPE
LEAD
LOCATION
MEMBERSHIP
PAYMENT
PROJECT
PROJECT_STATUS
PROJECT_SUBSTATUS
TECHNICIAN

Shopify

We have fixed an issue in our Shopify connector where we were unable to capture deletes in the METAFIELD table. This issue occurs only when you delete all the metafields in the source. We recommend that you re-sync your connector if you observe any data integrity issues. We are gradually rolling out this change to all existing connectors.

Simplecast

We now re-import the ANALYTICS_DOWNLOAD, ANALYTICS_DOWNLOAD_COLLECTION and AVERAGE_COMPLETION tables in every sync to capture updates and deletes. Previously, we incrementally synced these tables.

Simplesat

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

SkuVault

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

AVAILABLE_QUANTITY
ITEM_QUANTITY
KIT
PRODUCT
PURCHASE_ORDER
TRANSACTION

Statsig

We now incrementally sync the AUDIT_LOG table to capture new records.

We have changed the connector type of our Statsig connector from Lite to Standard. We are gradually rolling out this upgrade to all existing connectors.

Swoogo

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

EVENT
EVENT_BADGE
EVENT_QUESTION
CALL_FOR_SPEAKER_CONTACT
CALL_FOR_SPEAKER_REVIEW
CALL_FOR_SPEAKER_SUBMISSION
PACKAGE
PAGE
REGISTRANT
REGISTRANT_LINE_ITEM
REGISTRANT_TYPE
SESSION
SPEAKER
SPONSOR
TRANSACTION

Tableau

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

WORKBOOK
VIEW

The Trade Desk

We have added new properties as a replacement for the legacy IndustryCategoryID property, which we no longer sync. For more information, see The Trade Desk's New Properties in Advertiser and Ad Group Endpoints documentation.

Upland Software

We no longer perform a weekly re-import for the CALL table.

Workday RaaS

We now support OAuth authentication to connect to Workday RaaS.

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

Zendesk Support

We now include the USER_VOTE table in the syncs by default. Previously, we excluded this table from the sync by default. You can now select or deselect the USER_VOTE table to sync from the Schema tab on your connector details page.

REST API Improvements

Added new field to Retrieve a Connector Schema Config response

We have added a new field, supports_columns_config, to the response of our REST API Retrieve a Connector Schema Config endpoint. The supports_columns_config field indicates whether the table supports column configuration.

Changed response format for Retrieve Connector Types

We have added the following new fields to the response for our REST API Retrieve connector types:

supported_features
service_status_updated_at

The data field contains all fields returned in the response in the old format.

An example of the new response format:

{
  "code": "Success",
  "data": {
      "items": [
        {
          "id": "facebook_ads",
          "name": "Facebook Ads",
          "type": "Marketing",
          "connector_class": "standard",
          "description": "Facebook Ads provides attribute data on Facebook Ads",
          "icon_url": "https://fivetran.com/integrations/facebook/resources/facebook.svg",
          "icons": [
            "https://fivetran.com/integrations/facebook/resources/facebook-logo.svg",
            "https://fivetran.com/integrations/facebook/resources/facebook-logo.png"
          ],
          "link_to_docs": "https://fivetran.com/docs/connectors/applications/facebook-ads",
          "link_to_erd": "https://fivetran.com/docs/connectors/applications/facebook-ads#schemainformation",
          "service_status": "general_availability",
          "service_status_updated_at": "2024-01-01",
          "supported_features": [
            {
              "id": "CUSTOM_DATA",
              "notes": ""
            },
            {
              "id": "CAPTURE_DELETES",
              "notes": ""
            },
            {
              "id": "DATA_BLOCKING",
              "notes": "Column level"
            },
            {
              "id": "COLUMN_HASHING",
              "notes": ""
            },
            {
              "id": "RE_SYNC",
              "notes": ""
            },
            {
              "id": "HISTORY",
              "notes": ""
            },
            {
              "id": "API_CONFIGURABLE",
              "notes": "API Configuration"
            },
            {
              "id": "PRIORITY_FIRST_SYNC",
              "notes": "All tables"
            },
            {
              "id": "FIVETRAN_DATA_MODELS",
              "notes": ""
            },
            {
              "id": "PRIVATE_NETWORKING",
              "notes": ""
            },
            {
              "id": "AUTHORIZATION_VIA_API",
              "notes": ""
            }
          ]
        }
      ]
  }
}