March 2019

Performance improvements

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 destinations before April 30. Not doing so will result in a connection failure.

Databases:

• MariaDB
• MongoDB
• MySQL
• Oracle
• PostgreSQL
• SQL Server

Destinations:

• Redshift
• Azure Synapse
• Snowflake

If you don't use any of the above databases or destinations with Fivetran, you don't need to take any action.

Support for ISO 8601 format timestamps

Fivetran now infers and syncs ISO 8601 timestamp formats (for example, 2011-12-03T10:15:30+01:00[Europe/Paris] and 2011-12-03T10:15:30+01:00) as timestamp values.

TIMESTAMP WITHOUT TIMEZONE support

Fivetran has added core support for the TIMESTAMP WITHOUT TIMEZONE data type. Up until now, Fivetran assumed that timestamps without timezone were in UTC. This addition means that for the following databases with a TIMESTAMP WITHOUT TIMEZONE type will replicate to a more correct destination type:

• MySQL
• Oracle
• PostgreSQL
• SQL Server

TIMESTAMP WITHOUT TIMEZONE support is immediately available for Oracle, PostgreSQL, and SQL Server. MySQL and MariaDB support will be released soon.

This change is backwards compatible. Fivetran 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 verification

Fivetran is rolling out TLS verification for connections to databases and destinations. TLS allows for both encryption and authentication of the connections. Select your trusted certificates in your database and destination setup tests. For more information see our TLS Verification documentation.

Schema changes

Amplitude

We have added three new tables:

• USER_ALIASING_PROFILE
• USER_PROPERTY
• USER_MERGE_TIME

We have changed the composite primary key of the EVENT table. The new primary key consists of the event_id, device_id, and client_event_time columns. Previously, the key consisted of the event_id and projectName columns.

We have deleted the DEVICE table.

Asana

We have added a new column, start_on, to the TASK table.

Criteo

We have added a new table, FACEBOOK_DPA_REPORT.

We have added a new column, advertiser_id, to the CAMPAIGN_PERFORMANCE_REPORT and TRANSACTION_ID_REPORT tables.

We have changed primary key to _fivetran_id for the CAMPAIGN_PERFORMANCE_REPORT and TRANSACTION_ID_REPORT tables because the API is returning category_id field values as null.

Google Ads

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.

Iterable

We no longer sync the previously-deprecated USER_MESSAGE table. You can access the same information from the EVENT table.

Kantata

We have added two new tables, RATE_CARD_VERSION_HISTORY and RATE_CARD_ROLE_HISTORY.

Microsoft Advertising

We've added the following new fields to the reporting tables below:

NetSuite SuiteAnalytics

We added several new tables following the NetSuite 2018.2 release. Their behavior is specified below.

• We will not sync ACCOUNT_PERIOD_ACTIVITY_PE separately because it contains a subset of the information in the larger table POSTING_ACCOUNT_ACTIVITY_PE which we already sync.

• We will re-import the following tables 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

• We will incrementally update the following tables:

  • BILLING_SUBSCRIPTIONS
  • EXPENSE_AMORTIZATION_RULES
  • EXPENSE_PLANS
  • GLOBAL_INVENTORY_RELATIONSHIPS
  • PLANNED_STANDARD_COSTS
  • SUBSCRIPTION_CHANGE_ORDERS
  • SUBSCRIPTION_PLANS

• BILLING_SUBSCRIPTION_LINES and SUBSCRIPTION_PLAN_LINES are child tables of BILLING_SUBSCRIPTIONS and SUBSCRIPTION_PLANS respectively. We will update the child tables along with the parent tables.

Zendesk Support

We have deprecated the TICKET_METRIC_EVENT table. We will stop syncing this table after May 1, 2019. The table will be replaced by the SLA_POLICY_HISTORY and TICKET_SLA_POLICY tables.

We have added a new table, SLA_POLICY_HISTORY with the following columns:

• id
• updated_at
• title
• description
• position
• created_at

We have added a new table, TICKET_SLA_POLICY with the following columns:

• sla_policy_id
• ticket_id
• policy_applied_at

Improvements

Adobe Analytics

Fivetran now supports conversion variable evar37 in the setup form.

Amplitude

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.

GitHub

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 Ads

We upgraded our connector from AdWords API v201806 to v201809 and handled deprecation. As part of the upgrade, we renamed the DESTINATION_URL_REPORT report to FINAL_URL_REPORT. Read more about the deprecations and changes in Google's AdWords API documentation.

Microsoft Dynamics 365 CRM

Fivetran now syncs binary data from Dynamics 365 Sources.

Oracle

Fivetran has significantly increased the speed of initial syncs in Oracle by leveraging information from a system metadata table called DBA_EXTENTS.

Salesforce

Fivetran will add a log message to customer logs when skipping an infrequently updated table.

Segment

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.

Shopify

In order to ensure the accuracy of Order data, we now use Shopify webhooks to capture order updates.

Stripe

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 to ACCOUNT
  • _APPLICATION_FEES to APPLICATION_FEE
  • _APPLICATION_FEE_REFUNDS to APPLICATION_FEE_REFUND
  • _BALANCE_TRANSACTIONS to BALANCE_TRANSACTION
  • _BANK_ACCOUNTS to BANK_ACCOUNT
  • _CARDS to CARD
  • _CHARGES to CHARGE
  • _COUPONS to COUPON
  • _CUSTOMERS to CUSTOMER
  • _DISPUTES to DISPUTE
  • _FEES to FEE
  • _INVOICES to INVOICE
  • _INVOICE_ITEMS to INVOICE_ITEM
  • _ORDER to ORDER
  • _ORDER_ITEM to ORDER_ITEM
  • _ORDER_RETURNED to ORDER_RETURN
  • _ORDER_RETURNED_ITEM to ORDER_RETURNED_ITEM
  • _PLANS to PLAN
  • _REFUNDS to REFUND
  • _REVIEWS to REVIEW
  • _SKU to SKU
  • _SOURCE to SOURCE
  • _SUBSCRIPTIONS to SUBSCRIPTION
  • _TOPUP to TOPUP
  • _TRANSFERS to TRANSFER

• Deprecated Tables

  • _RECIPIENTS
  • _SUBSCRIPTION_PLAN

The sunset date for version 0 is June 15, 2019. Connect to the new Stripe v1 connector.

Zendesk Support

You can now configure your Zendesk Support connector through the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.