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.toml as an alternative to requirements.txt for defining dependencies in your connector project. Please refer to Managing Project Dependencies for more details.
• Improved overall performance and stability.
• .ftignore has been replaced by .gitignore. You can now create a .gitignore file in the root of your connector project to specify files and directories that should be excluded during fivetran deploy and fivetran package. If you have an existing .ftignore file, rename it to .gitignore because 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.

Fivetran Proxy Agent

Version 1.2.0

We have released Fivetran Proxy Agent version 1.2.0, which is bundled with High-Volume Agent versions 6.2.0_39 and 6.2.0_40. This release includes the following updates:

• Security updates: Updated the bundled JRE to Azul Zulu 17.64.17 (Java 17.0.18) to address multiple CVEs.
• Improved filesystem resilience: The file handler is now resilient to filesystem errors.
• Bug fix: Added the missing logType field to Proxy Agent log records.
• Bug fix: Fixed client_data_session_id mismatches in logs.
• Improved logging: Enhanced proxy process ID representation in logs.

You can download the updated package from the Downloads page.

Lite Connectors

Lite connectors are now available for the following sources:

• Adform
• Coda
• Credly
• Fathom
• IBACOS
• MaintainX
• Mollie
• National Heavy Vehicle Regulator
• Refiner
• Rivo

Logs

AWS CloudWatch

We have deprecated the Access Key authentication method for CloudWatch. Use the IAM Role authentication method instead.

In RESCHEDULED events, sync_end now always includes isRoutine

We now always include the isRoutine field in the sync_end log event when status is RESCHEDULED, including when the value is false. This field indicates whether a reschedule is an expected routine reschedule, true, rather than an error-driven one, false. For more information, see our Logs documentation.

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 in oldValues and newValues.
• 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: The delete_destination event now includes oldValues with the destination's name and service type. The service field is present only when deleting via DELETE /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 in oldValues.
• delete_proxy_agent: Logged when a proxy agent is deleted via the dashboard or API. Includes the agent name in oldValues.
• delete_connection: When a destination is deleted, Fivetran emits one delete_connection log event per connection as part of the cascade-deleted operation. These events have interactionMethod: "SYSTEM".

Partner SDK

MotherDuck

The MotherDuck destination is now generally available.

Read our MotherDuck destination documentation.

Quickstart Package Updates

Quickstart data model package updates

v1.5.1

Documentation

• Corrects field documentation to match what's used in our models from tax_rate and purchase_order tables.

v1.4.1

Bug Fix

• Fixes a datatype casting issue for email_list_id in int_iterable__list_user_unnest model that was causing Databricks warehouse errors.

v1.4.1

Bug Fix

• Fixes the adapter.dispatch() call in the netsuite_union_relations macro, which was incorrectly dispatching to the zendesk namespace instead of netsuite.

v1.5.1

Bug Fix

• Fixes a run error in netsuite2__balance_sheet that can occur when the Additional Account Columns (accounts_pass_through_columns) variable is configured.

v0.9.1

PR #31 includes the following update.

Under the Hood

• Updates integration_tests/dbt_project.yml to ensure that the employee history models are generated in the docs and picked up by Quickstart.

v2.5.2

Under the Hood

• Adds get_*_columns() macros for all staging source tables and updates the corresponding staging models to use fivetran_utils.fill_staging_columns(). Staging models now handle missing source columns gracefully by filling them with null rather than raising an error.
• Adjusts row_count__connection_daily_events test to dynamically reference connection or connector source tables

v1.8.0

Bug Fix

• For warehouses using the insert_overwrite strategy, updates the incremental filter in jira__daily_issue_field_history to align with the model’s partition grain. This helps prevent issues with incomplete partition coverage.
  • You must run a --full-refresh after upgrading to apply this fix to existing data.

Under the Hood

• Updates integrity test for jira__daily_sprint_issue_history to track the last sprint-related event per day, ensuring that only sprint IDs recorded at the final event timestamp for each issue/day are included.

v1.5.0

Schema/Data Change

3 total changes • 2 possible breaking changes

v1.2.1

Under the Hood

• Introduces the partition_by_source_relation macro to conditionally include source_relation in window function PARTITION BY clauses only when multiple sources are configured via the pinterest_ads_union_schemas and pinterest_ads_union_databases variables.
• Replaces hardcoded source_relation partitioning in the following models with the partition_by_source_relation macro:
  • stg_pinterest_ads__ad_group_history
  • stg_pinterest_ads__advertiser_history
  • stg_pinterest_ads__campaign_history
  • stg_pinterest_ads__keyword_history
  • stg_pinterest_ads__pin_promotion_history

