October 2023

Edit Historical Sync Time Frame value for Google connectors

We have added the ability to update the Historical Sync Time Frame value even after a Google connector has been set up.

The following connectors now support this feature:

WARNING: Updating the timeframe option to a larger value will trigger a connector re-sync.

Lite Connectors

Lite connectors are now available for the following sources:

Transformations for dbt Core

dbt Core versions 1.5.8, 1.6.6 support

We now support dbt Core version 1.5.8 and 1.6.6. You can use these versions to run your projects.

NOTE: For the above-mentioned versions of dbt Core, we don't support SQL Server, Azure Synapse, and 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.

New dbt Quickstart packages

We have added new Quickstart packages for the following connectors:

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

Support for Private Git dbt Core packages with SSH key access

We now support access to private Git dbt Core packages in the repository with the dbt project for Scheduled in Code transformations using the same SSH key. For more information on the configuration syntax, see dbt's documentation.

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

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

Fivetran Platform Connector to version 1.1.0
Google Ads to version 0.9.3
Intercom to version 0.8.0
Jira to version 0.15.0
NetSuite SuiteAnalytics to version 0.9.0
QuickBooks to version 0.12.0
Zendesk Support to version 0.11.2

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

New connectors

Customer.io

Customer.io is an automated messaging platform. Read our Customer.io connector documentation.

SAP ERP on HANA

You can now replicate data from your SAP ECC and S4 systems on HANA to any supported Fivetran destinations. Read our SAP ERP on HANA connector documentation.

Schema changes

ActiveCampaign

We have added three new tables, CONTACT, ACCOUNT_CONTACT, and CONTACT_TAG.

We have renamed the following tables:

CUSTOM_ACCOUNT_FILED to CUSTOM_ACCOUNT_FIELD
CUSTOM_ACCOUNT_FILED_VALUE to CUSTOM_ACCOUNT_FIELD_VALUE
E-COM_ORDER to E_COM_ORDER
E-COM_CUSTOMER to E_COM_CUSTOMER
E-COM_ORDER_PRODUCT to E_COM_ORDER_PRODUCT
TAG to TAGS
USERGROUP to USER_GROUP

We have removed the ACCOUNT_ASSOCIATION_CONTACT table.

We have changed the following columns:

Table name	Changes
`ACCOUNT_ASSOCIATION`	Removed the `ACCOUNT_ASSOCIATION_CONTACT` foreign key relation and added `CONTACT` foreign key relation.
`AUTOMATION`	Renamed `cdate` and `mdate` columns to `c_date` and `m_date`. Added `entitlements_violation` columns.
`CALENDER`	Renamed `cdate` and `mdate` columns to `c_date` and `m_date`.
`CAMPAIGN`	Renamed `cdate`, `ldate`, `mdate`, `sdate`, and `user` columns to `c_date`, `l_date`, `m_date`, `s_date`, and `user_id`. Updated the foreign key relation name `user` to `user_id`.
`CONNECTION`	Renamed `cdate` and `udate` columns to `c_date` and `u_date`.
`CONTACT_CUSTOM_FIELD`	Renamed `cdate` and `udate` to `c_date` and `u_date`.
`CONTACT_CUSTOM_FIELD_VALUE`	Renamed `cdate` and `udate` columns to `c_date` and `u_date`. Removed `ACCOUNT_ASSOCIATION_CONTACT` as foreign key relation and added `CONTACT` table as a foreign key relation.
`DEAL`	Renamed `cdate`, `edate`, `mdate`, `group`, and `percent` columns to `c_date`, `e_date`, `m_date`, `groups`, and `percentage`. Removed `ACCOUNT_ASSOCIATION_CONTACT` table as a foreign key relation and added `CONTACT` table as a foreign key relation. Added the foreign key relation for the `DEAL` and `TASK` tables.
`DEAL_CUSTOM_FIELD`	Renamed `known_fieldId` column to `known_field_id`.
`DEAL_CUSTOM_FIELD_OPTION`	Renamed `filed_option` column to `field_option`.
`FORM`	Renamed `cdate`, `submitdata_url`, and `udate` columns to `c_date`, `submit_data_url`, and `u_date`.
`GROUPS`	Renamed `sdate` column to `s_date`.
`LIST`	Renamed `cdate` and `udate` columns to `c_date` and `u_date`.
`MESSAGE`	Renamed `cdate`, `ed_instnceid`, `mdate`, and `userid` columns to `c_date`, `ed_instnce_id`, `m_date`, and `user_id`.
`NOTE`	Renamed `cdate` and `mdate` columns to `c_date` and `m_date`. Removed `ACCOUNT_ASSOCIATION_CONTACT` foreign key relation and added `CONTACT` foreign key relation.
`ORDER_PRODUCT`	Renamed `ecomOrder` column to `e_com_order`. Updated the foreign key relation name for `order_id` to `e_com_order` column.
`PIPELINE`	Renamed `cdate` and `udate` columns to `c_date` and `u_date`.
`SAVED_RESPONSE`	Renamed `cdate`, `ldate`, and `mdate` columns to `c_date`, `l_date`, and `m_date`.
`SCHEMA_RELATIONSHIP`	Renamed `hasMany` columns to `has_many`.
`SCORE`	Renamed `cdate` and `mdate` columns to `c_date` and `m_date`.
`SECONDARY_CONTACT`	Renamed `cdate` column to `c_date`. Removed `ACCOUNT_ASSOCIATION_CONTACT` foreign key relation and added `CONTACT` as a foreign key relation.
`SEGMENT`	Added `segment_id_v2` column.
`STAGE`	Renamed `cdate`, `order`, `group`, and `udate` columns to `c_date`, `orders`, `groups`, and `u_date`.
`TASK`	Renamed `cdate`, `edate`, `udate`, and `user` columns to `c_date`, `e_date`, `u_date` and `user_id`. Removed `ACCOUNT_ASSOCIATION_CONTACT` as a foreign key relation and added `CONTACT` table as a foreign key. Updated the foreign key relation name `user` to `user_id`.
`TASK_TYPE`	Renamed `cdate` and `udate` to `c_date` and `u_date`.
`USERS`	Renamed `local_zoneid` column to `local_zone_id`. Removed the `password_updated_utc_timestamp` column

