August 2024

Lite Connectors

Lite connectors are now available for the following sources:

Sunset Connectors

FinancialForce

We sunset our FinancialForce connector. Effective Aug 01, 2024, we will no longer support the creation of new FinancialForce connectors.

We recommend you to use our Salesforce connector to sync your Certinia (formerly known as FinancialForce) data.

Microsoft Dynamics 365 Finance

We sunset our Microsoft Dynamics 365 Finance connector and replaced it with the new Microsoft Dynamics 365 Finance and Operations connector that allows you to sync data by pulling it from the Azure Data Lake storage connected to your Azure Synapse Link. Effective August 22, 2024, we will no longer support the creation of new Microsoft Dynamics 365 Finance connectors. However, we will continue to support all existing Microsoft Dynamics 365 Finance connectors until November 1, 2024.

Sunset Destinations

BigQuery DTS

We sunset our BigQuery DTS destination. Effective Aug 13, 2024, we will no longer support the creation of new BigQuery DTS destinations.

We recommend that you use a BigQuery destination for your data.

Transformations

dbt Core version 1.8.4 support

We now support dbt Core* version 1.8.4. You can use this version to run your projects.

NOTE: For this dbt Core version, we don't support MySQL and SQL Server destinations. These destinations are not currently supported by custom dbt Core adapters.

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

Schema changes

ActiveCampaign

We have added two new tables:

CAMPAIGN_LIST
CONTACT_LIST

Algolia

Effective August 26, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to ensure data integrity.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

43 total changes • 31 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`AVERAGE_CLICK_POSITION`
column	Rename Column	`index` 🔑	`index_name` 🔑
`CLICK_POSITION`
column	Primary Key Change	`end_date` 🔑	`end_date`	No longer a part of a composite primary key.
column	Rename Column	`index` 🔑	`index_name` 🔑
column	Primary Key Change	`start_date` 🔑	`start_date`	No longer a part of a composite primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`CLICK_POSITION_POSITION`
column	Deprecated Column	`click_position_end_date` 🔑		No longer primary key.
column	Rename Column	`click_position_index` 🔑	`click_position_index_name` 🔑
column	Deprecated Column	`click_position_start_date` 🔑		No longer primary key.
column	Primary Key Change		`click_position_fivetran_id` 🔑	New primary key.
`CLICK_THROUGH_RATE`
column	Rename Column	`index` 🔑	`index_name` 🔑
`CONVERSION_RATE`
column	Rename Column	`index` 🔑	`index_name` 🔑
`COUNTRY`
column	Rename Column	`index` 🔑	`index_name` 🔑
column	New Column		`end_date`
column	New Column		`start_date`
`FILTER`
column	Rename Column	`index` 🔑	`index_name` 🔑
column	New Column		`end_date`
column	New Column		`start_date`
`HIT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	Rename Column	`index`	`index_name`
column	New Column		`end_date`
column	New Column		`start_date`
`INDEX`
column	Rename Column	`index` 🔑	`index_name` 🔑
`INDEX_DETAIL`
column	Rename Column	`index`	`index_name`
`INDEX_REPLICA`
column	Rename Column	`index_id` 🔑	`index_name` 🔑
`RULE`
column	Rename Column	`index`	`index_name`
`SEARCH`
column	Rename Column	`index`	`index_name`
column	New Column		`end_date`
column	New Column		`start_date`
`SEARCH_COUNT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	Rename Column	`index`	`index_name`
`SEARCH_NO_CLICK`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	Rename Column	`index`	`index_name`
column	New Column		`end_date`
column	New Column		`start_date`
`SEARCH_NO_CLICK_RATE`
column	Rename Column	`index` 🔑	`index_name` 🔑
`SEARCH_NO_RESULT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	Rename Column	`index`	`index_name`
column	New Column		`end_date`
column	New Column		`start_date`
`SEARCH_NO_RESULT_RATE`
column	Rename Column	`index` 🔑	`index_name` 🔑
`SETTINGS`
column	Rename Column	`index`	`index_name`
`TOP_SEARCH (new table name: SEARCH)`
table	Rename Table	`TOP_SEARCH`	`SEARCH`
`USER_COUNT`
column	Rename Column	`index` 🔑	`index_name` 🔑

Appcues

Effective August 14, 2024 we use a new Augest 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made the following schema changes.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

12 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name
`MOBILE`
table	New Table		`MOBILE`
`MOBILE_STEP`
table	New Table		`MOBILE_STEP`
`MOBILE_TAG`
table	New Table		`MOBILE_TAG`
`MOBILE_TRAIT`
table	New Table		`MOBILE_TRAIT`
`PIN`
table	New Table		`PIN`
`PIN_MOBILE`
table	Deprecated Table	`PIN_MOBILE`
`PIN_MOBILE_STEP`
table	Deprecated Table	`PIN_MOBILE_STEP`
`PIN_MOBILE_TAG`
table	Deprecated Table	`PIN_MOBILE_TAG`
`PIN_MOBILE_TRAIT`
table	Deprecated Table	`PIN_MOBILE_TRAIT`
`PIN_STEP`
table	New Table		`PIN_STEP`
`PIN_TAG`
table	New Table		`PIN_TAG`
`PIN_TRAIT`
table	New Table		`PIN_TRAIT`

Brightcove

Effective August 22, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`ANALYTICS_REPORT`
column	New Column			`analytics_date`

Criteo

We've added the following fields to the ADSET table:

datasetId
objective
videoChannel
frequencyCappingMode

For more information, see the Criteo ERD.

Deputy

Effective August 21, 2024 we use a new August 2024. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to new tables are added.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

7 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPANY`
column	Renamed Column	`contact`	`contact_id`	Renaming for better data identification
`CONTACT`
table	New Table		`CONTACT`
`OPERATIONAL_UNIT`
column	Renamed Column	`contact`	`contact_id`	Renaming for better data identification
`PAY_PERIOD`
table	New Table		`PAY_PERIOD`
`RESOURCE_TIMESHEET`
column	Renamed Column	`creator`	`creator_id`	Renaming for better data identification
`STRESS_PROFILE`
table	New Table		`STRESS_PROFILE`
`TIMESHEET_PAY_RETURN`
table	New Table		`TIMESHEET_PAY_RETRUN`

Destini

Effective August 14, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required to adhere to standard naming conventions.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`PRODUCT`
column	Rename Column	`timestamp`	`timestamps`	Updated to adhere to standard naming conventions.
`TIMESTAMP (new table name: TIMESTAMPS)`
table	Rename Table	`TIMESTAMP`	`TIMESTAMPS`	Updated to adhere to standard naming conventions.
column	Rename Column	`timestamp`	`timestamps`	Updated to adhere to standard naming conventions.

Drip

