February 2019

Destination SSH keys

Fivetran now uses SSH keys entirely unique to your destination while creating any SSH tunnel connections.

Find the key in your Destination Setup Page and add it to authorized keys on your SSH tunnel server. See detailed instructions in our SSH Tunnel Configuration documentation.

New connectors

Azure Database for MariaDB

Azure Database for MariaDB is a MariaDB database service built on Microsoft's scalable cloud infrastructure for application developers.

See our Azure Database for MariaDB setup instructions.

Azure Database for MySQL

Azure Database for MySQL is a MySQL database service built on Microsoft's scalable cloud infrastructure for application developers.

See our Azure Database for MySQL setup instructions.

Lightspeed Retail

Lightspeed Retail is a cloud-based point of sale (POS) solution that is suitable for retailers.

Read our Lightspeed Retail connector documentation.

Splunk

Splunk is a software platform that searches, analyzes and visualizes the machine-generated data gathered from websites, applications, sensors, and devices.

Read our Splunk connector documentation.

Schema changes

Amplitude

We have added a new table, EVENT_AMPLITUDE_ATTRIBUTION_ID.

We have changed the primary key of the USER table from user_id to amplitude_id and project_name.

Apple Search Ads

In the CAMPAIGN_HISTORY table, we changed the loc_invoice_detail_order_number column from INT to STRING.

Iterable

We have deprecated the USER_MESSAGE table. We will stop syncing this table after March 15, 2019.

We have added a new column, workflow_id, to the CAMPAIGN_HISTORY table.

Jira

The PROJECT table will have key and project_type_key columns either after re-sync or for all new Jira connections.

Kantata

We now re-sync the ASSIGNMENT table daily to detect deleted records.

We have deprecated the RATE_CARD table and will remove the table after March 20, 2019.

We have added the RATE_CARD_HISTORY table to replace RATE_CARD and RATE_CARD_SET_HISTORY tables.

Marketo

Fivetran now fetches lead activities following the Marketo Activities Data Retention Policy.

High volume activities are fetched for the past 90 days. This includes following activities:

• Add to List
• Change Score
• Change Data Value
• Visit Webpage
• Sync Lead to SFDC
• Sync Lead to Microsoft
• Update Opportunity
• Request Campaign

All other activities are fetched for the past 25 months.

Microsoft Advertising

We have added a new table, AD_ATTRIBUTE_HISTORY.

Optimizely

We released a new version of the Optimizely connector and have made the following schema changes:

• Renamed the existing EVENT table to VISITOR_ACTION table.
• Added a new EVENT table that syncs from /v2/events.
• Converted existing tables EXPERIMENT, EXPERIMENT_PAGE, CAMPAIGN and CAMPAIGN_PAGE to HISTORY tables.
• Dropped EXPERIMENT_STATUS and CAMPAIGN_STATUS tables.
• Separated existing METRIC table into EXPERIMENT_METRIC_HISTORY and CAMPAIGN_METRIC_HISTORY tables.
• Added field event_id in the EXPERIMENT_METRIC_HISTORY and CAMPAIGN_METRIC_HISTORY tables.
• Separated existing CHANGE table into EXPERIMENT_CHANGE_HISTORY and CAMPAIGN_CHANGE_HISTORY tables.

PostgreSQL

TIMESTAMP column types will now be represented as TIMESTAMP WITHOUT TIME ZONE in the destination.

TSRANGE columns will be represented as JSON, with TIME WITHOUT TIME ZONE encoded as STRING.

Salesforce Marketing Cloud

We dropped the following fields from the TRIGGERED_SEND table:

• cc_email
• interaction_id
• is_always_on
• is_send_logging
• pre_header
• replyto_address
• replyto_display_name
• send_window_delete

Shopify

We have added the following new tables:

• DRAFT_ORDER
• DRAFT_ORDER_NOTE_ATTRIBUTE
• DRAFT_ORDER_LINE
• DRAFT_ORDER_LINE_TAX_LINE

Twitter Ads

We upgraded the connector to Twitter Ads API version v4. Read more about their new version on Twitter's documentation. As part of the upgrade, we have made the following schema changes:

• Removed the VIDEO_HISTORY and VIDEO_REASON_HISTORY tables as Twitter deprecated the videos endpoint.
• Removed the preview_url column from the CARD_HISTORY table.
• Renamed the app_country_code column of the CARD_HISTORY table to country_code.

UserVoice

We have renamed the MESSAGE table to SUPPORTER_MESSAGE.

Xero

We have made the following primary key changes:

• invoice_id is new the primary key of the _INVOICE_LINE_ITEM table.
• overpayment_id is new the primary key of the _OVERPAYMENT_LINE_ITEM table.
• prepayment_id is new the primary key of the _PREPAYMENT_LINE_ITEM table.
• repeating_invoice_id is new the primary key of the _REPEATING_INVOICE_LINE_ITEM table.

Fivetran will not store the deleted line_item records for the above tables.

Zendesk Support

We have added a new table, TICKET_CUSTOM_FIELD, with id and title columns. For custom fields, TICKET_FIELD_HISTORY.field_name is a field ID that references TICKET_CUSTOM_FIELD.id.

Improvements

Amazon DynamoDB

You can now re-sync individual tables from the dashboard.

HubSpot

We now automatically sync new fields in the ENGAGEMENT_* tables.

LinkedIn Ad Analytics

We have released a new version of the LinkedIn Ad Analytics connector. The new version delivers Ad Analytics reports at campaign and creative levels. The schema change adds metadata tables in addition to report tables.

Read our LinkedIn Ad Analytics connector documentation.

Microsoft Advertising

We have added support for the new Ad Type Responsive Search Ad. We have upgraded V0 of our connector to use the latest Bing Ads SDK v.12 as the previous version v.11 is deprecated.

Deprecated Fields

The AccountStatus field has been deprecated for CAMPAIGN_PERFORMANCE and AD_GROUP_PERFORMANCE report types.

Renamed Fields

The following fields have been renamed. These renamed fields are updated in your setup form but the column names in your destination remain unchanged.

Microsoft Dynamics 365 CRM

The tables that do not support Change Tracking will be shown as Not Recommended in Standard Config.

SQL Server

Tables with clustered indices are now queried using smaller page sizes. This reduces the contiguous length of time that a Fivetran connector has a lock on a table from which it's reading, without adversely affecting sync speeds.