Link to log servicelink
You can now navigate directly to your log service from the Connection Details page of your Fivetran dashboard.
Okta SAML Supportlink
We also support Just In Time (JIT) provisioning, meaning that we’ll automatically create an account for each user the first time they log in with Okta.
Azure SQL Databaselink
Azure SQL Database is a managed relational cloud database service that you can use to build data-driven applications and websites in the programming language of your choice, without needing to manage infrastructure.
Google Search Consolelink
Google Search Console allows you to monitor, maintain, and troubleshoot your site’s presence in Google Search results.
MySQL on Google Cloud SQLlink
MySQL on Google Cloud SQL is a fully-managed database service that makes it easy to set up, maintain, manage, and administer your MySQL relational databases on Google Cloud Platform.
PostgreSQL on Azure Databaselink
PostgreSQL on Azure Database is a managed relational cloud database service that can handle mission-critical workloads with predictable performance, security, high availability, and dynamic scalability.
PostgreSQL on Google Cloud SQL Databaselink
PostgreSQL on Google Cloud SQL Database is a fully-managed database service that makes it easy to set up, maintain, manage, and administer your PostgreSQL relational databases on Google Cloud Platform.
Sigma Computing is the next-generation of analytics for cloud data warehouses with a familiar spreadsheet-like interface that gives business experts the power to ask any question of their data no matter the query.
We have added two new tables,
CONTACT_ACTIVITYtable contains contact activity data.
VISITORtable contains details about visitors to your website.
We have added a new field,
archived, to the
We have added two new fields,
callee_object_id, to the
We have added three new fields to the
COMPANY table -
We have dropped the primary key constraint from the
value field in the
_fivetran_id has replaced
id as the only primary key in the
We have converted the settings tables to be history tables by making the
last_modified field a second primary key. We have renamed the following tables to reflect this change:
|OLD TABLE NAME||NEW TABLE NAME|
We have separated the
DIMENSION tables into various sub-tables, which each have a foreign key relationship with their respective parent entity.
Mavenlink’s custom field value type
currency contains both cents and currency code data (for example, a
currency value of
[12,USD] = 12 cents USD). We have split
currency data into two columns,
We no longer sync the
We have added two new fields,
end_date, to the
We have renamed the
CAMPAIGN_CATEGORY table to
CATEGORY. It has a foreign key relationship to the
We have made the following changes to the
- The primary key is now
- We have renamed the
We have added a new table,
We have added the following columns to the tables below:
|TABLE NAME||NEW COLUMN NAME|
Our setup form now correctly handles directory patterns that don’t end with
We now use case-sensitive collation for string columns so that JOINs handle case correctly.
We now create column store indexes for all tables in Azure SQL Database. If column store indexing fails, you will be automatically notified that you need to upgrade the resource class of the user.
Azure recommends using Parquet files instead of CSVs, because they don’t interpret CSVs reliably. Fivetran will write your data to a Parquet file and upload it to Azure Blob Storage.
We have added two new response root nodes,
deletecontains the entities and records to be deleted. Fivetran does not delete these records; instead, we mark them as deleted by setting the
_fivetran_deletedcolumn value to
schemaspecifies primary key columns for each entity.
If you are specifying the
delete node, you must also specify
For more information, see our Functions documentation.
DoubleClick Campaign Managerlink
In the setup form, you can now select only one Floodlight Configuration ID per account.
DoubleClick For Publisherlink
We have reduced the data window dynamically by one day in case of report failure.
When we encounter malformed files during our syncs, we now skip them and send you a warning so that you can fix the files in question. Previously, our entire sync would fail if malformed files were present.
File Sources (S3, GCS, FTP, etc)link
We now parse ISO DATE format (yyyy-mm-dd-hh:mm:ss) correctly.
Group-specific SSH keyslink
Fivetran now supports unique SSH keys per warehouse/group for SSH tunnels, SFTP, Marin, etc.
Mandrill silently revises aggregate clicks and opens metrics in the API results, so we have implemented a 30-day rollback sync to accurately capture this data.
Mavenlink returns choice ID data for custom field types
multi. We now fetch the choice value instead of the choice ID.
We now fully support the
SET data type and consistently sync it as a JSON array. Previously, we synced
SET as a string during the initial import and as an integer when processed from the binary logs. If any values were incorrectly synced prior to this change, you will need to initiate a re-sync to correct them.
We have updated the JDBC driver to version 7.20.50.
For logical replication mode, we have switched to a different logical decoding plugin that consumes significantly less disk and memory resources on the database instance.
We can now correctly parse Postgres array data types with escaped characters.
We have corrected the way our system interprets timestamps. The ReCharge API produces timestamps that look like
2018-01-01T00:00:00. Previously, we interpreted these timestamps as UTC, when they were actually Eastern Time (ET). This meant that all destination timestamps were off by 4 or 5 hours, depending on daylight savings. All timestamps are now correctly converted from ET to UTC before they arrive in your destination. Note that there is still one hour each year where the timestamp is ambiguous due to daylight savings time. ReCharge is working on a fix for this in their API.
We can now sync columns with the data type
DATETIMEOFFSET. The values are converted to UTC using the timezone information present in the data.
We now fetch data for all Source Name Native, Search, and Other for Keyword Stats reports.
Zendesk uses various non-standard time formats in different regions. We can now parse non-standard times like
Mon Jan 1 2018, 00:00:00 GMT-0300 (Hora oficial do Brasil) and
Mon Apr 30 2018 15:44:04 GMT+0000 when they come from Zendesk.
We have added logs for the following applications:
- Apple Search Ads
- Bing Ads Reports
- Facebook Ad Account
- Google Cloud Storage
- Marin Software
- Microsoft Azure Blob Storage
- Yahoo Gemini