Effective August 7, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to invalid combined tables.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`EMAIL_SERIES_CAMPAIGN_SUBSCRIBER`
table	Deprecated Table	`EMAIL_SERIES_CAMPAIGN_SUBSCRIBER`		Data now available in the `EMAIL_SERIES_SUBSCRIBER_ACTIVE`, `EMAIL_SERIES_SUBSCRIBER_UNSUBSCRIBED`, and `EMAIL_SERIES_SUBSCRIBER_REMOVED` tables.
`EMAIL_SERIES_SUBSCRIBER_ACTIVE`
table	New Table		`EMAIL_SERIES_SUBSCRIBER_ACTIVE`
`EMAIL_SERIES_SUBSCRIBER_REMOVED`
table	New Table		`EMAIL_SERIES_SUBSCRIBER_REMOVED`
`EMAIL_SERIES_SUBSCRIBER_UNSUBSCRIBED`
table	New Table		`EMAIL_SERIES_SUBSCRIBER_UNSUBSCRIBED`

Everhour

Effective August 27, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to a null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`TEAM_TIMER`
column	Primary Key Change	`started_at`	`started_at` 🔑	Added to primary key.
column	Primary Key Change	`task_id` 🔑	`task_id`	No longer primary key.

Facebook Ads

We have removed the messenger_sponsored_message column from the CREATIVE_HISTORY table because it is no longer supported by Facebook's Marketing API.

FireHydrant

Effective August 7, 2024 we use a new July 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required to fix the weekly re-sync feature. We've added new columns to differentiate between archived and non-archived data.

20 total changes • 0 possible breaking changes

Table/column	Change type	New name
`INCIDENT`
column	New Column	`is_archived`
`INCIDENT_CHANNEL`
column	New Column	`is_archived`
`INCIDENT_CONFERENCE_BRIDGE`
column	New Column	`is_archived`
`INCIDENT_CONFERENCE_BRIDGE_ATTACHMENT`
column	New Column	`is_archived`
`INCIDENT_CONVERSATION`
column	New Column	`is_archived`
`INCIDENT_CUSTOM_FIELD`
column	New Column	`is_archived`
`INCIDENT_ENVIRONMENT`
column	New Column	`is_archived`
`INCIDENT_FUNCTIONALITY`
column	New Column	`is_archived`
`INCIDENT_IMPACT`
column	New Column	`is_archived`
`INCIDENT_IMPACT_CONVERSATION`
column	New Column	`is_archived`
`INCIDENT_LAST_NOTE_CONVERSATION`
column	New Column	`is_archived`
`INCIDENT_LAST_NOTE_STATUS_PAGE`
column	New Column	`is_archived`
`INCIDENT_MILESTONE`
column	New Column	`is_archived`
`INCIDENT_RETRO_EXPORT`
column	New Column	`is_archived`
`INCIDENT_ROLE_ASSIGNMENT`
column	New Column	`is_archived`
`INCIDENT_SERVICE`
column	New Column	`is_archived`
`INCIDENT_STATUS_PAGE`
column	New Column	`is_archived`
`INCIDENT_TAG_LIST`
column	New Column	`is_archived`
`INCIDENT_TEAM_ASSIGNMENT`
column	New Column	`is_archived`
`INCIDENT_TICKET`
column	New Column	`is_archived`

Fivetran Platform Connector

We have deprecated the broken column of the CONNECTOR_TYPE table.

See our Fivetran Platform Connector ERD for more information.

Fountain

Effective August 5, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to invalid combined tables.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

17 total changes • 10 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`APPLICANT_BACKGROUND_CHECK`
column	Primary Key Change	`applicant_id`	`applicant_id` 🔑	Added to primary key.
column	Primary Key Change	`candidate_id` 🔑	`candidate_id`	No longer primary key.
column	Primary Key Change	`report_id` 🔑	`report_id`	No longer primary key.
column	New Column		`background_applicant_id`
column	Primary Key Change		`index` 🔑	Added to primary key.
`APPLICANT_COURSE_RESULT`
table	New Table		`APPLICANT_COURSE_RESULT`
`APPLICANT_LABEL`
table	New Table		`APPLICANT_LABEL`
`APPLICANT_LESSONLY_RESULT`
column	Primary Key Change	`applicant_id`	`applicant_id` 🔑	Added to primary key.
column	Primary Key Change	`lesson_url` 🔑	`lesson_url`	No longer primary key.
column	Primary Key Change		`index` 🔑	Added to primary key.
`APPLICANT_PATH_RESULT`
table	New Table		`APPLICANT_PATH_RESULT`
`APPLICANT_RESULT`
table	Deprecated Table	`APPLICANT_RESULT`		Data now available in the `APPLICANT_PATH_RESULT` and `APPLICANT_COURSE_RESULT` tables.
`LABEL`
table	Deprecated Table	`LABEL`		Data now available in the `STAGE_LABEL` and `APPLICANT_LABEL` tables.
`STAGE_LABEL`
table	New Table		`STAGE_LABEL`
`TEMPLATE_FUNNEL`
table	New Table		`TEMPLATE_FUNNEL`
`TEMPLATE_TIMESTAMP_FUNNEL`
table	Deprecated Table	`TEMPLATE_TIMESTAMP_FUNNEL`		Data now available in the `TEMPLATE_FUNNEL` and `TIMESTAMP_FUNNEL` tables.
`TIMESTAMP_FUNNEL`
table	New Table		`TIMESTAMP_FUNNEL`

GetFeedback

