May 2023

Dashboard Improvements

Connector Status page updates

We aligned the connector Status page with other parts of the UI and have introduced the following changes:

• Added status badge to the connector page to align it with the information on the Connector List.
• Moved information text related the connector to a new part of the page.
• Moved the sync timestamp to above the sync chart.
• Removed duplicate information.

The connector status page now looks as follows:

Compared to how it looked before:

We also updated icons on the initial sync cards and now display a Resume Initial Sync button if a connector is paused during the initial sync.

New User Settings section

We added User Settings, a new settings section where you can access and edit information about the current user. To access it, click your name in the bottom left corner and go to User Settings.

In the Details tab, you can:

• Update your name
• Reset your password
• Update your user picture

In the Resources tab, you can access the lists of your destinations, connectors, and teams.

Release notes page link

We have added a Release notes link to the Fivetran dashboard. You can find it in the Resources & Support section of the navigation menu:

Lite Connectors

Lite connectors are now available for the following sources:

• Ada
• Brex
• Drip
• Guru
• Khoros Care
• Orbit
• Productboard
• RetailNext
• Retently
• Rithum
• Samsara
• SCORM
• Squarespace
• Survicate
• When I Work

New connectors

BigQuery

BigQuery is a cloud data warehouse. Read our BigQuery connector documentation.

Firebase

Firebase is an application development platform. Fivetran supports the Firebase Cloud Firestore database. Read our Firebase connector documentation.

Schema changes

BigCommerce

We have added two new tables, COUPON_STATE_RESTRICTION and COUPON_ZIP_RESTRICTION.

Braze

We have added two new tables, CANVAS_EXIT_EVENT and CANVAS_EXPERIMENT_STEP_CONVERSION_EVENT.

We now support the CANVAS_EXPERIMENT_STEP_ENTRY_EVENT table.

We have added the following new columns to the CONTENT_CARD_EVENT table:

• app_group_id
• abort_log
• abort_type
• canvas_step_message_variation_id
• canvas_step_message_variation_updated_at
• dispatch_id

We have added the following new columns to the EMAIL_EVENT table:

• app_group_id
• abort_log
• abort_type
• canvas_step_message_variation_id
• canvas_step_message_variation_updated_at
• device_id:DEVICE

We have added the following new columns to the IN_APP_MESSAGE_EVENT table:

• abort_log
• abort_type
• ad_id
• ad_id_type
• ad_tracking_enabled
• app_group_id
• browser
• canvas_step_message_variation_id
• canvas_step_message_variation_updated_at
• carrier
• dispatch_id
• resolution
• version

We have added the following new columns to the PUSH_NOTIFICATION_EVENT table:

• abort_log
• abort_type
• app_group_id
• canvas_step_message_variation_id
• canvas_step_message_variation_updated_at

We have added the following new columns to the NEWSFEED_CARD_EVENT table:

• abort_log
• abort_type
• app_group_id
• browser
• carrier
• resolution

We have added the following new columns to the SMS_EVENT table:

• app_group_id
• abort_type
• abort_log
• canvas_step_message_variation_id
• canvas_step_message_variation_updated_at
• timezone
• url
• short_url
• user_agent

We have added the following new columns to the SUBSCRIPTION_EVENT table:

• app_group_id
• app_id
• state_change_source

We have added the following new columns to the WEBHOOK_EVENT table:

• abort_log
• abort_type
• app_group_id
• canvas_step_message_variation_id
• canvas_step_message_variation_updated_at
• device_id
• dispatch_id

Facebook Pages

We have added the following new columns to the POST_ATTACHMENT_HISTORY table to store the URL address and size information for the image inside of the post attachment:

• media_image_src
• media_image_height
• media_image_width

Freshservice

We no longer use the _fivetran_deleted column in the ASSET_COMPONENT table. This change means that deleted data will be absent from the destination instead of being marked as deleted in the _fivetran_deleted column.

Gong

We have added two new tables, SCORECARD_ACTIVITY and SCORECARD_ACTIVITY_ANSWER.

We have migrated the name and value columns from the CALL_INTERACTION_STAT table to the CALL_INTERACTION table.

We have removed the CALL_INTERACTION_STAT table.

Google Analytics 4 Export