We have implemented incremental sync for the CONTACT and DEAL tables.

ADP Workforce Now

We no longer sync the following columns to the WORKER_REPORT_TO table because the Workers API does not return them:

reports_to_relationship
reports_to_relationship_effective_date
reports_to_relationship_long_name
reports_to_relationship_short_name
reports_to_relationship_subdivision_type

Brex

We have added a new table, EXPENSE.

commercetools

We have added new columns, shipping_address_* and billing_address_*, to the ORDERS table.

We have removed the foreign key relationship of the shipping_address_id and billing_address_id columns to the CUSTOMER_ADDRESS table, in the ORDERS table.

Firebase

We now sync the subcollection data related to a particular document in a separate table, instead of syncing it in the same row, in the nested_data column.

For example, For a collection named customer and its subcollection, address, we sync all the subcollection data of address in a separate table with the same name. The ADDRESS table in the destination has the following schema:

_path - Contains the whole reference path of the subcollection document.
_id - Contains the ID of the subcollection document.
updated_at - updated_at timestamp of the subcollection document.
data - Contains the JSON data of the subcollection document.

You may observe an increase in your Monthly Active Rows (MAR) usage.

Fivetran Platform Connector

We now sync source and destination metadata to the following tables:

COLUMN_LINEAGE
DESTINATION_COLUMN_METADATA
DESTINATION_SCHEMA_METADATA
DESTINATION_TABLE_METADATA
SCHEMA_LINEAGE
SOURCE_COLUMN_METADATA
SOURCE_SCHEMA_METADATA
SOURCE_TABLE_METADATA
TABLE_LINEAGE

This functionality replaced the Metadata API. If you are using the Metadata API, you should have received an email with details regarding the deprecation timeline.

Google Analytics 4

We have added the Audience pre-built report.

HubSpot

We have added the following new tables to support the HubSpot Quotes API:

QUOTE
QUOTE_COMPANY
QUOTE_CONTACT
QUOTE_DEAL
QUOTE_LINE_ITEM
QUOTE_PROPERTY_HISTORY

These tables are available by default for all HubSpot connectors created after October 12, 2023. We are gradually rolling out these changes to all existing HubSpot connectors.

We have introduced the following schema changes for connectors created on or after October 17, 2023:

We have upgraded to API v3 to sync the TICKET_PIPELINE, TICKET_PIPELINE_STAGE, DEAL_PIPELINE and DEAL_PIPELINE_STAGE tables.
We have deprecated the active column for all the four tables mentioned above.
We have added a new column, write_permissions, to the TICKET_PIPELINE_STAGE and DEAL_PIPELINE_STAGE tables.

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

Intercom

We have upgraded our Intercom connector from Intercom API version 2.9 to 2.10. As part of the upgrade, we have made the following schema changes:

We have added the following new tables:
- HELP_CENTER_HISTORY
- TICKET_CONTACT_HISTORY
- TICKET_HISTORY
- TICKET_LINK_HISTORY
- TICKET_PART_ATTACHMENT_HISTORY
- TICKET_PART_HISTORY
- TICKET_TYPE_ATTRIBUTE_HISTORY
- TICKET_TYPE_HISTORY
We have deprecated the SECTION_HISTORY table.
We have added a new column, help_center_id, to the COLLECTION_HISTORY table.
We have deprecated the section_id column from the ARTICLE_HISTORY table.

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

LinkedIn Ad Analytics

We have set timeGranularity to MONTHLY for Demographic reports, according to LinkedIn's recommendations. As a part of this change, we have made the following schema changes:

We have added the following tables:
- MONTHLY_AD_ANALYTICS_BY_MEMBER_COMPANY
- MONTHLY_AD_ANALYTICS_BY_MEMBER_COMPANY_SIZE
- MONTHLY_AD_ANALYTICS_BY_MEMBER_COUNTRY_V2
- MONTHLY_AD_ANALYTICS_BY_MEMBER_INDUSTRY
- MONTHLY_AD_ANALYTICS_BY_MEMBER_JOB_FUNCTION
- MONTHLY_AD_ANALYTICS_BY_MEMBER_JOB_TITLE
- MONTHLY_AD_ANALYTICS_BY_MEMBER_REGION_V2
- MONTHLY_AD_ANALYTICS_BY_MEMBER_SENIORITY
We have deprecated the following tables:
- AD_ANALYTICS_BY_MEMBER_COMPANY
- AD_ANALYTICS_BY_MEMBER_COMPANY_SIZE
- AD_ANALYTICS_BY_MEMBER_COUNTRY_V2
- AD_ANALYTICS_BY_MEMBER_INDUSTRY
- AD_ANALYTICS_BY_MEMBER_JOB_FUNCTION
- AD_ANALYTICS_BY_MEMBER_JOB_TITLE
- AD_ANALYTICS_BY_MEMBER_REGION_V2
- AD_ANALYTICS_BY_MEMBER_SENIORITY

Okta

We have added two new tables, PROFILE_MAPPING and POLICY.

Ortto

We have changed the composite primary key of the PERSON_AUDIENCE table. The new composite key is a combination of the person_id and audience_id columns. Previously, we used the person_id, audience_id, and subscribed_from columns as the composite primary key.

Outreach

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

TABLE	NEW COLUMNS
`CONTENT_CATEGORY`	`color`
`MAIL_ALIAS`	`email_hash`
`MAILBOX`	`email_hash`
`OPPORTUNITY`	`currency_type`
`RULESET`	`ooto_auto_extraction_enabled`, `meeting_booked_action`, `name`, `sms_opt_out_action`, and `sms_received_action`
`SEQUENCE`	`locked_at`
`USER`	`calls_view_id`, `default_ruleset_id`, `kaia_recordings_view_id`, `tasks_view_id`, `teams_view_id`, and `users_view_id`

We no longer sync the following columns of the tables below:

TABLE	COLUMNS
`EMAIL_ADDRESS`	`bounced_at`
`SEQUENCE_STATE`	`auto_resume_ooto_prospects`, `include_unsubscribe_links`, `sequence_exclusivity`, and `step_overrides_enabled`
`TASK`	`click_count`

Now, the following columns in the tables below have a foreign key relationship to the listed referenced tables:

TABLE	COLUMN	REFERENCED TABLE (in the respective order of columns)
`EVENT`	`account_id`, `call_id`, `opportunity_id`, `task_id`	`ACCOUNT`, `CALL`, `OPPORTUNITY`, `TASK`
`MAILING`	`follow_up_sequence_id`, `user_id`	`SEQUENCE`, `USER`
`RULESET`	`call_task_priority_id`	`TASK_PRIORITY`
`SEQUENCE_STEP`	`task_priority_id`	`TASK_PRIORITY`