Effective August 12, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to ensure data integrity.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CHOICE_TRANSLATION`
table	New Table		`CHOICE_TRANSLATION`
`COMPONENT_TRANSLATION`
table	New Table		`COMPONENT_TRANSLATION`
`TRANSLATION`
table	Deprecated Table	`TRANSLATION`		Data now available in the `COMPONENT_TRANSLATION` and `CHOICE_TRANSLATION` tables.

Google Ads

We've renamed the DISCOVERY_CAROUSEL_AD_HISTORY metadata table to DEMAND_GEN_CAROUSEL_AD_HISTORY.

We've renamed the DISCOVERY_MULTI_ASSET_AD_HISTORY metadata table to DEMAND_GEN_MULTI_ASSET_AD_HISTORY.

We've renamed the segments.sk_ad_network_conversion_value to segments.sk_ad_network_fine_conversion_value.

We now support the following new resources as custom reports with new metrics for Performance Max and Search campaigns:

We now support the PER_STORE_VIEW resource as custom report.

We now support new fields for the CAMPAIGN report:

campaign.keyword_match_type
campaign.fixed_cpm.goal
campaign.fixed_cpm.target_frequency_info.target_count
campaign.fixed_cpm.target_frequency_info.time_unit
campaign.target_cpv
campaign.video_brand_safety_suitability
campaign.video_campaign_settings.video_ad_inventory_control.allow_in_feed
campaign.video_campaign_settings.video_ad_inventory_control.allow_in_stream
campaign.video_campaign_settings.video_ad_inventory_control.allow_shorts

We now support new fields for the AD_GROUP report:

ad_group.fixed_cpm_micros
ad_group.target_cpv_micros

We've added support for a new segments to the CAMPAIGN report:

segments.sk_ad_network_redistributed_fine_conversion_value
segments.sk_ad_network_version

We've added support for a new segment segments.ad_format_type, which lets you segment the following reports based on the video ad format type:

AD_GROUP
AD_GROUP_AD
AD_GROUP_AD_ASSET_VIEW
CAMPAIGN
CUSTOMER

We've added support for a new metric, metrics.search_impression_share, to the GENDER_VIEW report.

We've added support for a new metric, metrics.phone_calls, to the KEYWORD_VIEW report.

We've added support for a demand_gen_carousel_ad and demand_gen_multi_asset_ad fields to the AD_GROUP_AD report.

We've added the following new fields to the SHARED_CRITERION_HISTORY metadata table:

brand_display_name
brand_primary_url
brand_rejection_reason
brand_status

HubSpot

We have added support for property history tables for custom objects. These new tables are named <custom_object>_property_history and are located within the corresponding custom object tables.

Effective August 12, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

7 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ENGAGEMENT_LEAD`
table	New Table	`ENGAGEMENT_LEAD`
`LEAD`
table	New Table	`LEAD`
`LEAD_COMPANY`
table	New Table	`LEAD_COMPANY`
`LEAD_CONTACT`
table	New Table	`LEAD_CONTACT`
`LEAD_PIPELINE`
table	New Table	`LEAD_PIPELINE`
`LEAD_PIPELINE_STAGE`
table	New Table	`LEAD_PIPELINE_STAGE`
`LEAD_PROPERTY_HISTORY`
table	New Table	`LEAD_PROPERTY_HISTORY`

iLevel

Effective August 12, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

