Improved Service Performancelink
We are changing our architecture to allow for much higher data throughput. Starting on April 30, 2019, all Fivetran connectors will originate from a new set of fixed IP addresses. For the US region, these IPs are:
Update your IP whitelists for the following databases and warehouses before April 30. Not doing so will result in a connection failure.
- SQL Server
- AWS Redshift
- Azure Synapse
If you don’t use any of the above databases or warehouses with Fivetran, you don’t need to take any action.
Support for ISO 8601 format timestampslink
Fivetran now infers and syncs ISO 8601 timestamp formats (e.g. 2011-12-03T10:15:30+01:00[Europe/Paris] and 2011-12-03T10:15:30+01:00) as timestamp values.
TIMESTAMP WITHOUT TIMEZONE Supportlink
Fivetran has added core support for a TIMESTAMP WITHOUT TIMEZONE type. Up until now, Fivetran assumed that timestamps without timezone were in UTC. This addition means databases with a TIMESTAMP WITHOUT TIMEZONE type - MySQL, Oracle, Postgres, SQL Server - will replicate to a more correct destination type. TIMESTAMP WITHOUT TIMEZONE support is immediately available for Oracle, Postgres, and SQL Server. MySQL / MariaDB support will be released soon.
|SQL Server||DATETIME, DATETIME2, SMALLDATETIME|
|MySQL / MariaDB||DATETIME|
This change is backwards compatible. Fivetran’s core will continue assuming UTC time zone if the destination type is TIMESTAMP WITH TIMEZONE. In order to get the more specific type, drop the table in the destination and re-sync the table in your Fivetran dashboard.
Fivetran is rolling out TLS verification for connections to databases and warehouses. TLS allows for both encryption and authentication of the connections. Select your trusted certificates in your database and destination setup tests. See details in our TLS Verification docs.
Added 3 new tables
Changed the primary key from event_id, projectName to event_id, device_id, client_event_time in
Added new field
We’ve added new fields to reporting tables.
Added a new table
Changed primary key to
category_idfield from the composite primary key is coming in as
Facebook Ad Insightslink
We have removed the following tables from Facebook Ad Insights. They are now included in the Facebook Ad Account connector with much more detail:
In all the report tables, the primary key
_fivetran_id now contains
hash id instead of
row index to ensure each row has a unique ID.
We are no longer syncing the previously-deprecated
USER_MESSAGE table. You can access the same information from the
We added several new tables following the Netsuite 2018.2 release. Their behavior is specified below.
ACCOUNT_PERIOD_ACTIVITY_PEwill not be synced separately because it contains a subset of the information in the larger table
POSTING_ACCOUNT_ACTIVITY_PEwhich we already sync.
The following tables will be re-imported based on sync frequency:
The following tables will be updated incrementally:
SUBSCRIPTION_PLAN_LINESare sub tables of
SUBSCRIPTION_PLANSrespectively and will be updated along with the parent tables.
TICKET_METRIC_EVENTtable is deprecated. We will stop syncing this table after May 1, 2019. It will be replaced by the
Added new table
SLA_POLICY_HISTORYwith the following fields:
Added new table
TICKET_SLA_POLICYwith the following fields:
Fivetran now supports Conversion Variable
evar37 in the setup form.
We have changed the value of
2014-07-16. This change means that for most Amplitude tables (except
EVENT_TYPE), we only sync data that was created after July 16, 2014. We have made this change to protect the integrity of your data.
Amplitude introduced the
client_event_time parameter, a part of the primary key for the
EVENT table, on July 16, 2014. Because earlier events don’t have the
client_event_time parameter, we can’t form the primary key for them. Without the primary key, we cannot deduplicate the data. Therefore, we cannot write that data to the destination if that data was created before Amplitude introduced the
Fivetran will sync binary data from Dynamics 365 Sources.
We have fixed a problem where the first commit in a git branch was skipped during our syncs. If any records in your COMMIT table were skipped prior to this change, you will need to initiate a re-sync to capture this data.
- We upgraded our connector from AdWords API v201806 to v201809 and handled deprecation.
- Renamed the report
- Read more about the deprecations and changes in Google’s AdWords API documentation.
Fivetran has significantly increased the speed of initial syncs in Oracle by leveraging information from a system metadata table called
- Fivetran will add a log message to Customer Logs when skipping an infrequently updated table.
track API we now sync the custom attributes
company/domains/* into the single column
company_domain as a JSON value. This change improves connector stability. Previously, each custom attribute of
company/domains/* created a new column, sometimes creating columns in excess of the maximum allowed by the destination, which caused some connectors to fail.
In order to ensure the accuracy of Order data, we now use Shopify Webhooks to capture Order Updates.
Added support for Sisense V7.3. The new version uses OAuth for its authentication. To use Fivetran with Sisense V7.3, follow the setup instructions for V7.3.
We have released a new version of the Stripe connector, version 1.
- The new version contains changed, added and deprecated tables. In the existing tables we have added new fields and removed the deprecated ones. See the schema for details.
- The sunset date for version 0 is June 15, 2019.
- Connect to the new Stripe v1 integration.
Link to Stripe Documentation..
- You can now configure your Zendesk connector through the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.