April 2026
Connector SDK
fivetran-connector-sdk PyPI package
We have released version 2.8.1 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- We now support
pyproject.tomlas an alternative torequirements.txtfor defining dependencies in your connector project. Please refer to Managing Project Dependencies for more details. - Improved overall performance and stability.
.ftignorehas been replaced by.gitignore. You can now create a.gitignorefile in the root of your connector project to specify files and directories that should be excluded duringfivetran deployandfivetran package. If you have an existing.ftignorefile, rename it to.gitignorebecause the package no longer reads.ftignore.- We now allow and support all file types to be uploaded during deployment.
- Improved user experience for memory utilisation in testers and enhanced logging.
- Improved testers with bug fixes for transactional checkpointing.
- Minor enhancements and improvements.
We have released version 2.8.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- Improved overall performance and stability.
- Better user experience with enhanced logging.
- Updated testers that now support Transactional Checkpoint.
- Minor enhancements and improvements.
Fivetran GCP Middle East Servers
We have added new servers in the GCP Middle East (Dammam) region.
If you're on a Business Critical plan, you can now select this region in your destination setup form. Connectors configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in the Middle East, your data does not leave the Middle East during processing.
For more information, see our data residency documentation.
Lite Connectors
Lite connectors are now available for the following sources:
Logs
AWS CloudWatch
We have deprecated the Access Key authentication method for CloudWatch. Use the IAM Role authentication method instead.
New audit trail log events
We've added the following new audit trail log events:
Account-level events (Enterprise plan or higher):
edit_account— Account data change: Logged when an account's display name is changed. Only changed fields are included inoldValuesandnewValues.edit_account— User keys enabled or disabled: Logged when user API keys are enabled or disabled for an account.edit_account— CMK enabled, disabled, or deleted: Logged when a customer-managed key (CMK) is enabled, disabled, or deleted. Key content and credentials are not logged.
Destination-level events (Enterprise plan or higher):
delete_destination: Thedelete_destinationevent now includesoldValueswith the destination's name and service type. Theservicefield is present only when deleting viaDELETE /v1/destinations/{destinationId}.
Connection-level events (Enterprise plan or higher):
delete_private_link: Logged when a private link is deleted via the dashboard or API. Includes the private link name inoldValues.delete_proxy_agent: Logged when a proxy agent is deleted via the dashboard or API. Includes the agent name inoldValues.delete_connection: When a destination is deleted, Fivetran emits onedelete_connectionlog event per connection as part of the cascade-deleted operation. These events haveinteractionMethod: "SYSTEM".
Partner SDK
MotherDuck
The MotherDuck destination is now generally available.
Read our MotherDuck destination documentation.
Quickstart Transformations
Multi-source Quickstart packages during connection setup
When you set up a connection for a connector that supports multi-source Quickstart packages, such as Ad Reporting, Fivetran now prompts you to configure a Quickstart transformation automatically after the connection tests pass. You can choose to join an existing multi-source transformation or create a new one — in both cases, only multi-source transformations are available for these connector types. For more information, see the Quickstart management page.
Schema fetch optimisation
Fixed-schema connectors
We've implemented a new mechanism to fetch source schema quicker when creating a new connection. Now, instead of deriving the schema from source data, we use fixed schema models. This allows you to see the schema blocking and hashing screen almost immediately after creating a new connection.
As a result of this improvement, you may see empty tables and columns in the Schema tab of existing connections that have not yet synced to your destination.
Transformations for dbt Core
dbt Core version adoption
We have added support of dbt Core* version 1.11.8 for the following destinations:
Although other destinations support different dbt Core versions, they don't support dbt Core 1.11.8 due to lack of available dbt adapters for this version.
We now support the following destinations for dbt Core* version 1.10.20:
See previous dbt Core version adoption entries in the Transformations for dbt Core Release Notes to check which destinations already support this version.
We now support the following destinations for dbt Core* version 1.11.5:
See previous dbt Core version adoption entries in the Transformations for dbt Core Release Notes to check which destinations already support this version.
We now support the following destinations for dbt Core* version 1.11.7:
See previous dbt Core version adoption entries in the Transformations for dbt Core Release Notes to check which destinations already support this version.
* 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:
- Connectors supporting the Ad Reporting data model to version 2.5.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 19, 2026.
- Fivetran Platform to version 2.5.2. We are gradually rolling out this change. All Quickstart transformations will be updated by May 12, 2026.
- Google Ads to version 1.3.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 11, 2026.
- Iterable to version 1.4.1. We are gradually rolling out this change. All Quickstart transformations will be updated by May 18, 2026.
- Microsoft Dynamics 365 CRM to version 0.2.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 17, 2026.
- Pinterest Ads to version 1.2.1. We are gradually rolling out this change. All Quickstart transformations will be updated by May 18, 2026.
- QuickBooks to version 1.5.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 17, 2026.
- SAP ERP on HANA to version 0.7.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 11, 2026.
- Shopify to version 1.7.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 18, 2026.
- Stripe to version 1.7.0. We are gradually rolling out this change. All Quickstart transformations will be updated by May 24, 2026.
Schema changes
Amazon Selling Partner
We have discontinued support for the SMALL_AND_LIGHT_ENROLLMENT table. The FBA Small and Light API has been unsupported since September 2023.
We have added the following new tables:
FULFILLMENT_REMOVAL_ORDER_DETAIL_REPORTNET_PURE_PRODUCT_MARGIN_REPORT_WEEKLYREPEAT_PURCHASE_REPORT_WEEKLYSEARCH_TERMS_REPORT_WEEKLYSETTLEMENT_REPORTSTORAGE_FEE_CHARGES_REPORTVENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_WEEKLYVENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_WEEKLYVENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_WEEKLYVENDOR_INVENTORY_SOURCING_RETAIL_REPORT_WEEKLYVENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_WEEKLYVENDOR_SALES_MANUFACTURING_RETAIL_REPORT_WEEKLYVENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_WEEKLYVENDOR_SALES_SOURCING_RETAIL_REPORT_WEEKLYVENDOR_TRAFFIC_REPORT_WEEKLY
AppsFlyer
We've added a new table, PARTNERS_DAILY. The table contains aggregate performance metrics grouped by date, media source, and campaign, synced via the Pull API. It supports both user acquisition and retargeting data.
Asana
We've added a new table, TASK_DEPENDENCY. The table contains task dependency relationships, linking tasks to the tasks they depend on.
We have added support for reference-type custom fields in the TASK, PROJECT, and PORTFOLIO tables. Values from these fields now appear as dynamic custom_* columns containing the GID(s) of the referenced objects.
BambooHR
We've added a new table, JOB_SUMMARY. The table contains job opening summaries, including title, location, department, status, hiring lead, and applicant counts for each open position.
Braze
We have added the following three new columns to the MESSAGE_VARIATION table:
actionimage_urllarge_image_url
We've added the is_sms_fallback column to the SMS_EVENT table.
We have added the following new columns to the WHATSAPP_EVENT table:
catalog_idflow_idin_reply_tomessage_idproduct_idtemplate_name
We have added a new table, WHATSAPP_FLOW_RESPONSE, to store WHATSAPP_EVENT flow response data.
Campfire
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
BALANCE_SHEET | |||||
| column | Primary Key Change | start_date 🔑 | Added to primary key. | ||
CASH_FLOW | |||||
| column | Primary Key Change | start_date 🔑 | Added to primary key. | ||
INCOME_STATEMENT | |||||
| column | Primary Key Change | start_date 🔑 | Added to primary key. | ||
TRAIL_BALANCE | |||||
| column | Primary Key Change | start_date 🔑 | Added to primary key. | ||
Cin7 Core
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
PRODUCT_AVAILABILITY | |||||
| column | Primary Key Change | product_id 🔑 | product_id | No longer primary key | |
| column | Primary Key Change | _fivetran_id 🔑 | New primary key | ||
Coupa
We have added the following new columns to the ORDER_LINE table:
manufacturer_namemanufacturer_part_number
To backfill the historical data for these columns, re-sync the ORDER table.
Criteo Retail Media
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REPORT_CAMPAIGN | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | Discontinued Column | hour | |||
REPORT_LINE_ITEM | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | Discontinued Column | hour | |||
Eloqua
We have added a new column, email_clickthrough_saved_id, to the CONTACT_ACTIVITY table.
Facebook Pages
We've added three new columns:
permalink_urlto thePOST_HISTORYtablepage_total_media_view_uniqueto theUNIQUE_DAILY_PAGE_METRICS_TOTALtablepost_total_media_view_uniqueto theUNIQUE_LIFETIME_POST_METRICS_TOTALtable
Factbird
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ANDON_CALL | |||||
| table | New Table | ANDON_CALL | |||
ANDON_CALL_TAG | |||||
| table | New Table | ANDON_CALL_TAG | |||
Fortnox
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
VOUCHER_ROW | |||||
| column | Primary Key Change | account_number 🔑 | account_number | No longer a primary key. | |
| column | Primary Key Change | index 🔑 | New primary key. | ||
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ACCOUNT | |||||
| column | Discontinued Column | cost_center | |||
| column | Discontinued Column | project | |||
VOUCHER_ROW | |||||
| column | New Column | cost_center | |||
| column | New Column | project | |||
GitHub
We have removed the following deprecated tables that have been replaced by COPILOT_ORG_METRIC and COPILOT_USER_METRIC and their sub-tables:
COPILOT_METRICCOPILOT_METRIC_TEAMDOTCOM_CHAT_MODELDOTCOM_CHAT_MODEL_TEAMDOTCOM_PULL_REQUEST_REPOSITORYDOTCOM_PULL_REQUEST_REPOSITORY_MODELDOTCOM_PULL_REQUEST_REPOSITORY_TEAMDOTCOM_PULL_REQUEST_REPOSITORY_MODEL_TEAMIDE_CHAT_EDITORIDE_CHAT_EDITOR_MODELIDE_CHAT_EDITOR_TEAMIDE_CHAT_EDITOR_MODEL_TEAMIDE_CODE_COMPLETION_EDITORIDE_CODE_COMPLETION_EDITOR_MODELIDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGEIDE_CODE_COMPLETION_EDITOR_TEAMIDE_CODE_COMPLETION_EDITOR_MODEL_TEAMIDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE_TEAMIDE_CODE_COMPLETIONS_TOTAL_LANGUAGEIDE_CODE_COMPLETIONS_TOTAL_LANGUAGE_TEAM
HubSpot
We have added a new table, LEAD_DEAL, to store data for the associations between leads and deals.
We have added the following new tables for each custom object we sync:
<CUSTOM_OBJECT_NAME>_PIPELINEto store pipeline definitions for the custom object type<CUSTOM_OBJECT_NAME>_PIPELINE_STAGEto store stage definitions for the custom object pipelines
We have added the following new tables to store Listings object data:
LISTINGLISTING_COMPANYLISTING_CONTACTLISTING_DEALLISTING_ENGAGEMENTLISTING_PIPELINELISTING_PIPELINE_STAGELISTING_PROPERTY_HISTORYLISTING_TICKET
We have added the following new tables to store Orders object data:
ORDERORDER_COMPANYORDER_CONTACTORDER_DEALORDER_ENGAGEMENTORDER_FEEDBACK_SUBMISSIONORDER_INVOICEORDER_LINE_ITEMORDER_PAYMENTORDER_PIPELINEORDER_PIPELINE_STAGEORDER_PROPERTY_HISTORYORDER_QUOTEORDER_TICKET
We have added the following new tables to store Projects object data:
PROJECTPROJECT_COMPANYPROJECT_CONTACTPROJECT_DEALPROJECT_ENGAGEMENTPROJECT_LISTINGPROJECT_PIPELINEPROJECT_PIPELINE_STAGEPROJECT_PROPERTY_HISTORYPROJECT_SERVICEPROJECT_TICKET
We are gradually rolling out these changes to all existing connections.
Impact Brand
We have added a new column, expiration_date, to the PARTNER_PROGRAM table.
Instagram Business
We have added the following new columns to the MEDIA_INSIGHTS table:
video_photo_repostscarousel_album_repostsreel_repostsreel_crossposted_viewsreel_facebook_viewsreels_skip_rate
We have added the following new column to the USER_INSIGHTS table:
reposts
Intercom
We have added a new table, CONVERSATION_SOURCE_ATTACHMENT_HISTORY.
We have added a new column, statistics_adjusted_handling_time, to the CONVERSATION_HISTORY table.
Jira
We have added a new column, _fivetran_file_path, to the ATTACHMENT table to store the file path used for unstructured file replication and is constructed from the attachment ID and filename.
Kantata
We have added a new column, status, to the STORY table.
We have added custom field columns to the WORKSPACE_RESOURCE table.
Klaviyo
We have added a new table, PUSH_TOKEN.
We have added the following new mobile push subscription columns to the PERSON table:
SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_CONSENTSUBSCRIPTIONS_MOBILE_PUSH_MARKETING_TIMESTAMPSUBSCRIPTIONS_MOBILE_PUSH_MARKETING_METHODSUBSCRIPTIONS_MOBILE_PUSH_MARKETING_METHOD_DETAILSUBSCRIPTIONS_MOBILE_PUSH_MARKETING_CAN_RECEIVE_PUSH_MARKETING
Kustomer
We have added two new columns, response_business_time and response_time, to the MESSAGE table.
LinkedIn Ad Analytics
We have added two new columns, conversion_method and value_type, to the CONVERSION_HISTORY table.
We have added two new columns, leadgen_call_to_action_destination and leadgen_call_to_action_label, to the CREATIVE_HISTORY table.
We have added the following new columns to the CAMPAIGN_GROUP_HISTORY table:
objective_typetestdaily_budgettotal_budget_amounttotal_budget_currency_codebudget_optimization_bid_strategybudget_optimization_budget_optimization_strategy
Mailchimp
We've added a new table, CAMPAIGN_REPORT.
We've added a new table, CAMPAIGN_CLICK_REPORT.
We have added the following new columns to the AUTOMATION_EMAIL and CAMPAIGN tables:
clickssubscriber_clicksclick_rateopensunique_opensopen_rateThese columns contain report summary statistics sourced from thereport_summaryobject in the Mailchimp API response.
Microsoft Advertising
We have added a new column, final_url_suffix, to the following tables:
AD_GROUP_HISTORYAD_HISTORYCAMPAIGN_HISTORY
We've added a new table, CONVERSION_GOAL_HISTORY. The table contains historical records of conversion goals defined in Microsoft Advertising. We are gradually rolling out these changes to all existing connections.
You can populate the new table with data for free until April 13, 2026. Exclude the table from your connection schema before that date if you don't want it to count toward paid MAR.
We've added the SEARCH_CAMPAIGN_CHANGE_HISTORY_REPORT reporting table. We are gradually rolling out this change to all existing connections.
You can populate the new table with data for free until May 5, 2026. Exclude the table from your connection's schema before that date if you don't want the table's usage to count toward paid MAR.
See Microsoft documentation for more details.
Mixpanel
We have added a new column, event_time_ms, to the EVENT table.
Moloco
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CAMPAIGN_LAUNCH_NOTICE | |||||
| table | New Table | CAMPAIGN_LAUNCH_NOTICE | |||
CAMPAIGN_LAUNCH_NOTICE_CONFIRMATION | |||||
| table | New Table | CAMPAIGN_LAUNCH_NOTICE_CONFIRMATION | |||
PRODUCT_CATEGORY | |||||
| table | New Table | PRODUCT_CATEGORY | |||
OneTrust
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ASSESSMENT | |||||
| column | Type Change | create_date | create_date | Data type changed from ISO-LOCAL-DATE-TIME to Instant. | |
| column | Type Change | last_updated_date | last_updated_date | Data type changed from ISO-LOCAL-DATE-TIME to Instant. | |
LOGIN_HISTORY | |||||
| column | Type Change | login_datetime | login_datetime | Data type changed from ISO-LOCAL-DATE-TIME to ISO-INSTANT. | |
USER_GROUP | |||||
| column | Type Change | created_date | created_date | Data type changed from ISO-LOCAL-DATE-TIME to ISO-INSTANT. | |
| column | Type Change | last_modified_date | last_modified_date | Data type changed from ISO-LOCAL-DATE-TIME to ISO-INSTANT. | |
Oracle Fusion Field Service
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
RESOURCE_DESCENDANT | |||||
| column | Primary Key Change | resource_id 🔑 | resource_id | No longer primary key | |
| column | Primary Key Change | resource_internal_id | resource_internal_id 🔑 | Added to primary key | |
RESOURCE_DESCENDANT_INVENTORY | |||||
| column | Discontinued Column | resource_descendant_resource_id 🔑 | No longer primary key | ||
| column | Primary Key Change | resource_descendant_internal_id 🔑 | New primary key | ||
RESOURCE_DESCENDANT_WORK_SCHEDULE | |||||
| column | Discontinued Column | resource_descendant_resource_id 🔑 | No longer primary key | ||
| column | Primary Key Change | resource_descendant_internal_id 🔑 | New primary key | ||
RESOURCE_DESCENDANT_WORK_SKILL | |||||
| column | Discontinued Column | resource_descendant_resource_id 🔑 | No longer primary key | ||
| column | Primary Key Change | resource_descendant_internal_id 🔑 | New primary key | ||
RESOURCE_DESCENDANT_WORK_ZONE | |||||
| column | Discontinued Column | resource_descendant_resource_id 🔑 | No longer primary key | ||
| column | Primary Key Change | resource_descendant_internal_id 🔑 | New primary key | ||
Outbrain
We've added the following new columns to the PROMOTED_LINK_HISTORY table:
creative_formatdescriptiontitle
We've added the cpm, roas, and total_roas columns to the following tables:
CAMPAIGN_REPORTPROMOTED_LINK_REPORTGEOLOCATION_REPORTSECTION_REPORTPUBLISHER_REPORT
We've added a new table, CROP_POINT. The table contains crop point data associated with image metadata entries.
Paylocity
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EMPLOYEE | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_DEDUCTION | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_DEDUCTION_COST_CENTER | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_EARNING | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_EARNING_COST_CENTER | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_FUTURE_PAY_RATE | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_POSITION_FAMILY | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_PUNCH_DETAIL | |||||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
EMPLOYEE_PUNCH_DETAILS_SEGMENT | |||||
| column | Primary Key Change | date 🔑 | date | No longer a primary key. | |
| column | Primary Key Change | punch_type 🔑 | punch_type | No longer a primary key. | |
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
| column | Primary Key Change | employee_punch_relative_end 🔑 | Added to primary key. | ||
| column | Primary Key Change | employee_punch_relative_start 🔑 | Added to primary key. | ||
| column | Primary Key Change | index 🔑 | Added to primary key. | ||
EMPLOYEE_PUNCH_DETAILS_SEGMENTS_COSTCENTER | |||||
| column | Primary Key Change | id 🔑 | id | No longer a primary key. | |
| column | Discontinued Column | punch_date 🔑 | No longer a primary key. | ||
| column | Discontinued Column | punch_type 🔑 | No longer a primary key. | ||
| column | Primary Key Change | company_id 🔑 | Added to primary key. | ||
| column | Primary Key Change | employee_punch_relative_end 🔑 | Added to primary key. | ||
| column | Primary Key Change | employee_punch_relative_start 🔑 | Added to primary key. | ||
| column | Primary Key Change | employee_punch_segment_index 🔑 | Added to primary key. | ||
| column | Primary Key Change | index 🔑 | Added to primary key. | ||
Pendo
We have added the following new tables:
SEGMENT_HISTORYSEGMENT_FILTERSEGMENT_PIPELINESEGMENT_DEPENDENT_METADATA
We are gradually rolling out this change to all existing connections.
Procore
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
BUDGET_VIEW_SNAPSHOT_DETAIL_ROW | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | Primary Key Change | budget_view_snapshot_id 🔑 | budget_view_snapshot_id | No longer a primary key. | |
| column | Primary Key Change | company_id 🔑 | company_id | No longer a primary key. | |
| column | Primary Key Change | project_id 🔑 | project_id | No longer a primary key. | |
QuickBooks
We have added a new column, exchange_rate, to the DEPOSIT table.
We've added a new table, CUSTOMER_TYPE. We are gradually rolling out this change to all existing connections.
We've added a new table, RECURRING_TRANSACTION. We are gradually rolling out this change to all existing connections.
Rakuten Advertising
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REPORT | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | New Column | consumer_country | |||
| column | New Column | transaction_id | |||
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REPORT | |||||
| column | New Column | consumer_city | |||
| column | New Column | consumer_region | |||
Ramp
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
BILL | |||||
| column | New Column | draft_bill_created_at | |||
| column | New Column | status_summary | |||
REIMBURSEMENT | |||||
| column | New Column | accounting_date | |||
| column | New Column | sync_status | |||
TRANSACTION | |||||
| column | New Column | accounting_date | |||
| column | New Column | sync_status | |||
Reddit Ads
We've added the following new columns to all non-conversion report tables:
app_install_mmp_install_countapp_install_mmp_total_install_countapp_install_skan_install_countapp_install_skan_total_install_count
These columns are a substitute for app_install_install_count, which will be deprecated in May 2026.
Revel Systems
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ESTABLISHMENT | |||||
| table | New Table | ESTABLISHMENT | |||
POS_STATION | |||||
| table | New Table | POS_STATION | |||
Sailthru
We have added the following new columns to the ES_CAMPAIGN table:
abtest_idabtest_percentabtest_segmentlabel_ids
Salesforce
We now sync event log objects from Salesforce. You will see these objects on your connection's schema page if you have a Salesforce Shield or Salesforce Event Monitoring add-on subscription and the necessary permissions to access them.
We have added the following tables to sync the corresponding Event Log objects:
AnalyticsChangeEventLogAnalyticsDownloadEventLogAnalyticsInteractEventLogAnalyticsPerfEventLogApexCalloutEventLogApexExecutionEventLogApexExtlCalloutEventLogApexRestApiEventLogApexSoapApiEventLogApexTriggerEventLogApexUnexpectedExcpEventLogApiTotalUsageEventLogAsyncReportRunEventLogAttachmentEventLogAuraRequestEventLogBlockedRedirectEventLogBulkApiEventLogBulkApi2EventLogBulkApiRequestEventLogChangeSetOperationEventLogConcurApexLimitEventLogContentDistributionEventLogContentDocLinkEventLogContentTransferEventLogContCalloutSummaryEventLogCspViolationEventLogDatabaseSaveEventLogDocAtchDownloadEventLogFlowNavMetricEventLogGroupMembershipEventLogInsufficientAccessEventLogInvocableActionEventLogKnowledgeArticleEventLogLightningErrorEventLogLightningLoggerEventLogLightningPageViewEventLogLightningPrfmEventLogLoginAsEventLogLoginEventLogLogoutEventLogMetadataApiOpEventLogNamedCredentialEventLogPackageInstallEventLogPermissionUpdateEventLogQueuedExecutionEventLogReportEventLogReportExportEventLogRestApiEventLogSalesforceLoginAsEventLogSandboxStatusEventLogSiteEventLogSearchEventLogSearchClickEventLogSoapApiEventLogTransactionSecurityEventLogUniqueQueryEventLogUriEventLogUiAgentInteractionEventLogUiTelemetryNavTmEventLogUiTelemetryRsrcTmEventLogVisualforceRequestEventLog
Since these tables do not have a primary key, we have added a synthetic primary key column named _fivetran_id to each of these tables. This column is a hash of all the other columns in the table and is used to ensure that each record is unique. Due to source limitations, we can only fetch data up to the last 1 year.
Since Salesforce recommends a 6-hour delay in data availability, we run a daily sync with a 30-hour lookback window to ensure data consistency.
Segment
We have added the following new columns to the IDENTIFIES table:
channelcompany_employee_countcompany_idcompany_industrycompany_namecompany_plancontext_device_advertising_idcontext_device_ad_tracking_enabledcontext_device_tokenidoriginal_timestampplan
We have added the following new columns to the GROUPS, PAGES, SCREENS, and TRACKS tables:
channelcontext_device_advertising_idcontext_device_ad_tracking_enabledcontext_device_tokenoriginal_timestamp
We have added a new column, plan, to the GROUPS table.
We have added the following new columns to the SCREENS table:
pathtitleurl
We have added the following new columns to the TRACKS table:
categorycoupondiscountorder_idpriceproduct_idquantityshippingskusubtotaltaxtotal
ShipStation
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
SHIPMENT | |||||
| column | Discontinued Column | advanced_options | |||
| column | Discontinued Column | dimensions | |||
| column | New Column | advanced_options_bill_to_account | |||
| column | New Column | advanced_options_bill_to_country_code | |||
| column | New Column | advanced_options_bill_to_my_other_account | |||
| column | New Column | advanced_options_bill_to_party | |||
| column | New Column | advanced_options_bill_to_postal_code | |||
| column | New Column | advanced_options_contains_alcohol | |||
| column | New Column | advanced_options_custom_field1 | |||
| column | New Column | advanced_options_custom_field2 | |||
| column | New Column | advanced_options_custom_field3 | |||
| column | New Column | advanced_options_merged_or_split | |||
| column | New Column | advanced_options_non_machinable | |||
| column | New Column | advanced_options_parent_id | |||
| column | New Column | advanced_options_saturday_delivery | |||
| column | New Column | advanced_options_source | |||
| column | New Column | advanced_options_store_id | |||
| column | New Column | advanced_options_warehouse_id | |||
| column | New Column | dimensions_height | |||
| column | New Column | dimensions_length | |||
| column | New Column | dimensions_units | |||
| column | New Column | dimensions_width | |||
SHIPMENT_MERGED | |||||
| table | New Table | SHIPMENT_MERGED | |||
Shopify
We have added the following new columns to the CUSTOMER table:
default_email_addressdefault_email_address_source_location_id
Square
We have added the two new columns, device_detail_device_id and device_detail_device_installation_id, to the PAYMENT table.
Stripe
We have added the following new columns to the PAYMENT_METHOD_CARD table:
exp_monthexp_yearlast4
We have added the following new columns to the SUBSCRIPTION_HISTORY table:
billing_mode_flexible_proration_discountsbilling_mode_typebilling_mode_updated_atnext_pending_invoice_item_invoicepending_invoice_item_intervalpending_invoice_item_interval_count
SurveyMonkey
We have added a new column, tag_data, to the RESPONSE_ANSWER table.
Tableau
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CONNECTED_APP | |||||
| column | New Column | site_id | |||
DATA_DRIVEN_ALERT | |||||
| column | New Column | site_id | |||
DATA_SOURCE | |||||
| column | New Column | site_id | |||
DATA_SOURCE_CONNECTION | |||||
| table | New Table | DATA_SOURCE_CONNECTION | |||
DATA_SOURCE_DEFAULT_PERMISSION | |||||
| table | New Table | DATA_SOURCE_DEFAULT_PERMISSION | |||
DATA_SOURCE_PERMISSION | |||||
| table | New Table | DATA_SOURCE_PERMISSION | |||
DATA_SOURCE_REVISION | |||||
| column | New Column | site_id | |||
DATA_SOURCE_TAG | |||||
| column | New Column | site_id | |||
DATABASES_DEFAULT_PERMISSION | |||||
| table | New Table | DATABASES_DEFAULT_PERMISSION | |||
FLOW | |||||
| column | New Column | site_id | |||
FLOW_CONNECTION | |||||
| table | New Table | FLOW_CONNECTION | |||
FLOW_DEFAULT_PERMISSION | |||||
| table | New Table | FLOW_DEFAULT_PERMISSION | |||
FLOW_PARAMETER | |||||
| column | New Column | site_id | |||
FLOW_PERMISSION | |||||
| table | New Table | FLOW_PERMISSION | |||
FLOW_TAG | |||||
| table | New Table | FLOW_TAG | |||
GROUPS | |||||
| column | New Column | site_id | |||
METRIC_DEFAULT_PERMISSION | |||||
| table | New Table | METRIC_DEFAULT_PERMISSION | |||
PROJECT | |||||
| column | New Column | site_id | |||
PROJECT_PERMISSION | |||||
| table | New Table | PROJECT_PERMISSION | |||
SERVER_SCHEDULE | |||||
| column | New Column | site_id | |||
TABLE_DEFAULT_PERMISSION | |||||
| table | New Table | TABLE_DEFAULT_PERMISSION | |||
USER_NOTIFICATION | |||||
| column | New Column | site_id | |||
USER_WORKBOOK | |||||
| table | New Table | USER_WORKBOOK | |||
USERS | |||||
| column | New Column | site_id | |||
USERS_PERSONAL_ACCESS_TOKEN | |||||
| table | New Table | USERS_PERSONAL_ACCESS_TOKEN | |||
VIEW | |||||
| column | New Column | site_id | |||
VIEW_PERMISSION | |||||
| table | New Table | VIEW_PERMISSION | |||
VIRTUAL_CONNECTION | |||||
| table | New Table | VIRTUAL_CONNECTION | |||
VIRTUAL_CONNECTION_DATABASE_CONNECTION | |||||
| table | New Table | VIRTUAL_CONNECTION_DATABASE_CONNECTION | |||
VIRTUAL_CONNECTION_DEFAULT_PERMISSION | |||||
| table | New Table | VIRTUAL_CONNECTION_DEFAULT_PERMISSION | |||
VIRTUAL_CONNECTION_PERMISSION | |||||
| table | New Table | VIRTUAL_CONNECTION_PERMISSION | |||
WORKBOOK | |||||
| column | New Column | site_id | |||
WORKBOOK_CONNECTION | |||||
| table | New Table | WORKBOOK_CONNECTION | |||
WORKBOOK_DEFAULT_PERMISSION | |||||
| table | New Table | WORKBOOK_DEFAULT_PERMISSION | |||
WORKBOOK_PERMISSION | |||||
| table | New Table | WORKBOOK_PERMISSION | |||
WORKBOOK_REVISION | |||||
| column | New Column | site_id | |||
WORKBOOK_TAG | |||||
| column | New Column | site_id | |||
Taboola
We have added a new column, cta_type, to the CAMPAIGN_ITEM table.
TikTok Ads
We now support additional metrics for basic custom reports. For a full list of available metrics visit TikTok API documentation.
We've added a new table, LOCATION. The table contains available ad delivery locations for each advertiser, including region hierarchy (country, province, city, district), area type, and age targeting support.
Workday HCM
As part of the phased rollout announced in January 2026, we have implemented the following schema changes for connections set up on or before January 5, 2026:
Stopped syncing data into the following legacy tables:
MILITARY_SERVICEPERSON_DISABILITYPERSONAL_INFORMATION_ETHNICITYRELATIVE_NAME
Renamed the following legacy tables:
MILITARY_SERVICEtoMILITARY_SERVICE_BACKUPPERSON_DISABILITYtoPERSON_DISABILITY_BACKUPPERSONAL_INFORMATION_ETHNICITYtoPERSONAL_INFORMATION_ETHNICITY_BACKUPRELATIVE_NAMEtoRELATIVE_NAME_BACKUP
Renamed the following new tables:
MILITARY_SERVICE_INCOMINGtoMILITARY_SERVICEPERSON_DISABILITY_INCOMINGtoPERSON_DISABILITYPERSONAL_INFORMATION_ETHNICITY_INCOMINGtoPERSONAL_INFORMATION_ETHNICITYRELATIVE_NAME_INCOMINGtoRELATIVE_NAME
Stopped syncing data into the following columns of the
PERSONAL_INFORMATIONtable, which are now available in theCOUNTRY_PERSONAL_INFORMATIONandPERSONAL_INFORMATION_COMMON_DATAtables:additional_nationalityblood_typecity_of_birthcity_of_birth_codecitizenship_statuscountry_of_birthcountry_region_of_birthdate_of_birthdate_of_deathgenderhispanic_or_latinohukou_localityhukou_postal_codehukou_region_codehukou_subregion_codehukou_type_codelast_medical_exam_datelast_medical_exam_valid_tolocal_hukoumarital_statusmarital_status_datemedical_exam_notesnative_regionnative_region_codepersonnel_file_agency_for_personpolitical_affiliationprimary_nationalityregion_of_birthreligionsocial_benefits_locality
Be sure to update your downstream queries to reflect these changes. To backfill historical data for the renamed tables, re-sync them.
Xero
We have added a new column, tracking_category_option_id, to the following tables: -BANK_TRANSACTION_LINE_ITEM_HAS_TRACKING_CATEGORY -INVOICE_LINE_ITEM_HAS_TRACKING_CATEGORY -MANUAL_JOURNAL_LINE_HAS_TRACKING_CATEGORY -OVERPAYMENT_LINE_ITEM_HAS_TRACKING_CATEGORY -PURCHASE_ORDER_LINE_ITEM_HAS_TRACKING_CATEGORY
We have added a new column, account_id, to the following tables:
BANK_TRANSACTION_LINE_ITEMSCREDIT_NOTE_LINE_ITEMINVOICE_LINE_ITEMOVERPAYMENT_LINE_ITEMPREPAYMENT_LINE_ITEMPURCHASE_ORDER_LINE_ITEMRECEIPT_LINE_ITEMREPEATING_INVOICE_LINE_ITEM
We have added a new table, CONTACT_PHONE. We will be rolling out this change soon. We have added a new column, reporting_code_updated_utc, to the ACCOUNT table.
Zendesk Support
We have added a new column, support_type, to the TICKET table.
Improvements
Amazon S3
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Azure Blob Storage
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Box
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Our Box connector now supports syncing files within nested folders, in Magic Folder mode. To support this enhancement, we have added a new toggle, Include subfolders, in the connection setup form. For more information, see our setup instructions. We are gradually rolling out this enhancement to all existing connections.
ChartMogul
We have fixed an issue that prevented us from populating the CUSTOMER_ATTRIBUTE_TAG table. We now populate this table with the correct data.
ClickUp
We now support syncing sprint tasks in the TASK table.
Collibra
We now sync data for both active and disabled users into the USERS table. Previously, we synced only active users into this table.
Consensus Demo Automation Platform
Fixed an issue in the TRACK_DEMO_BOARD table where certain fields were left empty due to an invalid extraction path. This fix ensures that external_opportunity_id, external_opportunity_name, external_account_id, and external_account_name are now extracted and filled as expected.
Databricks destination
We now support timezone-naive columns (LocalDateTime) for Databricks destinations as the native TIMESTAMP_NTZ type, preserving wall-clock values without session-timezone adjustments. This feature is currently in Public Preview. Contact our Support Team if you want to get it enabled.
Dropbox
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
File connectors
We have added a new toggle, Allow inconsistent row lengths, to the connection setup forms to support syncing rows in CSV files with inconsistent lengths for the following connectors:
- Amazon S3
- Azure Blob Storage
- Box
- Dropbox
- FTP
- Google Cloud Storage
- Google Drive
- SharePoint
- SFTP
- S3-Compatible Storage
This feature is available only to all new connections created after 13 April, 2026. We are gradually rolling out this feature to all existing connections. For more information, see our documentation.
Firebase
We have added a new optional toggle, Capture Deletes, to the connection setup form. To capture document deletions from your Firestore database, set the toggle to ON during connection configuration. If you don't want the connection to capture deletes, set the toggle to OFF. By default, the toggle is enabled. Disabling delete capture may improve the connection's performance. For more information, see our setup instructions.
FTP
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Google Ad Manager
We have upgraded our Google Ad Manager connector from version v202505 to v202602 of the Google Ad Manager API and handled deprecations and updates. Learn more about the deprecations and changes in the Google Ad Manager API documentation.
Google Calendar
We have updated the sync strategy for the EVENT table to accurately capture all timed events.
Google Cloud Storage
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Google Drive
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Greenhouse
We now support the Harvest v3 (OAuth 2.0) to connect the Greenhouse connector with Fivetran.
To support this enhancement, we have made the following changes:
- Added a new toggle button, Use Harvest API v3, to the setup form. The toggle button allows you to fetch data using the latest Harvest v3.
- Added two new fields, Client ID and Client secret, to the setup form.
- Added two new parameters,
client_idandclient_secret, to the Fivetran REST API.
For more information, see our setup instructions and REST API documentation. We are gradually rolling these changes to all existing destinations.
Jira
We now support Unstructured File Replication for our Jira connector. To support this enhancement, we have added a new toggle, Sync Jira files to your destination's object storage, to the connection setup form. This feature is available only for Jira Cloud connections. For more information, see our setup instructions. We are gradually rolling out this enhancement to all existing connections.
Klaviyo
We have added a new toggle, Sync predictive analytics for PERSON table, to the connection setup form to enable or disable syncing all columns with the prefix predictive_analytics_* to the PERSON table. For more information, see our setup instructions.
Managed Data Lake Service
We have improved how we handle BIGDECIMAL data for Managed Data Lake Service destinations. If a column’s precision is up to 38 and the scale is up to 10, we now preserve the original precision and scale when converting the data type to DECIMAL. Previously, we converted such columns to DECIMAL(38, 10) regardless of the source definition. This change applies only to new columns; existing columns remain unchanged. We are gradually rolling out this change to all existing destinations.
Managed Data Lake Service now supports the Source naming feature. We are gradually rolling out this enhancement to all existing destinations.
Microsoft Advertising
The Microsoft Advertising connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
Microsoft Dynamics 365 Business Central
The Microsoft Dynamics 365 Business Central connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
OneTrust
We have changed our sync strategy. We now re-import the USER_GROUP table to capture updates and mitigate source issues.
Playvox Workforce Management
We now sync scheduled shift data up to 1 month into the future for the SHIFT table.
We have updated our sync strategy for the SHIFT table. We now use incremental syncs instead of priority-first syncs.
PostgreSQL destination
We now sync binary columns to PostgreSQL destinations as the native bytea type. Previously, we stored binary data as base64-encoded or text strings, which required an explicit DECODE cast when querying. We are gradually rolling out this change to all existing destinations.
Row filtering support for boolean data type
Row filtering now supports the boolean data type. You can filter rows by boolean column values using the Equal To and Not Equal To operators, as well as Is NULL and Is not NULL.
For more information, see our row filtering documentation.
S3-Compatible Storage
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Samsara
We have added OAuth 2.0 as a new authentication method for the Samsara connector. To support this enhancement, we have made the following changes:
- Added a new drop-down menu, Authentication type, to the connection setup form. The drop-down menu allows you to select the authentication method.
- Added two new fields, App ID and App secret, to the connection setup form. These fields appear only when you select OAuth 2.0 authentication and allow you to provide your OAuth 2.0 app credentials.
- Renamed the Access Token field to API token.
- Added the following parameters to the Fivetran REST API:
auth_typeapp_idapp_secret
For more information, see our setup instructions.
SAP ERP on HANA
We’ve added a new sync mechanism No-trigger for our SAP ERP on HANA connector. When creating a new connection, you can choose one of the following sync mechanisms:
- Default: Uses triggers and shadow tables to capture deletes. This is the existing behavior.
- No-trigger: Uses only queries to detect changes, including deletes. No triggers or shadow tables are created in your SAP system. Column-store transparent tables replicate in Live mode with a Fivetran-generated
_fivetran_idcolumn as the primary key. Deletes are permanently removed from the destination (hard deletes).
You select the sync mechanism during initial connection setup, and you cannot change it after you save the connection.
For more information, see our Sync mechanisms and No-trigger sync mechanism documentation.
A new version of the Fivetran NetWeaver API is now available for download: v1900313.
Improvements in Fivetran NetWeaver API v1900313:
- We improved the segregation of database schemas in a source and fixed a bug where the table type was determined wrongly due to a reference to the wrong schema.
SFTP
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
SharePoint
We now allow you to update the primary key column after the initial sync when using the Upsert file using custom primary key option.
Upland Software
We have made the following changes to our sync strategy:
- We now incrementally sync the
CAMPAIGN_SUBSCRIBERtable to capture new records. - We now support priority-first sync for the
MESSAGEtable. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use.
Veeva Vault
We now support Unstructured File Replication for our Veeva Vault connector. To support this enhancement, we have added a new toggle, Sync Veeva Vault document files to your destination's object storage, to the connection setup form. For more information, see our setup instructions. We are gradually rolling out this enhancement to all existing connections.
Workday Adaptive Planning
Our Workday Adaptive Planning connector now supports sync modes for Account and Level. You can choose to sync specific accounts and levels or sync all accounts and levels. To support this enhancement, we have made the following changes in the setup form:
- Added two new options, Sync all accounts and Select specific accounts to the Account sync mode field.
- Added two new options, Sync all levels and Select specific levels to the Level sync mode field.
- Added a new section, Accounts selected, to select the specific accounts you want to include in your report.
- Added a new section, Levels selected, to select the specific levels you want to include in your report.
For more information, see our setup instructions and REST API documentation. We are gradually rolling out these enhancements to all existing connections.
Workday RaaS
We have removed the following deprecated fields from the Fivetran REST API for Workday RaaS connections to align with the multi-report flow configuration:
- Removed the
primary_keysparameter - Removed the
report_format_typeparameter - Removed the
report_urlparameter - Removed the
support_nested_columnsparameter - Removed the
generate_fivetran_pkparameter
These fields are now only used within the reports.fields configuration for individual reports in the multi-report flow. If you are using the Fivetran REST API or Terraform provider to manage Workday RaaS connections, please update your configurations to use the multi-report flow instead.
Zoho CRM
We have added support for the Zoho Japan (JP) data center. For more information, see our setup instructions.
REST API Improvements
Enable configurable variables for Quickstart Transformations
You can now configure custome variables for Quickstart Transformations by using the Transformation API resource. This lets you create more flexible and reusable transformation configurations. Supported variables are package-specific and are included in the package’s metadata.