155 total changes • 149 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CASH_TRANSACTION`
column	Rename Column	`attributes_as_of_date`	`as_of_date`
column	Rename Column	`attributes_base_amount`	`base_amount`
column	Rename Column	`attributes_base_currency`	`base_currency`
column	Rename Column	`attributes_client`	`client`
column	Rename Column	`attributes_cost_per_share`	`cost_per_share`
column	Rename Column	`attributes_custom_1`	`custom_1`
column	Rename Column	`attributes_custom_2`	`custom_2`
column	Rename Column	`attributes_custom_3`	`custom_3`
column	Rename Column	`attributes_custom_4`	`custom_4`
column	Rename Column	`attributes_custom_5`	`custom_5`
column	Rename Column	`attributes_custom_6`	`custom_6`
column	Rename Column	`attributes_description`	`description`
column	Rename Column	`attributes_group_id`	`group_id`
column	Rename Column	`attributes_investment`	`investment`
column	Rename Column	`attributes_last_modified_by`	`last_modified_by`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_local_amount`	`local_amount`
column	Rename Column	`attributes_local_currency`	`local_currency`
column	Rename Column	`attributes_original_id`	`original_id`
column	Rename Column	`attributes_owner`	`owner`
column	Rename Column	`attributes_scenario`	`scenario`
column	Rename Column	`attributes_security`	`security`
column	Rename Column	`attributes_share`	`share`
column	Rename Column	`attributes_transaction_category`	`transaction_category`
column	Rename Column	`attributes_transaction_date`	`transaction_date`
column	Rename Column	`attributes_transaction_type`	`transaction_type`
column	Rename Column	`attributes_value_per_share`	`value_per_share`
`CURRENCY`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_symbol`	`symbol`
`DATA_ITEM`
column	Rename Column	`attributes_aggregation_null_replacement`	`aggregation_null_replacement`
column	Rename Column	`attributes_aggregation_type`	`aggregation_type`
column	Rename Column	`attributes_applied_to_all_asset`	`applied_to_all_asset`
column	Rename Column	`attributes_calculation_type`	`calculation_type`
column	Rename Column	`attributes_category`	`category`
column	Rename Column	`attributes_description`	`description`
column	Rename Column	`attributes_excel_ticker`	`excel_ticker`
column	Rename Column	`attributes_exchange_rate`	`exchange_rate`
column	Rename Column	`attributes_format_type`	`format_type`
column	Rename Column	`attributes_is_carrybackward`	`is_carrybackward`
column	Rename Column	`attributes_is_carryover`	`is_carryover`
column	Rename Column	`attributes_is_monetary`	`is_monetary`
column	Rename Column	`attributes_is_number_comma_separated`	`is_number_comma_separated`
column	Rename Column	`attributes_is_putable`	`is_putable`
column	Rename Column	`attributes_is_scalable`	`is_scalable`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_number_of_decimal_place`	`number_of_decimal_place`
column	Rename Column	`attributes_option`	`option`
column	Rename Column	`attributes_rc_resolves_to`	`rc_resolves_to`
column	Rename Column	`attributes_value_type`	`value_type`
`DATA_ITEM_CATEGORY`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_sequence_number`	`sequence_number`
`DATA_ITEM_CATEGORY_RELATIONSHIP`
table	New Table		`DATA_ITEM_CATEGORY_RELATIONSHIP`
`DATA_ITEM_RELATIONSHIP`
table	New Table		`DATA_ITEM_RELATIONSHIP`
`DEAL`
column	Rename Column	`attributes_acquisition_date`	`acquisition_date`
column	Rename Column	`attributes_currency`	`currency`
column	Rename Column	`attributes_deal_type`	`deal_type`
column	Rename Column	`attributes_exit_date`	`exit_date`
column	Rename Column	`attributes_investment_amount`	`investment_amount`
column	Rename Column	`attributes_investment_name`	`investment_name`
column	Rename Column	`attributes_owner_name`	`owner_name`
column	Rename Column	`attributes_ownership`	`ownership`
column	Rename Column	`attributes_security_name`	`security_name`
column	Rename Column	`attributes_status`	`status`
`DOCUMENT_FOLDER`
column	Rename Column	`attributes_created_date`	`created_date`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`parent_folderid`	`parent_folder_id`
column	Rename Column	`parent_foldertype`	`parent_folder_type`
`DOCUMENT_RELATIONSHIP`
table	New Table		`DOCUMENT_RELATIONSHIP`
`ENTITY_ASSET`
column	Rename Column	`attributes_acquisition_as_of`	`acquisition_as_of`
column	Rename Column	`attributes_acquisition_date`	`acquisition_date`
column	Rename Column	`attributes_asset_type`	`asset_type`
column	Rename Column	`attributes_calendar_type`	`calendar_type`
column	Rename Column	`attributes_excel_ticker`	`excel_ticker`
column	Rename Column	`attributes_exit_as_of`	`exit_as_of`
column	Rename Column	`attributes_exit_date`	`exit_date`
column	Rename Column	`attributes_geography`	`geography`
column	Rename Column	`attributes_industry`	`industry`
column	Rename Column	`attributes_initial_period`	`initial_period`
column	Rename Column	`attributes_is_public`	`is_public`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_lead_investment_professional`	`lead_investment_professional`
column	Rename Column	`attributes_long_description`	`long_description`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_reporting_currency`	`reporting_currency`
column	Rename Column	`attributes_short_description`	`short_description`
column	Rename Column	`attributes_status`	`status`
column	Rename Column	`attributes_website`	`website`
`ENTITY_FUND`
column	Rename Column	`attributes_benchmark_vintage`	`benchmark_vintage`
column	Rename Column	`attributes_calendar_type`	`calendar_type`
column	Rename Column	`attributes_commitment`	`commitment`
column	Rename Column	`attributes_default_pme_index`	`default_pme_index`
column	Rename Column	`attributes_default_pme_liquidity_premium`	`default_pme_liquidity_premium`
column	Rename Column	`attributes_description`	`description`
column	Rename Column	`attributes_final_close_date`	`final_close_date`
column	Rename Column	`attributes_fund_size`	`fund_size`
column	Rename Column	`attributes_general_partner`	`general_partner`
column	Rename Column	`attributes_include_in_workflow`	`include_in_workflow`
column	Rename Column	`attributes_initial_close_date`	`initial_close_date`
column	Rename Column	`attributes_initial_poeriod`	`initial_poeriod`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_long_name`	`long_name`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_owner_type`	`owner_type`
column	Rename Column	`attributes_reporting_currency`	`reporting_currency`
column	Rename Column	`attributes_status`	`status`
column	Rename Column	`attributes_strategy`	`strategy`
column	Rename Column	`attributes_sub_strategy`	`sub_strategy`
column	Rename Column	`attributes_total_committed_capital`	`total_committed_capital`
column	Rename Column	`attributes_vintage`	`vintage`
`ENTITY_GROUP`
column	Rename Column	`attributes_applicable_to`	`applicable_to`
column	Rename Column	`attributes_entities_count`	`entities_count`
column	Rename Column	`attributes_entity_category_type`	`entity_category_type`
column	Rename Column	`attributes_entity_ids`	`entity_ids`
column	Rename Column	`attributes_name`	`name`
column	Primary Key Change	`relationships_entity_group_category_data_id` 🔑	`entity_group_category_data_id`	No longer primary key.
column	Rename Column	`relationships_entity_group_category_data_id` 🔑	`entity_group_category_data_id`
column	Rename Column	`relationships_entity_group_category_data_type`	`entity_group_category_data_type`
`OVERALL_RELATIONSHIP`
table	Deprecated Table	`OVERALL_RELATIONSHIP`		Data now available in the `SEGMENT_RELATIONSHIP`, `PERIODIC_DATA_RELATIONSHIP`, `TRANSACTION_TYPE_RELATIONSHIP`, `DOCUMENT_RELATIONSHIP`, `DATA_ITEM_RELATIONSHIP`, and `DATA_ITEM_CATEGORY_RELATIONSHIP` tables.
`PERIODIC_DATA_RELATIONSHIP`
table	New Table		`PERIODIC_DATA_RELATIONSHIP`
`SCENARIO`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_short_name`	`short_name`
`SECURITY`
column	Rename Column	`authorized_option`	`fundamental_authorized_option`
column	Rename Column	`closed_date`	`fundamental_closed_date`
column	Rename Column	`commencement_date`	`fundamental_commencement_date`
column	Rename Column	`conversion_ratio_denominator`	`fundamental_conversion_ratio_denominator`
column	Rename Column	`conversion_ratio_numerator`	`fundamental_conversion_ratio_numerator`
column	Rename Column	`converts_to`	`fundamental_converts_to`
column	Rename Column	`currency`	`fundamental_currency`
column	Rename Column	`exercise_price`	`fundamental_exercise_price`
column	Rename Column	`maturity_date`	`fundamental_maturity_date`
column	Rename Column	`options_available_for_grant`	`fundamental_options_available_for_grant`
column	Rename Column	`options_issued`	`fundamental_options_issued`
column	Rename Column	`outstanding_principal`	`fundamental_outstanding_principal`
column	Rename Column	`outstanding_share`	`fundamental_outstanding_share`
column	Rename Column	`outstanding_unit`	`fundamental_outstanding_unit`
column	Rename Column	`outstanding_warrant`	`fundamental_outstanding_warrant`
column	Rename Column	`price_per_share`	`fundamental_price_per_share`
`SEGMENT`
column	Rename Column	`attributes_is_active`	`is_active`
column	Rename Column	`attributes_is_allow_rollup`	`is_allow_rollup`
column	Rename Column	`attributes_is_global`	`is_global`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_null_replacement`	`null_replacement`
`SEGMENT_RELATIONSHIP`
table	New Table		`SEGMENT_RELATIONSHIP`
`TRANSACTION_TYPE_RELATIONSHIP`
table	New Table		`TRANSACTION_TYPE_RELATIONSHIP`
`VALUATION_DATAITEM`
column	Rename Column	`attributes_category`	`category`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_value_type`	`value_type`
`VALUATION_ITERATION`
column	Rename Column	`attributes_last_modified_date`	`last_modified_date`
column	Rename Column	`attributes_name`	`name`
column	Rename Column	`attributes_status`	`status`
column	Rename Column	`attributes_valuation_period`	`valuation_period`
`VALUATION_STATIC_DETAL`
column	Rename Column	`attributes_name`	`name`

Impact

We have removed the CLICK table.

Effective August 5, 2024 we use a new July 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes for more efficient data management and retrieval.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

5 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ACTION`
table	Deprecated Table	`ACTION`		Data now available in the `ACTION_EVENT` and `ACTION_LOCKING` tables.
`ACTION_EVENT`
table	New Table		`ACTION_EVENT`
`ACTION_INQUERY_COMMENT`
column	Rename Column	`user` 🔑	`user_name` 🔑
`ACTION_LOCKING`
table	New Table		`ACTION_LOCKING`
`ADS`
column	Rename Column	`language`	`languages`

Jotform

Effective August 14, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to a null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`FORM_PROPERTY_CONDITION`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Rename Column	`index`	`execution_index`	Renaming the column because we've added a new `index` column generated by Fivetran.
column	Primary Key Change	`index`	`index` 🔑	Added to primary key.

Lattice

Effective August 28, 2024 we use a new Aug 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made the following schema changes.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPETENCY`
table	Deprecated Table	`COMPETENCY`		Data from the `COMPETENCY` table is available in the `FEEDBACK_COMPETENCY` and `REVIEW_COMPETENCY` tables.
`FEEDBACK_COMPETENCY`
table	New Table		`FEEDBACK_COMPETENCY`
`REVIEW_COMPETENCY`
table	New Table		`REVIEW_COMPETENCY`

Linear