v0.7.0

Schema/Data Change

2 total changes • 0 breaking changes

v1.2.1

Bug Fix

• Fixes a Redshift error in qualtrics__contact, qualtrics__survey, and qualtrics__distribution where percentile_cont raised a "Non supported data-type in order-by expression" error. Redshift requires float values in ORDER BY expressions within percentile_cont. The following fields are now cast to float on Redshift before being passed to the percentile calculation:
  • qualtrics__contact and qualtrics__survey: duration_in_seconds, progress
  • qualtrics__distribution: time_to_open_in_seconds, time_to_start_in_seconds, time_to_complete_in_seconds

Under the Hood

• Introduces the qualtrics_percentile macro to manage Redshift-specific percentile behavior. The macro dispatches to a Redshift implementation that applies the float cast, and delegates to fivetran_utils.percentile for all other warehouses.

v1.6.0

Schema/Data Changes

4 total changes • 1 possible breaking change

Feature Update

• For dbt Core users: Introduces using_customer_type variable to sync data from the customer_type source table. See the README on how to configure this variable.

v1.7.0

Under the Hood

• Updates stripe__subscription_item_mrr_report to cap the MRR date spine at the end of the current month instead of deriving it from the maximum current_period_end across all subscriptions. Because current_period_end is a future timestamp for active subscriptions, the previous approach generated rows for months that have not yet occurred. The model now reflects only months up to and including the current month. See the DECISIONLOG for more details.

Bug Fix

• Fixes a bug affecting a small number of customers due to the stripe__customer_metadata variable being erroneously included in the dbt_utils.star exception list of the customer_transactions_overview CTE of stripe__customer_overview. When the stripe__customer_metadata was enabled, it had the potential to cause model run failures due to column-count mismatches with union all branch.

v1.7.0

Schema/Data Changes (--full-refresh required after upgrading)

3 total changes • 3 possible breaking changes

Bug Fix

