September 2024

Hybrid Deployment

Our Hybrid Deployment model is now generally available.

For the complete list of connectors and destinations supporting this model, see our Hybrid Deployment documentation.

Lite Connectors

Lite connectors are now available for the following sources:

• Attio
• BillingPlatform
• Buildium
• Bazaarvoice
• Gmail
• myosh
• Okendo
• OnceHub
• Planhat
• RevenueCat
• RevOps
• RevX
• ShipNetwork

Table re-sync and table selection support

We have made the following improvements to our Lite connectors:

• Added table re-sync support. Previously, we only supported connector-level re-syncs.

  NOTE: Event-based tables and tables with a retention period at the source don't support this feature.

• You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Transformations for dbt Core

ClickHouse dbt adapter support

We now support the ClickHouse destination for scheduled in code and scheduled in Fivetran transformations by default for all supported dbt Core versions.

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

Schema changes

Amazon Ads

We have added a new prebuilt report, CAMPAIGN_PLACEMENT_REPORT_INCOMING.

Until December 5, 2024, all usage for this report will count towards free MAR.

Amazon Selling Partner

We have added the following new tables to support the Catalog module for Amazon vendor accounts:

• CATALOG
• ITEM_CLASSIFICATION_SALES_RANK
• ITEM_CONTRIBUTOR
• ITEM_DIMENSION
• ITEM_DISPLAY_GROUP_SALES_RANK
• ITEM_IDENTIFIER
• ITEM_IMAGE
• ITEM_PRODUCT_TYPE
• ITEM_RELATIONSHIP
• ITEM_SUMMARY
• ITEM_VARIATION_THEME
• ITEM_VENDOR_DETAILS

We have made the following schema changes for all Amazon Selling Partner connectors:

• We have changed the primary key of the VENDOR_RETAIL_PROCUREMENT_SHIPMENT table and its child tables. The new composite key is a combination of the vendor_shipment_identifier and transaction_date columns. If any of the two columns are NULL, we will skip these tables to avoid sync failures.
• We have changed the primary key of the CONTAINER_PACKED_ITEM table. The new composite key is a combination of the index, container_sequence_number, container_type, transaction_date, and vendor_shipment_identifier columns to avoid data integrity issues.
• We have changed the primary key of the SHIPMENT_STATUS_DETAIL table. The new composite key is a combination of the index, transaction_date, and shipment_status columns.
• We will skip the records of the VENDOR_SHIPPING_ORDER if any of the columns purchase_order_date or purchase_order_number is null.

Appfigures

Attentive

Care Quality Commission

Checkr

Cin7

Cin7 Core

Close

Collibra

Coupa

We have added the expense_line_id column as a part of the composite primary key in the EXPENSE_ATTENDEE table.

Eventbrite

Facebook Ads

We have added a new prebuilt report, BASIC_AD_ACTION_VALUES.

Float

Google Ads

We've added new prebuilt reports with leads data:

• LEAD_FORM_SUBMISSION_DATA
• LOCAL_SERVICES_LEAD
• LOCAL_SERVICES_LEAD_CONVERSATIONS

We are slowly rolling these reports out to all existing connectors.

NOTE: Syncing the LEAD_FORM_SUBMISSION_DATA report requires specific access permissions.

Also, we've added new prebuilt reports:

• CLICK_STATS
• LANDING_PAGE_STATS
• SEARCH_KEYWORD_STATS
• SEARCH_TERM_STATS

We are slowly rolling these reports out to all existing connectors.

Google Campaign Manager 360

Google Campaign Manager 360 now supports higher timeline granularity for reports.

We are gradually rolling out this feature to all existing connectors.

Guru

We now re-import the COLLECTION table once a week to capture updates and deletes.

HubSpot

Intercom

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

• ai_agent_last_answer_type
• ai_agent_participated
• ai_agent_rating
• ai_agent_rating_remark
• ai_agent_resolution_state
• ai_agent_source_title
• ai_agent_source_type

We have added a new table, CONVERSATION_AI_AGENT_CONTENT_SOURCE with following columns:

• content_type
• locale
• title
• url

If you want to sync the historical data you would need to do a resync.

We are gradually rolling out these changes all existing connectors.

Katana

Marketo

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

• auto_copy_to_text
• is_open_tracking_disabled
• pre_header

Pendo

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

• isCoreEvent
• isSuggested
• kind

To sync the historical data for these columns, contact Fivetran support.

Rarible

RetailNext

Rootly

S3 Data Lake

