Changing the account namelink
You can now change your account name on the Settings tab of the account management page on your Fivetran dashboard. Only account owners can make this change.
Account name editor:
Improved connector linkslink
We’ve updated the structure of our URLs to allow you to link to connectors directly without switching destinations. Previously, our URLs only took you to the connector page if you were viewing its associated destination. Now, our URLs take you to the connector page, regardless of which destination you’re currently viewing.
NOTE: The URL does not take you to the connector page if you do not have access to that connector.
URLs that use the old format still function.
Improved connector links:
New alerts stylelink
We have redesigned our dashboard alerts to make them easier to read.
Redesigned connector list filterslink
We have increased the size of the search box in the connector list to make it easier to read. We also changed the order of the status and source filters so that they correspond to the column order below.
Old connector list filters:
New connector list filters:
dbt 0.20.1 supportlink
We now support dbt 0.20.1. You can use this version to run your projects.
dbt Threads Limit Increased to 32link
We now support up to 32 dbt threads. Note that the number of threads must be compatible with your destination type. For example, Snowflake supports only 8 concurrent queries.
Fivetran Business Criticallink
Fivetran now offers a new plan level, Business Critical, for maximum security over data infrastructure, pipelines, and access. The plan includes several new security-focused features, including customer-managed keys and AWS PrivateLink support.
Learn more about Business Critical and our other plans at the Fivetran pricing plan comparison page.
Free MAR for Private Preview Connectorslink
All new MAR associated with connectors in private preview is now free. Fivetran automatically applied this change to all accounts on August 1, 2021, at midnight UTC. This change applies only to MAR incurred after August 1, 2021, and will not be applied retroactively to previous months’ MAR. When a connector moves into beta, we begin charging paid MAR for it.
Datadog is a monitoring and analytics platform for cloud applications.
SAP HANA is an in-memory, column-oriented, relational database management system.
TikTok Ads is a video-sharing social networking platform.
We have added a new primary key column,
activty_type, to the
CONTACT_ACTIVTY table. This change prevents data integrity issues when multiple contact activities have the same
We have removed the
AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT reports from the Report name list to support Google AdWords API changes.
We have fixed a bug where Iterable connectors created before June 14, 2021, synced the
CAMPAIGN_SUPPRESSION_LIST_HISTORY table as
CAMPAIGN_SUPRESSION_LIST_HISTORY in the destination. We now sync data to both versions of the table in your destination. Be sure to update your queries.
We have added the following new tables:
We have added a new primary key column,
index, to the following tables:
We have added a new primary key column,
segment_index, to the following tables:
We have removed the
confirmation_number column from the following tables:
We have added a new table,
PROMOTION_CODE. See Stripe’s promotion code documentation for more details.
We have deprecated the
metadata_* columns from the Stripe schema.
Apple Search Adslink
Our Apple Search Ads connector now supports multithreading. We can now use multiple parallel API requests to fetch ticket data from your Apple Search Ads account to your destination, leading to faster sync speeds. The connector’s sync speed depends on your Apple Search Ads API quota and account metadata.
We have upgraded our Apple Search Ads connector from version 3 to 4 of the Apple Search Ads API. For more information, see Apple Search Ads API documentation.
We have added support for OAuth 2.0.
We now support AWS PrivateLink for Business Critical accounts. AWS PrivateLink allows VPCs and AWS-hosted or on-premises services to communicate with one another without exposing traffic to the public internet. You can use AWS PrivateLink with your source, destination, or both your source and destination.
We have added support for the BIGNUMERIC data type to store decimal types. For source connectors created after August 3, 2021, we convert DECIMAL data type to BIGNUMERIC data type in your BigQuery destination.
We are gradually rolling out this change to all existing connectors.
You can now opt to use an external service account to load data into your BigQuery destination. Set the Use own Service Account toggle to ON. For more information, see our setup instructions.
Our Box connector is now generally available.
Cloud Service Provider - AWS supportlink
We now use Amazon Web Services (AWS) as a cloud service provider in addition to Google Cloud Platform (GCP). Depending on the plan you are on, you can now select the cloud service provider (AWS or GCP) your connectors are run on.
See our Data Residency documentation for more details.
In the connector setup form, you can now select what timezone you want to use to sync the Transaction ID and Statistics reports. If you don’t select a timezone, Fivetran fetches the reports using the default timezone (UTC).
In the connector setup form, you can now select what metrics you want to use to sync the Statistics reports. In addition to the general metrics list displayed by default, you can select additional metrics from the drop-down list that opens when you click anywhere in the Metrics field.
We now support customer-managed keys for Business Critical accounts. With customer-managed keys, you own the master key that Fivetran uses to encrypt your credentials and temporary data, giving you greater control over Fivetran’s access to your data.
Learn more in our customer-managed keys documentation.
We have added support for lifetime aggregation with prebuilt and custom reports.
Our Facebook Pages connector is now generally available.
The HubSpot connector now supports History Mode for the following tables:
We are gradually rolling out this improvement to all existing customers. For more information about History Mode, see our documentation.
Now we just skip any relevant issue field record during the sync if your Jira installation returns the HTTP 500 Internal Server error. Previously, the entire sync would fail in that case.
We have updated the value of the log event’s
connector_id property. Previously, the
connector_name properties both contained the connector name. Now,
connector_id contains the connector ID, while
connector_name still contains the connector name.
Learn more in our log events documentation.
Our Microsoft Advertising connector now supports multithreading. We can now use multiple parallel API requests to fetch Ads data from your Microsoft Advertising account to your destination, leading to faster sync speeds. The connector’s sync speed depends on your Microsoft Advertising account metadata.
We have changed our sync strategy and now retrieve events data from Mixpanel using Processing Time
event.mp_processing_time_ms. Previously, we used Event Time
event.time. During internal performance testing, we observed a reduction in sync time. To ensure data integrity, we have rolled back the
EVENT table’s cursor by six days. As a result of this rollback, you may observe a longer sync duration in your next sync.
We have added the option to deselect the following tables from syncing:
To deselect these tables, go to the schema tab of your Mixpanel connector in your Fivetran dashboard.
NOTE: If you deselect these tables and later reselect them, you will need to manually re-sync the reselected tables, because we do not maintain their state due to a lack of timestamp support in the source.
Our Outbrain connector now supports multithreading. We now use multiple parallel API requests to sync ticket data from your Outbrain account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Outbrain API quota and account metadata.
We have added support for the TIMESTAMP_TZ data type. For source connectors created after August 30, 2021, we convert INSTANT data type to TIMESTAMP_TZ data type in your Redshift destination.
We now capture deletes for the following tables:
We use webhooks to capture deletes for these tables.
Our Snapchat Ads connector now supports multithreading. We now use multiple parallel API requests to sync ticket data from your Snapchat Ads account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Snapchat Ads API quota and account metadata.
We now support the
PAYMENT_INTENT table for Stripe Connect accounts. If you’d like to sync data from Stripe connected accounts, contact our support team.
The Stripe connector now supports table-level re-syncs.
We now support table grouping in the Schema tab of your connector details page.
The Stripe connector now supports History Mode for the following tables:
We are gradually rolling out this improvement to all existing customers.
Our Taboola connector now supports multithreading. We now use multiple parallel API requests to sync ticket data from your Taboola account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Taboola API quota and account metadata.
We have added support for storing data in two cloud-specific buckets, Google Cloud Storage (GCP) and Amazon S3 (AWS). We restrict your data within the selected cloud provider and the already supported United States (US) and European Union (EU) regions. New connectors will utilize storage based on the cloud service provider selected in the destination setup form. We will continue to store the existing connectors’ data in Google Cloud Storage in their respective regions.
We have added support for the JSON: API media type
REST API Improvementslink
Validation of the ‘schema’ and ‘table’ path parameterslink
We have added validation for the
table path parameters for the Re-sync Connector Table Data endpoint.
In order for a request to succeed, you need to specify its parameters correctly.
Now you may get the following error when calling this endpoint even if it has worked fine before:
HTTP 404 "message" : "Cannot find entity 'Schema' with id '<your_connector_schema_id>'."
This means that you have been using the wrong
You can find the name of your database schema and table on the Schema tab of the connector details page.
NOTE: Make sure you don’t use the connector schema name instead of the database schema name.
See our Re-sync Connector Table Data endpoint documentation for details.