• Resolves an intermittent Databricks error in shopify__customer_emails and shopify_gql__customer_emails caused by a non-deterministic row_number() window function in int_shopify__customer_email_rollup and int_shopify_gql__customer_email_rollup. The ordering now includes customer_id as a tiebreaker so results are deterministic when multiple customers share the same email and created_timestamp. (#154)

v1.8.0

Schema/Data Changes

5 total changes • 5 possible breaking changes

v2.5.0

Upstream Breaking Change

• Increases the required google_ads package to version 1.3.0
  • This version includes configurable threshold variables for customizable diagnostic report optimization logic.

Schema/Data Change - Google Ads

8 total changes • 2 possible breaking changes

v1.2.0

Schema/Data Changes (--full-refresh required after upgrading)

4 total changes • 2 possible breaking changes

Upstream Dependency Changes

• Increases the required Shopify package to version 1.7.0. Refer to the dbt_shopify CHANGELOG for the full scope of upstream changes, including new refund and return models from version 1.6.0.

Bug Fixes

• Updated window functions in shopify_holistic_reporting__orders_attribution to partition by order_id and source_relation. Previously, in multi-source union setups, orders from different Shopify sources sharing the same order_id could be incorrectly grouped, resulting in wrong last-touch event selection and inflated campaign/flow interaction counts.

Under the Hood

• Added the partition_by_source_relation macro, which conditionally appends source_relation to a window function's PARTITION BY clause when multiple Shopify or Klaviyo sources are unioned. This centralizes multi-source partitioning logic and avoids repeating the union variable check across models.
• Added a DECISIONLOG entry documenting the source_relation partitioning behavior and the intentional omission of source_relation from the deduplication window in int__klaviyo_person_rollup.

v1.5.0

Feature Update

• Adds new variables to aggregate the netsuite2__balance_sheet and netsuite2__income_statement models, removing transactions and transaction lines from their granularity. By default, these models will continue to output data at the transaction line level. (PR #193)
  • netsuite2__aggregate_balance_sheet (default: false) When set to true:
    • netsuite2__balance_sheet outputs data at the account + accounting_period + subsidiary + account_category grain.
    • The primary key (balance_sheet_id) is hashed on (accounting_period_id, account_name, account_id, subsidiary_id, account_category, source_relation), plus to_subsidiary_id and accounting_book_id if included.
    • balance_sheet_transaction_detail_columns pass-through columns are ignored.
    • netsuite2__balance_sheet is run as a table instead of incrementally.
  • netsuite2__aggregate_income_statement (default: false) When set to true:
    • netsuite2__income_statement outputs data at the account + accounting_period + department + location + class grain.
    • The primary key (income_statement_id) is hashed on (accounting_period_id, account_name, subsidiary_id, department_id, location_id, class_id, source_relation), plus to_subsidiary_id and accounting_book_id if included.
    • income_statement_transaction_detail_columns pass-through columns are ignored.
    • netsuite2__income_statement is run as a table instead of incrementally.
• Adds support for Fivetran's history mode for the Netsuite2 source tables that currently support it (PR #195). When history mode is enabled in your Fivetran connector, the staging models below now filter on _fivetran_active to include only current, active records. Users without history mode enabled are unaffected, while users with history mode will see a drop in records (full refresh recommended):
  • stg_netsuite2__accounting_books
  • stg_netsuite2__accounting_periods
  • stg_netsuite2__accounts
  • stg_netsuite2__currencies
  • stg_netsuite2__customer_subsidiary_relationships
  • stg_netsuite2__customers
  • stg_netsuite2__departments
  • stg_netsuite2__employees
  • stg_netsuite2__entities
  • stg_netsuite2__entity_address
  • stg_netsuite2__items
  • stg_netsuite2__jobs
  • stg_netsuite2__location_main_address
  • stg_netsuite2__locations
  • stg_netsuite2__subsidiaries
  • stg_netsuite2__transactions
  • stg_netsuite2__vendor_categories
  • stg_netsuite2__vendor_subsidiary_relationships
  • stg_netsuite2__vendors

Only currently active records are included, while inactive records are filtered out. Please open a Feature Request if you would like historical records to be persisted.

Under the Hood

• Adds partition_by_source_relation() macro to avoid constant expression errors in Redshift.
• Limits the current accounting period from consistency data validation tests.
• Consolidates duplicative joins in netsuite2__balance_sheet
• Adds _fivetran_active to the get_netsuite2_*_columns() macros and src_netsuite2.yml source definitions for all 19 affected tables.
• Documents _fivetran_active in models/docs.md.

v1.3.0

Schema/Data Change

8 total changes • 2 possible breaking changes

Feature Updates

• New configurable threshold variables - Introduces customizable threshold variables for diagnostic report optimization logic. See Configure diagnostic report thresholds in the README for configuration examples.

Under the Hood

• Adds ephemeral intermediate model int_google_ads__campaigns_accounts providing shared campaign and account dimensional data.
  • Refactors existing reports (ad_group_report, ad_report, keyword_report, search_term_report, url_report) to use shared int_google_ads__campaigns_accounts intermediate model.
• Adds the get_threshold_high_lows macro that processes diagnostic threshold configurations for use in budget and bid recommendations.
• Removes unused field descriptions (absolute_top_impression_percentage) from source documentation as they are not used in downstream reports.

v1.6.0

Schema/Data Changes

21 total changes • 9 possible breaking changes

Under the Hood

• Adds YAML documentation for new models and columns.
• Updates seed files to reflect corrected column names and new columns.
• Removes DECISIONLOG entry for aggregating returns on order date to reflect that returns are now correctly applied on the refund date, matching Shopify finance report behavior.

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.

The schema_status property removal for several connectors

After optimizing schema fetch for the connectors below, these connections no longer use the pre-initial-sync schema capture flow described in schema_status.

Affected connectors

• Adyen
• Amazon Ads
• Amplitude
• AWS CloudTrail
• Coupa
• Facebook Pages
• GitHub
• Instagram Business
• Apple App Store
• LinkedIn Company Pages
• Outbrain
• SAP Business ByDesign
• Shopify
• Twilio
• Twitter
• Workday Financial Management
• Workday HCM
• Xero
• YouTube Analytics

REST API request changes (breaking)

For the connectors listed above, the schema_status request field is no longer supported in:

• Update a Connection

If your automation still sends schema_status for these connectors, requests may fail.

REST API response changes

For the connectors listed above, schema_status is no longer returned for flows that previously exposed it, including:

• List All Connections
• Create a Connection
• Retrieve Connection Details
• Update a Connection
• Run Connection Setup Tests
• List All Connections within a Group

If your downstream transformations or orchestration rely on this field, update them to handle its absence.

Dashboard flow change

In the Fivetran dashboard, these connectors no longer show the schema prefetch and review step before initial sync. After connection creation, you proceed directly to the initial sync flow.

Transformations for dbt Core

dbt Core version adoption

We have added support of dbt Core version 1.11.8 for the following destinations:

• BigQuery
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server

We now support the following destinations for dbt Core version 1.10.20:

• ClickHouse Cloud
• Redshift
• SQL Server

We now support the following destinations for dbt Core version 1.11.5:

• Redshift
• SQL Server

We now support the following destinations for dbt Core version 1.11.7:

• ClickHouse Cloud
• Redshift
• SQL Server

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_REPORT
• NET_PURE_PRODUCT_MARGIN_REPORT_WEEKLY
• REPEAT_PURCHASE_REPORT_WEEKLY
• SEARCH_TERMS_REPORT_WEEKLY
• SETTLEMENT_REPORT
• STORAGE_FEE_CHARGES_REPORT
• VENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_WEEKLY
• VENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_WEEKLY
• VENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_WEEKLY
• VENDOR_INVENTORY_SOURCING_RETAIL_REPORT_WEEKLY
• VENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_WEEKLY
• VENDOR_SALES_MANUFACTURING_RETAIL_REPORT_WEEKLY
• VENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_WEEKLY
• VENDOR_SALES_SOURCING_RETAIL_REPORT_WEEKLY
• VENDOR_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 the following new tables:

• JOB_SUMMARY. The table contains job opening summaries, including title, location, department, status, hiring lead, and applicant counts for each open position.
• JOB_APPLICATION. The table contains applicant tracking data for job applications, including applicant details, application status, rating, and associated job information.

Braze

We have added the following three new columns to the MESSAGE_VARIATION table:

• action
• image_url
• large_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_id
• flow_id
• in_reply_to
• message_id
• product_id
• template_name

We have added a new table, WHATSAPP_FLOW_RESPONSE, to store WHATSAPP_EVENT flow response data.

Campfire

Cin7 Core

Coupa

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

• manufacturer_name
• manufacturer_part_number

To backfill the historical data for these columns, re-sync the ORDER table.

Criteo Retail Media

Eloqua

We have added a new column, email_clickthrough_saved_id, to the CONTACT_ACTIVITY table.

Employment Hero

Facebook Pages

We've added three new columns:

• permalink_url to the POST_HISTORY table
• page_total_media_view_unique to the UNIQUE_DAILY_PAGE_METRICS_TOTAL table
• post_total_media_view_unique to the UNIQUE_LIFETIME_POST_METRICS_TOTAL table

Factbird

Fortnox

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_METRIC
• COPILOT_METRIC_TEAM
• DOTCOM_CHAT_MODEL
• DOTCOM_CHAT_MODEL_TEAM
• DOTCOM_PULL_REQUEST_REPOSITORY
• DOTCOM_PULL_REQUEST_REPOSITORY_MODEL
• DOTCOM_PULL_REQUEST_REPOSITORY_TEAM
• DOTCOM_PULL_REQUEST_REPOSITORY_MODEL_TEAM
• IDE_CHAT_EDITOR
• IDE_CHAT_EDITOR_MODEL
• IDE_CHAT_EDITOR_TEAM
• IDE_CHAT_EDITOR_MODEL_TEAM
• IDE_CODE_COMPLETION_EDITOR
• IDE_CODE_COMPLETION_EDITOR_MODEL
• IDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE
• IDE_CODE_COMPLETION_EDITOR_TEAM
• IDE_CODE_COMPLETION_EDITOR_MODEL_TEAM
• IDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE_TEAM
• IDE_CODE_COMPLETIONS_TOTAL_LANGUAGE
• IDE_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>_PIPELINE to store pipeline definitions for the custom object type
• <CUSTOM_OBJECT_NAME>_PIPELINE_STAGE to store stage definitions for the custom object pipelines

We have added the following new tables to store Listings object data:

• LISTING
• LISTING_COMPANY
• LISTING_CONTACT
• LISTING_DEAL
• LISTING_ENGAGEMENT
• LISTING_PIPELINE
• LISTING_PIPELINE_STAGE
• LISTING_PROPERTY_HISTORY
• LISTING_TICKET

We have added the following new tables to store Orders object data:

• ORDER
• ORDER_COMPANY
• ORDER_CONTACT
• ORDER_DEAL
• ORDER_ENGAGEMENT
• ORDER_FEEDBACK_SUBMISSION
• ORDER_INVOICE
• ORDER_LINE_ITEM
• ORDER_PAYMENT
• ORDER_PIPELINE
• ORDER_PIPELINE_STAGE
• ORDER_PROPERTY_HISTORY
• ORDER_QUOTE
• ORDER_TICKET

We have added the following new tables to store Projects object data:

• PROJECT
• PROJECT_COMPANY
• PROJECT_CONTACT
• PROJECT_DEAL
• PROJECT_ENGAGEMENT
• PROJECT_LISTING
• PROJECT_PIPELINE
• PROJECT_PIPELINE_STAGE
• PROJECT_PROPERTY_HISTORY
• PROJECT_SERVICE
• PROJECT_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_reposts
• carousel_album_reposts
• reel_reposts
• reel_crossposted_views
• reel_facebook_views
• reels_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 column, predictive_analytics_ranked_channel_affinity, to the PERSON table.

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_CONSENT
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_TIMESTAMP
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_METHOD
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_METHOD_DETAIL
• SUBSCRIPTIONS_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_type
• test
• daily_budget
• total_budget_amount
• total_budget_currency_code
• budget_optimization_bid_strategy
• budget_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:

• clicks
• subscriber_clicks
• click_rate
• opens
• unique_opens
• open_rate These columns contain report summary statistics sourced from the report_summary object in the Mailchimp API response.

Microsoft Advertising

We have added a new column, final_url_suffix, to the following tables:

• AD_GROUP_HISTORY
• AD_HISTORY
• CAMPAIGN_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

OneTrust

Oracle Fusion Field Service

Outbrain

We've added the following new columns to the PROMOTED_LINK_HISTORY table:

• creative_format
• description
• title

We've added the cpm, roas, and total_roas columns to the following tables:

• CAMPAIGN_REPORT
• PROMOTED_LINK_REPORT
• GEOLOCATION_REPORT
• SECTION_REPORT
• PUBLISHER_REPORT

We've added a new table, CROP_POINT. The table contains crop point data associated with image metadata entries.

Paylocity

Pendo

We have added the following new tables:

• SEGMENT_HISTORY
• SEGMENT_FILTER
• SEGMENT_PIPELINE
• SEGMENT_DEPENDENT_METADATA

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

Procore

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

Ramp

Reddit Ads

We've added the following new columns to all non-conversion report tables:

• app_install_mmp_install_count
• app_install_mmp_total_install_count
• app_install_skan_install_count
• app_install_skan_total_install_count

These columns are a substitute for app_install_install_count, which will be deprecated in May 2026.

Revel Systems

RTB House

Sailthru

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

• abtest_id
• abtest_percent
• abtest_segment
• label_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:

• AnalyticsChangeEventLog
• AnalyticsDownloadEventLog
• AnalyticsInteractEventLog
• AnalyticsPerfEventLog
• ApexCalloutEventLog
• ApexExecutionEventLog
• ApexExtlCalloutEventLog
• ApexRestApiEventLog
• ApexSoapApiEventLog
• ApexTriggerEventLog
• ApexUnexpectedExcpEventLog
• ApiTotalUsageEventLog
• AsyncReportRunEventLog
• AttachmentEventLog
• AuraRequestEventLog
• BlockedRedirectEventLog
• BulkApiEventLog
• BulkApi2EventLog
• BulkApiRequestEventLog
• ChangeSetOperationEventLog
• ConcurApexLimitEventLog
• ContentDistributionEventLog
• ContentDocLinkEventLog
• ContentTransferEventLog
• ContCalloutSummaryEventLog
• CspViolationEventLog
• DatabaseSaveEventLog
• DocAtchDownloadEventLog
• FlowNavMetricEventLog
• GroupMembershipEventLog
• InsufficientAccessEventLog
• InvocableActionEventLog
• KnowledgeArticleEventLog
• LightningErrorEventLog
• LightningLoggerEventLog
• LightningPageViewEventLog
• LightningPrfmEventLog
• LoginAsEventLog
• LoginEventLog
• LogoutEventLog
• MetadataApiOpEventLog
• NamedCredentialEventLog
• PackageInstallEventLog
• PermissionUpdateEventLog
• QueuedExecutionEventLog
• ReportEventLog
• ReportExportEventLog
• RestApiEventLog
• SalesforceLoginAsEventLog
• SandboxStatusEventLog
• SiteEventLog
• SearchEventLog
• SearchClickEventLog
• SoapApiEventLog
• TransactionSecurityEventLog
• UniqueQueryEventLog
• UriEventLog
• UiAgentInteractionEventLog
• UiTelemetryNavTmEventLog
• UiTelemetryRsrcTmEventLog
• VisualforceRequestEventLog

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.

Salesforce Commerce Cloud

We have added two new tables, PRICE_BOOK and PRICE_BOOK_SITE_ASSIGNMENT. The two tables need the sfcc.price-books authorization scope for the API client. We are gradually rolling out this change to all existing connections.

SAP Concur

We've added the following new tables:

• VENDOR. The table contains vendor records from the SAP Concur Invoice module.
• VENDOR_BANK. The table contains bank account information associated with vendors.
• VENDOR_STATUS. The table contains status messages associated with vendor records.
• VENDOR_GROUP. The table contains group associations for vendors.
• VENDOR_BANK_STATUS. The table contains status messages associated with vendor bank records.

Segment

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

• channel
• company_employee_count
• company_id
• company_industry
• company_name
• company_plan
• context_device_advertising_id
• context_device_ad_tracking_enabled
• context_device_token
• id
• original_timestamp
• plan

We have added the following new columns to the GROUPS, PAGES, SCREENS, and TRACKS tables:

• channel
• context_device_advertising_id
• context_device_ad_tracking_enabled
• context_device_token
• original_timestamp

We have added a new column, plan, to the GROUPS table.

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

• path
• title
• url

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

• category
• coupon
• discount
• order_id
• price
• product_id
• quantity
• shipping
• sku
• subtotal
• tax
• total

ShipStation

Shopify

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

• default_email_address
• default_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_month
• exp_year
• last4

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

• billing_mode_flexible_proration_discounts
• billing_mode_type
• billing_mode_updated_at
• next_pending_invoice_item_invoice
• pending_invoice_item_interval
• pending_invoice_item_interval_count

SurveyMonkey

We have added a new column, tag_data, to the RESPONSE_ANSWER table.

We have added new columns to the SURVEY_HISTORY table:

• buttons_text_exit_button
• buttons_text_prev_button
• buttons_text_done_button
• buttons_text_next_button
• is_owner
• question_count
• preview
• response_count
• collect_url
• edit_url
• href
• analyze_url
• summary_url
• page_count

We have added new columns to the SURVEY_PAGE_HISTORY table:

• question_count
• href

Tableau

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.

We've added the following new columns to the ADGROUP_HISTORY table:

• messaging_app_type
• messaging_app_account_id
• phone_region_code
• phone_region_calling_code
• phone_number
• message_event_set_id
• deep_funnel_optimization_status
• deep_funnel_event_source
• deep_funnel_event_source_id
• deep_funnel_optimization_event
• automated_keywords_enabled
• app_config_app_ids
• custom_conversion_id
• is_lhf_compliance

We've also added the ADGROUP_SEARCH_KEYWORD_HISTORY table, which syncs information about search keywords data for a specific ad group, such as keyword, match type, keyword bid type, keyword bid, and audit status.

Twilio

We've added the following new columns to the CONVERSATION table.

• url
• attributes
• timer_date_inactive
• timer_date_closed

We've added the following new columns to the CONVERSATION_MESSAGE table.

• url
• attributes
• delivery_total
• delivery_sent
• delivery_delivered
• delivery_read
• delivery_failed
• delivery_undelivered

We've added new columns, url and attributes, to the CONVERSATION_USER table.

We've added a new table, CONVERSATION_MESSAGE_MEDIA. The table contains one row per media attachment on a conversation message, including content type, filename, and size.

Workday Financial Management

We have added a new child table, CUSTOMER_INVOICE_LINE_WORKTAG, to the CUSTOMER_INVOICE table.

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_SERVICE
  • PERSON_DISABILITY
  • PERSONAL_INFORMATION_ETHNICITY
  • RELATIVE_NAME

• Renamed the following legacy tables:

  • MILITARY_SERVICE to MILITARY_SERVICE_BACKUP
  • PERSON_DISABILITY to PERSON_DISABILITY_BACKUP
  • PERSONAL_INFORMATION_ETHNICITY to PERSONAL_INFORMATION_ETHNICITY_BACKUP
  • RELATIVE_NAME to RELATIVE_NAME_BACKUP

• Renamed the following new tables:

  • MILITARY_SERVICE_INCOMING to MILITARY_SERVICE
  • PERSON_DISABILITY_INCOMING to PERSON_DISABILITY
  • PERSONAL_INFORMATION_ETHNICITY_INCOMING to PERSONAL_INFORMATION_ETHNICITY
  • RELATIVE_NAME_INCOMING to RELATIVE_NAME

• Stopped syncing data into the following columns of the PERSONAL_INFORMATION table, which are now available in the COUNTRY_PERSONAL_INFORMATION and PERSONAL_INFORMATION_COMMON_DATA tables:

  • additional_nationality
  • blood_type
  • city_of_birth
  • city_of_birth_code
  • citizenship_status
  • country_of_birth
  • country_region_of_birth
  • date_of_birth
  • date_of_death
  • gender
  • hispanic_or_latino
  • hukou_locality
  • hukou_postal_code
  • hukou_region_code
  • hukou_subregion_code
  • hukou_type_code
  • last_medical_exam_date
  • last_medical_exam_valid_to
  • local_hukou
  • marital_status
  • marital_status_date
  • medical_exam_notes
  • native_region
  • native_region_code
  • personnel_file_agency_for_person
  • political_affiliation
  • primary_nationality
  • region_of_birth
  • religion
  • social_benefits_locality

Be sure to update your downstream queries to reflect these changes. To backfill historical data for the renamed tables, re-sync them.

We have added two new columns, position_worker_type and worker_type, to the WORKER_POSITION table.

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_ITEMS
• CREDIT_NOTE_LINE_ITEM
• INVOICE_LINE_ITEM
• OVERPAYMENT_LINE_ITEM
• PREPAYMENT_LINE_ITEM
• PURCHASE_ORDER_LINE_ITEM
• RECEIPT_LINE_ITEM
• REPEATING_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

Adobe Analytics Data Feed

We have updated our sync strategy. Now, in each report suite's main data table, the following post_* columns contain human-readable values that we resolve from the Adobe lookup files:

• post_browser
• post_color
• post_connection_type
• post_country
• post_event_list
• post_javascript
• post_language
• post_os
• post_resolution
• post_search_engine

Previously, the values were raw numeric IDs.

The changes are consistent with how we sync matching non-post_ columns (such as browser, color, and connection_type).

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.

Amazon Selling Partner

We have added a 30-day rollback window for the SALES_AND_TRAFFIC_BUSINESS_REPORT_DAILY report to ensure more complete historical data is captured during syncs.

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.

Email

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
• Email
• 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.

We have modified how the _line system column reflects the row position in your destination. The _line system column now displays its physical row position in the source file, even if we skip rows from the sync due to the on_error=skip setting in your destination. Therefore, if we now skip syncing a physical row, the position of the _line column in your destination will remain unchanged. It will always match the corresponding row positions in the source file to ensure a consistent mapping between the source file and your destination. Previously, we updated the _line column sequentially, which was calculated based on the rows that were successfully synced. This change is available only for new connections created after April 22, 2026.

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_id and client_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.

We have added two new options, FORM and SEGMENT to select the custom report type in the connection setup form. You can now select the FORM and SEGMENT custom reports from the Type drop-down menu while configuring your connection in Pack Mode. For more information, see the setup instructions and the REST API Configuration.

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

We have added support for the PostgreSQL 18 idle_replication_slot_timeout parameter. For more information, see our PostgreSQL documentation.

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_type
  • app_id
  • app_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_id column 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.

SAP OData

The SAP OData connector is now available in Beta. You can now set up SAP OData connections without requesting Private Preview access.

For more information, see our SAP OData documentation and SAP OData Setup Guide.

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_SUBSCRIBER table to capture new records.
• We now support priority-first sync for the MESSAGE table. 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 is now generally available.

Read our Workday Adaptive Planning documentation for more information.

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_keys parameter
• Removed the report_format_type parameter
• Removed the report_url parameter
• Removed the support_nested_columns parameter
• Removed the generate_fivetran_pk parameter

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