We have added a new column, event_timestamp, to the ITEM table.

HubSpot

We have added two new tables, ASSOCIATION_TYPE and CONTACT_COMPANY.

We have added two new columns, created_at and updated_at, to the following tables:

• DEAL_PIPELINE
• DEAL_PIPELINE_STAGE
• PROPERTY
• TICKET_PIPELINE
• TICKET_PIPELINE_STAGE

We have added the show_currency_symbol column to the PROPERTY table.

We have added a new column, type_id, to the following tables:

• DEAL_COMPANY
• DEAL_CONTACT

We have also included the type_id column as a part of the composite primary key for these tables. You can use the type_id column to identify primary associations.

These changes are available in all HubSpot connections created after May 8, 2023. We are gradually rolling out these changes to the existing HubSpot connections.

We have made the following schema changes to support HubSpot API v3:

• We have added the following new tables:

  • ENGAGEMENT_COMMUNICATION
  • ENGAGEMENT_POSTAL_MAIL
  • ENGAGEMENT_PROPERTY_HISTORY
  • LINE_ITEM_DEAL

• We no longer support the following tables:

  • ENGAGEMENT_PUBLISHING_TASK
  • ENGAGEMENT_EMAIL_BCC
  • ENGAGEMENT_EMAIL_CC
  • ENGAGEMENT_EMAIL_TO

• We have deprecated the following tables:

  • ENGAGEMENT_EMAIL_BCC
  • ENGAGEMENT_EMAIL_CC
  • ENGAGEMENT_EMAIL_TO

  The data from these deprecated tables will be available as columns in the ENGAGEMENT_EMAIL table. For more information, see HubSpot's Properties documentation.

• We have changed the primary key for a few ENGAGEMENT_* tables. The new composite primary key is a combination of the id and type columns. Previously, the id column was the primary key.

• To support the primary key change for older connectors, we have deleted the ENGAGEMENT_* tables and re-synced them.

• We have deprecated most of the existing columns of the ENGAGEMENT_* tables to standardize column naming conventions. We now sync the data only into the child tables' property_* columns. Check your HubSpot connector dashboard for the properties for each engagement type. However, we won't be able to create the new columns if you have set the Block all option in the SCHEMA CHANGE SETTINGS.

• We have deprecated the columns of the ENGAGEMENT table. We now sync the data into the child table's property_* columns.

• We no longer support the following columns in the tables below:

  Column	Table
  object_type	TICKET
  selected	LINE_ITEM_PROPERTY_HISTORY
  deal_id	LINE_ITEM

• To standardize the delete column, we have replaced the is_delete column with _fivetran_deleted column for the LINE_ITEM, TICKET, and PRODUCT tables. We will apply the changes to the older connectors as part of the migration.

• We have added a new table, LINE_ITEM_DEAL, to store data related to the association between line_item records and deal records.

• We have added a new column, type_id, to the following tables:

  • ENGAGEMENT_DEAL
  • ENGAGEMENT_COMPANY
  • ENGAGEMENT_CONTACT
  • TICKET_COMPANY
  • TICKET_CONTACT
  • TICKET_DEAL
  • TICKET_ENGAGEMENT

• We have added two new columns, source and, source_id, to the following tables:

  • LINE_ITEM_PROPERTY_HISTORY
  • PRODUCT_PROPERTY_HISTORY

These changes are available for all HubSpot connections created after May 12, 2023. We are gradually rolling out these changes to all existing HubSpot connections. See the HubSpot ERDs for more details.

Kantata

We have added the following new tables:

• SKILL
• SKILL_CATEGORY
• SKILL_MEMBERSHIP

We are gradually rolling out this change to all existing connections.

LinkedIn Company Pages

We have switched to the /posts endpoint. As a result of this switch, we have changed the column list of some of the existing tables and added some new tables.

Marketo

We now sync campaign data from the Smart Campaigns API endpoint and have made the following schema changes:

• We have added the following new columns to the CAMPAIGN table:

  • computed_url
  • flow_id
  • folder_id
  • folder_type
  • is_communication_limit_enabled
  • is_requestable
  • is_system
  • max_members
  • qualification_rule_type
  • qualification_rule_interval
  • qualification_rule_unit
  • recurrence_start_at
  • recurrence_end_at
  • recurrence_interval_type
  • recurrence_interval
  • recurrence_weekday_only
  • recurrence_day_of_month
  • recurrence_day_of_week
  • recurrence_week_of_month
  • smart_list_id
  • status