Salesforce

We will no longer sync theFIVETRAN_FORMULA_HISTORY table and formula field translations into the sql, view_sql, and reason_null columns in the FIVETRAN_FORMULA table effective November 1, 2023.

We will also drop the FIVETRAN_FORMULA_HISTORY table, and the deprecated columns in the FIVETRAN_FORMULA table, starting February 1, 2024,

Instead, you can find the formula field translations and error information in the FIVETRAN_FORMULA_MODEL and FIVETRAN_FORMULA_FAILURE_REASON tables.

Salesforce Commerce Cloud

We have added a new table, SOURCE_CODE_GROUP.

Salesforce Marketing Cloud

We have made the following schema changes to address the data redistribution and data integrity issues caused due to the incorrect selection of the primary key:

Moved the alias, total_clicks, and unique_clicks columns from the LINK to the LINK_SEND table.
Changed the primary key from a combination of send_id and link_id columns to the id column, in the LINK_SEND table.

Statsig

We have added the following new tables:

AUDIT_LOG
AUDIT_LOG_CHANGE_RULE
AUDIT_LOG_CHANGE_RULE_CONDITION
EVENT_CONFIG_CHANGE
EXPERIMENT
EXPERIMENT_GROUP
EXPERIMENT_PRIMARY_METRIC
EXPERIMENT_PRIMARY_METRIC_TAG
EXPERIMENT_SECONDARY_METRIC
EXPERIMENT_SECONDARY_METRIC_TAG
EXPERIMENT_TAG
METRIC

We no longer sync the UNIT_METRICS_DAILY_REPORT table because Statsig does not support it.

Stripe

We have added two new columns, flat_amount_decimal and unit_amount_decimal, to the TIER table.

Survicate

We have added the following new tables:

EMPTY_AND_BUTTON_NEXT_RESPONSE
FORM_RESPONSE
MATRIX_RESPONSE
NPS_RESPONSE
QUESTION
QUESTION_ANSWER_CHOICE
RANKING_RESPONSE
RATING_AND_SMILEY_SCALE_RESPONSE
RESPONSE
RESPONDENT_ATTRIBUTE
SINGLE_MULTIPLE_AND_DROPDOWN_RESPONSE
TEXT_AND_DATE_RESPONSE

We have removed the following tables:

POINT
POINT_ANSWER
VISITOR
VISITOR_RESPONSE

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

created_at
enabled
launch_end_at
launch_start_at
launch_responses_limit
type

Teamwork

We have added the following new tables:

BOARD_COLUMN
CARD
CARD_ASSIGNED_PEOPLE
PROJECT_OWNER
PROJECT_BUDGET
PROJECT_BUDGET_NOTIFICATION
UTILIZATION

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

archived_by_user_id
board_data
category_color
category_name
company_color
company_is_owner
completed_by_user_id
completed_on
date_archived
defaults
notify_everyone
portfolio_board

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

color
tag_project_id

Twilio

We have added a new table, VERIFICATION_ATTEMPT.

Workday HCM

We have made the following schema changes for the connectors created before October 6, 2023:

We have added the following new tables:
- POSITION_ORGANIZATION
- POSITION_WORKER_TYPE_RESTRICTION
- COMMUNICATION_USAGE
- ORGANIZATION_POSITION_GROUP_POSITION
- ORGANIZATION_LEADER
- ORGANIZATION_POSITION_GROUP_POSITION
- ORGANIZATION_DOCUMENT_FIELD_RESULT
- SUPERVISORY_ORGANIZATION_LOCATION
We will stop syncing the following tables after October 13, 2023
- COMMUNICATION_USAGE_DATA
- ORG_DOCUMENT_FIELD_RESULT
- ORG_JOB_PROFILE_EXEMPT
- ORG_LEADER
- ORG_POSITION_GRP_POSITION_TYPE
- POSITION_COMPANY_ASSIGNMENT
- POSITION_COST_CENTER_ASSIGNMENT
- POSITION_CUSTOM_ORGANIZATION_ASSIGNMENT
- POSITION_JOB_PROFILE_EXEMPT
- POSITION_REGION_ASSIGNMENT
- POSITION_STATUS
- POSITION_WORKER_TYPE_REFERENCE
- SUPERVISORY_ORG_LOCATION
- WORKER_CONTINGENT_CONTRACT
Be sure to update your queries.
We have added the following new columns to the tables below:

TABLE	NEW COLUMNS
`POSITION_JOB_PROFILE`	`job_profile_id`
`JOB_REQUISITION_ADDITIONAL_LOCATION`	`location_id`
`POSITION_LOCATION`	`location_id`
`POSITION_DOCUMENT_FIELD_RESULT`	`integration_document_field` `index`
`POSITION_JOB_FAMILY`	`job_family_id`
`WORKER_LEAVE_STATUS`	`leave_request_event_id`
`WORKER_LEAVE_REQUEST_DETAIL`	`leave_request_event_id`
`WORKER`	`contract_pay_rate` `contract_assignment_details` `contract_end_date` `contract_currency_code` `contract_frequency_name` `contract_vendor_name`
`WORKER_POSITION`	`headcount_restriction_code` `management_level_code`
`WORKER_POSITION_PAYROLL_REPORTING_CODE`	`payroll_reporting_id`
`WORKER_POSITION_JOB_CLASSIFICATION`	`job_group_code`
`ORGANIZATION`	`supervisory_position_availability_date` `supervisory_position_earliest_hire_date` `supervisory_position_worker_type` `supervisory_position_time_type`
`ORGANIZATION_ROLE`	`role_id`
`POSITION_PERIOD_SALARY_PLAN`	`period_salary_plan_id` `period_salary_plan_code`
`POSITION_UNIT_SALARY_PLAN`	`unit_salary_plan_id` `unit_salary_plan_code`
`POSITION_MERIT_PLAN`	`merit_plan_id` `merit_plan_code`
`POSITION_COMMISSION_PLAN`	`commission_plan_id` `commission_plan_code`
`POSITION_PAY_PLAN`	`pay_plan_id` `pay_plan_code`
`POSITION_CALCULATED_PLAN`	`calculated_plan_id` `calculated_plan_code`
`POSITION_UNIT_ALLOWANCE_PLAN`	`unit_allowance_plan_id` `unit_allowance_plan_code`
`POSITION_ALLOWANCE_PLAN`	`allowance_plan_id` `allowance_plan_code`
`POSITION_STOCK_PLAN`	`stock_plan_id` `stock_plan_code`
`POSITION_BONUS_PLAN`	`bonus_plan_id` `bonus_plan_code`

We no longer sync the following columns in the tables below:

TABLE	COLUMNS
`JOB_REQUISITION_ADDITIONAL_LOCATION`	`id`
`ORGANIZATION`	`position_availability_date` `position_earliest_hire_date` `position_worker_type` `position_time_type` `code`
`ORGANIZATION_ROLE`	`id`
`POSITION_ALLOWANCE_PLAN`	`id`
`POSITION_BONUS_PLAN`	`id`
`POSITION_CALCULATED_PLAN`	`id`
`POSITION_COMMISSION_PLAN`	`id`
`POSITION_DOCUMENT_FIELD_RESULT`	`id` `field_name`
`POSITION_JOB_FAMILY`	`id` `job_family_code`
`POSITION_JOB_PROFILE`	`id`
`POSITION_LOCATION`	`id`
`POSITION_MERIT_PLAN`	`id`
`POSITION_PAY_PLAN`	`id`
`POSITION_PERIOD_SALARY_PLAN`	`id`
`POSITION_STOCK_PLAN`	`id`
`POSITION_UNIT_ALLOWANCE_PLAN`	`id`
`POSITION_UNIT_SALARY_PLAN`	`id`
`WORKER_LEAVE_REQUEST_DETAIL`	`id`
`WORKER_LEAVE_STATUS`	`id`
`WORKER_POSITION`	`headcount_restriction_id` `job_category_id` `job_family_id` `job_profile_name` `management_level_id` `position_code` `position_title` `position_time_type`
`WORKER_POSITION_JOB_CLASSIFICATION`	`job_group_id`
`WORKER_POSITION_PAYROLL_REPORTING_CODE`	`id` `code`

Be sure to update your queries.

We have added the following new tables to support the Workday Recruiting module:

