March 2024link
Fivetran Azure Central India Serverslink
We have added new servers in the Azure Central India (Pune) 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 US, your data does not leave the US during processing.
We now support Azure Private Link connections to sources and destinations in the centralindia (Pune) region.
For more information, see our data residency documentation.
Fivetran Azure Japan Serverslink
We have added new servers in the Azure Japan East (Tokyo) 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 US, your data does not leave the US during processing.
We now support Azure Private Link connections to sources and destinations in the japaneast (Tokyo) region.
For more information, see our data residency documentation.
Lite Connectorslink
Lite connectors are now available for the following sources:
Transformations for dbt Corelink
dbt Core version 1.7.9 supportlink
We now support dbt Core version 1.7.9. You can use this version to run your projects.
NOTE: For dbt Core versions later than 1.1.5, we don't support MySQL destinations. For dbt Core versions later than 1.4.9, we don't support SQL Server and Azure Synapse destinations. These destinations are not currently supported by custom dbt Core adapters.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
Support of multiple targets in dbt for Core* transformationslink
In addition to being able to change the default target, you can now define multiple additional targets when setting up a dbt for Core* transformation.
Deleting a custom target deletes the models associated with it.
When you set up a transformation, you assign one of the targets you defined for your dbt project to be used with the model. You can set up several transformations using the same model but different targets.
Transformations that use additional targets have a pill displaying the name of the additional target used.
Target management for transformations for dbt Corelink
You can now edit targets when using dbt for Core* transformations. This allows you to change certain properties when using transformations without changing the associated destination's settings.
The following Snowflake destination settings are now also managed via targets:
- Host
- Port
- Database
- User
- Role
- Auth
We removed them from the dbt Transformations setup form.
To manage targets from the dbt Transformations setup form, set the Show Advanced Options toggle to ON.
When adding or editing a target, you can add and define additional parameters, and override and remove the existing ones. Refer to you destination's documentation to check which parameters stored as key-value pairs it supports by clicking the link to the specific destination's documentation in the target details pane.
To override the destination's authentication settings, set the Custom destination authentication settings toggle to ON.
To revert the destination's settings use the Restore default values button.
* 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.
New connectorslink
Adyenlink
Adyen is a payment, revenue, and financial management platform.
Read our Adyen connector documentation.
Azure DevOpslink
Azure DevOps is a suite of tools that help teams manage their entire software development lifecycle.
Read our Azure DevOps connector documentation.
Schema changeslink
Appfigureslink
We have removed the REPLY
table.
Attentivelink
We have changed the primary key for the SMS_INBOUND
table. The new primary key is the fivetran-id
column. Previously, we used a composite primary key which was a combination of the subscriber_external_id
and fivetran-id
columns.
Auth0link
We have changed the primary key for the USER_IDENTITIES
table. We now use the fivetran-id
column as the primary key for this table. Previously, we used a combination of the index
and user_id
columns as the composite primary key.
Brazelink
We have added a new column, message_extras
, to the following tables:
CONTENT_CARD_EVENT
EMAIL_EVENT
PUSH_NOTIFICATION_EVENT
SMS_EVENT
WEBHOOK_EVENT
Chameleonlink
We have added the following new columns to the MICRO_SURVEY_RESPONSE
table:
comment_step_dropdown_item
comment_step_other_text
other_text
Checkrlink
We have renamed the ruleset_id
column of the ASSESSMENT
table to id
.
We have changed the primary key of the ASSESSMENT
table. The new primary key is the _fivetran_id
column. Previously, the primary key was a combination of the ruleset_id
and report_id
columns.
We have changed the primary key of the REPORT_ADDRESS
table. The new primary key is the _fivetran_id
column. Previously, the primary key was a combination of the _fivetran_id
and report_id
columns.
We have changed the composite primary key of the ASSESSMENT_RESULT
table. The new composite primary key is a combination of the index
and _fivetran_id
columns. Previously, we used the index
, report_id
, and ruleset_id
columns as the composite primary key.
We have changed the composite primary key of the ASSESSMENT_RESULT_ASSESSED_OBJECT
table. The new composite primary key is a combination of the object_id
, assessment_result_index
, and _fivetran_id
columns. Previously, we used the index
, assessment_result_index
, report_id
, and ruleset_id
columns as the composite primary key.
Facebook Pageslink
We have added the following new tables to support Facebook Reels:
LIFETIME_REEL_METRICS_BY_TYPE
LIFETIME_REEL_METRICS_TOTAL
REEL_HISTORY
UNIQUE_LIFETIME_REEL_METRICS_TOTAL
You can view the full list of metrics for reel insights in the Facebook's documentation.
We are gradually rolling out the change to all our Facebook Pages connectors.
Firebaselink
We have updated subcollection names to begin with a forward slash ("/").
Frontlink
We have changed the primary key in the CONTACT_NOTE
table from the index
column to a combination of the contact_id
and index
columns.
HappyFoxlink
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
SLA | Will resync | ||||
column | Deprecated Column | index 🔑 | Column removed | ||
column | Primary Key Change | report_id 🔑 | report_id | No longer primary key | |
column | New Column | _fivetran_id 🔑 | New primary key |
Instagram Businesslink
- We have added a new field,
story_swipe_forward
, to theMEDIA_INSIGHTS
table. The existingnavigation
field in theMEDIA_INSIGHTS
table is broken down bystory_navigation_action_type
to the following navigation actions viewers take upon viewing the media:story_exits
story_taps_back
story_taps_forward
story_swipe_forward
Linearlink
We have removed the ISSUE_HISTORY
table.
We have added the following new tables:
ISSUE_HISTORY_1
ISSUE_HISTORY_2
ISSUE_HISTORY_3
ISSUE_HISTORY_4
Muxlink
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
ASSET_INPUT_INFO | Will resync | ||||
column | Primary Key Change | asset_id 🔑 | asset_id | No longer primary key | |
column | Deprecated Column | index 🔑 | Column removed | ||
column | New Column | _fivetran_id 🔑 | New primary key | ||
ASSET_INPUT_INFO_TRACK | |||||
column | Deprecated Column | asset_input_info_asset_id 🔑 | Column removed | ||
column | Deprecated Column | asset_input_info_index 🔑 | Column removed | ||
column | New Column | _fivetran_id 🔑 | New primary key |
PartnerStack Vendorlink
We have changed the primary key in the FORM_TEMPLATE_FIELD
table. The new composite key is a combination of the index
and form_template_id
columns.
TikTok Adslink
We have added a new column, tiktok_item_id
, to the AD_HISTORY
table. You can find details about the tiktok_item_id
field in the TikTok ads documentation.
Improvementslink
Adobe Analyticslink
We now support the OAuth Server-to-Server credentials authentication method for Adobe Analytics connectors.
Users are recommended to migrate to OAuth Server-to-Server credentials because Adobe is deprecating the Service Account (JWT) credentials authentication method on January 1, 2025.
ADP Workforce Nowlink
We have added the following tables to your schema:
WORKER_LEAVE
WORKER_TIME_CARD
WORKER_TIME_CARD_DAILY_TOTAL
WORKER_TIME_CARD_HOME_LABOR_ALLOCATION
WORKER_TIME_CARD_PERIOD_TOTAL
We have started to sync Worker TimeCard
and Worker Leave
endpoints. To make sure all your data is synced, see the prerequisites for the ADP Workforce Now connector.
Amplitudelink
Fivetran now supports extracting event data from Amplitude using Cloud Storage Export. We are gradually rolling out this feature to all connectors.
For more information, see our Amplitude setup guide.
BigCommercelink
Our BigCommerce connector is now generally available.
Read our BigCommerce documentation.
BigQuerylink
We are rolling out the optimized sync feature for the following types for BigQuery tables:
- regular tables
- partitioned tables that do not require a partition filter.
When the feature rolls out to your connector, we will automatically re-sync all your selected tables. This re-sync will not count towards MAR. To take advantage of the optimization, make sure to grant the the necessary service account permissions.
Closelink
We have changed the sync strategy for the CONTACT
and LEAD
tables and their child tables. We no longer capture deletes for these tables.
commercetoolslink
We now support syncing data from text columns in all locales in our commercetools connector. Previously, we supported only de-DE
and en-US
for syncing data from text columns.
Emaillink
While syncing your email attachments, we now store the date and time when the email was sent in the _modified
column. Previously, this column contained the date and time when the connector uploaded the attachments to our internal S3 bucket.
NOTE: This change is not applicable to the syncs already completed before March 16, 2024.
Facebook Adslink
We have upgraded our Facebook Ads connector to version 18.0 of the Facebook API. For more information, see Facebook's summary of Graph API v18.0 and Marketing API v18.0.
We have deprecated the following insight metrics:
quality_ranking
conversion_rate_ranking
engagement_rate_ranking
Existing reports won't be affected, but the fields will not be available for new reports.
Firebaselink
We have enhanced the connector to enable you to sync subcollections with the same name as top-level collections. You can now sync both subcollections and collections that share identical names.
Google Calendarlink
We now perform a full re-sync for the EVENT
table to capture updates and deletes.
Google Cloud Storagelink
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.
Google Drivelink
We have fixed a bug in our Google Drive connector that prevented syncing files with the same names across different folders. To sync these files, we now use a regular expression for the file path that includes the prefix instead of using just the regular expression for the file name in the File Pattern field. For more information, see our setup instructions.
High-Volume Agent SQL Serverlink
Our High-Volume Agent SQL Server connector is now generally available. Read our High-Volume Agent SQL Server connector documentation.
Iterablelink
We have added support for EU-based Iterable accounts. For more information, see our setup instructions.
Jotformlink
You can now specify your custom API base URL while setting up your connector. To enable you to specify your custom base URL, we have made the following changes to the connector setup form:
- Added a new option, Custom, to the Base URL drop-down menu.
- Added a new field, Custom base URL, which allows you to specify your custom base URL.
NOTE: The Custom base URL field appears only when you select Custom in the Base URL drop-down menu.
For more information, see our setup instructions.
Maxio Chargifylink
We now incrementally sync the COMPONENT_PRICE_POINT
table and its child tables to capture new records.
We now also capture deletes for the COMPONENT_PRICE_POINT
table.
Named instance support for SQL Server HVAlink
Over the course of two weeks, we will be rolling out support for named instances in the High-Volume Agent SQL Server and High-Volume Agent SAP ECC on SQL Server connectors.
Reltiolink
Our Reltio connector now supports table-level re-syncs.
Rithumlink
We have renamed our ChannelAdvisor connector to Rithum, following ChannelAdvisor's name change. This name change applies to the Fivetran dashboard and our documentation.
Stripelink
We have changed the sync strategy for the PLAN
table. To capture new records and updates, we now re-import this table every time we perform a sync for the connector. Previously, we re-imported this table once a day.
Support for TRUNCATE commandlink
Our MariaDB and MySQL connectors now support the TRUNCATE
command.
WorkRamplink
We now incrementally sync the EVENT
table and its child tables to capture new records.
Wrikelink
We now incrementally sync the ATTACHMENT
table and its child tables to capture new records.
Zuoralink
To improve data integrity, we have started doing once a week lookback periods for data updates on certain tables. This way, your information remains accurate and up-to-date.
The following tables will now have a 14-day lookback period:
CREDIT_MEMO_APPLICATION_ITEM
CREDIT_TAXATION_ITEM
DEBIT_MEMO_ITEM
DEBIT_TAXATION_ITEM
INVOICE_ITEM
INVOICE_ITEM_ADJUSTMENT
PAYMENT_APPLICATION_ITEM
REFUND_APPLICATION_ITEM
REVENUE_EVENT_ITEM
REVENUE_EVENT_ITEM_DEBIT_MEMO_ITEM
REVENUE_EVENT_ITEM_INVOICE_ITEM
REVENUE_EVENT_ITEM_INVOICE_ITEM_ADJUSTMENT
TAXATION_ITEM
The following tables will now have a 90-day lookback period:
CREDIT_MEMO_ITEM
REVENUE_EVENT_ITEM_CREDIT_MEMO_ITEM
REST API Improvementslink
New field added in Destinations APIlink
For the following endpoints, we added a new field, daylight_saving_time_enabled
:
If the field value is set to true
, the UTC offset is shifted in accordance with the daylight saving time. This option can only be used for the US region.
Log eventslink
New Log Eventlink
We have added a new log event, schema_migration_end
. See our Logs documentation for more information.