To avoid naming conflicts with Iceberg's reserved field names, we now prefix the following column names with # before writing them to the Iceberg tables in your destination:

• _deleted
• _file
• _partition
• _pos
• _spec_id
• file_path
• pos
• row

We will verify the existing column names in your destination and rename the columns with these reserved names. You may observe a sync delay when we rename your existing columns.

We are gradually rolling this change to all existing destinations.

Salesforce Marketing Cloud

We now sync the triggered_send_key field to the ACTIVITY table.

Shopify

We have added two new tables, COMPANY and COMPANY_CONTACT.

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

Shortcut

Skilljar

SkuVault

Snyk

Subscript

Ticket Tailor

TikTok Ads

We added the ad_format field to the AD_HISTORY table. We also added a new table, UTM_PARAM.

For more information, see the TikTok API documentation.

Transcend

Trisolute

Upland Software

Workday Financial Management

We have added the ledger_type column to the LEDGER table. Re-sync the parent table, JOURNAL_ENTRY, to backfill the historical data, or reach out to Fivetran Support to do the re-sync for you.

YouTube Analytics

We've added support for the audience retention report.

We've added support for following metadata:

• captions
• comments

Re-authorize your connector to start using comments metadata.

Zoom

Improvements

Alchemer

We have made the following improvements to the connector:

• Added table re-sync support. Previously, we only supported connector-level re-syncs.

  NOTE: Event-based tables and tables with a retention period at the source don't support this feature.

• You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Amazon S3

The Amazon S3 connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Amazon Selling Partner

We have fixed a bug where we didn’t sync a few records of the VENDOR_RETAIL_PROCUREMENT_ORDER and VENDOR_RETAIL_PROCUREMENT_ORDER_ITEM tables.

Assembled

We have made the following improvements to the connector:

• Added table re-sync support. Previously, we only supported connector-level re-syncs.

  NOTE: Event-based tables and tables with a retention period at the source don't support this feature.

• You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Azure Data Lake Storage

We no longer perform hex encoding to store binary values in the destination.

We now support the Iceberg format for your destination tables. This feature is now available in beta. For more information, see our Azure Data Lake Storage documentation.

Checkr

We no longer capture deletes for the CANDIDATE table and its child tables.

ChurnZero

We now support priority-first sync for the CHURN_SCORE_CALCULATION and CHURN_SCORE_FACTOR_CALCULATION tables.

We now sync only the last 2 days' worth of data for the CHURN_SCORE_CALCULATION table during each incremental sync.

Connector List UI

We added a new design for Connector List on Connector Page.

Email

We have made the following changes to the Lines to Skip and Skip Footer Lines fields in the setup form:

• Renamed the Lines to Skip field to Skip Header Lines
• Added toggles to the Skip Header Lines and Skip Footer Lines fields, which allow you to specify the number of lines you want the connector to skip

For more information, see our setup instructions.

FTP

We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.

GitHub

We have added support for GitHub App authentication.

GoCardless

We now incrementally sync the EVENT table.

Gong

We have made the following improvements to the connector:

• Added table re-sync support. Previously, we only supported connector-level re-syncs.

  NOTE: Event-based tables and tables with a retention period at the source don't support this feature.

• You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Google Analytics 4

You can now filter a custom report on a dimension that is not a part of the report.

For more details, see our Google Analytics 4 Setup Guide.

Google Display & Video 360

We've added the option to set the report aggregation by specyfying a date range.

We are slowly rolling this feature out to all existing connectors.

HubSpot

We have added support for HubSpot's Custom Events API to sync the custom events and its definitions data in your HubSpot account. We are gradually rolling out this improvement to all existing connectors.

Iterable

We have added a new field, Historical Sync Time Frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. The default value is ALL_TIME. You can edit the connection details and set the time frame value for an existing connector. We have also added support for the historic_sync_time_frame field for connectors created using the Create a Connector endpoint. For more information, see our REST API config.

The historical sync limit only applies to the EVENT table.

Katana

We made the following changes to the sync strategy:

• We now incrementally sync the MANUFACTURE_ORDER_OPERATION and MANUFACTURING_ORDERING_RECIPE tables.

• We now re-import only the following tables to capture updates and deletes:

  • PRODUCTION_OPERATION
  • RECIPE
  • SALES_ORDER_FULFILLMENT

Lever

You can now select to allow or deny syncing the confidential data while setting up a Lever connector. This functionality is enabled by default for connectors created after July 29, 2024.

Linear

We can now retrieve and sync your archived issues into the ISSUE table.

MySQL