• We have removed the program_name column from the CAMPAIGN table.

We now support incremental updates for the CAMPAIGN table. We perform a full re-import of the table on the weekends to capture deletes.

Connections created after May 18, 2023, will support these changes by default. We are gradually rolling out these changes to all existing connections.

Microsoft Advertising

We now sync Headlines and Descriptions data of Responsive Ads into the AD_ATTRIBUTE_HISTORY table.

We have added a new column, asset_performance_label, to the AD_ATTRIBUTE_HISTORY table. For more information, see Microsoft's assetPerformanceLabel documentation.

Outreach

We have added a new table, MAILING_RECIPIENT. We are gradually rolling out this change to all existing connections.

Pardot

We have added a new table, LIST_EMAIL, to store the details of your sent emails.

Pendo

We have changed the primary key of the EVENT table. Now, we use only the _fivetran_id column as the primary key. Previously, we used a composite primary key which was a combination of the following columns:

• _fivetran_id
• accountId
• visitorId
• hour
• remoteIp
• server
• userAgent

Pipedrive

We have changed the composite primary key of the PERSON_EMAIL and PERSON_PHONE tables. The new composite key is a combination of the person_id and index columns.

Workday HCM

We have added a new table, WORKER_EVENT, which stores the event history data of Workers. We are gradually rolling out this change to all existing connections. For more information, see our Workday HCM ERD.

Zendesk Support

We have added a new column, id, to the TICKET_FIELD_OPTION table.

We have added the following new child tables to the TICKET_FORM_HISTORY table to support Ticket Forms:

• AGENT_CONDITION
• AGENT_CONDITION_REQUIRED_STATUS
• END_USER_CONDITION
• TICKET_FORM_FIELD
• TICKET_FORM_RESTRICTED_BRAND

Improvements

ADP Workforce Now

Our ADP Workforce Now connector is now generally available. Read our ADP Workforce Now connector documentation.

Amazon Ads

We have changed the INT data type to DOUBLE for the following metric columns in the PURCHASED_PRODUCT_KEYWORD_REPORT and PURCHASED_PRODUCT_TARGETING_REPORT reports:

• sales_other_sku_1_d
• sales_other_sku_7_d
• sales_other_sku_14_d
• sales_other_sku_30_d

Amazon DynamoDB

We now infer the data type of the partition and sort keys. Previously, we synced the keys as STRING. We use automatic data type assignment to find the optimal data type that we can use before writing the data to your destination.

Apple Search Ads

We removed the legacy OAuth authorization mode due to OAuth deprecated in the Apple Search Ads API.

AppsFlyer

We can now sync the raw data and aggregate data reports from the Pull API V2. For more information, see our AppsFlyer documentation and the REST API configuration parameters.

Azure Cosmos DB for NoSQL

Our Azure Cosmos DB for NoSQL connector is now generally available. Read our Azure Cosmos DB connector documentation.

BigQuery

We now support large tables. You can now configure a query results table to import large datasets. We have added a new toggle, Use working dataset for queries, to the connector setup form. For more information, see our setup instructions.

Braze

We now sync the following events types from Braze Currents into the corresponding destination tables:

For more information, see Braze's Message engagement events.

We have made the Folder (or Prefix) field mandatory in the connector setup form.

Confluent Cloud

You can now configure your Confluent Cloud destination using the Fivetran REST API.

Email

We now automatically skip files containing poorly formatted lines. We have removed the Error Handling option from the connector setup form. We no longer support the on_error config parameter in our REST API connector setup configuration.

Our Email connector can now sync packed JSON files. We have added a new drop-down menu, JSON Delivery Mode, to the connector setup form. The drop-down menu provides you the option to choose how Fivetran should handle your JSON data. For more information, see our setup instructions.

Facebook Ads

We have implemented incremental sync for the following tables:

• CAMPAIGN_HISTORY
• AD_SET_HISTORY
• AD_HISTORY

