June 2025
Connector SDK
fivetran-connector-sdk PyPI package
We have released version 1.6.0 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Minor bug fixes and improvements.
- Improved logging.
We have released version 1.5.1 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Important fix around timestamp parsing and formatting.
We have released version 1.5.0 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Environment variable naming improvements.
- Improvements to the
--forceargument andresetcommand. - Performance improvements.
- Usage of latest versions for dependent libraries.
- Improved logging.
- Minor improvements and bug fixes.
fivetran-api-playground PyPI package
We have released version 1.0.0 of the fivetran-api-playground PyPI package. This release adds the following:
- Minor improvements and bug fixes.
- Updated dependencies.
Dashboard Improvements
New Events list
We've added a new Events list to the Connection Status tab in the Fivetran dashboard. This list centralizes key information about your connection in one place, such as sync details, connection updates, and alerts.

You can now view the following information for your connections:
- Event type: The type of event described in that row. There are four event types: Action, Sync, Error, and Warning.
- Action: A connection update such as a schema change or a connection pause.
- Error: An error that is disrupting your data syncs.
- Sync: A connection sync and its status (successful, rescheduled, canceled, failed, or unknown).
- Warning: A warning about a problem with your connection that you may need to fix but is not disrupting your data syncs.
- Start time: The event's start time.
- End time: The event's end time.
- Sync duration: The total duration of the sync, including the extract and load phases. The sync duration can be longer than the extract and load phases because of additional processes, such as de-duplication.
- Extract: The duration of the extract phase, when Fivetran extracts data from the source.
- Load: The duration of the load phase, when Fivetran loads your data into the destination.
- Loaded rows: The number of rows loaded into the staging tables in the destination. This field represents the data that we moved during the sync, but it is not the unique count of changed rows.
- Action: Click View to view additional details about an error or warning event.
Fivetran Proxy Agent
New version
A new version of the Fivetran Proxy Agent has been released and is bundled with the High-Volume Agent version 6.1.0/79. You can download the new version from the Downloads page.
The new version includes an updated JRE that addresses CVE-2024-21235, as detailed in the Azul CVE Fixes documentation. It can connect to an infrastructure with smarter scaling, ensuring higher uptime for connections using the newest agent. In order to take advantage of this feature, you must allowlist the new hostname for the region your Proxy Agent is registered in.
Any newly created Proxy Agents must use version 6.1.0/79 or later. Existing Proxy Agents can continue to use their current version, but we recommend upgrading to take advantage of the latest features and security updates.
Lite Connectors
Lite connectors are now available for the following sources:
Improved control over multi-value setup form fields
We have changed the behavior of the setup form fields that accept multiple values. You can now specify values for these fields only during the initial connection setup and cannot modify them after you set up the connection. This change ensures data integrity for your connections. If you want to change these field values for any existing connection, you have to set up a new connection with the updated values.
We have made this change to the following connectors and setup form fields:
| CONNECTOR | FIELD |
|---|---|
| Akamai | Type Name |
| CJ Commission Detail | Company IDs |
| Clari | Forecast ID |
| Cloudbeds | Property ID |
| LINE Ads | Group ID |
| myosh | Server variable |
| Pigment | View ID |
| Qualaroo | Survey IDs |
| Rakuten Advertising | Report keys |
| Rarible | Collection Address |
| Sentry | Project IDs |
| SISTRIX | Domain |
| Statistics Netherlands CBS | Catalog identifier |
| Unicommerce | Facility code |
Transformations for dbt Core
Account-level transformations
The transformation list now has items from all groups of the account the current user has access to. Adding a transformation to any destination of the account is now possible without switching the group The new "Manage projects" page containing all connected dbt projects in the account is now available
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
dbt Core version 1.9.8 support
We now support dbt Core* version 1.9.8. You can use this version to run your projects.
For this dbt Core version, we don't support MySQL and Azure Synapse 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.
Updated dbt Quickstart packages
We have added a new Quickstart package for the Microsoft Dynamics 365 CRM connector.
We have updated the Quickstart packages for the following connectors:
- Connectors supporting the Ad Reporting data model to version 1.15.0.
- Connectors supporting the App Reporting data model to version 0.6.0.
- Connectors supporting the Shopify Holistic Reporting data model to version 0.8.0.
- Amazon Ads to version 0.5.0.
- Amplitude to version 0.7.0.
- Apple App Store to version 0.6.0.
- Apple Search Ads to version 0.6.0.
- Asana to version 0.9.0.
- Facebook Ads to version 0.10.0.
- Fivetran Platform to version 2.2.0.
- GitHub to version 0.9.0.
- Google Ads to version 0.14.0.
- Google Play to version 0.5.0.
- Greenhouse to version 0.9.0.
- HubSpot to version 0.24.0.
- Intercom to version 0.10.0.
- Jira to version 0.21.0.
- Klaviyo to version 0.9.0.
- Lever to version 0.8.0.
- LinkedIn Ad Analytics to version 0.12.0.
- Mailchimp to version 0.12.0.
- Microsoft Advertising to version 0.12.0.
- Mixpanel to version 0.13.0.
- NetSuite SuiteAnalytics to version 0.20.0.
- Pendo to version 0.6.0.
- Pinterest Ads to version 0.13.0.
- QuickBooks to version 0.20.0.
- Recurly to version 0.7.0.
- Reddit Ads to version 0.5.0.
- Sage Intacct to version 0.7.0.
- Salesforce to version 1.3.0.
- Snapchat Ads to version 0.10.0.
- Stripe to version 0.19.0.
- TikTok Ads to version 0.9.0.
- Twilio to version 0.5.0.
- Twitter Ads to version 0.10.0.
- Workday HCM to version 0.4.0.
- Zendesk Support to version 0.24.1.
Unstructured file replication
We have released the beta version of our Unstructured File Replication feature. The feature enables you to sync unstructured files, regardless of the file format, to the supported destinations with integrated object storage capabilities. You can manage and store both unstructured and structured data from a unified storage location.
The June 2025 beta release is free. We have designed the free beta program to allow you to test and validate your Artificial Intelligence (AI) and Retrieval-Augmented Generation (RAG) use cases at scale before the feature's general availability. We will convert the usage insights from the no-cost beta period into a transparent, value‑aligned pricing model.
Schema changes
Adobe Workfront
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CALENDAR | |||||
| column | New Column | name | |||
PROGRAM | |||||
| table | New Table | PROGRAM | |||
RESERVED_TIME | |||||
| table | New Table | RESERVED_TIME | |||
Aha!
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
GOAL | |||||
| column | Discontinued Column | parent_id | |||
GOAL_PARENT | |||||
| table | New Table | GOAL_PARENT | |||
Amazon Selling Partner
We have removed the following tables from the schema dashboard, as they were never part of the connector’s data sync:
ADDITIONAL_SELLER_INPUTSAMAZON_PREP_FEES_DETAILASIN_INBOUND_GUIDANCEAVAILABLE_DELIVERY_EXPERIENCE_OPTIONAVAILABLE_SHIPPING_SERVICE_OPTIONINBOUND_SHIPMENT_INFOINBOUND_SHIPMENT_ITEMINBOUND_SHIPMENT_ITEM_PREP_DETAILITEM_CONTRIBUTORMERCHANT_FULFILLMENT_SHIPMENTMERCHANT_FULFILLMENT_SHIPMENT_ITEMNON_PARTNERED_LTL_DATA_OUTPUTNON_PARTNERED_SMALL_PARCEL_PACKAGE_OUTPUTPARTNERED_LTL_DATA_OUTPUTPARTNERED_LTL_DATA_OUTPUT_PALLETPARTNERED_SMALL_PARCELPARTNERED_SMALL_PARCEL_PACKAGE_OUTPUTPREORDER_INFO_RESULTPREP_INSTRUCTIONSKU_INBOUND_GUIDANCETAX_REGISTRATION_DETAILS_FOR_RETAIL_SHIPPINGTRANSPORT_CONTENT
This update does not affect any data sync behavior.
Awin
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REPORTS_AGGREGATED_BY_CAMPAIGN | |||||
| column | New Column | end_date | |||
| column | New Column | start_date | |||
Braintree
We have added the risk_data_transaction_risk_score column to the TRANSACTION and CREDIT_CARD_VERIFICATION tables.
We have also added a new table, DECISION_REASON, to sync decision_reasons with the risk_data_id.
We will gradually roll out this feature to all connections.
We've added the following columns to the ANDROID_PAY_DETAILS table:
commercialcountry_of_issuancedebithealthcareissuing_bankpayrollprepaid
We've added the following columns to the APPLE_PAY_CARD table:
bincommercialcountry_of_issuancedebithealthcareissuing_bankpayrollprepaid
Braze
We've added the created_at column to the USER table. This column contains the timestamp of when the user profile was created in Braze, in ISO 8601 format.
This allows you to better track the lifecycle of users and analyze registration patterns and tenure across your Braze user base.
Chargebee Product Catalog 2.0
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
HOSTED_PAGE | |||||
| table | New Table | HOSTED_PAGE | |||
HOSTED_PAGE_TRANSACTION | |||||
| table | New Table | HOSTED_PAGE_TRANSACTION | |||
SUBSCRIPTION_RENEWAL_ESTIMATE | |||||
| table | New Table | SUBSCRIPTION_RENEWAL_ESTIMATE | |||
SUBSCRIPTION_RENEWAL_ESTIMATE_INVOICE_LINE_ITEM | |||||
| table | New Table | SUBSCRIPTION_RENEWAL_ESTIMATE_INVOICE_LINE_ITEM | |||
Coupa
We have added a new column, released_at, to the CP_PAYMENT table to store the date and time when a purchase order was sent to the supplier. We will automatically re-sync the historical data for this column.
We have added the following columns to the INVENTORY_TRANSACTION table:
adjustment_codeadjustment_code_created_atadjustment_code_idadjustment_code_nameadjustment_code_typeadjustment_code_updated_at
We now sync TAG data from the REQUISITION_LINE table. We have added a column requisition_line_id to the TAG table.
Criteo
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ADSET | |||||
| column | New Column | attribution_configuration_lookback_window | |||
| column | New Column | attribution_configuration_method | |||
Facebook Pages
We have made the following changes to the DAILY_PAGE_METRICS_TOTAL and UNIQUE_DAILY_PAGE_METRICS_TOTAL tables:
- Added the
page_daily_followsandpage_followscolumns to theDAILY_PAGE_METRICS_TOTALtable - Added the
page_daily_follows_uniqueandpage_daily_unfollows_uniquecolumns to theUNIQUE_DAILY_PAGE_METRICS_TOTALtable
For more information about the metrics that these columns store, see Facebook documentation.
Factbird
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
BATCH | |||||
| column | New Column | product_id | |||
LINE_STOP | |||||
| table | New Table | LINE_STOP | |||
Freshservice
We have added two new timestamp columns, created_at and updated_at, to the PROJECT_TASK table.
We have added a new column, spam, to the TICKET table.
Front
Front will sunset the Group API and replace it with the List API on September 1, 2025. To support the API change, we have added a new table, LIST. We'll continue to sync data to both GROUP and LIST tables. We will stop syncing data to the GROUP table on September 6, 2025.
We have also added a new child table, CONTACT_LIST, to the parent table CONTACT. The new table is identical to the CONTACT_GROUP table. We'll continue to sync data to both the CONTACT_GROUP and CONTACT_LIST tables. We will stop syncing data to the CONTACT_GROUP table on September 6, 2025. Be sure to update your queries.
Gong
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CALL | |||||
| column | New Column | brief | |||
| column | New Column | call_outcome_category | |||
| column | New Column | call_outcome_id | |||
| column | New Column | call_outcome_name | |||
CALL_HIGHLIGHT_ITEM | |||||
| table | New Table | CALL_HIGHLIGHT_ITEM | |||
CALL_KEYPOINT | |||||
| table | New Table | CALL_KEYPOINT | |||
CALL_OUTLINE | |||||
| table | New Table | CALL_OUTLINE | |||
CALL_OUTLINE_ITEM | |||||
| table | New Table | CALL_OUTLINE_ITEM | |||
CALL_TRACKER | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | New Column | count | |||
Google Ads
We've added a new metadata table, CAMPAIGN_CONVERSION_GOAL_HISTORY. We are slowly rolling that report out to all existing connections.
Google Analytics 4 Export
We have added the following columns to the EVENT table:
session_traffic_source_last_click.cross_channel_campaign.campaign_idsession_traffic_source_last_click.cross_channel_campaign.campaign_namesession_traffic_source_last_click.cross_channel_campaign.mediumsession_traffic_source_last_click.cross_channel_campaign.sourcesession_traffic_source_last_click.cross_channel_campaign.source_platform
To backfill the historical data for these columns, re-sync the connection or contact Fivetran Support to re-sync it for you.
Google Display & Video 360
We've added support for multi-reporting to all new Google Display & Video 360 connections created after June 30, 2025. Once you create a connection, it will sync all available reports by default.
We now sync the following metadata:
Greenhouse
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EMAIL | |||||
| column | Rename Column | froms | from_email | ||
| column | Rename Column | tos | to_email | ||
EMAIL_TEMPLATE | |||||
| column | Rename Column | froms | from_email | ||
Help Scout
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
DOC_REPORT | |||||
| table | New Table | DOC_REPORT | |||
DOC_REPORT_FAILED_SEARCH | |||||
| table | New Table | DOC_REPORT_FAILED_SEARCH | |||
DOC_REPORT_POPULAR_SEARCH | |||||
| table | New Table | DOC_REPORT_POPULAR_SEARCH | |||
DOC_REPORT_TOP_ARTICLE | |||||
| table | New Table | DOC_REPORT_TOP_ARTICLE | |||
DOC_REPORT_TOP_CATEGORY | |||||
| table | New Table | DOC_REPORT_TOP_CATEGORY | |||
TAG_HISTORY | |||||
| column | New Column | slug | |||
HubSpot
In the DEAL_PIPELINE_STAGE table, we have corrected the name of the closed_won column to is_closed. The data in this column represents whether a deal is closed or not, regardless of its label. You can still use the label column to determine whether a deal is "closed won" or "closed lost". This change ensures the HubSpot connector more accurately reflects your source data.
We are gradually rolling out these changes to all existing connectors. We will populate both closed_won and is_closed for a transition period. After this period, you can drop the closed_won column at your convenience.
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
MARKETING_CAMPAIGN | |||||
| table | New Table | MARKETING_CAMPAIGN | |||
MARKETING_CAMPAIGN_ASSET | |||||
| table | New Table | MARKETING_CAMPAIGN_ASSET | |||
MARKETING_CAMPAIGN_BUDGET_ITEM | |||||
| table | New Table | MARKETING_CAMPAIGN_BUDGET_ITEM | |||
MARKETING_CAMPAIGN_CONTACT | |||||
| table | New Table | MARKETING_CAMPAIGN_CONTACT | |||
MARKETING_CAMPAIGN_SPEND_ITEM | |||||
| table | New Table | MARKETING_CAMPAIGN_SPEND_ITEM | |||
Kantata
We've added a new column, provider_lead_name, to the WORKSPACE table. The column contains the name of the team lead for the provider side of the project. This addition improves visibility into project ownership and team structure.
We've added a new table, ACCOUNT_COLOR. The table contains account-level color definitions that can be associated with projects for categorization purposes.
We have added a new column, account_color_id, to the WORKSPACE table.
LinkedIn Ad Analytics
We've added the following fields to the CREATIVE_HISTORY table:
document_ad_referencedocument_ad_gated_leadgen_preview_page_countevent_ad_postevent_ad_direct_sponsored_contentevent_ad_eventevent_ad_hide_preview_video
We will fetch all post links in event_ad_post and document_ad_reference, and add them to the POST_HISTORY table.
Microsoft Dynamics 365 CRM
We have added a new column, renamed_attributename, to the STRINGMAP table. The column contains the values of attributename that are renamed according to the destination renaming rules. For more information, see our documentation.
PagerDuty
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
USERS_CONTACT_METHOD | |||||
| column | New Column | address | |||
Persona
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
USER_AUDIT_LOG | |||||
| column | Rename Column | custom_* | get_params | ||
Pipe17
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ARRIVAL_LINE_ITEM | |||||
| column | Primary Key Change | arrival_id | arrival_id 🔑 | Added to primary key. | |
CONNECTOR_ENTITY | |||||
| column | Primary Key Change | connector_id | connector_id 🔑 | Added to primary key. | |
FULFILLMENT_LINE_ITEM | |||||
| column | Primary Key Change | fulfillment_id | fulfillment_id 🔑 | Added to primary key. | |
| column | Primary Key Change | sku | sku 🔑 | Added to primary key. | |
| column | New Column | bundle_quantity_partial | |||
FULFILLMENT_LINE_ITEM_BUNDLE_QUANTITY_PARTIAL | |||||
| table | Discontinued Table | FULFILLMENT_LINE_ITEM_BUNDLE_QUANTITY_PARTIAL | Data is available in the bundle_quantity_partial column of the FULFILLMENT_LINE_ITEM table. | ||
FULFILLMENT_TRACKING_NUMBER | |||||
| column | Primary Key Change | fulfillment_id | fulfillment_id 🔑 | Added to primary key. | |
FULFILLMENT_TRACKING_URL | |||||
| column | Primary Key Change | fulfillment_id | fulfillment_id 🔑 | Added to primary key. | |
ORDER_DISCOUNT | |||||
| column | Primary Key Change | line_item_id 🔑 | line_item_id | No longer a primary key. | |
| column | Primary Key Change | index 🔑 | New primary key. | ||
PRODUCT_PUBLISHED | |||||
| column | Primary Key Change | sku 🔑 | sku | No longer a primary key. | |
| column | Primary Key Change | index 🔑 | New primary key. | ||
PURCHASE_LINE_ITEM | |||||
| column | Primary Key Change | purchase_id | purchase_id 🔑 | Added to primary key. | |
RECEIPT_LINE_ITEM | |||||
| column | Primary Key Change | receipt_id | receipt_id 🔑 | Added to primary key. | |
SHIPMENT_LINE_ITEM | |||||
| column | Primary Key Change | shipment_id | shipment_id 🔑 | Added to primary key. | |
SHIPPING_METHOD_MAPPED_METHOD | |||||
| column | Primary Key Change | shipping_method_id | shipping_method_id 🔑 | Added to primary key. | |
SUPPLIER_CONTACT | |||||
| column | Primary Key Change | supplier_id | supplier_id 🔑 | Added to primary key. | |
TRANSFER_LINE_ITEM | |||||
| column | Primary Key Change | transfer_id | transfer_id 🔑 | Added to primary key. | |
Qualtrics
We have made the following improvements to the QUESTION_RESPONSE table:
Added a new column,
text, to store the values that respondents enter in the text boxes associated with the Other option in Qualtrics. The new column avoids the creation of multiple records for such values.We have fixed a bug where the
question_option_keycolumn incorrectly stored the recode value of a question option. We now correctly map the recode value to the corresponding question option key before storing it.
We are gradually rolling out these changes to all existing connections.
Salesforce Commerce Cloud
We now use the following new columns in the CUSTOMER table to store each customer’s primary address details:
primary_address_address_1primary_address_address_2primary_address_cityprimary_address_company_nameprimary_address_country_codeprimary_address_creation_dateprimary_address_etagprimary_address_first_nameprimary_address_full_nameprimary_address_job_titleprimary_address_last_modifiedprimary_address_last_nameprimary_address_phoneprimary_address_post_box,primary_address_postal_codeprimary_address_salutationprimary_address_second_nameprimary_address_state_codeprimary_address_suffixprimary_address_suiteprimary_address_title
SendGrid
We've added a new column, sg_machine_open, to the EVENT table. The column indicates whether an email open event was generated by an automated system (machine) rather than a human user.
SharePoint
We have added the custom_metadata column to metadata tables for the SharePoint connector. This column contains the custom properties of the file replicated to your stage. This change applies only if you have selected unstructured as the File Type in the connection setup form.
Shopify
We have removed column async_usage_count, from the DISCOUNT_REDEEM_CODE table.
Simplesat
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ANSWER | |||||
| column | New Column | choices | |||
| column | New Column | follow_up_answer_choice | |||
| column | New Column | follow_up_answer_choices | |||
CUSTOMER | |||||
| column | New Column | custom_* | |||
| column | New Column | external_id | |||
SmartHR
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EMPLOYEE | |||||
| column | Discontinued Column | department | |||
| column | Discontinued Column | position | |||
EMPLOYEE_POSITION | |||||
| table | New Table | EMPLOYEE_POSITION | |||
SonarQube
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ISSUE_COMMENT | |||||
| column | Primary Key Change | login 🔑 | login | No longer a primary key. | |
Square
We've added the disputed_payment_id column to the DISPUTE table. This column contains the Square-generated unique ID of the payment that was disputed, providing a direct foreign key reference to the PAYMENT table.
We've also added a new table, PAYMENT_PROCESSING_FEE, to sync processing fees data associated with payments. Reach out to support to re-sync the parent table, PAYMENT, to backfill for historical data.
The new table will be gradually rolled out to all customers over the next few days.
Statsig
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EXPERIMENT | |||||
| column | New Column | active_review_description | |||
| column | New Column | active_review_id | |||
| column | New Column | active_review_status | |||
| column | New Column | allocation_duration | |||
| column | New Column | analysis_end_time | |||
| column | New Column | analytics_type | |||
| column | New Column | assignment_source_experiment_name | |||
| column | New Column | assignment_source_name | |||
| column | New Column | benjamini_hochberg_per_metric | |||
| column | New Column | benjamini_hochberg_per_variant | |||
| column | New Column | benjamini_primary_metrics_only | |||
| column | New Column | bonferroni_correction_per_metric | |||
| column | New Column | cohort_wait_until_end_to_include | |||
| column | New Column | cohorted_analysis_duration | |||
| column | New Column | cohorted_metrics_mature_after_end | |||
| column | New Column | control_group_id | |||
| column | New Column | external_experiment_name | |||
| column | New Column | fixed_analysis_duration | |||
| column | New Column | health_check_status | |||
| column | New Column | identifier_mapping_mode | |||
| column | New Column | identity_resolution_source | |||
| column | New Column | inline_targeting_rules_json | |||
| column | New Column | is_analysis_only | |||
| column | New Column | owner_email | |||
| column | New Column | owner_id | |||
| column | New Column | owner_name | |||
| column | New Column | owner_type | |||
| column | New Column | review_settings_required_review | |||
| column | New Column | scheduled_reload_hour | |||
| column | New Column | scheduled_reload_type | |||
| column | New Column | secondary_id_type | |||
| column | New Column | sequential_testing | |||
| column | New Column | subtype | |||
| column | New Column | target_exposure | |||
| column | New Column | team | |||
| column | New Column | team_id | |||
| column | New Column | version | |||
EXPERIMENT_ALLOWED_REVIEWER | |||||
| table | New Table | EXPERIMENT_ALLOWED_REVIEWER | |||
EXPERIMENT_ASSIGNMENT_SOURCE_FILTER | |||||
| table | New Table | EXPERIMENT_ASSIGNMENT_SOURCE_FILTER | |||
EXPERIMENT_HEALTH_CHECK | |||||
| column | New Column | type | |||
EXPERIMENT_LINK | |||||
| table | New Table | EXPERIMENT_LINK | |||
EXPERIMENT_OTHER_MATRIX | |||||
| table | New Table | EXPERIMENT_OTHER_MATRIX | |||
GATE | |||||
| column | New Column | active_review_description | |||
| column | New Column | active_review_id | |||
| column | New Column | active_review_status | |||
| column | New Column | measure_metric_lifts | |||
| column | New Column | owner_email | |||
| column | New Column | owner_id | |||
| column | New Column | owner_name | |||
| column | New Column | owner_type | |||
| column | New Column | release_pipeline_id | |||
| column | New Column | review_settings_required_review | |||
| column | New Column | team_id | |||
| column | New Column | version | |||
GATE_ALLOWED_REVIEWER | |||||
| table | New Table | GATE_ALLOWED_REVIEWER | |||
GATE_MONITORING_METRIC | |||||
| table | New Table | GATE_MONITORING_METRIC | |||
Stripe
We've added two new columns, current_period_start and current_period_end, to the SUBSCRIPTION_ITEM table. The columns contain the subscription item’s current billing start and end period.
Transcend
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ACTIVITY | |||||
| table | New Table | ACTIVITY | |||
ASSESSMENT_FILE | |||||
| table | New Table | ASSESSMENT_FILE | |||
ASSESSMENT_FORM | |||||
| table | New Table | ASSESSMENT_FORM | |||
ASSESSMENT_FORM_ASSIGNEE | |||||
| table | New Table | ASSESSMENT_FORM_ASSIGNEE | |||
ASSESSMENT_FORM_ATTRIBUTE_VALUE | |||||
| table | New Table | ASSESSMENT_FORM_ATTRIBUTE_VALUE | |||
ASSESSMENT_FORM_COMMENT | |||||
| table | New Table | ASSESSMENT_FORM_COMMENT | |||
ASSESSMENT_FORM_EXTERNAL_ASSIGNEE | |||||
| table | New Table | ASSESSMENT_FORM_EXTERNAL_ASSIGNEE | |||
ASSESSMENT_FORM_REVIEWER | |||||
| table | New Table | ASSESSMENT_FORM_REVIEWER | |||
ASSESSMENT_FORM_SECTION | |||||
| table | New Table | ASSESSMENT_FORM_SECTION | |||
ASSESSMENT_FORM_SECTION_QUESTION | |||||
| table | New Table | ASSESSMENT_FORM_SECTION_QUESTION | |||
ASSESSMENT_FORM_TEMPLATE | |||||
| table | New Table | ASSESSMENT_FORM_TEMPLATE | |||
ASSESSMENT_FORM_TEMPLATE_ATTRIBUTE_KEY | |||||
| table | New Table | ASSESSMENT_FORM_TEMPLATE_ATTRIBUTE_KEY | |||
ASSESSMENT_FORM_TEMPLATE_SECTION | |||||
| table | New Table | ASSESSMENT_FORM_TEMPLATE_SECTION | |||
ASSESSMENT_FORM_TEMPLATE_SECTION_ASSIGNEE | |||||
| table | New Table | ASSESSMENT_FORM_TEMPLATE_SECTION_ASSIGNEE | |||
ASSESSMENT_FORM_TEMPLATE_SECTION_EXTERNAL_ASSIGNEE | |||||
| table | New Table | ASSESSMENT_FORM_TEMPLATE_SECTION_EXTERNAL_ASSIGNEE | |||
ASSESSMENT_FORM_TEMPLATE_SECTION_QUESTION | |||||
| table | New Table | ASSESSMENT_FORM_TEMPLATE_SECTION_QUESTION | |||
ASSESSMENT_GROUP | |||||
| table | New Table | ASSESSMENT_GROUP | |||
ASSESSMENT_GROUP_ATTRIBUTE_VALUE | |||||
| table | New Table | ASSESSMENT_GROUP_ATTRIBUTE_VALUE | |||
ASSESSMENT_GROUP_REVIEWER | |||||
| table | New Table | ASSESSMENT_GROUP_REVIEWER | |||
ASSESSMENT_QUESTION | |||||
| table | New Table | ASSESSMENT_QUESTION | |||
ASSESSMENT_QUESTION_ANSWER_OPTION | |||||
| table | New Table | ASSESSMENT_QUESTION_ANSWER_OPTION | |||
ASSESSMENT_QUESTION_COMMENT | |||||
| table | New Table | ASSESSMENT_QUESTION_COMMENT | |||
ASSESSMENT_QUESTION_PREVIOUS_SUBMISSION | |||||
| table | New Table | ASSESSMENT_QUESTION_PREVIOUS_SUBMISSION | |||
ASSESSMENT_QUESTION_PREVIOUS_SUBMISSION_ANSWER | |||||
| table | New Table | ASSESSMENT_QUESTION_PREVIOUS_SUBMISSION_ANSWER | |||
ASSESSMENT_QUESTION_SELECT_OPTION | |||||
| table | New Table | ASSESSMENT_QUESTION_SELECT_OPTION | |||
ASSESSMENT_QUESTION_SELECTED_ANSWER | |||||
| table | New Table | ASSESSMENT_QUESTION_SELECTED_ANSWER | |||
ASSESSMENT_SECTION_COMMENT | |||||
| table | New Table | ASSESSMENT_SECTION_COMMENT | |||
COOKIE | |||||
| column | Discontinued Column | avc_email_verified | |||
| column | Discontinued Column | business_user_overview | |||
| column | Discontinued Column | consent_do_not_sell_integration | |||
| column | Discontinued Column | controller_manual_instructions | |||
| column | Discontinued Column | datapoints_customizable | |||
| column | Discontinued Column | disqualification_reasons | |||
| column | Discontinued Column | form_config | |||
| column | Discontinued Column | has_api_functionality | |||
| column | Discontinued Column | has_avc_functionality | |||
| column | Discontinued Column | has_content_classification_functionality | |||
| column | Discontinued Column | has_plugins | |||
| column | Discontinued Column | has_silo_discovery_functionality | |||
| column | Discontinued Column | has_usp_api_support | |||
| column | Discontinued Column | hero_background_color | |||
| column | Discontinued Column | hero_image_url | |||
| column | Discontinued Column | integration_status | |||
| column | Discontinued Column | intro_message | |||
| column | Discontinued Column | is_complete | |||
| column | Discontinued Column | is_featured | |||
| column | Discontinued Column | is_prompt_avendor_compatible | |||
| column | Discontinued Column | is_suggested | |||
| column | Discontinued Column | minimum_sombra_version | |||
| column | Discontinued Column | plain_text | |||
| column | Discontinued Column | prompt_avendor_email_address | |||
| column | Discontinued Column | prompt_email_template_id | |||
| column | Discontinued Column | see_other_integrations | |||
| column | Discontinued Column | website | |||
DATA_FLOW | |||||
| column | Discontinued Column | avc_email_verified | |||
| column | Discontinued Column | business_user_overview | |||
| column | Discontinued Column | consent_do_not_sell_integration | |||
| column | Discontinued Column | controller_manual_instructions | |||
| column | Discontinued Column | datapoint_customizable | |||
| column | Discontinued Column | disqualification_reasons | |||
| column | Discontinued Column | form_config | |||
| column | Discontinued Column | has_api_functionality | |||
| column | Discontinued Column | has_avc_functionality | |||
| column | Discontinued Column | has_content_classification_functionality | |||
| column | Discontinued Column | has_plugin | |||
| column | Discontinued Column | has_silo_discovery_functionality | |||
| column | Discontinued Column | has_usp_api_support | |||
| column | Discontinued Column | hero_background_color | |||
| column | Discontinued Column | hero_image_url | |||
| column | Discontinued Column | integration_status | |||
| column | Discontinued Column | intro_message | |||
| column | Discontinued Column | is_complete | |||
| column | Discontinued Column | is_featured | |||
| column | Discontinued Column | is_prompt_avendor_compatible | |||
| column | Discontinued Column | is_suggested | |||
| column | Discontinued Column | minimum_sombra_version | |||
| column | Discontinued Column | plain_text | |||
| column | Discontinued Column | prompt_avendor_email_address | |||
| column | Discontinued Column | prompt_email_template_id | |||
| column | Discontinued Column | see_other_integrations | |||
| column | Discontinued Column | website | |||
Twilio
We have added a new column, attributes, to the PARTICIPANT table.
VWO
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
GOAL | |||||
| column | New Column | urls | |||
GOAL_URL | |||||
| table | Discontinued Table | GOAL_URL | Data is available as a JSON object in the urls column of the GOAL table. | ||
Workday HCM
We have added a new column, id_type, to the PERSON_IDENTITY_DOCUMENT table.
We have made the following schema changes to the ASSESS_TALENT_NOMINATION table:
- Added a new primary key column,
index - Removed the
jobProfileIdcolumn from the composite primary key
WorkRamp
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
SCORM_ASSIGNMENT | |||||
| column | Primary Key Change | assigner 🔑 | assigner | No longer a primary key. | |
| column | Primary Key Change | scorm_id 🔑 | scorm_id | No longer a primary key. | |
| column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
| column | New Column | user_email | |||
Zendesk Support
We have added the following new columns to the GROUP table:
defaultdescriptionis_public
Improvements
BigMarker
We have updated our sync strategy and now re-import the CONFERENCE table and its child tables during every sync.
Centra
We have changed the sync strategy for the ORDERS and PRODUCT_VARIANT tables. We now re-import the ORDERS table weekly and the PRODUCT_VARIANT table daily.
Criteo
We have upgraded our Criteo connector from version 2024.07 to 2025.04 of the Criteo API. Learn more in Criteo's Version 2025.04 Release Notes.
We are gradually rolling out this improvement to all existing connections.
Datadog
We have updated our sync strategy. We now sync only the last 1 month of data for the LOG and RUM_EVENT tables due to source limitations.
We have improved the setup experience for Email connections.
- Added a new configuration option, Preview Files to perform an intermediate test during configuration
- Added support for displaying fields based on the file type
- Added a new field, Quote character, to use an enclosing character
- Reorganised fields to make the setup form more intuitive
- Removed Infer as an option from the File Type field
- Removed the Enable Advanced Options toggle
- Changed the Null Sequence field to a toggle
- For the Delimiter character(s) field, we now use
,as the default value - For the Line Separator field, we now use
\nas the default value
For more information, see our setup instructions and REST API configuration.
We are gradually rolling out these changes to all existing connections.
File connectors
We are deprecating support for the log file type in file connectors. Use the csv file type instead. Log files will now be processed the same way as CSV files. This change streamlines file type handling without affecting functionality.
Gainsight Customer Success
We now capture deletes for the CALL_TO_ACTION and CS_TASK cockpit objects. Due to source limitations, we capture deletes only from the last 15 days. To retrieve older deletes, you must re-sync these tables once.
We are gradually rolling out this change to all existing connections.
Gmail
We've removed the User ID field from the setup form because it is no longer required to establish a connection with Gmail.
This update has been rolled out to all connections.
Google Calendar
We have changed our sync strategy and now incrementally sync the EVENT table and its child tables. Previously, we re-imported the table.
We are gradually rolling out this change to all existing connections.
We have changed the sync strategy for the SETTING table. We now re-import the table once a week. Previously, we re-imported it during every sync.
We are gradually rolling out this change to all existing connections.
Gorgias
Effective June 10, 2025 we no longer perform a monthly re-import of the TICKET table to capture deletes. We now detect and sync deleted records for this table without re-importing it.
HubSpot
We have added support for HubSpot's Marketing Campaigns API to sync your HubSpot account's marketing campaigns data.
We are gradually rolling out this improvement to all existing connections.
Lever
You can now sync confidential data for the following tables:
OPPORTUNITIESPOSTINGREQUISITION
This feature is only applicable to connections created after July 29, 2024.
Managed Data Lake Service
We no longer create the sequence_number.txt file in your data lake, as the Fivetran Iceberg REST Catalog already handles change tracking for Iceberg tables.
Microsoft Lists
The Microsoft Lists connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
Microsoft Power BI
We now re-import the REFRESHABLE table and its child tables during every sync.
Oracle Business Intelligence Publisher
We have updated our sync strategy. We now sync all tables, regardless of whether a primary key is defined.
Persona
We have changed our sync strategy and now incrementally sync the following tables:
ACCOUNTCASESLISTREPORTTRANSACTIONUSER_AUDIT_LOG
PostgreSQL "bit" data type support
We now support syncing the bit data type as STRING.
PostgreSQL geometric data type support
We now support syncing the following data types as JSON:
- line
- lseg
- box
- path
- polygon
- circle
See all supported data types in our PostgreSQL Type transformations and mapping documentation.
Qualtrics
The Qualtrics connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
You can now opt to sync data of all directories or specific directories from your Qualtrics account to your destination. We have added a new mode, Directory Selection, to the connection setup form. Depending on your preference, you can select the All directories or Selected directories option. For more information, see our Directory selection documentation. We are gradually rolling out this feature to all existing connections.
Redshift
We have added support for the SUPER data type to store JSON data. For source connections of accounts created after June 12, 2025, we convert JSON data type to SUPER data type in your Redshift destination. For more information about how to parse your JSON data from Redshift destinations, see our Redshift documentation.
Rippling
We now re-import the USERS table once a month.
Sage Intacct
We now support deselection of child tables. We will gradually roll out this change to all existing Sage Intacct connections starting on June 16, 2025.
Salesforce
We have added the ApexCodeCoverage tooling API object to our Salesforce connector. You can select this table on the connection schema page to start syncing it.
We are rolling this out gradually for all connections.
Sentry
We have made the following changes to the sync strategy for Sentry connections:
We now re-import the following tables once a month instead of weekly:
ORGANIZATION_RELEASEORGANIZATION_TEAMPROJECT_RELEASE_FILEPROJECT_SERVICE_HOOK
We no longer re-import the
PROJECT_ERROR_EVENTandPROJECT_ISSUEtables on a weekly basis.
Shopify
We have added a missing scope, read_fulfillments, to our Shopify OAuth configuration. This scope is required to register the fulfillment_events/delete webhook.
If you've already connected your Shopify account, re-authorize it to make sure that the new scope is applied.
Short.io
We have made the following changes to our sync strategy for the Short.io connector:
We now incrementally sync the
LINKtable.We also re-import the
LINKtable and its child tables monthly to capture updates and deletes.We no longer sync the
COUNTRY_RULEStable, as its data can be retrieved from theLINK_STATISTICS_COUNTRYtable.We no longer sync the
REGION_RULEStable, as it does not provide any added value to the customer.We no longer capture updates and deletes for the
DOMAIN_STATISTICStable.
Sigma Computing
We now support multithreading for all tables except for the CONNECTION and WORKBOOK tables and their child tables.
Snapchat Ads
The Snapchat Ads connector now lets you select individual accounts to sync, instead of selecting entire organizations.
Snowflake
We now support Google Cloud Storage as an external stage for unstructured files. We have updated the destination setup form and changed the Storage for Unstructured Files toggle to a drop-down menu.
sticky.io
We now capture updates for the ORDERS table. Previously, we only captured new records for this table. To capture updates, we now re-import the ORDERS tables once a month.
Stripe
We have changed the sync strategy for the COUPON table to prevent service disruptions caused by Stripe API's rate limits. We no longer re-import the table every week. Instead, we re-import the table only when you manually re-sync it.
Zendesk Support
We have added option, Max Zendesk API usage (%), to the connection setup form. This option allows you to set the percentage of the API rate limit you want Fivetran to use. For more information, see our setup instructions.
REST API Improvements
Marketo
You can now set the prioritise_bulk_export_over_rest parameter using the Fivetran REST API. This parameter allows your connection to use BULK export to extract both the LEAD and ACTIVITY_* tables to improve connection performance and reduce the number of API calls.
Proxy Agent changes
We have made changes to support the latest version of the Proxy Agent. We have made the following changes to the response of the Create a Proxy Agent and Retrieve Proxy Agent Details of our Proxy Agent Management API:
Added the following parameters:
client_cert- the public certificate used by the proxy agentclient_private_key- the private key used by the proxy agent
Removed the following parameters:
proxy_server_uri- the proxy server URI