November 2019

Connector Status page updates

We have redesigned the Connector Status page to include detailed information about your syncs:

The Sync History chart shows how long each step of your sync took, along with the data volume for your entire sync. We have also improved the chart's load time.
The User Actions list shows what has changed in your connector within last 30 days and tracks who made those changes.
The Stats list shows your connector's average sync time for the last 14 days and the number of schema changes in the last 30 days.

Connector Status Page Updates

New connectors

Adobe Analytics Data Feed

Adobe Analytics Data Feed delivers raw clickstream data in a batched manner on a recurring daily or hourly delivery schedule.

Read our Adobe Analytics Data Feed connector documentation.

Anaplan

Anaplan is a cloud-based platform for business planning and modeling.

Read our Anaplan connector documentation.

Schema changes

Microsoft Advertising

We have made a number of schema changes to our Microsoft Advertising connector (formerly Bing Ads) to support version 13 of the Bing Ads SDK.

We have removed the click_calls and manual_calls fields from the following tables:

ACCOUNT_PERFORMANCE_DAILY_REPORT
ACCOUNT_PERFORMANCE_HOURLY_REPORT
ACCOUNT_IMPRESSION_PERFORMANCE_DAILY_REPORT
ACCOUNT_IMPRESSION_PERFORMANCE_HOURLY_REPORT
AD_GROUP_PERFORMANCE_DAILY_REPORT
AD_GROUP_PERFORMANCE_HOURLY_REPORT
AD_GROUP_IMPRESSION_PERFORMANCE_DAILY_REPORT
AD_GROUP_IMPRESSION_PERFORMANCE_HOURLY_REPORT
CAMPAIGN_PERFORMANCE_DAILY_REPORT
CAMPAIGN_PERFORMANCE_HOURLY_REPORT
CAMPAIGN_IMPRESSION_PERFORMANCE_DAILY_REPORT
CAMPAIGN_IMPRESSION_PERFORMANCE_HOURLY_REPORT

We have removed the average_cpp field from the following tables:

ACCOUNT_PERFORMANCE_DAILY_REPORT
ACCOUNT_PERFORMANCE_HOURLY_REPORT

We have removed the impression_lost_to_bid_percent, impression_lost_to_expected_ctr_percent,impression_lost_to_ad_relevance_percent, andimpression_lost_to_rank_percent fields from the following tables:

ACCOUNT_PERFORMANCE_DAILY_REPORT
ACCOUNT_PERFORMANCE_HOURLY_REPORT
ACCOUNT_IMPRESSION_PERFORMANCE_DAILY_REPORT
ACCOUNT_IMPRESSION_PERFORMANCE_HOURLY_REPORT
AD_GROUP_PERFORMANCE_DAILY_REPORT
AD_GROUP_PERFORMANCE_HOURLY_REPORT
AD_GROUP_IMPRESSION_PERFORMANCE_DAILY_REPORT
AD_GROUP_IMPRESSION_PERFORMANCE_HOURLY_REPORT
CAMPAIGN_PERFORMANCE_DAILY_REPORT
CAMPAIGN_PERFORMANCE_HOURLY_REPORT
CAMPAIGN_IMPRESSION_PERFORMANCE_DAILY_REPORT
CAMPAIGN_IMPRESSION_PERFORMANCE_HOURLY_REPORT

The data that was previously split amongst these four columns is now aggregated in the impression_lost_to_rank_agg_percent column.

We have added the following tables:

SEARCH_QUERY_PERFORMANCE_HOURLY_REPORT
SEARCH_QUERY_PERFORMANCE_DAILY_REPORT
PRODUCT_SEARCH_QUERY_PERFORMANCE_HOURLY_REPORT
PRODUCT_SEARCH_QUERY_PERFORMANCE_DAILY_REPORT

Shopify

We have added a new table, APPLIED_GIFT_CARD, which is a replica of the existing GIFT_CARD table. APPLIED_GIFT_CARD is the correct name for this table. We will update both tables with data for the past three months, then remove the GIFT_CARD table. Be sure to update your queries with the new name before we remove the GIFT_CARD table.

We have added a new column, test, to the ORDER table.

Stripe

We have added a new column, network, to the CARD table.

Zendesk Support

We now add system data to the TICKET table. Each new system data column will have the prefix system_ (for example, system_location).

Improvements

Adobe Analytics

You can now select how many months' worth of reporting data you'd like to include in your initial sync. Choose from the following options:

3 months
6 months
12 months (default)
24 months
All time

Amazon Aurora PostgreSQL Destination

We now officially support Amazon Aurora PostgreSQL as one of our destinations.

Read our Amazon Aurora PostgreSQL documentation.

Amplitude

The Amplitude connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Amplitude's priority-first syncs fetch the most recent 15 days' worth of data from all tables.

To learn more, see our priority-first sync documentation.

Aurora RDS MySQL Destination

We now officially support Aurora RDS MySQL as one of our destinations.

See our Aurora RDS MySQL setup instructions.

Azure Synapse

Our Azure Synapse destination is now generally available.

