June 2021

Dashboard Improvements

Filter selected tables on Schema tab

We now support filtering by selected tables. To view only selected tables, click the filter icon, then select Only show selected tables.

Selected table filter:

Filtered list:

Improved email notification management

We have redesigned the Notifications page in the Fivetran dashboard to make it easier for you to manage your email notifications. You can now manage your notifications at the connector, transformation, and account levels to ensure that you only receive the notifications that you want.

Learn more about notifications in our notifications documentation.

Schema change settings menu replaces checkbox

We replaced the Include new schemas and tables by default checkbox on the Schema tab of the connector details page with the Schema Change Settings menu.

Schema change settings menu:

User Filter on Account Page

We have added a user filter on the Users tab of the Account page. See Account Management.

User Filter:

Expanded Free MAR Operations

The following operations now count towards free MAR:

• Re-syncs that Fivetran support initiates in your dashboard
• Re-syncs that Fivetran engineers initiate to fix connector bugs specific to your account

Previously, these operations counted towards paid MAR.

You can now view the free MAR for the actions that the Fivetran Platform Connector performs.

You can now track your MAR on the Usage tab of your Fivetran dashboard.

These changes were automatically applied to your account on June 1, 2021 at midnight UTC.

SSH Tunnels

More stable SSH tunnels

We now retry new SSH Tunnel connections if we run into temporary network errors. Previously, our connection attempts failed when we ran into temporary network errors. We will roll this change out gradually over the next month.

Transformations for dbt Core

Custom credentials for Snowflake

You can now customize the credentials that Fivetran uses to access your Snowflake destination to run dbt jobs. Add your credentials in the Credentials section of your dbt Tranformations setup form. Learn more in our dbt setup guide.

Skip dbt docs serve command

We now skip the dbt docs serve command, which starts a webserver on port 8000 to serve documentation locally. This command is not intended to be used with Fivetran.

Schema changes

Asana

We have removed the hearted and assignee_status fields from the TASK table.

We have added a new field, num_likes, to replace the num_hearts field in the TASK table. Asana has deprecated the num_hearts field. We will discontinue the num_hearts field from the TASK table after July 31, 2021. Be sure to update your queries.

Braze

We have added a new table, RANDOM_BUCKET_NUMBER_EVENT. For more information, see Braze's Customer Behavior and User Events documentation.

Facebook Ads

We no longer support the attribution_spec field for ad accounts because it has been deprecated.

We now support the following fields in the ACCOUNT_HISTORY table:

• extended_credit_invoice_group
• failed_delivery_checks
• is_in_3ds_authorization_enabled_market
• is_in_middle_of_local_entity_migration

We now support the conversion_domain and issues_info fields in the AD_HISTORY table.

We now support the following fields in the AD_SET_HISTORY table:

• asset_feed_id
• daily_min_spend_target
• daily_spend_cap
• is_dynamic_creative
• issues_info
• learning_stage_info
• lifetime_min_spend_target
• lifetime_spend_cap
• multi_optimization_goal_weight
• optimization_sub_event
• review_feedback

We now support the following fields in the CAMPAIGN_HISTORY table:

• ad_strategy_id
• budget_remaining
• is_skadnetwork_attribution
• last_budget_toggling_time
• lifetime_budget
• pacing_type
• promoted_object
• smart_promotion_type
• special_ad_categories
• special_ad_category
• special_ad_category_country
• topline_id

We now support the following fields in the CREATIVE_HISTORY table:

• authorization_category
• bundle_folder_id
• categorization_criteria
• category_media_source
• destination_set_id
• dynamic_ad_voice
• effective_authorization_category
• effective_instagram_media_id
• enable_direct_install
• messenger_sponsored_message
• object_store_url
• place_page_set_id
• playable_asset_id

We now support the following fields in the CUSTOM_AUDIENCE_HISTORY table:

• customer_file_source
• external_event_source
• pixel_id

Fivetran Platform Connector

From June 1, 2021 00:00 UTC, our Fivetran Platform Connector reports only paid Monthly Active Rows (MAR). This is a forward only change that will not be applied for the previous months. The Usage tab in the Dashboard will continue to display both free and paid MAR. We have increased visibility into free MAR in the Dashboard and made certain types of re-sync free. No action is required on your part. For more details, see the Expanded Free MAR Operations changelog.

Google Ads

We have added the ad_group_id field to the following tables:

• AD_GROUP_CRITERION_LABEL_HISTORY
• CUSTOM_PARAMETER_HISTORY
• DISAPPROVAL_REASON_HISTORY
• FINAL_APP_URL_HISTORY
• FINAL_MOBILE_URL_HISTORY
• FINAL_URL_HISTORY.

We have added the campaign_id and updated_at fields to the LOCATION table.

Google Campaign Manager 360

