August 2021

Cloud Service Provider - AWS Support

We now use Amazon Web Services (AWS) as a cloud service provider in addition to Google Cloud Platform (GCP). Depending on the plan you are on, you can now select the cloud service provider (AWS or GCP) for your connectors.

See our Data Residency documentation for more details.

Dashboard Improvements

Change account name

You can now change your account name on the Settings tab of the account management page on your Fivetran dashboard. Only Account Administrators can make this change.

Account name editor:

Improved connector links

We've updated the structure of our URLs to allow you to link to connectors directly without switching destinations. Previously, our URLs only took you to the connector page if you were viewing its associated destination. Now, our URLs take you to the connector page, regardless of the destination you're currently viewing.

NOTE: The URL does not take you to the connector page if you do not have access to that connector.

URLs that use the old format still function.

Improved connector links:

New alerts style

We have redesigned our dashboard alerts to make them easier to read.

Old alert:

New alert:

Redesigned connector list filters

We have increased the size of the search box in the connector list to make it easier to read. We also changed the order of the status and source filters so that they correspond to the column order below.

Old connector list filters:

New connector list filters:

Fivetran Business Critical

Fivetran now offers a new plan level, Business Critical, for maximum security over data infrastructure, pipelines, and access. The plan includes several new security-focused features, including customer-managed keys and AWS PrivateLink support.

Learn more about Business Critical and our other plans at the Fivetran pricing plan comparison page.

AWS PrivateLink

We now support AWS PrivateLink for Business Critical accounts. AWS PrivateLink allows VPCs and AWS-hosted or on-premises services to communicate with one another without exposing traffic to the public internet. PrivateLink is the most secure connection method. You can use AWS PrivateLink with your source, destination, or both your source and destination.

Learn more in our database connection and destination connection documentation.

Customer-managed keys

We now support customer-managed keys for Business Critical accounts. With customer-managed keys, you own the master key that Fivetran uses to encrypt your credentials and temporary data, giving you greater control over Fivetran's access to your data.

Learn more in our customer-managed keys documentation.

Free MAR for Private Preview connectors

All new Monthly Active Rows (MAR) associated with connectors in private preview is now free. Fivetran automatically applied this change to all accounts on August 1, 2021, at midnight UTC. This change applies only to MAR incurred after August 1, 2021, and will not be applied retroactively to previous months' MAR. When a connector moves into beta, we begin charging paid MAR for it.

New connectors

Datadog

Datadog is a monitoring and analytics platform for cloud applications.

Read our Datadog connector documentation.

TikTok Ads

TikTok Ads is a video-sharing social networking platform.

Read our TikTok Ads connector documentation.

Transformations for dbt Core

dbt 0.20.1 support

We now support dbt 0.20.1. You can use this version to run your projects.

Increased thread limit

We now support up to 32 dbt threads. Note that the number of threads must be compatible with your destination type. For example, Snowflake supports only 8 concurrent queries.

Schema changes

Eloqua

We have added a new primary key column, activty_type, to the CONTACT_ACTIVTY table. This change prevents data integrity issues when multiple contact activities have the same id.

Google Ads

We have removed the URL_PERFORMANCE_REPORT and AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT reports from the Report name list to support Google AdWords API changes.

Iterable

We have fixed a bug where Iterable connectors created before June 14, 2021, synced the CAMPAIGN_SUPPRESSION_LIST_HISTORY table as CAMPAIGN_SUPRESSION_LIST_HISTORY in the destination. We now sync data to both versions of the table in your destination. Be sure to update your queries.

Pipedrive

We have added the following new tables:

• FILTER
• FILTER_HELPER
• LEAD_HISTORY
• LEAD_LABEL_HISTORY
• LEAD_LEAD_LABEL
• LEAD_SOURCE
• TEAM
• TEAM_USER
• GOAL
• GOAL_RESULT
• SUBSCRIPTION
• SUBSCRIPTION_PAYMENT
• PERMISSION_SET
• PERMISSION
• PERMISSION_ASSIGNMENT

SAP Concur

We have added a new primary key column, index, to the following tables:

• AIR
• CAR
• DINING
• EVENT
• HOTEL
• PARKING
• RAIL
• TRAVEL

We have added a new primary key column, segment_index, to the following tables:

• CHARGE_FIXED
• CHARGE_PERCENTAGE
• CHARGE_RATE
• CHARGE_RATE_WITH_ALLOWANCE

We have removed the confirmation_number column from the following tables:

• AIR
• CAR
• DINING
• EVENT
• HOTEL
• PARKING
• RAIL
• TRAVEL
• CHARGE_FIXED
• CHARGE_PERCENTAGE
• CHARGE_RATE
• CHARGE_RATE_WITH_ALLOWANCE

Stripe

We have added a new table, PROMOTION_CODE. See Stripe's promotion code documentation for more details.

We have deprecated the metadata_* columns from the Stripe schema.

Improvements

Apple Search Ads

Our Apple Search Ads connector now supports multithreading. We can now use multiple parallel API requests to fetch data from your Apple Search Ads account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Apple Search Ads API quota and account metadata.

We have upgraded our Apple Search Ads connector from version 3 to 4 of the Apple Search Ads API. For more information, see Apple Search Ads API documentation.

We have added support for OAuth 2.0.

BigQuery

We have added support for the BIGNUMERIC data type to store decimal types. For connectors created after August 3, 2021, we convert BIGDECIMAL data type to BIGNUMERIC data type in your BigQuery destination. We are gradually rolling out this change to all existing connectors.