CANDIDATE
CANDIDATE_CERTIFICATION
CANDIDATE_EDUCATION
CANDIDATE_EXPERIENCE
CANDIDATE_GOVERNMENT_ID
CANDIDATE_LANGUAGE
CANDIDATE_NAME
CANDIDATE_NATIONAL_ID
CANDIDATE_POOL_MEMBERSHIP
CANDIDATE_SKILL
CANDIDATE_SOCIAL_MEDIA_ACCOUNT
CANDIDATE_TAG
CANDIDATE_WEBSITE
EXTERNAL_REFERENCE_LINE
EXTERNAL_REFERENCE_PARTICIPANT
INTERVIEW
INTERVIEW_COMPETENCY
FEEDBACK_COMPETENCY_ASSESSMENT
INTERVIEW_FEEDBACK
INTERVIEW_FEEDBACK_DETAIL
INTERVIEW_SESSION
INTERVIEW_SESSION_DETAIL
INTERVIEW_QUESTIONNAIRE
INTERVIEWER
JOB_APPLICATION
JOB_APPLIED_TO
MULTIPLE_CHOICE_ANSWER
PRE_HIRE
PRE_HIRE_REFERRED_BY_WORKER
PRE_HIRE_POSITIONS_CONSIDERED
PRE_HIRE_BACKGROUND_CHECK_STATUS
PRE_HIRE_RESUME
PRE_HIRE_EDUCATION
PRE_HIRE_JOB_HISTORY
PRE_HIRE_TRAINING_ACHIEVEMENT
PRE_HIRE_INTERNAL_PROJECT_EXPERIENCE
PRE_HIRE_COMPETENCY_ACHIEVEMENT
PRE_HIRE_CERTIFICATION_ACHIEVEMENT
PRE_HIRE_LANGUAGE_ACHIEVEMENT
PRE_HIRE_LANGUAGE_ABILITY
PRE_HIRE_WORK_EXPERIENCE
PRE_HIRE_PROFESSIONAL_AFFILIATION
PRE_HIRE_AWARD_AND_ACTIVITY
QUESTIONNAIRE
QUESTIONNAIRE_ANSWER
QUESTIONNAIRE_SETUP
SCORE_FOR_MULTIPLE_CHOICE

To sync these tables, enable the security domains necessary for the Recruiting module.

We have added two new columns, compensation_grade_id and compensation_grade_profile_id, to the WORKER table. Be sure to re-sync the WORKER table to backfill the data for these columns or contact Fivetran Support to re-sync it for you.

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

Wrike

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

attachment_count
custom_item_type_id
owner_id

Zendesk Support

We have added following new tables:

AUTOMATION
AUTOMATION_ACTION
AUTOMATION_CONDITION
CONTENT_TAG
GROUP_SLA_POLICY_HISTORY
GROUP_SLA_POLICY_METRIC_HISTORY
MACRO
MACRO_ACTION
SUSPENDED_TICKET
SUSPENDED_TICKET_ATTACHMENT
TICKET_GROUP_SLA_POLICY
TICKET_SIDE_CONVERSATION
TICKET_SIDE_CONVERSATION_EVENT
TICKET_SIDE_CONVERSATION_RECIPIENT
TRIGGER
TRIGGER_ACTION
TRIGGER_CONDITION

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

Improvements

ActiveCampaign

We have implemented incremental sync for the CONTACT and DEAL tables.

Ada

We now support syncing custom fields in the CONVERSATION table. We have added the prefixes, metavariable_ and variable_, in the CONVERSATION table to sync the custom fields.

This change is applicable to all new and existing connectors. To apply these changes to your existing connector, make sure you re-sync your connector or contact Fivetran Support to re-sync it for you.

Amazon DynamoDB

We have improved the performance of our Amazon DynamoDB connector during incremental syncs and re-syncs. We have observed that the connector now extracts your data 5 times faster improving the sync speed by 2 times.

Amazon Selling Partner

We now support the Reports API. To sync data from these reports, go to the Schema tab of your Fivetran dashboard and select your report tables. If you are unable to select the report tables, re-authorize the connector. To learn more, see our Reports document.

Apache Kafka destination

Our Apache Kafka destination is now generally available. Read our Apache Kafka destination documentation. The following Kafka implementations are now generally available:

AWS Lambda

You can now add custom payloads as key-value pairs when you configure the Lambda connector. For more information, see our AWS Lambda setup guide.

AWS MSK

Our AWS MSK connector is now generally available. Read our AWS MSK connector documentation.

Azure Data Lake Storage