Google introduced a breaking change in their API, which changed the names of multiple dimensions and metrics. As a result, we have been unable to sync new data to the affected custom columns since May 23, 2021. We added a new column for each dimension and metric whose name was changed and synced the updates into it. You can find a complete list of affected dimensions and metrics in Google's Reporting updates announcement.
Check if any of your connectors use these dimensions and metrics. Contact our support team if you face any problems with your connectors.

HubSpot

We have added the following new tables, to support HubSpot's Marketing Email API:

• MARKETING_EMAIL
• MARKETING_EMAIL_CAMPAIGN
• MARKETING_EMAIL_CONTACT
• MARKETING_EMAIL_CONTACT_LIST

Instagram Business

We have added a new field, followers_count, to the USER_HISTORY table.

Jira

We have added a new field, is_active, to the ISSUE_FIELD_HISTORY and ISSUE_MULTISELECT_HISTORY tables. The field allows you to assemble the complete current state of an issue without a full table scan. It is true for the current issue records and false for historical issue records. To get values in the is_active field for all issues, re-sync your connector. We are gradually rolling out this feature to connectors set up after September 10, 2020.

Marketo

We have added a new table, FOLDER, to support Marketo API's Folders endpoint.

Mixpanel

We now use the _fivetran_id and time columns as the schema's primary keys to support Mixpanel's deduplication logic. We select the _fivetran_id value based on the following conditions:

• For connectors created before November 20, 2020, we select the _fivetran_id value based on the following conditions:

  • If the record's event.time value is before July 1, 2021, we calculate the _fivetran_id value by generating the hash for the entire record.
  • If the record's event.time value is after July 1, 2021, we use the record's insert_id value as the _fivetran_id value.

• For connectors created after November 20, 2020, we use the record's insert_id value as the _fivetran_id value.

We now sync the event.time field as TIMESTAMP_NTZ. Previously, we synced the field as TIMESTAMP_TZ.

Improvements

Airtable

We now display a warning on your connector dashboard when we detect that Airtable has deleted your payloads.

Criteo

We have upgraded our Criteo connector from version 2020.07 to 2021.01 of the Criteo API and handled deprecations and updates. Learn more about the deprecations and changes in Criteo's API documentation.

Databricks

Our Databricks destination now supports Databricks SQL endpoint connections. For more information, see our setup instructions.

We now support Databricks on Google Cloud.

Dropbox

We have added support for syncing files/folders in root folder for Dropbox team spaces.

Facebook Ads

We have upgraded our Facebook Ads connector from version 9.0 to 10.0 of the Facebook Marketing API and handled deprecations and updates. Learn more about the deprecations and changes in the Facebook Marketing API v10.0 changelog.

NOTE: Starting from version 10.0, Facebook API returns a maximum of 37 months' worth of data.

We have changed the data type of the instant_experience_outbound_clicks field from LONG to List<AdsActionStats> to support the new Facebook API version. Now, the field provides detailed information about the number of clicks on links in an Instant Experience that take users off Facebook-owned properties. To ensure data integrity, re-sync any reports where you have used this field.

Google Play

We now support two new Store Performance statistics reports, stats_store_performance_country and stats_store_performance_traffic_source. We are gradually rolling out this change to all existing connectors.

Jira

We now sync system Jira fields, such as project andpriority, even if there are custom fields with the same names. Previously, we skipped all fields that had the same names. This feature applies to connectors set up before September 10, 2020. Connectors created after this date sync all fields regardless of the names.

Lever

We can now sync confidential opportunities to the OPPORTUNITY table. Previously, we were only able to sync non-confidential opportunities.

Redshift

We have added a new optional field, Cluster region, to the destination setup form. You can now choose the AWS Region of your S3 bucket. Fivetran will use the data staging bucket in the cluster region you select. If you use VPC security policies, you must select the same region as the Redshift cluster. If you do not specify the cluster region, we will use your data processing location as the cluster region.

We have added a new optional field, Cluster ID, to the destination setup form. If you authenticate using IAM and use an SSH tunnel to connect, you must enter the Cluster ID and the Cluster region.

We have added a new setup test to validate if you have provided the Cluster ID and Cluster region details in the setup form. We perform this test only if you use IAM authentication and an SSH tunnel to connect.

Square

We have updated our OAuth scopes to support the Disputes endpoint of the Square API. You must re-authorize the connector. On your Connector Details page, go to the Setup tab, click Edit connection details, and then click Re-authorize connection. See Square's documentation for more information.

REST API Improvements

New Field Added in API Request

We have expanded the Create a connector endpoint. Now, you can:

• set the frequency of your syncs using the sync_frequency request parameter
• set the start time of your daily syncs using the daily_sync_time request parameter if you set the sync_frequency parameter to 1440

New Field Added in API Response

We now display the role field for each user in the response for the List All Users endpoint.

New REST API Endpoints

We have implemented a new Group Management API endpoint for our REST API. You can now leverage the new Modify a group feature.