February 2022

Dashboard Improvements

Improved email notifications

We have standardized our email notifications' subject lines, content, and sender to make them easier to read. These changes allow you to quickly identify what the notification is about and resolve the issue.

IMPORTANT: If you manage your email notifications with subject or sender filters in your email application, update them to reflect these changes.

Learn more about email notifications in our Notifications documentation.

Renamed Tasks to Errors

In the Fivetran dashboard, we are renaming Tasks to Errors to describe their purpose more accurately. We are rolling out this change to all users in the coming weeks.

An Error is an issue that prevents your connector from processing any data. Learn more about Errors in our Alerts documentation.

We also now create an Unknown Error when your connector sync fails three times in a row for an unknown reason. Previously, we sent an email notification but did not create an Error in the dashboard.

Schema Tab - Primary and Foreign Keys Indicators

We now indicate primary key columns with a black key icon and foreign key columns with a white key icon on the Schema tab of the connector details page in your Fivetran dashboard.

schema_tab_keys

Fivetran GCP India Servers

We have added new servers in the Google Cloud Platform India (asia-south1) region.

You can now select India as your data processing location in your destination setup form. This means that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in India, your data does not leave India during processing.

For more information, see our data residency documentation.

Transformations for dbt Core

Integrated Scheduling

We have released integrated scheduling for Transformations for dbt Core*. Integrated scheduling lets you automatically trigger dbt model runs immediately after a connector sync completes. As a result, it reduces data latency by running transformations on new data as soon as it's loaded into your destination. It also helps you save on cloud computing costs by not running transformations on outdated data. To learn more about integrated scheduling, see Transformations for dbt Core.

Learn how to add your dbt models and schedule their runs directly in the Fivetran dashboard.

Add new transformation for dbt Core in Fivetran dashboard

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Select dbt Version in Setup Form

You can now specify your dbt version in the Transformations for dbt Core setup form. Previously, we required you to use the deployment.yml file to specify your dbt version. If you included a dbt version in the deployment.yml file, we now ignore it. To learn more, see the Transformations for dbt Core setup guide.

New connectors

Zendesk Sell

Zendesk Sell is a sales CRM solution and sales force automation tool.

Read our Zendesk Sell connector documentation.

Schema changes

Coupa

We are deprecating the following tables:

EASY_FORM
EASY_FORM_WIDGET
EASY_FORM_WIDGET_RULE

Facebook Ads

We have added three new tables:

AD_STUDY stores ad campaign data for the brand_lift_studies field
ADSET_SCHEDULE stores ad set data for the adset_schedule field
LOOKALIKE_TARGET_COUNTRY_NAME stores target_country_names field data for a custom audience lookalike_spec

We have added a new field, has_advertiser_opted_in_odax, to the ACCOUNT_HISTORY table. Learn more in Facebook's Ad Account documentation.

We have added a new field, preview_shareable_link, to the AD_HISTORY table. Learn more in Facebook's Ad documentation.

We have added two new fields, ad_strategy_group_id and bid_strategy, to the CAMPAIGN_HISTORY table. Learn more in Facebook's Campaign documentation.

We have added the following new fields to the CREATIVE_HISTORY table:

link_destination_display_url
source_instagram_media_id
thumbnail_id
platform_customizations
template_url_spec Learn more in Facebook's Ad Creative documentation.

We have added the following new fields to the CUSTOM_AUDIENCE_HISTORY table:

lookalike_origin_event_name
lookalike_origin_event_source_name
lookalike_product_set_name Learn more in Facebook's Custom Audience documentation.

GitHub

We have added a new table, STARGAZER, that stores information about repository stargazers.

We no longer update the stargazers_count column of the REPOSITORY table. For connectors created after February 9, 2022, this column is not present in the REPOSITORY table.

Google Ads

We now support Google Ads API v9. We have made the following schema changes:

We added the ASSET_GROUP_PRODUCT_GROUP_VIEW and HOTEL_RECONCILIATION reports
We now populate the cpc_bid_ceiling_micros and cpc_bid_floor_micros columns for the MAXIMIZE_CONVERSION_VALUE and MAXIMIZE_CONVERSIONS bidding strategy types in the CampaignBiddingStrategyHistory table
We now populate the in_stream_action_button_label and in_stream_action_headline columns for VIDEO_NON_SKIPPABLE_IN_STREAM_AD in the VideoAdHistory table

We have removed the keyword_ad_group_criterion field from the AD_STATS pre-built report in the Google Ads connectors that use the new Google Ads API. This field segments data by keyword and all other segments are excluded from the report when this field is used. As a result, we observed discrepancies in the fetched reporting data. For all connectors using the new Google Ads API and syncing the AD_STATS table, Fivetran re-syncs the AD_STATS table to backfill the correct historical data.

