March 2026

Connector SDK

fivetran-connector-sdk PyPI package

We have released version 2.7.2 of the fivetran-connector-sdk PyPI package. This release includes the following updates:

• Security fixes for vulnerabilities in requests package.
• Improved overall performance and stability.
• Minor enhancements and improvements.
• Updated testers.

We have released version 2.7.1 of the fivetran-connector-sdk PyPI package. This release includes the following updates:

• Improved logging for fivetran debug and fivetran reset
• Minor enhancements and improvements.
• Updated tester - fixed vulnerabilities and logging.

We have released version 2.7.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates:

• Changes the default Python version to 3.13 since the Performance Profiling feature uses py-spy, which is not supported by Python versions > 3.13. You can still change the runtime Python version to 3.14 by using --python-version argument passed to fivetran deploy command or directly from the setup form after deployment.
• Minor enhancements and improvements.

We have released version 2.6.2 of the fivetran-connector-sdk PyPI package. This release includes the following updates:

• A new help command for the PyPI package that provides users with additional information about the package and its usage.
• Improved error handling and logging.
• Better handling of conflicting packages.
• Minor enhancements and improvements.

Fivetran Connector SDK

Connector SDK connectors now support VPN tunnel as a connection option. A VPN tunnel provides a secure, encrypted site-to-site VPN connection between your network and Fivetran's network, enabling your connector code to access your source over a private network. You must have an Enterprise or Business Critical plan to use a VPN tunnel connection for Connector SDK.

We've enabled performance profiling for Connector SDK syncs. You can now analyze CPU usage and code execution time using flamegraphs generated via py-spy, available for production syncs (if supported) and local debugging.

For more information, including how to analyze flamegraphs, see our Performance Profiling documentation.

fivetran-api-playground PyPI package

We have released version 1.1.4 of the fivetran-api-playground PyPI package. This release adds the following:

• Upgrades the flask library dependency to 3.1.3 .
• Upgrades the faker library dependency to 40.4.0 .
• Upgrades the colorama library dependency to 0.4.6 .

We have released version 1.1.5 of the fivetran-api-playground PyPI package. This release adds support for session token expirations. Session tokens now expire after 1 hour, and the login endpoint returns an expires_in field indicating the token's validity period.

Dashboard Improvements

Schema change details in events list

You can now view detailed information about schema changes directly on the Connection Status tab in the Fivetran dashboard. When you click on a schema change event in the events list, a detail view displays the total count of changes and organizes them into categories:

• Schemas: Schemas that were enabled or disabled
• Tables: Tables that were selected or deselected for syncing
• Columns: Columns that were enabled or disabled, and changes to column hashing and encryption settings
• Sync modes: Changes to table sync settings (soft delete, history mode, or live sync)

This read-only view allows you to see exactly what was changed in a schema update without leaving the Status page.

For more details, see our Connection Status documentation.

Lite Connectors

Lite connectors are now available for the following sources:

• Campfire

Logs

Azure Monitor

Our Azure Monitor external logging service now supports the Log Ingestion API. The Log Ingestion API replaces the legacy Data Collector API and provides improved reliability, flexibility, and support for Data Collection Rules (DCR)-based log routing.

Datadog

We've added support for the AP2 region for the Datadog external logging service.

Grafana Loki External Logging

We now support Grafana Loki as an external logging service. You can connect Grafana Loki at both the account and destination levels to collect and query your Fivetran logs. We are gradually rolling out this feature to all accounts.

To set up Grafana Loki logging services, go to Account Settings > General > External Logging or go to your destination settings in your Fivetran dashboard. For more information, see our Grafana Loki Setup guide.

Query execution time in extract_summary log event

The extract_summary log event now includes two new execution time fields for database connectors:

• total_execution_time — the total accumulated query execution time in milliseconds across all tables during the sync.
• execution_time — the accumulated query execution time in milliseconds for each individual entry in the objects array.

These fields give you visibility into which tables have the highest query execution cost, helping you identify performance bottlenecks at the table level.

Partner SDK

Partner-Built Program

At this time, we are not accepting new submissions to the Partner-Built program.

MotherDuck

The MotherDuck destination is now in beta.

Read our MotherDuck destination documentation.

Quickstart Package Updates

Quickstart data model package updates

v1.3.1

Documentation

• Removes dynamic count_visitors_* columns from the pendo__guide and pendo__guide_daily_metrics models in pendo.yml to prevent persist_docs errors when these columns are not present.

v1.4.1

Documentation

• Removed documentation from zendesk.yml for dynamic columns from zendesk__ticket_field_history and zendesk__ticket_backlog to prevent persist_docs errors when these columns are not present.

v0.6.3

Bug Fix

• Fixes a SQL compilation error on BigQuery in the bsid and bsad models to cast _dataaging to string to avoid datatype failures, ensuring consistent types regardless of how the source column is synced.

v0.1.0

Bug Fix

• Updates the string_mapping macro to pass a warning in cases where no mapping fields are found.

Under the Hood

• Updates integration tests and seed data to test when no string mapping fields are found.

v1.5.2

Documentation

• In the quickstart.yml file:
  • Made several corrections to Quickstart supported_vars descriptions to reflect correct time granularity for jira_issue_history_buffer and lookback_window variables.

v1.4.2