During the sync, Fivetran only fetches entities that have the updated_time value greater than the cursor value. The cursor can be reset by triggering a full or table-specific re-sync. For more information, read our Facebook Ads documentation.

FTP

Our FTP connector can now sync packed JSON files from FTP and FTPS servers. We have added a new drop-down menu, JSON Delivery Mode, to the connector setup form. The drop-down menu provides you the option to choose how Fivetran should handle your JSON data. For more information, see our setup instructions.

Function connectors

We have added support for the soft delete sync mode. For more information, see our Function connectors' overview documentation.

Google Ad Manager

We have upgraded our Google Ad Manager connector from version 202211 to 202305 of the Google Ad Manager API. As part of the upgrade, we have made the following changes:

• We have added the following new columns:

  • BID_AVERAGE_CPM
  • BID_COUNT
  • DEALS_BIDS
  • DEALS_BID_RATE
  • DEALS_BID_REQUESTS
  • DEALS_WINNING_BIDS
  • DEALS_WIN_RATE
  • PROGRAMMATIC_MATCH_RATE
  • PROGRAMMATIC_RESPONSES_SERVED
  • TOTAL_PROGRAMMATIC_ELIGIBLE_AD_REQUESTS
  • YIELD_GROUP_AUCTIONS_WON
  • YIELD_GROUP_BIDS
  • YIELD_GROUP_BIDS_IN_AUCTION
  • YIELD_GROUP_CALLOUTS
  • YIELD_GROUP_ESTIMATED_CPM
  • YIELD_GROUP_ESTIMATED_REVENUE
  • YIELD_GROUP_IMPRESSIONS
  • YIELD_GROUP_MEDIATION_CHAINS_SERVED
  • YIELD_GROUP_MEDIATION_FILL_RATE
  • YIELD_GROUP_MEDIATION_PASSBACKS
  • YIELD_GROUP_MEDIATION_THIRD_PARTY_ECPM
  • YIELD_GROUP_SUCCESSFUL_RESPONSES

• We have added the following new dimensions:

  • AD_TECHNOLOGY_PROVIDER_DOMAIN
  • AD_TECHNOLOGY_PROVIDER_ID
  • AD_TECHNOLOGY_PROVIDER_NAME
  • BID_RANGE
  • BID_REJECTION_REASON
  • BID_REJECTION_REASON_NAME
  • DATE_PT
  • DAY_OF_WEEK_PT
  • IS_ADX_DIRECT
  • MONTH_YEAR_PT
  • TCF_VENDOR_ID
  • TCF_VENDOR_NAME
  • WEEK_PT

• We have removed the following dimensions:

  • INVENTORY_OWNERSHIP_CODE
  • INVENTORY_OWNERSHIP_NAME
  • NETWORK_PARTNER_ID
  • NETWORK_PARTNER_NAME

For more information about the changes, see Google Ad Manager API's changelog.

Google Ads

We have upgraded our Google Ads connector from version 13 to 13.1 of the Google Ads API and added the following metrics to custom reports:

• metrics.average_target_cpa_micros
• metrics.average_target_roas

For more information about the changes, see the Google Ads API's changelog.

Google Cloud Storage

We can now sync packed JSON files from Google Cloud Storage. We have added a new drop-down menu, JSON Delivery Mode, to the connector setup form. The drop-down menu provides you the option to choose how Fivetran should handle your JSON data. For more information, see our setup instructions.

Height

Our Height connector is now generally available. Read our Height connector documentation.

HubSpot

We now use HubSpot API v3 to sync the following parent tables and their associated child tables:

• ENGAGEMENT

  • ENGAGEMENT_CALL
  • ENGAGEMENT_COMMUNICATION
  • ENGAGEMENT_COMPANY
  • ENGAGEMENT_CONTACT
  • ENGAGEMENT_DEAL
  • ENGAGEMENT_EMAIL
  • ENGAGEMENT_MEETING
  • ENGAGEMENT_NOTE
  • ENGAGEMENT_POSTAL_MAIL
  • ENGAGEMENT_PROPERTY_HISTORY
  • ENGAGEMENT_TASK

• LINE_ITEM

  • LINE_ITEM_DEAL
  • LINE_ITEM_PROPERTY_HISTORY

• PRODUCT

  • PRODUCT_PROPERTY_HISTORY

