March 2019link
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:
- 35.227.135.0/29
- 35.234.176.144/29
- 52.0.2.4/32.
Update your IP safelists for the following databases and warehouses before April 30. Not doing so will result in a connection failure.
Databases:
- MariaDB
- MongoDB
- MySQL
- Oracle
- PostgreSQL
- SQL Server
Warehouses:
- Redshift
- Azure Synapse
- Snowflake
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, PostgreSQL, SQL Server - will replicate to a more correct destination type. TIMESTAMP WITHOUT TIMEZONE support is immediately available for Oracle, PostgreSQL, and SQL Server. MySQL / MariaDB support will be released soon.
Source | Applicable Type |
---|---|
Oracle | TIMESTAMP |
PostgreSQL | TIMESTAMP |
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.
TLS Verificationlink
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.
Schema changeslink
Amplitudelink
Added 3 new tables
USER_ALIASING_PROFILE
USER_PROPERTY
USER_MERGE_TIME
Changed the primary key from event_id, projectName to event_id, device_id, client_event_time in
EVENT
table. DeletedDEVICE
table.
Asanalink
Added new field start_on
to TASK
table.
Criteolink
Added a new table
FACEBOOK_DPA_REPORT
.Added
advertiser_id
toCAMPAIGN_PERFORMANCE_REPORT
andTRANSACTION_ID_REPORT
.Changed primary key to
_fivetran_id
forCAMPAIGN_PERFORMANCE_REPORT
andTRANSACTION_ID_REPORT
because thecategory_id
field from the composite primary key is coming in asnull
.
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:
ACCOUNT
CAMPAIGN
ADSET
AD
Google Adslink
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.
Iterablelink
We are no longer syncing the previously-deprecated USER_MESSAGE
table. You can access the same information from the EVENT
table.
Mavenlinklink
- Added
RATE_CARD_VERSION_HISTORY
andRATE_CARD_ROLE_HISTORY
tables.
Microsoft Advertisinglink
We've added new fields to reporting tables.
Reporting Table | Fields |
---|---|
ACCOUNT_IMPRESSION_PERFORMANCE_DAILY_REPORT | absolute_top_impression_share_percent , click_share_percent |
AD_GROUP_IMPRESSION_PERFORMANCE_DAILY_REPORT | absolute_top_impression_share_percent , click_share_percent |
CAMPAIGN_IMPRESSION_PERFORMANCE_DAILY_REPORT | absolute_top_impression_share_percent , click_share_percent |
PRODUCT_DIMENSION_PERFORMANCE_DAILY_REPORT | assisted_impressions , assisted_clicks |
PRODUCT_DIMENSION_PERFORMANCE_HOURLY_REPORT | assisted_impressions , assisted_clicks |
PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_DAILY_REPORT | absolute_top_impression_share_percent , click_share_percent , assisted_impressions , assisted_clicks |
PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_HOURLY_REPORT | absolute_top_impression_share_percent , click_share_percent , assisted_impressions , assisted_clicks |
AD_PERFORMANCE_DAILY_REPORT | ad_description, ad_description_2 |
AD_PERFORMANCE_HOURLY_REPORT | ad_description , ad_description_2 |
NetSuitelink
We added several new tables following the NetSuite 2018.2 release. Their behavior is specified below.
ACCOUNT_PERIOD_ACTIVITY_PE
will not be synced separately because it contains a subset of the information in the larger tablePOSTING_ACCOUNT_ACTIVITY_PE
which we already sync.The following tables will be re-imported based on sync frequency:
CUSTOMER_SUBSIDIARY_MAP
POSTING_ACCOUNT_ACTIVITY_PE
PRICE_BOOKS
PRICE_BOOK_LINE_INTERVALS
PRICE_PLANS
PRICE_TIERS
REVENUE_PLAN_VERSIONS
STANDARD_COST_COMPONENTS
The following tables will be updated incrementally:
BILLING_SUBSCRIPTIONS
EXPENSE_AMORTIZATION_RULES
EXPENSE_PLANS
GLOBAL_INVENTORY_RELATIONSHIPS
PLANNED_STANDARD_COSTS
SUBSCRIPTION_CHANGE_ORDERS
SUBSCRIPTION_PLANS
BILLING_SUBSCRIPTION_LINES
andSUBSCRIPTION_PLAN_LINES
are sub tables ofBILLING_SUBSCRIPTIONS
andSUBSCRIPTION_PLANS
respectively and will be updated along with the parent tables.
Zendesklink
The
TICKET_METRIC_EVENT
table is deprecated. We will stop syncing this table after May 1, 2019. It will be replaced by theSLA_POLICY_HISTORY
andTICKET_SLA_POLICY
tables.Added new table
SLA_POLICY_HISTORY
with the following fields:id
updated_at
title
description
position
created_at
Added new table
TICKET_SLA_POLICY
with the following fields:sla_policy_id
ticket_id
policy_applied_at
Improvementslink
Adobe Analyticslink
Fivetran now supports Conversion Variable evar37
in the setup form.
Amplitudelink
We have changed the value of initial_sync_start_time
to 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 client_event_time
parameter.
GitHublink
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.
Google Adslink
- We upgraded our connector from AdWords API v201806 to v201809 and handled deprecation.
- Renamed the report
DESTINATION_URL_REPORT
toFINAL_URL_REPORT
. - Read more about the deprecations and changes in Google's AdWords API documentation.
Microsoft Dynamics 365 CRMlink
Fivetran now syncs binary data from Dynamics 365 Sources.
Oraclelink
Fivetran has significantly increased the speed of initial syncs in Oracle by leveraging information from a system metadata table called DBA_EXTENTS
.
Salesforcelink
- Fivetran will add a log message to Customer Logs when skipping an infrequently updated table.
Segmentlink
For the 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.
Shopifylink
In order to ensure the accuracy of Order data, we now use Shopify Webhooks to capture Order Updates.
Sisenselink
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.
Stripelink
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.
Added Tables
ATTRIBUTE
AUTHORIZATION
CARDHOLDER
DISPUTE_BALANCE_TRANSACTION
FILE
INVOICE_DISCOUNT
ISSUING_CARD
ISSUING_DISPUTE
PAYMENT_INTENT
PAYOUT
PRODUCT
SHIPPING_METHOD
SUBSCRIPTION_DISCOUNT
SUBSCRIPTION_ITEM
TIER
TRANSACTION
TRANSFER_REVERSAL
Renamed Tables
_ACCOUNT
->ACCOUNT
_APPLICATION_FEES
->APPLICATION_FEE
_APPLICATION_FEE_REFUNDS
->APPLICATION_FEE_REFUND
_BALANCE_TRANSACTIONS
->BALANCE_TRANSACTION
_BANK_ACCOUNTS
->BANK_ACCOUNT
_CARDS
->CARD
_CHARGES
->CHARGE
_COUPONS
->COUPON
_CUSTOMERS
->CUSTOMER
_DISPUTES
->DISPUTE
_FEES
->FEE
_INVOICES
->INVOICE
_INVOICE_ITEMS
->INVOICE_ITEM
_ORDER
->ORDER
_ORDER_ITEM
->ORDER_ITEM
_ORDER_RETURNED
->ORDER_RETURN
_ORDER_RETURNED_ITEM
->ORDER_RETURNED_ITEM
_PLANS
->PLAN
_REFUNDS
->REFUND
_REVIEWS
->REVIEW
_SKU
->SKU
_SOURCE
->SOURCE
_SUBSCRIPTIONS
->SUBSCRIPTION
_TOPUP
->TOPUP
_TRANSFERS
->TRANSFER
Deprecated Tables
_RECIPIENTS
_SUBSCRIPTION_PLAN
- The sunset date for version 0 is June 15, 2019.
- Connect to the new Stripe v1 integration.
Link to Stripe Documentation..
Zendesk Supportlink
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.