Bug Fix

• Fixes PostgreSQL compatibility issue in get_url_tags_query() macro where jsonb columns were incorrectly processed using json_array_elements() instead of jsonb_array_elements(), causing database errors when url_tags column is stored as jsonb datatype.

v1.6.1

Bug Fix

• Updates the subscription_discount source column reference from checkout_session_id to checkout_session to match the raw Stripe source naming convention. The output column name checkout_session_id is preserved as an alias in the staging layer, so there is no downstream impact.

v0.6.2

Documentation

• Adds missing, removes stale, and corrects column-level descriptions for the following models:
  • marc
  • mchb
  • mkpf
  • mseg
  • sap__0fi_gl_14
  • sap__0material_attr
  • stg_sap__bseg
  • stg_sap__dd07l
  • stg_sap__dd07t
  • stg_sap__marc
  • stg_sap__mchb
  • stg_sap__mchp

v0.3.2

Documentation

• Updates column descriptions for line_item_line_item_type and related fields to be more concise.
• Updates README to remove badges and replace with plain-text dbt Core version compatibility.

Under the Hood

• Adds a persist_docs conditional to integration tests to enable relation and column documentation persistence, except for Databricks targets.

v1.3.3

Documentation

• Updates user_id column descriptions in stg_amplitude, amplitude_event_enhanced, and amplitude_session_enhanced for clarity and conciseness.
• Updates the README to remove badge images and add dbt Core™ supported version information in plain text.

Under the Hood

• Adds persist_docs configuration to integration_tests/dbt_project.yml to validate column-level documentation persistence.

v1.7.2

Schema/Data Change

1 total change • 0 possible breaking changes

v0.8.2

Feature Updates

• Updates the quickstart.yml:
  • Adds workday__employee_daily_history, workday__monthly_summary, and workday__worker_position_org_daily_history to the list of public models.
  • Adds supported_vars entry for employee_history_start_date to allow users to configure the employee history start date in Quickstart.
  • Adds employee_history_enabled table variables for worker_history, worker_position_history, and personal_information_history to prevent missing sources from blocking downstream Quickstart models.

v1.5.1

Bug Fix

• Fixes non-deterministic SLA reply time calculations in int_zendesk__reply_time_business_hours and int_zendesk__reply_time_combined for tickets with multiple SLA policies. Previously, lapsed_business_minutes and breach calculations mixed results across policies when the same ticket_id, metric, and sla_applied_at had more than one sla_policy_name. Window functions now partition by sla_policy_name to correctly isolate each policy's calculation.

v1.4.1

Bug Fix

• Updates URL tag processing to handle native JSON datatypes across all supported warehouses, preventing errors when url_tags columns are stored as JSON/JSONB/VARIANT/SUPER instead of strings.

Feature Update

• Adds the get_column_datatype() macro to retrieve the datatype of a specific column.
• Updates the get_url_tags_query() macro with datatype detection to handle both native JSON columns and JSON-like string columns across BigQuery (JSON), Snowflake (VARIANT), Redshift (SUPER), and PostgreSQL (JSONB).

Under the Hood

• Adds native JSON testing to integration_tests.
• Updates the vertical_sum_conversion_value integrity test to validate both conversions_value and conversions.

v1.6.0

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

1 total change • 1 possible breaking change

v1.5.0

Schema/Data Change

4 total changes • 2 possible breaking changes

Under the Hood

• Replaces reference to stg_zendesk__user with int_zendesk__user_aggregates in zendesk__ticket_summary to better align with dbt best practices and reduce DAG complexity.

v1.4.2

Bug Fixes