Read our Azure Synapse destination documentation.

Front

The Front connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Front's priority-first syncs fetch the most recent 30 days' worth of data from the CONVERSATION table and its child tables.

To learn more, see our priority-first sync documentation.

Google Ads

We now force the creation of schemas even if they contain no data. This is especially helpful for Looker users, since Looker's pre-built SQL queries fail if all tables and columns in a schema are not present. Previously, we did not create schemas when they contained no data.

We now sync default empty -- values to your destination as NULL values to keep column types consistent.

Help Scout

We now store all conversation events that occur between our data syncs. Previously, each sync only fetched the latest event for each conversation.

We do not receive the customerWaitingSince object from webhooks. All CONVERSATION_HISTORY records synced via webhooks will not have the following fields:

customer_waiting_since_time
customer_waiting_since_friendly
customer_waiting_since_latest_reply_from

The Help Scout connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Help Scout's priority-first syncs fetch the most recent 15 days' worth of data from the CUSTOMER_HISTORY and CONVERSATION_HISTORY tables and their child tables.

To learn more, see our priority-first sync documentation.

Iterable

The Iterable connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Iterable's priority-first syncs fetch the most recent seven days' worth of data from the EVENT table.

To learn more, see our priority-first sync documentation.

Marketo

We have released version 3 of our Marketo connector. This new version:

Fixes data integrity issues with Marketo activities by fetching them using BULK API
Syncs your most recent activity data first using priority-first sync

For more details about Marketo version 3, see our Marketo documentation.

Microsoft Advertising

We have renamed our Bing Ads connector to Microsoft Advertising, following Microsoft's name change. This name change applies to the Fivetran dashboard and our documentation.

We have upgraded our connector to use Bing Ads SDK version 13, since the previous version (v.12) has been deprecated. For more information, see Microsoft's Bing Ads API version 13 documentation.

Mixpanel

The Mixpanel connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Mixpanel's priority-first syncs fetch the most recent 15 days' worth of data from the EVENT table.

To learn more, see our priority-first sync documentation.

NetSuite SuiteAnalytics

We have changed reimport frequency for reimported tables:

Table Import Duration	Import Frequency
20 secs or less	Re-import in every sync
Between 20 secs and 60 mins	Re-imported twice a day
More than 60 mins	Re-imported once a week

Tables that take longer than 20 seconds to import get marked as not recommended on the dashboard and include a message on how frequently Fivetran syncs them. For more information, see our NetSuite SuiteAnalytics documentation.

Oracle

We now support the TIMESTAMP WITH LOCAL TIME ZONE column type. It will appear as TIMESTAMP in your destination.

We've fixed some bugs with NUMBER and FLOAT column types with high precision or scale. Previously, these values might have been rounded, but they are now copied to the destination exactly as they appear in the source database. Oracle 11g is an exception to this fix because LogMiner incorrectly rounds some values.

We no longer re-sync tables when we detect GRANT DDL operations. We will roll out this change to all connectors over the next four weeks.

Pardot

We have fixed a bug in our Pardot connector. Previously, we only synced visitors flagged as "Identified," because by default, the visitor endpoint we use to sync visitors only syncs visitors flagged as "Identified." We have changed the setting and now sync all visitors.

Because of this bug, there may be a mismatch between the list of visitors in your Pardot dashboard and in the VISITOR table in your destination. If you notice a mismatch, you need to re-sync the VISITOR table to fix it. Contact support to trigger a re-sync.

Pendo

The Pendo connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Pendo's priority-first syncs fetch the most recent seven days' worth of data from the ACCOUNT_HISTORY and VISITOR_HISTORY tables.

To learn more, see our priority-first sync documentation.

PostgreSQL

We can now use unique key constraints to import tables without a primary key, making imports more efficient and reliable. This fix will be gradually rolled out over the next few weeks.

We now require that the PostgreSQL database configuration parameter statement_timeout is either 0 (the default value to disable the timeout) or is greater than 5 minute. Fivetran validates this value during the setup test.

Salesforce Marketing Cloud

The Salesforce Marketing Cloud connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Salesforce Marketing Cloud's priority-first syncs fetch the most recent 14 days' worth of data from the following tables:

EVENT
SUBSCRIBER
TRIGGERED_SEND
SEND
EMAIL
LIST_SUBSCRIBER
LIST

To learn more, see our priority-first sync documentation.

Snowflake

We now support Snowflake on Google Cloud Platform. For more information, see Snowflake's website.

Twitter Ads

We have improved the sync speed for our Twitter Ads connector.

Previously, we made one API call per entity ID per day of data during syncs. We therefore had to make a large number of API calls when we fetched data for multiple entity IDs and/or for multiple days' worth of data. Making so many API calls slowed down our syncs.

Now Fivetran can fetch multiple days' worth of data for up to 20 entity IDs in a single API call, which makes syncs significantly faster.

Zendesk Support

The Zendesk connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Zendesk's priority-first syncs fetch the most recent 15 days' worth of data from the TICKET table and its child tables.

To learn more, see our priority-first sync documentation.