• TICKET

  • TICKET_COMPANY
  • TICKET_CONTACT
  • TICKET_DEAL
  • TICKET_ENGAGEMENT
  • TICKET_PROPERTY_HISTORY

New HubSpot connections created on or after May 12, 2023, will support this feature by default.

We are gradually rolling out the changes to all existing connections.

Iterable

We have added options to select Events and Custom Event in the connector setup form. You can now select the Events that you want to sync from the list. You can also select specific Custom Event that you want to sync in EVENT table. For more information, see our Sync events documentation.

Outreach

You can now block tables and select or deselect tables to be synced on the Schema tab of the connector details page. As part of this improvement, we disable the cursor for tables you deselect. When you select the deselected tables to be synced again, we re-sync these tables to maintain data integrity.

Pardot

We can now sync the EMAIL table into your destination using the Pardot API version 5 endpoints.

PostgreSQL

We can now sync tables with DATE primary keys using Fivetran Teleport Sync. For more information, see our PostgreSQL documentation.

Reddit Ads

We have released pre-built, dbt Core-compatible data models for Reddit Ads. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* 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.

S3 Data Lake

We have added support for the BINARY data type.

We have added support for two new AWS Regions, Asia Pacific (Tokyo) (ap-northeast-1) and Asia Pacific (Sydney) (ap-southeast-2).

Sage Intacct

We have fixed a bug where we didn't sync Sage Intacct custom objects. We have updated our sync mechanism to now sync custom objects.

If you don't want to sync custom objects, deselect the custom object tables from the Schema tab of your connector details page.

Salesforce

We have added formula fields translation support for Databricks and PostgreSQL destinations.

Salesforce Commerce Cloud

The Salesforce Commerce Cloud connector now supports priority-first sync for the CAMPAIGN and CATALOG tables. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Salesforce Commerce Cloud's priority-first syncs fetch the most recent 15 days' worth of data from the supported tables. We are gradually rolling out this change to all existing connections. To learn more, see our priority-first sync documentation.

SAP Concur

We have added support for the following new endpoints as SAP Concur has deprecated the Get Report Details (reportDetails) endpoint:

• Allocations (GET /api/v3.0/expense/allocations)
• Attendees (GET /api/v3.0/expense/attendees)
• Expense Entries (GET /api/v3.0/expense/entries)
• Itemizations (GET /api/v3.0/expense/itemizations)

SFTP

We now support syncing PGP (Pretty Good Privacy) encrypted files. We have added a new advanced configuration, PGP Encryption Options, to the connector setup form. For more information, see our setup instructions.

Our SFTP connector can now sync packed JSON files from SSH servers. We have added a new drop-down menu, JSON Delivery Mode, to the connector setup form. The drop-down menu provides you the option to choose how Fivetran should handle your JSON data. For more information, see our setup instructions.

Splunk Logging

We have added a new optional field, Splunk Channel Identifier, to the setup form. For more information, see our setup instructions.

The Trade Desk

Our The Trade Desk connector is now generally available. Read our The Trade Desk connector documentation.

Twilio

You can now exclude the following tables from your syncs:

• ADDRESS
• CALL
• COACHED_CALL
• CONFERENCE
• CONFERENCE_PARTICIPANT
• CONFERENCE_PARTICIPANT_EXTENDED
• EXECUTION
• EXECUTION_STEP
• FLOW_HISTORY
• INCOMING_PHONE_NUMBER
• OUTGOING_CALLER_ID
• TRUNK
• USAGE_RECORD

Workday RaaS

We have renamed our Workday connector to Workday RaaS. This name change applies to the Fivetran dashboard and our documentation.

YouTube Analytics

We now support table-level re-syncs for YouTube Analytics connections.

Zuora

We have released pre-built, dbt Core-compatible data models for Zuora. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* 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.

REST API Improvements

S3 Data Lake

You can now configure your S3 Data Lake destination using the Fivetran REST API.

Webhook automatic deactivation

Now, we deactivate a webhook if it consistently fails for more than three days and only responds with non-2xx codes. To activate the webhook, ensure that the setup is correct by retrieving the webhook details and updating them with corrected information along with passing "active": true in the request. Alternatively, you can create a new webhook.