All MySQL implementations now support the Hybrid Deployment model. We are gradually rolling out this feature to all existing destinations. For more information, see the individual destination setup guides.

Okta

We have made the following improvements to the connector:

• Added table re-sync support. Previously, we only supported connector-level re-syncs.

  NOTE: Event-based tables and tables with a retention period at the source don't support this feature.

• You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

The Okta connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

OneLake

We no longer perform hex encoding to store binary values in the destination.

Oracle Fusion Cloud Applications

We now support JSON Web Token (JWT) Authentication for our Oracle Fusion Cloud Application connectors.

We are gradually rolling out this feature for all the connectors.

The Oracle Fusion Cloud Applications connectors now support the Hybrid Deployment model. For more information, see our setup instructions:

• Oracle Fusion Cloud Applications - CRM
• Oracle Fusion Cloud Applications - FSCM (ERP & SCM)
• Oracle Fusion Cloud Applications - HCM

Salesforce

We now display a warning when a table encounters issues capturing deletes, recommending that you manually re-sync the affected tables instead of automatically re-syncing them. For more information, see our Salesforce documentation.

We are gradually rolling out this improvement to all connectors.

SAP ERP on HANA

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

We fixed an issue with the INT1 data type (1 byte) that was incorrectly stored as 2 bytes. This caused issues on SAP systems running on big-endian architectures. The fix ensures proper handling of this data type, regardless of the system's endianness.

Additionally, for MDTC, we have modified unpacked column names so they are no longer prefixed by /FIVETRAN/.

For more information, see our SAP ERP on HANA documentation and SAP ERP on HANA setup guide.

Shopify

We have upgraded our connector to Shopify API v2024-04. As a part of the upgrade, we have added a new column, is_removed, to the ORDER_SHIPPING_LINE table. We are gradually rolling out this improvement to all existing connectors.

Slack

We have made the following improvements to the connector:

• Added table re-sync support. Previously, we only supported connector-level re-syncs.

  NOTE: Event-based tables and tables with a retention period at the source don't support this feature.

• You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Snowflake

We now support Snowflake's internal stage to temporarily store data before writing it to Snowflake destinations configured for the Hybrid Deployment model.

Our Snowflake connector is now generally available. See our Snowflake connector documentation.

We have introduced a new sync mechanism to fetch your data from your Snowflake connector. This new method uses Change Data Capture (CDC) sync leveraging Snowflake's Time Travel feature. To enable Time Travel sync, you must either enable change tracking for all tables or grant OWNERSHIP privileges to Fivetran for update capture.

SQL Server

All SQL Server implementations now support the Hybrid Deployment model. We are gradually rolling out this feature to all existing destinations. For more information, see the individual destination setup guides.

Toggl Track

We have removed the Password dropdown field from the setup configuration as it had a fixed default value, making it an unnecessary field for customers.

Workday RaaS

You can now use a Fivetran-generated primary key for your Workday RaaS reports without a suitable primary (single or composite) key. We have added a new toggle, Use Fivetran Generated Primary Key, to the connector setup form. We generate a fivetran_id primary key based on a hash of all the columns in the report.

REST API Improvements

Hybrid Deployment Agent Management API

We have renamed our Local Processing Agent Management API to Hybrid Deployment Agent Management API. We will stop supporting the previous paths that were applicable to the Local Processing Agent Management API in 3 months from now. Therefore, you must migrate to the new API before we stop supporting the old paths.

We have added a new parameter, hybrid_deployment_agent_id, to the Connector Management API and Destination Management API. The new parameter defines the Hybrid Deployment Agent ID and is a duplicate of the local_processing_agent_id parameter. We will remove the local_processing_agent_id parameter in future.

New Destination Management endpoint to list destinations within account

We have implemented a new Destination Management API endpoint for our REST API. You can now leverage the new List all destinations within an account feature.

New System Keys management tab Private Preview

We added a new tab where you can add, view, and rotate the previously introduced System Keys in your Fivetran dashboard. To manage System Keys, you must have administrative permissions on the account. Learn more in our System Keys management documentation.

You can add a new System Key by uploading a JSON file with the key access rules. We then validate the file and show a summary of key permissions.

REST API doesn't allow to trigger initial sync for File connectors without Primary Keys defined.

We now restrict API users from triggering File connectors to sync if:

• the append_file_option field has its value set to upsert_file_with_primary_keys
• and the primary keys are not defined in the schema configuration

We also restrict the following actions for such connectors:

• Creating a new connector in an un-paused state via API;
• Updating the connector's paused field to false via API request;
• Forcing the connector sync or re-sync via API request.