Effective August 26, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is necessary due to a missing column in the PROJECT table.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PROJECT`
column	New Column			`start_date`

Loop

Effective August 6, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

11 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`RETURN_CANCELLED`
table	New Table		`RETURN_CANCELLED`
`RETURN_CANCELLED_EXCHANGE`
table	New Table		`RETURN_CANCELLED_EXCHANGE`
`RETURN_CANCELLED_LINE_ITEM`
table	New Table		`RETURN_CANCELLED_LINE_ITEM`
`RETURN_LIST`
table	Deprecated Table	`RETURN_LIST`		Previously, it was a combined table, but now we have separated the combined tables.
`RETURN_LIST_EXCHANGE`
table	Deprecated Table	`RETURN_LIST_EXCHANGE`		Previously, it was a combined table, but now we have separated the combined tables.
`RETURN_LIST_LINE_ITEM`
table	Deprecated Table	`RETURN_LIST_LINE_ITEM`		Previously, it was a combined table, but now we have separated the combined tables.
`RETURN_OPEN_CLOSED_EXPIRED_EXCHANGE`
table	New Table		`RETURN_OPEN_CLOSED_EXPIRED_EXCHANGE`
`RETURN_OPEN_CLOSED_EXPIRED_LINE_ITEM`
table	New Table		`RETURN_OPEN_CLOSED_EXPIRED_LINE_ITEM`
`RETURN_REVIEW`
table	New Table		`RETURN_REVIEW`
`RETURN_REVIEW_EXCHANGE`
table	New Table		`RETURN_REVIEW_EXCHANGE`
`RETURN_REVIEW_LINE_ITEM`
table	New Table		`RETURN_REVIEW_LINE_ITEM`

Mailgun

Effective August 12, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to the incorrect usage of combined tables.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

32 total changes • 5 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ACCEPTED_EVENT`
table	New Table		`ACCEPTED_EVENT`
`ACCEPTED_EVENT_MESSAGE_ATTACHMENT`
table	New Table		`ACCEPTED_EVENT_MESSAGE_ATTACHMENT`
`ACCEPTED_EVENT_MESSAGE_RECIPIENT`
table	New Table		`ACCEPTED_EVENT_MESSAGE_RECIPIENT`
`ACCEPTED_EVENT_ROUTE`
table	New Table		`ACCEPTED_EVENT_ROUTE`
`ACCEPTED_EVENT_TAG`
table	New Table		`ACCEPTED_EVENT_TAG`
`CLICKED_EVENT`
table	New Table		`CLICKED_EVENT`
`CLICKED_EVENT_TAG`
table	New Table		`CLICKED_EVENT_TAG`
`COMPLAINED_EVENT`
table	New Table		`COMPLAINED_EVENT`
`COMPLAINED_EVENT_MESSAGE_ATTACHMENT`
table	New Table		`COMPLAINED_EVENT_MESSAGE_ATTACHMENT`
`COMPLAINED_EVENT_TAG`
table	New Table		`COMPLAINED_EVENT_TAG`
`DELIVERED_EVENT`
table	New Table		`DELIVERED_EVENT`
`DELIVERED_EVENT_MESSAGE_ATTACHMENT`
table	New Table		`DELIVERED_EVENT_MESSAGE_ATTACHMENT`
`DELIVERED_EVENT_TAG`
table	New Table		`DELIVERED_EVENT_TAG`
`EVENT`
table	Deprecated Table	`EVENT`		Data now available in the `STORED_EVENT`, `COMPLAINED_EVENT`, `UNSUBSRCIBED_EVENT`, `CLICKED_EVENT`, `OPENED_EVENT`, `FAILED_EVENT`, `DELIVERED_EVENT`, `REJECTED_EVENT`, and `ACCEPTED_EVENT` tables.
`EVENT_MESSAGE_ATTACHMENT`
table	Deprecated Table	`EVENT_MESSAGE_ATTACHMENT`		Data now available in the `ACCEPTED_EVENT_MESSAGE_ATTACHMENT`, `REJECTED_EVENT_MESSAGE_ATTACHMENT`, `DELIVERED_EVENT_MESSAGE_ATTACHMENT`, `FAILED_EVENT_MESSAGE_ATTACHMENT`, `STORED_EVENT_MESSAGE_ATTACHMENT`, and `COMPLAINED_EVENT_MESSAGE_ATTACHMENT` tables.
`EVENT_MESSAGE_RECIPIENT`
table	Deprecated Table	`EVENT_MESSAGE_RECIPIENT`		Data now available in the `ACCEPTED_EVENT_MESSAGE_RECIPIENT` and `STORED_EVENT_MESSAGE_RECIPIENT` tables.
`EVENT_ROUTE`
table	Deprecated Table	`EVENT_ROUTE`		Data now available in the `ACCEPTED_EVENT_ROUTE` table.
`EVENT_TAG`
table	Deprecated Table	`EVENT_TAG`		Data now available in the `UNSUBSCRIBED_EVENT_TAG`, `COMPLAINED_EVENT_TAG`, `CLICKED_EVENT_TAG`, `STORED_EVENT_TAG`, `OPENED_EVENT_TAG`, `FAILED_EVENT_TAG`, `DELIVERED_EVENT_TAG`, `REJECTED_EVENT_TAG`, and `ACCEPTED_EVENT_TAG` tables.
`FAILED_EVENT`
table	New Table		`FAILED_EVENT`
`FAILED_EVENT_MESSAGE_ATTACHMENT`
table	New Table		`FAILED_EVENT_MESSAGE_ATTACHMENT`
`FAILED_EVENT_TAG`
table	New Table		`FAILED_EVENT_TAG`
`OPENED_EVENT`
table	New Table		`OPENED_EVENT`
`OPENED_EVENT_TAG`
table	New Table		`OPENED_EVENT_TAG`
`REJECTED_EVENT`
table	New Table		`REJECTED_EVENT`
`REJECTED_EVENT_MESSAGE_ATTACHMENT`
table	New Table		`REJECTED_EVENT_MESSAGE_ATTACHMENT`
`REJECTED_EVENT_TAG`
table	New Table		`REJECTED_EVENT_TAG`
`STORED_EVENT`
table	New Table		`STORED_EVENT`
`STORED_EVENT_MESSAGE_ATTACHMENT`
table	New Table		`STORED_EVENT_MESSAGE_ATTACHMENT`
`STORED_EVENT_MESSAGE_RECIPIENT`
table	New Table		`STORED_EVENT_MESSAGE_RECIPIENT`
`STORED_EVENT_TAG`
table	New Table		`STORED_EVENT_TAG`
`UNSUBSCRIBED_EVENT`
table	New Table		`UNSUBSRCIBED_EVENT`
`UNSUBSCRIBED_EVENT_TAG`
table	New Table		`UNSUBSCRIBED_EVENT_TAG`

Ortto

