Azure Data Explorer Data Warehouse
We have added Azure Data Explorer as one of our supported data warehouses. You can now use Azure Data Explorer as your destination with Fivetran connectors.
Manage Transformations Permission
You can now assign the Manage Transformations permission for your custom roles. Manage custom roles on the account page.
We have added a new feature to the Fivetran pipeline – transformations. Transformations are SQL scripts that are executed in the destination based on specific events or conditions. The primary purpose of transformations is to map data into a specific shape that is easier or faster to use in the next pipeline elements.
Fivetran Log Connector
Fivetran Log Connector syncs logs and metadata about your connectors.
The Bing Ads API recently removed support for the
click_type_id field with
impression_* fields in the
We removed the column
click_type_id from the following tables:
Facebook Ad Account
We have removed the following fields from the
Facebook recently changed the permissions required to fetch these fields. We now require
business_management permissions to sync these fields. We've submitted the Fivetran App to Facebook App Review so that Facebook will grant
business_management permissions for it. After approval, we will sync these fields again.
LinkedIn Ad Analytics
We have dropped some existing fields from the
CREATIVE_HISTORY table and added new fields. The new fields sync all the data that the previous fields contained. The table now supports separate fields for each creative type with added prefix.
You will need to drop the
CREATIVE_SERVING_STATUS_HISTORY table. The tables will get populated in next sync.
Fields dropped from the
- some custom fields
Fields added to the
We have upgraded our Salesforce connector from Salesforce API version 41.0 to 45.0. The upgrade supports new objects available in Salesforce API 45.0. We will roll out the new version of our connector to all customers gradually over 3 months starting on July 12th.
We have added the new table
FULFILLMENT_EVENTwhich represents tracking events that belong to a fulfillment of one or more items in an order. It contains the following fields:
quantitycolumn to the
If we encounter insufficient permissions when we try to sync endpoints for a specific account, then we skip that endpoint for that account and give a warning in the dashboard.
The warning includes endpoints with their respective accounts as follows.
|Account ID||Skipped Endpoints|
If you receive this warning, give Account Administrator permissions for that account to the user which you used to create your Twitter Ads App.
- We have stopped syncing data to
We have added all the regional locations allowed in BigQuery to be data location. Now you can choose any location among them to be your data location. The data location you choose will be the same location where the query processing occurs.
The new locations allowed are:
|Region Name||Region Description|
|Region Name||Region Description|
|Region Name||Region Description|
BigQuery service accounts
Newly created warehouses will use a unique service account to access data instead of a fixed service account. Visit updated documentation to see the changes in the setup process.
For existing warehouses we provide a way to perform migration to unique service accounts. Whenever you save a transformation or destination configuration, a popup window will appear that will guide you through the migration process.
Fixed an out of memory error that occurs when the number of files in the current Braze bucket is extremely large.
Facebook Ad Insights
We will sunset service versions 3, 4, and 5 of our Facebook Ad Insights on October 1, 2019.
You need to upgrade to our newest version, service version 6, by October 1, 2019. To upgrade, create a new Facebook Ad Insights connector and sync into a new schema.
The newest version of the Facebook Ad Insights connector supports daily, weekly and monthly aggregation with prebuilt reports. This new implementation generates a new schema. You can review the schema information in our docs.
We have added the table blocking feature to all HubSpot tables. You can now choose which tables you'd like to sync or omit from syncing. To select or deselect tables, go to the schema page of your Fivetran dashboard.
If you wish to sync a child table, you must also sync its parent table.
We now support capturing deleted issues by using webhooks. We are gradually rolling out this feature to all our customers. When it's available for your account, you will see a switch on the Jira connector setup form labelled "Capture deletes". To enable capturing deletes, toggle the switch.
Oracle Table-Level Supplemental Logging Support
We have added support for table-level supplemental logging. This will reduce overhead when syncing with Fivetran if you only want to replicate some of your tables in an Oracle database.
We released a new version of our Pinterest Ads connector, service version 1. You can now select how many months of data you'd like to include in your initial sync. Choose from the following options:
- 3 months
- 6 months
- 12 months
- 24 months
- All time
We have fixed a bug in our PostgreSQL connectors which was preventing some syncs from making progress.
Previously, Postgres connectors using WAL syncs could not make progress through the WAL if all of the log events were related to tables Fivetran did not sync. For example, if you selected to sync the table
PUBLIC.MY_TABLE, and all log events were on
PUBLIC.YOUR_TABLE, Fivetran could not make progress.
Now Fivetran clears the WAL slot to the most recent LSN we examined if no rows were added, deleted, or updated in Fivetran-delivered tables.
We have changed the way we perform the initial sync for our Recurly connectors. Previously during the initial sync, our Recurly connector scanned for records from EPOCH to the time when the initial sync started.
Now Fivetran scans in reverse and completes the initial sync in small batches. Every sync fetches records created in the past between two dates that differ by 7 days. This process continues until we reach the beginning of time.
Redshift VACUUM removal
- Fivetran no longer performs
VACUUM DELETEfor your Redshift warehouses on the weekends, because Redshift now does it automatically. For more information on how Amazon Redshift schedules the
VACUUM DELETEoperation, check out Amazon's changelog.
- Fixed an out of memory error that occurs when the number of files in the folder is extremely large.
- Fivetran now reconnects if the SFTP session is disconnected by the SFTP server.
Stripe authentication change
- We have deprecated the OAuth 2.0 authentication mechanism for creating a new connector. Going forward, you need to use the restricted API key to create a new connector. We will continue to run existing connectors set up using the OAuth 2.0 mechanism. We encourage you to move to the new authentication for greater security.
- You can now configure your Twitter Ads connector through the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.