You can now connect Fivetran to your ADLS container using Azure PrivateLink connection. This feature is supported only in Business Critical plans. For more information, see our setup instructions.

Azure SQL Database

For the Azure SQL Database connector, you can now use Microsoft Entra ID (formerly Azure Active Directory) to authenticate and allow Fivetran to access your Azure SQL database. Learn more in our Azure SQL Database documentation.

Azure SQL Managed Instance

For the Azure SQL Managed Instance connector, you can now use Microsoft Entra ID (formerly Azure Active Directory) to authenticate and allow Fivetran to access your Azure SQL managed instance. Learn more in our Azure SQL Managed Instance documentation.

Confluent Cloud

We no longer support the PLAINTEXT security protocol. We support only SASL. In the destination setup form, we have removed the Security Protocol drop-down menu. In the REST API configuration, we no longer support the PLAINTEXT value for the security_protocol parameter.

Coupa

We have fixed a bug where we were facing delays in updating the records of the ORDER_HEADER table. We have updated our sync strategy and implemented a new weekly lookback window of 7 days to avoid data discrepancy issues of the ORDER_HEADER table.

Databricks

We no longer enforce the column names to be in lower case. We now ignore the case of the column names in your destination tables. Your queries and scripts will continue to execute because Databricks is case-insensitive.

NOTE: If you have previously synced a column name with upper case letters to your destination table and if a column data type changes in the table, we will rename all the columns in the table to lower case.

Facebook Ads

We have transferred pre-built reports from the connector setup form to the Schema tab of your Fivetran dashboard. Pre-built reports are now included by default and are treated as metadata tables, which means the only configurable option for them is select or deselect. This change is applicable to all new connectors created after October 13, 2023. You can now use the Connector Management API to modify pre-built reports in the same way as metadata tables. To do so, submit API requests to the Modify a Connector Schema Config endpoint.

Gong

We have changed the connector type of our Gong connector from Lite to Standard. New connectors created on or after November 2, 2023, use a new schema. As part of this upgrade, we have made the following schema changes:

We have added the following new tables:
- ACCOUNT_ENTITY_SCHEMA
- CONTACT_ENTITY_SCHEMA
- DEAL_ENTITY_SCHEMA
- ENGAGE_FLOW
- ENTITY_VALUE
- LANGUAGE_KEYWORDS
- LEAD_ENTITY_SCHEMA
- PERMISSION_CALL_ACCESS
- PERMISSION_COACHING_ACCESS
- PERMISSION_DEAL_ACCESS
- PERMISSION_EMAIL_ACCESS
- PERMISSION_FORECAST_ACCESS
- PERMISSION_FORECAST_EDIT_SUBMISSION_ACCESS
- PERMISSION_FORECAST_EDIT_TARGET_ACCESS
- PERMISSION_INSIGHT_ACCESS
- PERMISSION_LIBRARY_FOLDER_ACCESS
- PERMISSION_PROFILE
- TRACKER
- TRACKER_LANGUAGE
- TRACKER_SAID_IN_CALL_PARTS
- TRACKER_SAID_IN_TOPIC
We have renamed the following tables:
- CALL_PARTIE table to CALL_PARTICIPANT
- SCORECARD_ACTIVITY table to ANSWERED_SCORECARD
- SCORECARD_ACTIVITY_ANSWER table to ANSWERED_SCORECARD_ANSWER
We have grouped the following tables into the tables below:
- CALL_CONTEXT_OBJECT and CALL_CONTEXT_OBJECT_FIELD tables into the CALL_CONTEXT_INTEGRATION table
- CALL_PARTIE_OBJECT and CALL_PARTIE_OBJECT_FIELD tables into the CALL_PARTICIPANT_INTEGRATION table
- CALL_TRACKER, CALL_TRACKER_OCCURRENCE, CALL_TRACKER_PHRASE, and CALL_TRACKER_PHRASE_OCCURENCEtables into the CALL_TRACKER table
We have split the CALL_INSIGHT table into the CALL_VIDEO, CALL_TOPIC, and CALL_STRUCTURE tables.
We have added a new column, calendar_event_id, to the CALL table.
NOTE: This schema change applies to both existing and new connectors.

Google Analytics 4

You can now set a rollback window between 2 and 30 days for each report in your connector setup form. Learn more in our rollback sync documentation.

Google Drive