Effective August 7, 2024 we use a new July 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema changes are required due to renaming of a table as per the standard naming convention.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`TAGS (new table name: TAGS)`
table	Rename Table		`TAG`	`TAGS`	Updated to adhere to standard naming conventions.

Recurly

We have made the following schema changes for connectors created on or after August 13, 2024:

Removed coupon_id as a primary key from the COUPON_DISCOUNT table
Removed started_with_gift and converted_at columns from the SUBSCRIPTION_HISTORY table
Introduced the new table, SUBSCRIPTION_GIFT_CARD_MAPPING

REVIEWS.io

Effective August 29, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SURVEY_RESPONSE_ANSWER`
table	New Table		`SURVEY_RESPONSE_ANSWER`
`SURVEY_RESPONSE_DETAIL`
table	Deprecated Table	`SURVEY_RESPONSE_DETAIL`		Data now available in the `SURVEY_RESPONSE_ANSWER` table.

Rippling

Effective August 29, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to a null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPANY_ACTIVITY_SUBJECT`
column	Primary Key Change	`company_activity_id`	`company_activity_id` 🔑	Added to primary key.
column	Primary Key Change	`instance` 🔑	`instance`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.

Rocketlane

Effective August 26, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have added two columns in the PROJECT_FIELD table.

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`PROJECT_FIELD`
column	New Column	`value`
column	New Column	`value_label`
`TASK_FIELD`
column	New Column	`value`
column	New Column	`value_label`

RTB House

Effective August 1, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to a null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CLIENT`
column	Primary Key Change	`company_name`	`company_name` 🔑	Added to primary key.
column	Primary Key Change	`vat_number` 🔑	`vat_number`	No longer primary key.

Sailthru

We have added a new event_id fieild.

We have also updated the event_time field to enable the millisecond precission for event stream tables. For more information, see Event Stream Changes.

Fivetran will re-sync data from March 19, 2024, for all the event stream tables

Samsara

Effective August 14, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes to efficiently manage and retrieve data.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

7 total changes • 1 possible breaking changes

Table/column	Change type	Old name	Notes
`TAG_ADDRESS`
table	New Table
`TAG_ASSIGNMENT`
table	Deprecated Table	`TAG_ASSIGNMENT`	We now capture the tag assignment data in the `TAG_ADDRESS`, `TAG_DRIVER`, `TAG_EQUIPMENT`, `TAG_TRAILER`, `TAG_VEHICLE`, and `USER_ROLE` tables.
`TAG_DRIVER`
table	New Table
`TAG_EQUIPMENT`
table	New Table
`TAG_TRAILER`
table	New Table
`TAG_VEHICLE`
table	New Table
`USER_ROLE`
table	New Table

ServiceNow

On the Schema tab, we no longer mark tables as excluded if they are unavailable so you can choose whether you want to block them.

We have added support for the following data types for empty ServiceNow columns:

BREAKDOWN_ELEMENT
DOMAIN_PATH
HASH
HTML
TABLE_NAME
SYS_CLASS_NAME

Shopify

We have added the following new tables:

ADJUSTMENT_ORDER_TRANSACTION
BALANCE_TRANSACTION

Subscript

Effective August 7, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to a null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SPREAD`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Swoogo

Effective August 29, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to invalid fields causing the connector to fail.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

6 total changes • 6 possible breaking changes

Table/column	Change type	Old name
`CALL_FOR_SPEAKER_CONTACT`
column	Deprecated Column	`company`
column	Deprecated Column	`email`
column	Deprecated Column	`first_name`
column	Deprecated Column	`job_title`
column	Deprecated Column	`last_name`
column	Deprecated Column	`prefix`

Tempo

Effective August 2, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made the following schema changes to avoid data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

6 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name
`PLAN_PERIOD_VALUE`
column	Rename Column	`from`	`from_date`
column	Rename Column	`to`	`to_date`
`ROLE`
column	Rename Column	`default`	`is_default`
`TEAM_MEMBERSHIP`
column	Rename Column	`from`	`from_date`
column	Rename Column	`to`	`to_date`
`TIMESHEET_REVIEWER`
column	Rename Column	`account_id`	`reviewer_account_id`

Thinkific

Effective August 13, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to a null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

5 total changes • 5 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`USERS_ADMINISTERED_COURSE`
column	Rename Column	`users_id`	`user_id`
`USERS_CUSTOM_PROFILE_FIELD`
column	Primary Key Change	`id`	`custom_profile_field_definition_id` 🔑	New primary key.
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Rename Column	`users_id`	`user_id`
`USERS_ROLE`
column	Rename Column	`users_id`	`user_id`

TikTok Ads

We've added support for the custom_event_type dimension for custom reports.

We've also added new page event metrics to custom reports:

View Content Metrics:

cost_per_page_content_view_event
page_content_view_event_rate
page_content_view_events
total_page_view_content_events_value
value_per_page_content_view_event

Custom Page Event Metrics:

cost_per_custom_page_event
custom_page_event_rate
custom_page_events
custom_page_events_value
value_per_custom_page_event

For more information, see TikTok API documentation.

Transcend

Effective August 27, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required due to the deprecation of fields from the source side.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

9 total changes • 9 possible breaking changes

Table/column	Change type	Old name
`ATTRIBUTE_KEY`
column	Deprecated Column	`enabled_on_airgap_cookie`
column	Deprecated Column	`enabled_on_airgap_data_flow`
column	Deprecated Column	`enabled_on_business_entitie`
column	Deprecated Column	`enabled_on_data_silo`
column	Deprecated Column	`enabled_on_data_sub_categorie`
column	Deprecated Column	`enabled_on_process_purpose_subcategory`
column	Deprecated Column	`enabled_on_request`
column	Deprecated Column	`enabled_on_sub_datapoint`
column	Deprecated Column	`enabled_on_vendor`

UKG Pro

Effective August 8, 2024 we use a new July 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have added new tables to capture the data of the platform configuration fields.

26 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`ADDRESS_FIELD_ROW`
table	New Table
`CONTACT_FIELD_ROW`
table	New Table
`EMPLOYEE_FIELD_ROW`
table	New Table
`EMPLOYMENT_FIELD_ROW`
table	New Table
`INTERNATIONAL_EMPLOYEE_FIELD_ROW`
table	New Table
`JOB_FIELD_ROW`
table	New Table
`LOCATION_FIELD_ROW`
table	New Table
`ORG_LEVEL_1_FIELD_ROW`
table	New Table
`ORG_LEVEL_2_FIELD_ROW`
table	New Table
`ORG_LEVEL_3_FIELD_ROW`
table	New Table
`ORG_LEVEL_4_FIELD_ROW`
table	New Table
`PERSON_FIELD_ROW`
table	New Table
`PHONE_NUMBER_FIELD_ROW`
table	New Table
`PLATFORM_CONFIG_ADDRESS`
table	New Table
`PLATFORM_CONFIG_CONTACT`
table	New Table
`PLATFORM_CONFIG_EMPLOYEE`
table	New Table
`PLATFORM_CONFIG_EMPLOYMENT`
table	New Table
`PLATFORM_CONFIG_INTERNATIONAL_EMPLOYEE`
table	New Table
`PLATFORM_CONFIG_JOB`
table	New Table
`PLATFORM_CONFIG_LOCATION`
table	New Table
`PLATFORM_CONFIG_ORG_LEVEL_1`
table	New Table
`PLATFORM_CONFIG_ORG_LEVEL_2`
table	New Table
`PLATFORM_CONFIG_ORG_LEVEL_3`
table	New Table
`PLATFORM_CONFIG_ORG_LEVEL_4`
table	New Table
`PLATFORM_CONFIG_PERSON`
table	New Table
`PLATFORM_CONFIG_PHONE_NUMBER`
table	New Table