Kustomer

We have added a new column, first_message_in_meta_to, to the CONVERSATION table. The column stores the message recipient's email address.

Microsoft Advertising

We have added the following new columns to the tables below:

TABLES	NEW COLUMNS
`AD_PERFORMANCE_*`	`conversions_qualified`, `all_conversions_qualified`, and `view_through_conversions_qualified`
`GOALS_AND_FUNNELS_*`	`all_conversions_qualified`, `view_through_conversions_qualified`
`KEYWORD_PERFORMANCE_*`	`conversions_qualified`, `all_conversions_qualified`, `view_through_conversions_qualified`
`PRODUCT_SEARCH_QUERY_PERFORMANCE_*`	`conversions_qualified`, `all_conversions_qualified`
`SEARCH_QUERY_PERFORMANCE_*`	`conversions_qualified`, `all_conversions_qualified`
`USER_LOCATION_PERFORMANCE_*`	`conversions_qualified`

Pinterest Ads

We have made the following schema changes to support Pinterest Ads API version 4:

We have added two new tables, PRODUCT_ITEM_REPORT and CATALOG_PRODUCT_GROUPS_HISTORY.

We have added the following fields to the tables below:

catalog_product_group_id to the PRODUCT_GROUP_HISTORY table
billing_profile_status, billing_type, merchant_id, and status to the ADVERTISER_HISTORY table
updated_time and created_time to the AUDIENCE_HISTORY table
enhanced_match_status, last_fired_time_ms, status, and version to the CONVERSION_TAG_HISTORY table
summary_status, status_time, end_time, and campaign_budget_optimization_enabled to the CAMPAIGN_HISTORY table

Pinterest has deprecated the following tables, so we have removed them:

TAG_HISTORY
APP_EVENT_TRACKING_CONFIG_HISTORY
ITEM_REPORT

Pinterest has deprecated the following fields, so we have removed them from the tables below:

deleted, exclude, and new_match_type from the KEYWORD_HISTORY table
NOTE: The deleted field was removed, but the archived field has similar usage. According to Pinterest, archiving a keyword effectively deletes it. The keywords no longer receive metrics and are no longer visible within the parent entity's keywords list. For more information, see Pinterest's documentation.
valid and active from the PRODUCT_GROUP_HISTORY table
test_account and is_one_tap from the ADVERTISER_HISTORY table
rule from the AUDIENCE_HISTORY table
num_matched_user_records and list_type from the CUSTOMER_LIST_HISTORY table
verification_status, click_window_days, conversion_type, view_window_days, created_time, engagement_window_days, and updated_time from the CONVERSION_TAG_HISTORY table
billing_group, product_filter, measurement_partner_campaign_id, and placement_exclusion from the CAMPAIGN_HISTORY table

We have updated the primary keys for the following tables:

id, updated_time, advertiser_id, and audience_type is a new primary key for the AUDIENCE_HISTORY table
date, product_group_id, advertiser_id, targeting_type, and targeting_value is a new primary key for the PRODUCT_GROUP_TARGETING_REPORT table

Stripe

We have added two new tables, ORDER_HISTORY and SUBSCRIPTION_HISTORY. We automatically sync these tables for connectors created after February 1, 2022.

Typeform

We have changed the data type of the number field from INT to DOUBLE in the RESPONSE_VARIABLE table.

Zuora

We have added the following new tables:

CALLOUT_HISTORY
CHARGE_METRICS_RUN
DISCOUNT_APPLY_DETAIL
DISCOUNT_CLASS
INVOICE_ADJUSTMENT
JOURNAL_ENTRY_DETAIL_CREDIT_BALANCE_ADJUSTMENT
JOURNAL_ENTRY_DETAIL_CREDIT_MEMO_APPLICATION_ITEM
JOURNAL_ENTRY_DETAIL_CREDIT_MEMO_ITEM
JOURNAL_ENTRY_DETAIL_CREDIT_TAXATION_ITEM
JOURNAL_ENTRY_DETAIL_DEBIT_MEMO_ITEM
JOURNAL_ENTRY_DETAIL_DEBIT_TAXATION_ITEM
JOURNAL_ENTRY_DETAIL_INVOICE_ADJUSTMENT
JOURNAL_ENTRY_DETAIL_INVOICE_ITEM
JOURNAL_ENTRY_DETAIL_INVOICE_ITEM_ADJUSTMENT
JOURNAL_ENTRY_DETAIL_INVOICE_PAYMENT
JOURNAL_ENTRY_DETAIL_PAYMENT_APPLICATION
JOURNAL_ENTRY_DETAIL_PAYMENT_APPLICATION_ITEM
JOURNAL_ENTRY_DETAIL_REFUND_APPLICATION
JOURNAL_ENTRY_DETAIL_REFUND_APPLICATION_ITEM
JOURNAL_ENTRY_DETAIL_REFUND_INVOICE_PAYMENT
JOURNAL_ENTRY_DETAIL_REVENUE_EVENT_ITEM
JOURNAL_ENTRY_DETAIL_TAXATION_ITEM