Our Google Drive connector can now sync spreadsheets in Merge Mode. For more information, see our setup instructions. This feature is in beta and available to all connectors. We will gradually roll out this feature to all existing connectors.

Intercom

We now re-import the ARTICLE_HISTORY table in every sync due to limitations in the Intercom API. We perform a re-import to ensure data integrity.

Kantata

We now re-import the USER and WORKSPACE_ALLOCATION tables once a week to ensure data integrity.

Marketo

We now support syncing custom fields in the PROGRAM_MEMBERSHIP table. On your Connector Details page, go to the Schema tab and select or deselect the custom fields you want to sync.

MongoDB

MongoDB connectors created on or after October 18, 2023, support two pack modes, Packed mode and Unpacked mode, at the connector level. We have now updated the default option of the Pack mode feature to Packed mode. When you select a pack mode on the Connector Details page, the selected behavior applies to all the tables enabled for the sync.

For MongoDB connectors created before October 18, 2023, we continue to support both the pack modes at the table level.

To learn more, see our MongoDB pack mode documentation.

Optimizely

We now support Pack Mode for all Optimizely connectors, so you can choose the form in which Fivetran delivers your data.

We have updated Packed as the default option for all new connectors. Whereas for all the existing connectors, we have retained Unpacked as the default selection to ensure continued service.

We are gradually rolling out this feature to all existing connectors. For more information, see our Pack mode documentation.

Pendo

Fivetran now supports extracting data from Pendo using Data Sync.

Recharge

The Recharge connector now supports priority-first sync for the DISCOUNT table. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Recharge's priority-first syncs fetch the most recent 15 days' worth of data from the supported tables. We are gradually rolling out this change to all existing connectors. To learn more, see our priority-first sync documentation.

Salesforce

We have added translation support for the following Global Variables:

Api
CustomMetadata
Organization
System.OriginDateTime

We now translate the formula fields containing these global variables. For more information about formula translations, see our documentation.

Slack

We have changed the connector type of our Slack connector from Lite to Standard. New connectors created on or after November 1, 2023, use a new schema. As part of this upgrade, we have made the following improvements and schema changes:

We have updated our sync strategy for the conversations.history and conversations.replies endpoints. We now sync all the conversations from both endpoints into the MESSAGE table and its child tables:
- MESSAGE_BLOCK
- MESSAGE_BLOCK_ELEMENT
- MESSAGE_REACTION
- MESSAGE_REACTION_USER
- MESSAGE_REPLY_USER
- MESSAGE_FILE
- MESSAGE_ATTACHMENT
Previously, we synced the data into the MESSAGE and MESSAGE_REPLY tables and their child tables.
We have added the following new tables:
- CHAT_PERMALINK
- PIN
- REMOTE_FILE
- REMOTE_FILE_CHANNEL
- TEAM_BILLING
- TEAM_PREFERENCE
We have renamed the following tables:
- USERGROUP table to USER_GROUP
- USERGROUP_PREFS_CHANNEL table to USER_GROUP_PREFS_CHANNEL
- USERGROUP_PREFS_GROUP table to USER_GROUP_PREFS_GROUP
- USERGROUP_USER table to USER_GROUP_USER
We have added three new columns to the USERS table:
- locale
- profile_api_app_id
- profile_bot_id
NOTE: This schema change applies to both existing and new connectors.

Snapchat Ads

We now support custom reports that allow you to select the following parameters and fields:

See our Custom Reports and Limitations documentation page for details.

Statsig

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

We have changed the authentication method for Statsig connector. We now use console secret key instead of the server-side secret key to authenticate the Statsig connector. Be sure to use the console secret key and re-authenticate your Statsig connector to ensure continued service. For more information, see Statsig's documentation.

Stripe

The Stripe connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Stripe's priority-first syncs fetch the most recent 30 days' worth of data from the supported tables.

We have rolled out this feature for all active connectors. If a connector is currently paused and if you unpause it within 2 months, the connector will start supporting priority-first sync as soon as you unpause it. However, if you unpause the connector after 2 months from now, we will consider it as a new connector and perform a historical sync on a priority-first basis. To learn more, see our priority-first sync documentation.

REST API Improvements

Kustomer

You can now configure the API usage limit of the Kustomer connector using our REST API. Previously, the default API usage limit was 90%. For more information, see our Kustomer API Configuration documentation.