• With variable configuration now available in Quickstart, the quickbooks__home_currency variable from the v1.1.1-a2 pre-release is now available across all 13 intermediate double-entry transaction models to optimize multi-currency handling. When the variable is set, transactions in the designated home currency will not apply exchange rate conversions on converted_amount, improving accuracy. When left empty, all transactions will see exchange rate conversions applied. (PR #197)
  • Updates the README with instructions for configuring the quickbooks__home_currency variable.
• Applies fixes in int_quickbooks__sales_receipt_double_entry model to correctly reference quickbooks__global_tax_account_reference and quickbooks__sales_tax_account_reference variables. (PR #197)
• 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 quickbooks_union_schemas and quickbooks_union_databases variables. This resolves partition by constant expression errors on Redshift. See the README on how to leverage these variables. (PR #198)

Under the Hood

• Changes default quickbooks__home_currency value to empty string for easier understanding within Quickstart UI. (PR #197)

v1.6.0

Schema/Data Changes

3 total changes • 0 possible breaking changes

Bug Fixes

• Removes convert_values macro from amount calculation in stripe__subscription_item_mrr_report. The macro is already applied at the staging layer and applying it to the metric calculation was causing a double conversion, leading to potential undercalculation of MRR values when stripe__convert_values was set to true.
• Adds convert_values macro to amount_off field value in stg_stripe__coupon table to ensure correct conversion of discounted amount when customers have the variable set to true.

Under the Hood

• Updates int_stripe__subscription_discount to source from the subscription_discount table via the new stg_stripe__subscription_discount staging model, instead of sourcing from the discount table via stg_stripe__discount.
• Adds integration test seed files subscription_discount_data.csv, subscription_discount_data_snowflake.csv, and subscription_discount_data_postgres.csv.

v1.7.0

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

3 total changes • 3 possible breaking changes

Bug Fix

• Updated stg_jira__sprint to filter out soft-deleted sprint records using the _fivetran_deleted flag.

Under the Hood

• Adds a new convert_string_to_numeric macro with warehouse-specific dispatch implementations to safely cast story point string values to numeric, handling edge cases such as comma-formatted numbers.

Documentation

• Updates model descriptions to remove static documentation for story_points, story_point_estimate, and team columns. Removes story point-related column documentation from jira__sprint_enhanced as these columns are dynamic and only present when added to var('issue_field_history_columns').
  • To retain story point data, add story points and/or story point estimate to the issue_field_history_columns variable in your dbt_project.yml (See the README for details). Quickstart users can add these fields in the Issue Field History Columns setting.

v1.4.0

Schema Changes

5 total changes • 0 possible breaking changes

Feature Update

• Adds support for the sla_policy_metric_history and ticket_sla_policy source tables to enable more granular SLA policy tracking based on ticket priority levels.
  • These new tables are dynamically enabled in Fivetran Quickstart based on whether they are being actively synced. For dbt Core users, the tables are enabled by default but can be disabled with the following configuration in your dbt_project.yml:

vars:
  using_sla_policy_metric_history: false
  using_ticket_sla_policy: false

• Adjusts SLA policy logic to use the current ticket priority level's targets for calculating metrics. Previously, targets were taken from the priority that a ticket was first assigned to.

Bug Fixes

• Updates Snowflake regex parsing in the extract_schedule_day() macro.
• Aligns with Zendesk's method of calculating agent replies and comment metrics for messaging/chat. Previously, we counted each individual chat message as a distinct comment. In accordance with Zendesk's docs, we now count active conversation sessions.
  • For example, if an agent sends three messages in the same active conversation and then the conversation ends, that exchange counts as one Agent reply. Previously, we would have counted three replies.

v1.4.0

Schema/Data Change

22 total changes • 21 possible breaking changes

Under the Hood

• Corrected get_*_columns macro fields for invoice_history, line_item_history, subscription_history that were cast as int instead of float to match the Recurly API type (number <float>).

Documentation

• Fixes link to streamlit_fivetran_billing_model repo in the README.

Quickstart Transformations

Custom naming convention for Quickstart Data Models

We have added support for custom schema naming convention in Quickstart Data Models. You can now define the naming convention of the schema in the destination where your staging and transformed models will land. For more details, see the Edit Schema Naming Conventions for Quickstart Transformations section.

Table and column descriptions persisted to destinations for Quickstart Data Models

Quickstart Data Models now automatically persist table descriptions as table comments and column descriptions as column comments to your destination, making your data more self-documenting and discoverable without additional configuration. Model descriptions are stored as table comments, and column descriptions are stored as column comments in your destination warehouse.

For Databricks, column-level comments are not supported.

Transformations for dbt Core

dbt Core version adoption

We have added support of dbt Core version 1.10.19 and 1.10.20 for the following destinations:

• BigQuery
• ClickHouse Cloud (1.10.19 is only available for now)
• Databricks
• PostgreSQL
• Redshift (1.10.19 is only available for now)
• Snowflake
• Teradata Vantage

We have added support of dbt Core version 1.11.6 and 1.11.7 for the following destinations:

• BigQuery
• ClickHouse Cloud (1.11.6 is only available for now)
• Databricks
• PostgreSQL
• Redshift (1.11.6 is only available for now)
• Snowflake
• Teradata Vantage

Type Locking

The type locking feature is now in beta. Type locking lets you lock the data types of your connection's columns in the destination.

For more information, see our Type Locking documentation.

New connectors

Smartsheet connector is in beta

The Smartsheet connector is now in beta. For more information, see the Smartsheet connector documentation.

Schema changes

We now automatically remove schemas and tables from the Schema tab in your dashboard if they were deleted from the source. The deletion occurs after a 7-day grace period.

All Fivetran connectors, apart from the ones that do not supply source schema information, support this feature.

ADP Workforce Now

We have added the following new child tables to the WORKER table:

• WORKER_PAID_TIME_OFF_ENTRY
• WORKER_PAID_TIME_OFF_REQUEST
• WORKER_PAID_TIME_OFF_ACCRUAL_BALANCE
• WORKER_PAID_TIME_OFF_BALANCE

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

BambooHR

We've added a new table, TIME_OFF_REQUEST_DATE. The table contains daily time-off date breakdowns for each time-off request, showing the specific dates and amounts for each day within a request period.

We've added a new table, TIMESHEET_ENTRY. The table contains time tracking records for employees, including clock-in/clock-out entries and hour-based entries, with optional project and task associations.

Braintree

We have added a new column, graphql_id, to the TRANSACTION table. The column contains the unique global identifier for the transaction in Braintree's GraphQL API. We have added the following new columns to the DISPUTE table:

• chargeback_protection_level
• graphql_id
• pre_dispute_program

Braze

We have added a new table, USER_DEVICE, to store device-level information for users. We are gradually rolling out this change to all existing connections.

Chargebee Product Catalog 2.0

Coupa

We have added the following new tables:

• QUOTE_REQUEST_ATTACHMENT_RESPONSE
• QUOTE_REQUEST_ATTACHMENT_RESPONSE_MAPPING
• QUOTE_RESPONSE
• QUOTE_RESPONSE_LINE
• QUOTE_RESPONSE_LINE_ATTACHMENT_MAPPING
• QUOTE_RESPONSE_LINE_EASY_FORM_DATA_MAPPING

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

Criteo

Our Criteo connector now supports custom reports. On the connection setup form, you can add campaign statistics custom reports. To learn more, see our Criteo Custom Reports documentation and the Criteo Setup Guide.

We've added the LOG_LEVEL_REPORT table to the Criteo connector, which supports log-level reports. This table provides device-level granular reporting data, enabling you to analyze individual advertising events with detailed information about user interactions, devices, and costs.

e-conomic

EasyPost

Employment Hero

Facebook Ads

We have added new columns to the CREATIVE_HISTORY table. These columns surface additional fields from the Ad Creative Video Data endpoint.

• video_call_to_action_type
• video_image_hash
• video_image_url
• video_link_description
• video_message
• video_page_welcome_message
• video_title

Facebook Pages

We have added the following new tables:

• DAILY_PAGE_METRICS_BY_EARNING_SOURCE
• DAILY_PAGE_METRICS_BY_MONETIZATION_TOOL
• DAILY_PAGE_MONETIZATION_METRICS
• DAILY_POST_METRICS_BY_MONETIZATION_TOOL
• DAILY_POST_MONETIZATION_METRICS
• LIFETIME_POST_METRICS_BY_MONETIZATION_TOOL
• LIFETIME_POST_MONETIZATION_METRICS

Fivetran Platform Connector

We've added support for schema, table, and column deletion events. These events are available in the SOURCE_SCHEMA_CHANGE_HISTORY, SOURCE_TABLE_CHANGE_HISTORY, and SOURCE_COLUMN_CHANGE_HISTORY tables of the Fivetran Platform connector and will be attributed the change type DELETE.

Additionally, these events will now be included in the schema change count value displayed in the Status tab on the Connection Details page.

GitHub

We've added the following tables to track auto-merge and merge queue activity on pull requests:

• PULL_REQUEST_AUTO_MERGE - this table records when auto-merge is enabled or disabled for a pull request, including the timestamp and who made the change, if any.

• PULL_REQUEST_MERGE_QUEUE - this table records when a pull request is added to or removed from the merge queue, including the timestamp and who made the change, if any.

• We've added a new table, COPILOT_SEAT. The table contains GitHub Copilot seat assignment data per organization, including assignee details, seat plan type, activity timestamps, and the team through which the seat was assigned.

We've added the following new tables to support GitHub Copilot usage metrics at the organization and user levels:

• COPILOT_ORG_METRIC — Daily Copilot usage totals for the organization.
• COPILOT_ORG_METRIC_BY_IDE — Organization Copilot usage broken down by IDE.
• COPILOT_ORG_METRIC_BY_FEATURE — Organization Copilot usage broken down by feature.
• COPILOT_ORG_METRIC_BY_LANGUAGE_FEATURE — Organization Copilot usage broken down by programming language and feature.
• COPILOT_ORG_METRIC_BY_LANGUAGE_MODEL — Organization Copilot usage broken down by programming language and model.
• COPILOT_ORG_METRIC_BY_MODEL_FEATURE — Organization Copilot usage broken down by model and feature.
• COPILOT_USER_METRIC — Daily Copilot usage totals per user.
• COPILOT_USER_METRIC_BY_IDE — Per-user Copilot usage broken down by IDE.
• COPILOT_USER_METRIC_BY_FEATURE — Per-user Copilot usage broken down by feature.
• COPILOT_USER_METRIC_BY_LANGUAGE_FEATURE — Per-user Copilot usage broken down by programming language and feature.
• COPILOT_USER_METRIC_BY_LANGUAGE_MODEL — Per-user Copilot usage broken down by programming language and model.
• COPILOT_USER_METRIC_BY_MODEL_FEATURE — Per-user Copilot usage broken down by model and feature.

We will discontinue support for the following tables once the underlying GitHub API endpoints are shut down on April 2, 2026:

• COPILOT_METRIC
• IDE_CODE_COMPLETION_TOTAL_LANGUAGE
• IDE_CODE_COMPLETION_EDITOR
• IDE_CODE_COMPLETION_EDITOR_MODEL
• IDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE
• IDE_CHAT_EDITOR
• IDE_CHAT_EDITOR_MODEL
• DOTCOM_CHAT_MODEL
• DOTCOM_PULL_REQUEST_REPOSITORY
• DOTCOM_PULL_REQUEST_REPOSITORY_MODEL
• COPILOT_METRIC_TEAM
• IDE_CODE_COMPLETION_TOTAL_LANGUAGE_TEAM
• IDE_CODE_COMPLETION_EDITOR_TEAM
• IDE_CODE_COMPLETION_EDITOR_MODEL_TEAM
• IDE_CODE_COMPLETION_EDITOR_MODEL_LANGUAGE_TEAM
• IDE_CHAT_EDITOR_TEAM
• IDE_CHAT_EDITOR_MODEL_TEAM
• DOTCOM_CHAT_MODEL_TEAM
• DOTCOM_PULL_REQUEST_REPOSITORY_TEAM
• DOTCOM_PULL_REQUEST_REPOSITORY_MODEL_TEAM

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

We have added a new column, label, to the ISSUE_LABEL table. We are gradually rolling out this change to all existing connections.

Google Ads

We've added theai_max_setting_enable_ai_max and ai_max_setting_bundling_required columns to the CAMPAIGN_HISTORY table.

We have upgraded our Google Ads connector to version v23.1 of the Google Ads API. Due to the upgrade, we've made the following changes:

• We have added two new columns, start_date_time and end_date_time, to the CAMPAIGN_HISTORY table. These columns replace the existing start_date and end_date columns, which will no longer be populated. The new columns use a datetime format instead of a date-only format.
• The lead_form_only column in the DEMAND_GEN_MULTI_ASSET_AD_HISTORY table will no longer be populated because the field has been removed from the Google Ads API.
• The CALL_AD_HISTORY table will no longer receive new data because the CallAd type has been removed from the Google Ads API. Existing historical data in the table is preserved.
• We have added the following reporting resources:
  • DETAIL_CONTENT_SUITABILITY_PLACEMENT_VIEW
  • GROUP_CONTENT_SUITABILITY_PLACEMENT_VIEW
  • MATCHED_LOCATION_INTEREST_VIEW
• We have added the following new fields to the PER_STORE_VIEW reporting resource:
  • address1
  • address2
  • business_name
  • city
  • country_code
  • phone_number
  • postal_code
  • province

Google Display & Video 360

Our Google Display & Video 360 connector can now sync the following metadata:

• channel
• custom_list
• combined_audience
• google_audience
• inventory_source_group
• line_item
• line_item_brand_lift_vendor_config
• line_item_brand_safety_vendor_config
• line_item_creative
• line_item_floodlight_activity_config
• line_item_partner_cost
• line_item_reach_vendor_config
• line_item_related_video
• line_item_video_ad_sequence_step
• line_item_viewability_vendor_config
• line_item_warning_message
• line_item_assigned_targeting_option
• line_item_assigned_combined_audience
• line_item_assigned_custom_list
• line_item_assigned_first_party_and_partner_audience
• line_item_assigned_google_audience
• inventory_source
• inventory_source_creative_config
• inventory_source_accessors_advertiser
• inventory_source_read_advertiser
• inventory_source_read_partner

See the connector's updated ERD for more details.

Google Search Ads 360

We have added new hourly prebuilt report tables:

• AD_GROUP_REPORT_HOURLY
• CAMPAIGN_REPORT_HOURLY
• CUSTOMER_REPORT_HOURLY

For a full list of prebuilt report tables the connector syncs, see the Google Search Ads 360 ERD.

Guru

HappyFox

Intercom

We have renamed the column away_mode_reassigned to away_mode_reassign in the ADMIN table to align with the Intercom API field name.

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

• applied_at
• applied_by_id
• applied_by_type
• tag_name

Jira

We've added the following columns to the ATTACHMENT_METADATA table:

• content_url
• thumbnail_url
• filename
• author_id
• created
• mime_type
• file_size

The connector now processes all attachment types from issues, not just ZIP files. For non-ZIP attachments, the table stores standard attachment metadata including download URLs, file information, and author details from the issue's attachment field.

Klaviyo

We have added a new table, ACCOUNT_HISTORY, to store account-level details of Klaviyo accounts for auditing and tracking purposes.

LinkedIn Ad Analytics

We've added the following new columns:

• audience_penetration
• average_dwell_time
• average_event_watch_time
• average_event_watch_time_over_15_seconds
• average_event_watch_time_over_2_minutes
• average_event_watch_time_over_30_seconds
• average_video_watch_time
• cost_per_event_view
• cost_per_event_view_over_15_seconds
• cost_per_event_view_over_2_minutes
• cost_per_event_view_over_30_seconds
• cost_per_qualified_lead
• document_completions
• document_first_quartile_completions
• document_midpoint_completions
• document_third_quartile_completions
• download_clicks
• event_views
• event_views_over_15_seconds
• event_views_over_2_minutes
• event_views_over_30_seconds
• event_watch_time
• headline_clicks
• headline_impressions
• post_click_job_applications
• post_click_job_apply_clicks
• post_click_registrations
• post_view_job_applications
• post_view_job_apply_clicks
• post_view_registrations
• qualified_leads
• reactions
• registrations
• subscription_clicks
• talent_leads
• valid_work_email_leads
• video_watch_time
• viral_document_completions
• viral_document_first_quartile_completions
• viral_document_midpoint_completions
• viral_document_third_quartile_completions
• viral_download_clicks
• viral_job_applications
• viral_job_apply_clicks
• viral_post_click_job_applications
• viral_post_click_job_apply_clicks
• viral_post_click_registrations
• viral_post_view_job_applications
• viral_post_view_job_apply_clicks
• viral_post_view_registrations
• viral_reactions
• viral_registrations
• viral_subscription_clicks

to the following following analytics tables:

• AD_ANALYTICS_BY_CAMPAIGN
• AD_ANALYTICS_BY_CREATIVE
• AD_ANALYTICS_BY_CREATIVE_WITH_CONVERSION_BREAKDOWN
• MONTHLY_AD_ANALYTICS_BY_MEMBER_COMPANY
• MONTHLY_AD_ANALYTICS_BY_MEMBER_COMPANY_SIZE
• MONTHLY_AD_ANALYTICS_BY_MEMBER_COUNTRY
• MONTHLY_AD_ANALYTICS_BY_MEMBER_INDUSTRY
• MONTHLY_AD_ANALYTICS_BY_MEMBER_JOB_FUNCTION
• MONTHLY_AD_ANALYTICS_BY_MEMBER_JOB_TITLE
• MONTHLY_AD_ANALYTICS_BY_MEMBER_REGION
• MONTHLY_AD_ANALYTICS_BY_MEMBER_SENIORITY

Microsoft Advertising

We have added the following reporting tables:

• ASSET_GROUP_PERFORMANCE_DAILY_REPORT
• ASSET_GROUP_PERFORMANCE_HOURLY_REPORT

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

You can populate the new tables with data for free until April 10, 2026. Be sure to exclude the tables that you don't want to count towards paid Monthly Active Rows (MAR) before this date.

We have added the status column to the following tables:

• CAMPAIGN_LABEL_HISTORY
• AD_GROUP_LABEL_HISTORY
• AD_LABEL_HISTORY
• KEYWORD_LABEL_HISTORY

The column indicates the association status between the label and the entity, and can have a value of Active or Deleted.

Optimizely

We have added two new columns, feature_key and feature_name, to the EXPERIMENT_HISTORY table.

We have added two new columns, feature_enabled and variable_values, to the EXPERIMENT_VARIATION_HISTORY table.

Paychex

Pipedrive

We have made the following changes to the PRODUCT_DEAL table:

• Removed the following columns:

  • active_flag
  • discount_percentage
  • duration
  • duration_unit
  • quantity_formatted
  • sum_formatted
  • sum_no_discount

• Renamed the following columns:

  • enabled_flag to is_enabled
  • last_edit to update_time

Pylon Support Platform

Sage Intacct

We now use the recordno column as the primary key for the PO_DOCUMENT table. Previously, we used the docid column as the primary key.

Salesforce Commerce Cloud

We have added a new column, image_absUrl, to the PRODUCT table.

Samsara

SAP Concur

We have added a new column, external_id, to the ATTENDEE table.

We have added the following new tables:

• PAYMENT_REQUEST
• PAYMENT_REQUEST_DIGEST
• PAYMENT_REQUEST_LINE_ITEM
• PAYMENT_REQUEST_LINE_ITEM_ALLOCATION
• PAYMENT_REQUEST_LINE_ITEM_MATCHED_PURCHASE_ORDER_RECEIPT

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

• company_id
• created_at
• date_of_birth
• display_name
• employee_number
• last_modified_at
• manager_display_name
• manager_id
• nick_name
• preference_24_hour
• preference_currency_symbol_location
• preference_date_format
• preference_default_cal_view
• preference_distance
• preference_end_day_view_hour
• preference_first_day_of_week
• preference_hour_minute_separator
• preference_negative_currency_format
• preference_negative_number_format
• preference_number_format
• preference_start_day_view_hour
• preferred_language
• start_date
• termination_date
• timezone
• title

Security Journey

Shopify

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

• default_phone_number
• default_phone_number_marketing_collected_from
• default_phone_number_marketing_opt_in_level
• default_phone_number_marketing_state
• default_phone_number_marketing_updated_at
• default_phone_number_source_location_id
• sms_marketing_consent_collected_from
• sms_marketing_consent_opt_in_level
• sms_marketing_consent_state
• sms_marketing_consent_updated_at

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

• payment_credit_card_name
• payment_credit_card_wallet
• payment_credit_card_expiration_month
• payment_credit_card_expiration_year
• payment_id.

We have added a new column, total_outstanding, to the ORDER table.

We have added two new columns, delivery_method_presented_name and delivery_method_service_code, to the FULFILLMENT_ORDER table. These columns represent the delivery option name shown to the buyer at checkout and the shipping method reference code, respectively, sourced from the nested DeliveryMethod object in Shopify's GraphQL API.

Snapchat Ads

We've added two new columns, measured_impressions and viewable_impressions, to the following prebuilt report tables:

• AD_DAILY_REPORT
• AD_HOURLY_REPORT
• AD_SQUAD_DAILY_REPORT
• AD_SQUAD_HOURLY_REPORT
• CAMPAIGN_DAILY_REPORT
• CAMPAIGN_HOURLY_REPORT

These viewability metrics indicate how many ad impressions were measured for viewability and how many met the viewability threshold.

These columns are not available in dimensional report tables, such as geo, device, or demographic breakdowns.

SonarQube

Spotify Ads

We have added the delivery_goal column to the AD_SET table and the delivery_goal_group column to the CAMPAIGN table.

Square

We have added a new column, ticket_name, to the ORDER table.

We have added a new table, CATALOG_ITEM_CATEGORY. You can use this table to join the CATALOG_ITEM and CATALOG_CATEGORY tables, since the category_id column in CATALOG_ITEM is now discontinued. We are gradually rolling out this change to all existing connections.

We have added two new columns, reporting_category_id and reporting_category_ordinal, to the CATALOG_ITEM table.

Stripe

We have added a new column, tax_behavior, to the PRICE table.

We have added a new column, next_invoice_sequence, to the CUSTOMER table.

We have added two new columns, trace_id_status and trace_id_value, to the PAYOUT table.

We have added following new columns to the CHARGE table:

• amount_captured
• failure_balance_transaction_id
• statement_descriptor_suffix

We have added two new columns, automatic_tax_enabled and automatic_tax_liability_type, to the SUBSCRIPTION_HISTORY table.

The Trade Desk

We have added the following new tables:

• AD_GROUP
• CREATIVE

These tables contain metadata about your ad groups and creatives, respectively. We are gradually rolling out this change to all existing connections.

TikTok Ads

We have added a new column, campaign_automation_type, to the CAMPAIGN_HISTORY table. The column indicates the campaign automation type and can take the following values: MANUAL, SMART_PLUS, or UPGRADED_SMART_PLUS.

Vitally

Workday Financial Management

We have added a new column, descriptor, to the WORKTAG table.

We have fixed foreign key references in the ACCOUNT_POSTING_RULE and ACCOUNT_POSTING_RULE_CONDITION tables. These tables now correctly reference the ledger_account_code field instead of the ledger_account_id field when establishing foreign key relationships to the LEDGER_ACCOUNT table.

This change improves data integrity by ensuring foreign keys point to the actual primary key field (ledger_account_code) of the LEDGER_ACCOUNT table.

Workday HCM

We have added a new table, COMPENSATION_STEP.

We have added a new column, requisition_role_code, to the JOB_REQUISITION_ROLE_ASSIGNMENT table.

Xero

We have added a new column, merged_to_contact_id, to the CONTACT table.

Improvements

Amazon S3

We now support specifying custom primary keys for tables created through dynamic table mapping.

Amazon Selling Partner

We now skip reports that return an HTTP 403 Forbidden error due to insufficient Amazon Selling Partner account permissions and log a warning instead of failing the sync. To address these warnings, ensure your account has the required permissions for the affected reports.

Azure Blob Storage

We now support specifying custom primary keys for tables created through dynamic table mapping.

Bazaarvoice

We have updated the sync strategy for the REVIEW table and its child tables. In addition to the incremental syncs that capture new records and updates, we now perform a weekly re-import to capture updates and deletes.

BigQuery destination

BigQuery destinations now support NaN and Infinity values for DOUBLE and FLOAT data types. Previously, we stored these values as NULL. Be sure to re-sync your connections to backfill existing records with NaN and Infinity values.

Churnkey

We have implemented pagination for the SESSION table.

CockroachDB

We now support tables with hash-sharded primary keys and tables with virtual columns in the primary key.

Criteo

We have upgraded our Criteo connector from version 2025.04 to 2026.01 of the Criteo API. Learn more in the Criteo API v2026.01 Release Notes. We're gradually rolling this change out to all existing connections.

Dropbox

Our Dropbox 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.

Gainsight Customer Success

Our Gainsight Customer Success connector now supports OAuth 2.O authentication. To support this enhancement, we have made the following changes:

• Added a new field, Authentication, to the connection setup form, allowing you to choose between OAuth 2.0 and API key authentication methods
• Added a new parameter, authentication_method, to the Fivetran REST API

For more information, see our setup instructions.

Google Ads

To stay within Google Ads API rate limits, account structure tables (campaigns, ad groups, ads, and similar) are refreshed at most once every 12 hours per account.

Google Cloud Storage

We now support specifying custom primary keys for tables created through dynamic table mapping.

Google Display & Video 360

We have added the ability to split reports by advertiser in multi-report mode. When enabled, reports are queried separately for each selected advertiser. Use this option when reporting API fails or times out on report generation due to large data volumes across multiple advertisers.

Google Drive

Our Google Drive 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.

Google Search Ads 360

We have updated our Google Search Ads 360 connector to support the Search Ads Reporting API version v0 (2026-03-10).

We've added support for the following fields for custom reports:

• ad_group.final_url_suffix
• ad_group.tracking_url_template
• ad_group_ad.ad.final_app_urls
• ad_group_ad.ad.final_mobile_urls
• ad_group_ad.ad.final_url_suffix
• ad_group_ad.ad.tracking_url_template
• ad_group_criterion.final_mobile_urls
• ad_group_criterion.url_custom_parameters
• asset.final_mobile_urls
• asset.final_url_suffix
• asset.url_custom_parameters
• campaign.feed_types

We've added support for the following metrics for custom reports:

• metrics.average_cart_size
• metrics.average_impression_frequency_per_user
• metrics.average_order_value_micros
• metrics.cost_of_goods_sold_micros
• metrics.gross_profit_margin
• metrics.gross_profit_micros
• metrics.orders
• metrics.revenue_micros
• metrics.unique_users
• metrics.units_sold

We've added support for the following segments for custom reports:

• segments.ad_format_type
• segments.geo_target_postal_code
• segments.vertical_ads_event_participant_display_names
• segments.vertical_ads_hotel_class
• segments.vertical_ads_listing_brand
• segments.vertical_ads_listing_city
• segments.vertical_ads_listing_country
• segments.vertical_ads_listing_region
• segments.vertical_ads_listing
• segments.vertical_ads_partner_account

HighLevel

We no longer support multiple location IDs for our HighLevel connector.

HubSpot

We have simplified how the HubSpot connector handles merged records to prevent duplicate data. When you merge records in HubSpot, Fivetran now marks the merged records as deleted (_fivetran_deleted = true). This change enables you to filter out inactive records without using complex joins.

We now support HubSpot's Services API to sync service records from your HubSpot account. To support this enhancement, we have added the following new tables:

• SERVICE
• SERVICE_COMPANY
• SERVICE_CONTACT
• SERVICE_DEAL
• SERVICE_ENGAGEMENT
• SERVICE_PIPELINE
• SERVICE_PIPELINE_STAGE
• SERVICE_PROPERTY_HISTORY
• SERVICE_TICKET

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

We have added a new table, DEAL_SPLIT, using HubSpot's Deal Splits API to sync deal split information from your HubSpot account.

Intercom

The Intercom connector now supports table re-syncs.

Klaviyo

You can now configure a rollback window of 2–90 days for custom reports in Klaviyo connections.

For more information, see our setup guide.

Looker

We have renamed the Subdomain field in the connection setup form to Domain.

MongoDB

We no longer support MongoDB server versions earlier than 4.0. If you have an existing connection to a MongoDB server running version 3.x or earlier, syncs will no longer work. To continue syncing, upgrade your MongoDB server to version 4.0 or later.

NetSuite SuiteAnalytics

History mode for the NetSuite SuiteAnalytics connector is now generally available.

Oracle

We have made the following improvements to the Binary Log Reader incremental sync method for our Oracle connector:

• We now support Oracle database versions from 11g R2 and above. Previously, we supported only Oracle 12c and 19c versions.

• We now support the Binary Log Reader method for our Oracle RAC connector.

Pinterest Ads

We've removed the engagement_attribution_window configuration option from the Pinterest Ads connector setup form as it's no longer supported by Pinterest. For more details, see Pinterest changelogs.

Pipedrive

We now sync string values exactly as returned by the Pipedrive API, without performing HTML decoding, for the following tables:

• ACTIVITY
• ACTIVITY_PERSON
• DEAL_HISTORY
• ORGANIZATION
• PERSON
• PIPELINE
• PRODUCT
• PRODUCT_PRICE
• STAGE

PostgreSQL

We now support PostgreSQL version 18. For more information, see our PostgreSQL documentation.

Sailthru

We have added a new Campaign query lookback window in days option to the Sailthru connector. This allows you to configure the lookback window between 2 and 90 days for the CAMPAIGN_QUERY table during incremental syncs. Previously, we fetched the last 60 days of campaign query data during each incremental sync. For more information, see our documentation.

Salesforce

We have added the API Usage Limit field to our Salesforce connection setup form to support configurable API usage limits. You can now set a custom API usage threshold based on your Salesforce edition and requirements.

This change is applicable to all Salesforce connections.

We now support implicit currency conversion in our formula field translations for Salesforce. For more information, see our documentation.

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

Samsara

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

• AGENT_SAMBIENT_AIR_TEMPERATURE_MILLI_CTATE
• BAROMETRIC_PRESSURE_PA
• DEF_LEVEL_MILLI_PERCENT
• ECU_SPEED_MPH
• ENGINE_COOLANT_TEMPERATURE_MILLI_C
• ENGINE_LOAD_PERCENT
• ENGINE_RPM
• INTAKE_MANIFOLD_TEMPERATURE_MILLI_C

To learn more, see our priority-first sync documentation.

SAP ERP on HANA

A new version of the Fivetran NetWeaver API is now available for download: v1900309.

Improvements in Fivetran NetWeaver API v1900309:

• We improved the performance of the /FIVETRAN/TRIGGERS transaction to avoid out-of-memory issues when displaying or cleaning data for large shadow tables.
• We improved handling of DDL changes in source and shadow tables.
• You can now use SAP Message Server to connect to SAP landscapes with multiple application server instances, leveraging SAP's built-in load balancing and automatic failover to healthy instances. For more information, see the relevant section in our SAP ERP on HANA Setup Guide.
• You can now route connections through SAP Router, an application-layer proxy that controls RFC traffic between external systems and your SAP landscape. For more information, see the relevant section in our SAP ERP on HANA Setup Guide.

SFTP

We now support specifying custom primary keys for tables created through dynamic table mapping.

Our SFTP 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.

SharePoint

Our SharePoint 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.

Slack

We have added a new drop-down menu, App Level, to the connection setup form. You can now specify the slack app level from which you want to sync the data. We have also added a new config parameter, app_level, to the Fivetran REST API.

Snowflake destination

Snowflake destinations now support NaN and Infinity values for DOUBLE and FLOAT data types. Previously, we stored these values as NULL. Be sure to re-sync your connections to backfill existing records with NaN and Infinity values.

The Default Virtual Warehouse drop-down menu in the destination setup form is now a mandatory field. You must select a virtual warehouse when configuring your Snowflake destination.

Splunk

You can now set a rollback window between 0 and 7 days for your Splunk connections. The default is 2 days. Learn more in our rollback sync documentation.

Zendesk Support

We now support Unstructured File Replication for our Zendesk connector. To support this enhancement, we have added a new toggle, Sync Zendesk files to your destination's object storage, to the connection setup form. For more information, see our setup instructions. We are gradually out this enhancement to all existing connections.