Webconnex

Effective August 7, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`FORM_INVENTORY`
column	Deprecated Column	`index` 🔑		No longer primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Wherefour

Effective August 7, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

12 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ADDRESS`
table	Deprecated Table	`ADDRESS`		Data now available in the `CUSTOMER_ADDRESS`, `CUSTOMER_BILLING_ADDRESS`, `CUSTOMER_SHIPPING_ADDRESS`, `INVOICE_BILLING_ADDRESS`, `INVOICE_SHIPPING_ADDRESS`, `ORDER_BILLING_ADDRESS`, `ORDER_SHIPPING_ADDRESS`, `ORDER_SHIP_FROM_ADDRESS`, `SHIPMENT_ADDRESS`, `VENDOR_BILLING_ADDRESS`, and `VENDOR_SHIPPING_ADDRESS` tables.
`CUSTOMER_ADDRESS`
table	New Table		`CUSTOMER_ADDRESS`
`CUSTOMER_BILLING_ADDRESS`
table	New Table		`CUSTOMER_BILLING_ADDRESS`
`CUSTOMER_SHIPPING_ADDRESS`
table	New Table		`CUSTOMER_SHIPPING_ADDRESS`
`INVOICE_BILLING_ADDRESS`
table	New Table		`INVOICE_BILLING_ADDRESS`
`INVOICE_SHIPPING_ADDRESS`
table	New Table		`INVOICE_SHIPPING_ADDRESS`
`ORDER_BILLING_ADDRESS`
table	New Table		`ORDER_BILLING_ADDRESS`
`ORDER_SHIP_FROM_ADDRESS`
table	New Table		`ORDER_SHIP_FROM_ADDRESS`
`ORDER_SHIPPING_ADDRESS`
table	New Table		`ORDER_SHIPPING_ADDRESS`
`SHIPMENT_ADDRESS`
table	New Table		`SHIPMENT_ADDRESS`
`VENDOR_BILLING_ADDRESS`
table	New Table		`VENDOR_BILLING_ADDRESS`
`VENDOR_SHIPPING_ADDRESS`
table	New Table		`VENDOR_SHIPPING_ADDRESS`

Workable

Effective August 14, 2024 we use a new Augest 2024. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made the following schema changes.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

8 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`JOB_APPLICATION_FORM`
column	New column		`supported_file_types`
`JOB_CHOICE`
table	Deprecated Table	`JOB_CHOICE`
`JOB_CUSTOM_ATTRIBUTE`
column	Primary Key Change	`job_id`	`job_id` 🔑	Added to composite primary key.
column	New column		`supported_file_types`
`JOB_CUSTOM_ATTRIBUTE_CHOICE`
table	New Table		`JOB_CUSTOM_ATTRIBUTE_CHOICE`
`JOB_QUESTION`
column	New column		`supported_file_types`
`JOB_QUESTION_CHOICE`
table	New Table		`JOB_QUESTION_CHOICE`
`SUPPORTED_FILE_TYPE`
table	Deprecated Table	`SUPPORTED_FILE_TYPE`

Zendesk Sell

We have added a new table, LEAD_CONVERSION.

Zoho Books

Effective August 12, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to a data integrity issue in the CREDIT_NOTE_INVOICE table.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`CREDIT_NOTE_INVOICE`
column	Primary Key Change			`credit_note_invoice_id` 🔑	New primary key.

Zoho Desk

Effective August 28, 2024 we use a new August 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes to efficiently manage and retrieve data.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

12 total changes • 12 possible breaking changes

Table/column	Change type	Old name	Notes
`ACCOUNT_CUSTOM_FIELD`
table	Deprecated Table	`ACCOUNT_CUSTOM_FIELD`	Data now available in the `ACCOUNT` table.
`ACCOUNT_TIME_ENTRY_CUSTOM_FIELD`
table	Deprecated Table	`ACCOUNT_TIME_ENTRY_CUSTOM_FIELD`	Data now available in the `ACCOUNT_TIME_ENTRY` table.
`AGENT_TIME_ENTRY_CUSTOM_FIELD`
table	Deprecated Table	`AGENT_TIME_ENTRY_CUSTOM_FIELD`	Data now available in the `AGENT_TIME_ENTRY` table.
`CALL_CUSTOM_FIELD`
table	Deprecated Table	`CALL_CUSTOM_FIELD`	Data now available in the `CALL` table.
`CONTACT_CUSTOM_FIELD`
table	Deprecated Table	`CONTACT_CUSTOM_FIELD`	Data now available in the `CONTACT` table.
`CONTACT_TIME_ENTRY_CUSTOM_FIELD`
table	Deprecated Table	`CONTACT_TIME_ENTRY_CUSTOM_FIELD`	Data now available in the `CONTACT_TIME_ENTRY` table.
`CONTRACT_CUSTOM_FIELD`
table	Deprecated Table	`CONTRACT_CUSTOM_FIELD`	Data now available in the `CONTRACT` table.
`PRODUCT_CUSTOM_FIELD`
table	Deprecated Table	`PRODUCT_CUSTOM_FIELD`	Data now available in the `PRODUCT` table.
`TASK_CUSTOM_FIELD`
table	Deprecated Table	`TASK_CUSTOM_FIELD`	Data now available in the `TASK` table.
`TASK_TIME_ENTRY_CUSTOM_FIELD`
table	Deprecated Table	`TASK_TIME_ENTRY_CUSTOM_FIELD`	Data now available in the `TASK_TIME_ENTRY` table.
`TICKET_CUSTOM_FIELD`
table	Deprecated Table	`TICKET_CUSTOM_FIELD`	Data now available in the `TICKET` table.
`TICKET_TIME_ENTRY_CUSTOM_FIELD`
table	Deprecated Table	`TICKET_TIME_ENTRY_CUSTOM_FIELD`	Data now available in the `TICKET_TIME_ENTRY` table.

Improvements

Adyen

Our Adyen connector now supports historical sync from all data center regions (EU, APSE, AU, US, and IN). If you want an existing connector to include historical reports from all regions configured in your Adyen account, re-sync your Adyen connector.

Airtable

We now skip formula fields containing the following error codes from the sync to prevent column data type changes in your destination:

#ERROR
invalid formula
NaN
circular reference
infinity

Amazon Selling Partner

We have fixed a bug whereby a few fields were being synced under an incorrect names in the item_offer_summary table. You need to trigger a resync to backfill the records with the correct column names.

AppsFlyer

The AppsFlyer connector now supports table-level data blocking. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables.

We have changed how we calculate the value of the primary key, _fivetran_id, of the EVENT table. We now calculate the _fivetran_id value as the hash of the following columns:

app_id
app_type
appsflyer_id
event_name
event_time
event_value
campaign_type
conversion_type

We have made this change to ensure we do not skip upserting any events. If you notice any events missing from your EVENT table, re-sync the table.

NOTE: Re-syncing the EVENT table only re-syncs the event data from Data Locker and Webhooks. Additionally, we only sync the last 30 days' worth of event data for Webhooks.

Coupa

We have identified and fixed a bug to prevent sync failures of the INVENTORY_TRANSACTION and CONTRACT_TEMPLATE tables. To sync the tables, update the core.contracts_template.read and core.inventory.transaction.read scopes in your Coupa OAuth Client. We are gradually rolling out this change to all existing connectors.

Criteo

We have upgraded our Criteo connector from version 2023.10 to 2024.07 of the Criteo API. For more information about the changes, see Criteo API's changelog.

Databricks

We now segregate staging schemas by destination to work around the limitation of the number of allowed tables in a single schema. We now use fivetran_<group_id>_staging as our staging schema name. Previously, we used _fivetran_staging as the staging schema name.

We recommend that you grant permission to create the schemas or provide the required permissions to the specific schemas. Grant the following permissions:

CREATE TABLE
MODIFY
SELECT

Flexport

We have updated the sync strategy for the INVOICE table to ensure data integrity. We now re-import the INVOICE table once a week to capture updates.

Google Ads

We now support Google Ads API v17.1.

Google Drive

We now support a new authentication method, OAuth2.0, for our Google Drive connector. Previously, we supported only service account authentication. To support this enhancement, we have added a new field, Authentication Method, to the connector setup form that allows you to choose the authentication method. This field has the following options:

Authorize with User account: Select this option to authenticate your Google Drive connectors using OAuth 2.0.
Authorize Service Account: Select this option if you want to authenticate using service account. This option is selected by default in the connector setup form.

You can opt to migrate your existing connector to Authorize with User account authentication method. For more information, see our setup instructions. We are gradually rolling out this feature to all existing connectors.

Greenhouse

For connectors created on or after July 18, 2024, we have enabled table-level selection or deselection for the Greenhouse connector.

GRIN

We have updated our sync strategy. We now re-import the following tables daily:

CUSTOM_PROPERTY_VALUE
CUSTOM_PROPERTY
PRODUCT_OPTION
PRODUCT_OPTION_VALUE
PRODUCT_VARIANT
ECOMMERCE_ACCOUNT

HubSpot

We have added support for HubSpot's Leads API to sync the leads and leads pipelines data in your HubSpot account. We are gradually rolling out this improvement to all existing connectors.

Impact

We have changed the connector type of our Impact connector from Lite to Standard. As part of this upgrade, we have added a new table, CLICK, to the schema.

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

Now the ACTION table will sync only the last 3 years of data due to source limitations.

Kantata

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

KeyPay

We have updated the sync strategy for the TIMESHEET table to ensure data integrity. We now also re-import the TIMESHEET table and its child tables once a week to capture updates and deletes.

Mailchimp

We will sunset the E-commerce store selection feature for all connectors on October 31, 2024. As a result, the E-Commerce Stores field in the setup form and the e-commerce parameter API will be removed. If you have configured your connector using our REST API, update the API configuration for your connector.

Microsoft Dynamics 365 CRM

We have added a new configuration option, Service Principal, in the connector setup form to support authentication using service principal. This feature is now in beta. For more information, see our Microsoft Dynamics 365 CRM setup guide.

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

Microsoft Dynamics 365 Finance and Operations

We can now sync empty tables and columns to your destination for your Microsoft Dynamics 365 Finance and Operations connector. For more information, see our Microsoft Dynamics 365 Finance and Operations connector documentation.

MongoDB

We now sync BSON_NULL and BSON_UNDEFINED data types. Learn more in our Type Transformations and Mapping documentation.

Okta

You can now select and deselect the following tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard:

GROUP_MEMBER
GROUP_ROLE
USER_ROLE

PayPal

For connectors created on or after July 18, 2024, we have enabled parent table-level selection and deselection for the PayPal connector.

Recurly

We have made the following changes to the Schema tab for connectors created on or after August 13, 2024:

We now display all table names in lowercase
We now display all tables, including the empty tables
We no longer support table-level selection and deselection for syncing

Sage Intacct

We have updated the connector's sync strategy. We now re-sync the past 16 days' worth of data every Saturday, compared to the previous 10 days. As a result, you may observe an increase in your Monthly Active Rows (MAR) usage.

SendGrid

You can now exclude any of the SendGrid tables from the sync.

SFTP

We now display the public key in two separate fields. To support this change, we have replaced the Public Key field with the SFTP Server Public Key and SSH Tunnel Public Key fields in the setup form.

We have renamed the following fields in the connector setup form:

Host Address to SFTP Server Host Address
Port to SFTP Server Port
Username to SFTP Server Username
Password to SFTP Server Password
Tunnel Username to SSH Tunnel Username
Tunnel Host Address to SSH Tunnel Host Address
Tunnel Port to SSH Tunnel Port

For more information, see our setup instructions.

Talkdesk

We have changed the sync strategy for the GUARDIAN_CALL_QUALITY table to ensure data integrity.

We now incrementally sync the GUARDIAN_SESSION table.

Be sure to re-sync the tables if you notice any records missing from them.

Typeform

We now support partial responses for RESPONSE table. For more information, see Partial Responses. We are gradually rolling out these change to all connectors.

We have added two new columns, response_type and staged_at, to the RESPONSE table. Be sure to re-sync your connector to backfill the data for these columns or contact our support team to re-sync it for you.

REST API Improvements

New Connector Management endpoint to list connectors within account

We have implemented a new Connector Management API endpoint for our REST API. You can now leverage the new List all connectors within account feature.

REST API support for QDM now in Private Preview.

We have implemented a new Quickstart Transformations Management resource for managing QDM transformations. You can now leverage the following new features:

System Keys in the REST API

We have implemented a new REST API resource for managing System Keys. These keys are divorced from users, and therefore easier to manage and audit, especially for customers with SAML. Read more at our System Keys reference docs. You can now leverage the following new features:

Log events

New Log Event

We have added a new log event, extract_summary. See our Logs documentation for more information.