You can now opt to use an external service account to load data into your BigQuery destination. Set the Use own Service Account toggle to ON. For more information, see our setup instructions.

Box

Our Box connector is now generally available.

Read our Box connector documentation.

Criteo

We now support all currencies listed in Criteo's currencies documentation. Previously, we only supported 25 currencies.

In the connector setup form, you can now select the timezone you want to use to sync the Transaction ID and Statistics reports. If you don't select a timezone, Fivetran fetches the reports using the default timezone (UTC).

In the connector setup form, you can now select the metrics you want to use to sync the Statistics reports. You can also select additional metrics to sync. In the Metrics field, click the down arrow icon and select the metrics.

Metrics list:

Facebook Ads

We have added support for lifetime aggregation with prebuilt and custom reports.

Facebook Pages

Our Facebook Pages connector is now generally available.

Read our Facebook Pages connector documentation.

HubSpot

The HubSpot connector now supports history mode for the following tables:

• COMPANY_PROPERTY_HISTORY
• CONTACT_PROPERTY_HISTORY
• DEAL_PROPERTY_HISTORY
• LINE_ITEM_PROPERTY_HISTORY
• PRODUCT_PROPERTY_HISTORY
• TICKET_PROPERTY_HISTORY

We are gradually rolling out this improvement to all existing connectors. For more information about history mode, see our documentation.

Jira

Now, if your Jira installation returns an HTTP 500 Internal Server error during a sync, we only skip the relevant issue field records from the sync. Previously, the entire sync failed.

Microsoft Advertising

Our Microsoft Advertising connector now supports multithreading. We can now use multiple parallel API requests to fetch Ads data from your Microsoft Advertising account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Microsoft Advertising account metadata.

Mixpanel

We have changed our sync strategy and now retrieve events data from Mixpanel using Processing Time event.mp_processing_time_ms. Previously, we used Event Time event.time. During internal performance testing, we observed a reduction in sync time. To ensure data integrity, we have rolled back the EVENT table’s cursor by six days. As a result of this rollback, you may observe a longer sync duration in your next sync.

You can now exclude the following tables from your syncs:

• ANSWER
• ANDROID_DEVICE
• IOS_DEVICE
• TRANSACTION

To exclude these tables, go to the Schema tab of your connector details page and deselect them.

NOTE: If you deselect these tables and later reselect them, you must manually re-sync the tables, because we don't maintain their state due to a lack of timestamp support in the source.

Outbrain

Our Outbrain connector now supports multithreading. We now use multiple parallel API requests to sync data from your Outbrain account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Outbrain API quota and account metadata.

Redshift

We have added support for the TIMESTAMP_TZ data type. For connectors created after August 30, 2021, we convert INSTANT data type to TIMESTAMP_TZ data type in your Redshift destination.

Shopify

We now use webhooks to capture deletes for the following tables:

• CHECKOUT
• COLLECTION
• CUSTOMER
• CUSTOMER_SAVED_SEARCH
• DRAFT_ORDER
• FULFILLMENT_EVENT
• INVENTORY_ITEM
• LOCATION
• ORDER
• PRODUCT

Snapchat Ads

Our Snapchat Ads connector now supports multithreading. We now use multiple parallel API requests to sync data from your Snapchat Ads account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Snapchat Ads API quota and account metadata.

Stripe

We now support the PAYMENT_INTENT table for Stripe Connect accounts. If you'd like to sync data from Stripe connected accounts, contact our support team.

The Stripe connector now supports table-level re-syncs.

We now support table grouping in the Schema tab of your connector details page.

The Stripe connector now supports history mode for the following tables:

• ORDER
• SUBSCRIPTION
• SUBSCRIPTION_ITEM

We are gradually rolling out this improvement to all existing connectors.

Taboola

Our Taboola connector now supports multithreading. We now use multiple parallel API requests to sync data from your Taboola account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Taboola API quota and account metadata.

Webhooks

We have added support for storing data in two cloud-specific buckets, Google Cloud Storage (GCP) and Amazon S3 (AWS). We restrict your data within the selected cloud provider and the already supported United States (US) and European Union (EU) regions. New connectors will utilize storage based on the cloud service provider selected in the destination setup form. We will continue to store the existing connectors' data in Google Cloud Storage in their respective regions.

We have added support for the JSON: API media type application/vnd.api+json.

Zuora

The Zuora Sandbox connector now supports the Central Sandbox environment. The environment supports both US and EU regions. See our setup instructions for more information.

REST API Improvements

Path parameters validation

We have added validation for the schema and table path parameters for the Re-sync Connector Table Data endpoint. For a request to succeed, you need to specify its parameters correctly.

When you call this endpoint with an incorrect schema value, you receive the following error:

HTTP 404
"message" : "Cannot find entity 'Schema' with id '<your_connector_schema_id>'."

NOTE: Your previously successful request may fail with the error, indicating that you have been using the wrong schema value.

You can find the name of your database schema and table on the Schema tab of the connector details page.

NOTE: Make sure you don't use the connector schema name instead of the database schema name.

See our Re-sync Connector Table Data endpoint documentation for details.

Log events

Log Event Property Update

We have updated the value of the log event's connector_id property. Previously, the connector_id and connector_name properties both contained the connector name. Now, connector_id contains the connector ID, while connector_name still contains the connector name.

Learn more in our Logs documentation.