Improvements

Box

The Box connector now supports syncing Microsoft Excel spreadsheets to your destination. We sync each worksheet in the spreadsheet as a unique table in your destination. We are gradually rolling out this improvement to all our existing connectors.

Datadog

Our Datadog log service is now generally available.

Read our Datadog documentation.

Dropbox

The Dropbox connector now supports syncing Microsoft Excel spreadsheets to your destination. We sync each worksheet in the spreadsheet as a unique table in your destination. We are gradually rolling out this improvement to all our existing connectors.

Facebook Ads

We have upgraded our Facebook Ads connector to version 13.0 of the Facebook API. For more information, see Facebook's v13.0 changelog.

Google Drive

The Google Drive connector now supports syncing Google Sheets and Microsoft Excel spreadsheets to your destination. We sync each worksheet in the spreadsheet as a unique table in your destination. We are gradually rolling out this improvement to all our existing connectors.

HubSpot

We have added support for custom objects. You can now sync custom objects from your HubSpot account to your destination. We create a destination table for each custom object. We are gradually rolling out this improvement to all our existing connectors.

Jira

You can now select Projects in the setup form to sync only their associated issues.

select_projects

Magic Folder Connectors

We now support syncing Microsoft Excel spreadsheets for the following Magic Folder connectors:

We are gradually rolling out this feature to all our existing connectors.

Mixpanel

We have added a new optional field, Data Region, to the connector setup form. If your Mixpanel data resides in the European Union, select the Data Region as EU.

OneDrive

The OneDrive connector now supports syncing Microsoft Excel spreadsheets to your destination. We sync each worksheet in the spreadsheet as a unique table in your destination. We are gradually rolling out this improvement to all our existing connectors.

Oracle E-Business Suite

Our Oracle E-Business Suite (EBS) connector is now generally available.

Read our Oracle EBS connector documentation.

Oracle RAC

Our Oracle RAC connector is now generally available.

See our Oracle RAC connector setup instructions.

Pinterest Ads

We have upgraded our connector from Pinterest Ads API version 3 to version 4, because Pinterest has deprecated version 3. For more information, see Pinterest Ads' API documentation.

Sage Intacct

We have implemented a new custom strategy to capture deleted records because the Sage Intacct API doesn't offer a reliable mechanism to capture deletes. For more information about the strategy, see our Capture deletes documentation.

Salesforce

We have upgraded our Salesforce connector to the Salesforce BULK API 2.0 version. The connector now uses both the Salesforce BULK API and REST API for incremental syncs. Previously, the connector used the REST API for incremental syncs. We are gradually rolling out the Bulk API feature to all our connectors. Your user experience may vary depending on the implementation status. Contact our support team to enable this feature on your connector.

Twilio

The initial sync now extracts all available records to the CONVERSATION and related tables. Subsequent syncs only extract records that were updated up to seven days before the last sync. Previously, we extracted every record with each sync, potentially causing lengthy syncs.

REST API Improvements

Adobe Analytics

We have updated the Adobe Analytics connector's REST API configuration parameters to support aggregating data by month, quarter, and year. Learn more in our Adobe Analytics Connector Config documentation.

Data processing region changes

We have added the following new regions:

GCP_US_EAST4
GCP_US_WEST1
GCP_EUROPE_WEST3
GCP_AUSTRALIA_SOUTHEAST1
GCP_NORTHAMERICA_NORTHEAST1
GCP_EUROPE_WEST2
GCP_ASIA_SOUTHEAST1
AWS_US_EAST_1
AWS_US_EAST_2
AWS_US_WEST_2
AWS_AP_SOUTHEAST_2
AWS_EU_CENTRAL_1
AWS_EU_WEST_1
AWS_EU_WEST_2
AZURE_EASTUS2
AZURE_AUSTRALIAEAST
GCP_ASIA_SOUTH1

We have deprecated the following regions:

US
EU
APAC
UK
CANADA
SINGAPORE

Response Message Changed

We have changed the Add a User to a Group API response message to more accurately reflect the action performed.

Before:

{
    "code": "Success",
    "message": "User has been invited to the group"
}

Now:

{
    "code": "Success",
    "message": "User has been added to the group"
}