July 2024
Hybrid Deployment
You can now use a Hybrid Deployment Agent for multiple destinations within a Fivetran account. Previously, each agent supported only one destination. To support this enhancement, the Agent name list in the destination setup form now displays the names of all the agents associated with your Fivetran account.
Lite Connectors
Lite connectors are now available for the following sources:
- Absorb LMS
- Boostr
- eBay
- Expensify
- Fone Dynamics
- Kevel
- Pingdom
- ReBound Returns
- SkillsTX
- SmartRecruiters
- Teamtailor
- Ticket Tailor
- Transcend
- Tymeshift
- Vonage Contact Center
Sunset Connectors
Google Analytics
We sunset our Google Analytics connector. Effective July 1, 2024, we will no longer support the creation of new Google Analytics connectors.
We do support a Google Analytics 4 connector.
Google Analytics (MCF)
We sunset our Google Analytics (MCF) connector. Effective July 1, 2024, we will no longer support the creation of new Google Analytics (MCF) connectors.
We do support a Google Analytics 4 connector.
Google Analytics 360
We sunset our Google Analytics 360 connector. Effective July 20, 2024, we will no longer support the creation of new Google Analytics 360 connectors.
We do support a Google Analytics 4 connector.
Transformations
Created a new page for adding a transformation
We've replaced the "Add transformation" drop-down menu with a dedicated page where you can select the type of the transformation you are adding.
Schema changes
Adyen
We have changed the data type of the merchantAccountCaptureDelay
column in the ACCOUNTCONFIG_REPORT
table from INT to STRING.
Assembled
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
EVENT_CHANGE | |||||
column | New Column | old_event_type |
BigCommerce
We have made the following schema changes for new connectors created on or after July 21, 2024:
Added two new columns,
id
andtype
, in thePAYMENT_METHOD
tableAdded two new table,
PAYMENT_METHOD_STORED_INSTRUMENT
andPAYMENT_METHOD_SUPPORTED_INSTRUMENT
Removed the
CATEGORY
table and sync the category data in theCATEGORY_TREE
tableRemoved the
BILLING_ADDRESS_CUSTOM_FIELD
table and added two new tables,CHECKOUT_BILLING_ADDRESS_CUSTOM_FIELD
andCONSIGNMENT_BILLING_ADDRESS_CUSTOM_FIELD
Renamed the
timestamp
column totimestamps
in theORDER_SHIPPING_ADDRESS_QUOTE
tableRenamed the primary key column from
tag
totags
in theSTORE_BLOG_TAG
tableChanged the primary key, from
index
to_fivetran_id
, for the following tables:CATEGORY_SETTING
CUSTOMER_SETTING_PER_CHANNEL
EMAIL_SETTING
LOCALE_SETTING
PRICE_LIST_RECORD
ROBOT_SETTING
SEARCH_SETTING
SECURITY_SETTING
SEO_SETTING
STATUS_SETTING
STORE_PROFILE_SETTING
STOREFRONT_PRODUCT_SETTING
Buzzsprout
PODCAST
and EPISODE
tables that use reserved keywords.Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
EPISODE | |||||
column | Rename Column | explicit | explicits | ||
column | Rename Column | tag | tags | ||
PODCAST | |||||
column | Rename Column | explicit | explicits | ||
column | Rename Column | language | languages |
Care Quality Commission
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
LOCATION_GAC_SERVICE_TYPE | |||||
column | Deprecated Column | _fivetran_id 🔑 | |||
column | Primary Key Change | index 🔑 | Part of new composite primary key | ||
column | Primary Key Change | location_id 🔑 | Part of new composite primary key | ||
LOCATION_HISTORIC_OVERALL_KEY_QUESTION_RATING | |||||
column | Deprecated Column | location_historic_rating_report_link_id 🔑 | |||
column | Primary Key Change | location_historic_rating_index 🔑 | Part of composite primary key | ||
LOCATION_HISTORIC_RATING | |||||
column | Primary Key Change | report_link_id 🔑 | report_link_id | No longer primary key | |
column | Primary Key Change | index 🔑 | Part of composite primary key | ||
LOCATION_HISTORIC_SERVICE_KEY_QUESTION_RATING | |||||
column | Primary Key Change | location_historic_service_rating_index 🔑 | Part of composite primary key | ||
LOCATION_HISTORIC_SERVICE_RATING | |||||
column | Deprecated Column | location_historic_rating_report_link_id 🔑 | |||
column | Primary Key Change | location_historic_rating_index 🔑 | Part of composite primary key | ||
LOCATION_REGULATED_ACTIVITY_CONTACT | |||||
column | Deprecated Column | _fivetran_id 🔑 | |||
column | Primary Key Change | index 🔑 | Part of new composite primary key | ||
column | Primary Key Change | location_id 🔑 | Part of new composite primary key | ||
column | Primary Key Change | location_regulated_activity_code 🔑 | Part of new composite primary key | ||
LOCATION_REPORT_RELATED_DOCUMENT | |||||
column | Deprecated Column | _fivetran_id 🔑 | |||
column | Primary Key Change | index 🔑 | Part of new composite primary key | ||
column | Primary Key Change | location_id 🔑 | Part of new composite primary key | ||
column | Primary Key Change | location_report_link_id 🔑 | Part of new composite primary key | ||
PROVIDER_CONTACT | |||||
column | Deprecated Column | _fivetran_id 🔑 | |||
column | Primary Key Change | index 🔑 | Part of new composite primary key | ||
column | Primary Key Change | provider_id 🔑 | Part of new composite primary key | ||
PROVIDER_HISTORIC_OVERALL_KEY_QUESTION_RATING | |||||
column | Deprecated Column | provider_historic_rating_report_link_id 🔑 | |||
column | Primary Key Change | provider_historic_rating_index 🔑 | Part of composite primary key | ||
PROVIDER_HISTORIC_RATING | |||||
column | Primary Key Change | report_link_id 🔑 | report_link_id | No longer primary key | |
column | Primary Key Change | index 🔑 | Part of composite primary key | ||
PROVIDER_HISTORIC_SERVICE_KEY_QUESTION_RATING | |||||
column | Primary Key Change | provider_historic_service_rating_index 🔑 | Part of composite primary key | ||
PROVIDER_HISTORIC_SERVICE_RATING | |||||
column | Deprecated Column | provider_historic_rating_report_link_id 🔑 | |||
column | Primary Key Change | provider_historic_rating_index 🔑 | Part of composite primary key | ||
PROVIDER_REPORT_RELATED_DOCUMENT | |||||
column | Deprecated Column | _fivetran_id 🔑 | |||
column | Primary Key Change | index 🔑 | Part of new composite primary key | ||
column | Primary Key Change | provider_id 🔑 | Part of new composite primary key | ||
column | Primary Key Change | provider_report_link_id 🔑 | Part of new composite primary key |
CircleCI
tag
columns in the PIPELINE
and WORKFLOW
tables use a reserved keyword.Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
PIPELINE | |||||
column | Rename Column | tag | tags | ||
WORKFLOW | |||||
column | Rename Column | tag | tags |
commercetools
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
MASTER_VARIANT | |||||
table | New Table | ||||
MASTER_VARIANT_ASSET | |||||
table | New Table | ||||
MASTER_VARIANT_ASSET_SOURCE | |||||
table | New Table | ||||
MASTER_VARIANT_ATTRIBUTE | |||||
table | New Table | ||||
MASTER_VARIANT_IMAGE | |||||
table | New Table | ||||
MASTER_VARIANT_PRICE | |||||
table | New Table | ||||
MASTER_VARIANT_PRICE_TIER | |||||
table | New Table |
Confluence
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
BLOG_POST_VERSION | |||||
column | New Column | page_body |
Criteo
We've made the following schema changes to support syncing creatives and ads data:
We have added a new table,
AD
, with the following fields:id
🔑creative_id
adset_id
description
end_date
name
start_date
We have added a new table,
CREATIVE
, with the following fields:id
🔑advertiser_id
author
dataset_id
description
format
name
status
adaptive_*
dynamic_*
image_*
We have added a new table,
HTML_TAG
, with the following fields:_fivetran_id
🔑creative_id
height
html_tag
width
We have added a new table,
IMAGE_SET
, with the following fields:_fivetran_id
🔑creative_id
headline_text
We have added a new table,
IMAGE
, with the following fields:_fivetran_id
🔑image_set_id
url
shape
We have added a new table,
IMAGE_URL
, with the following fields:_fivetran_id
🔑creative_id
url
We have added a new table,
LOGO
, with the following fields:_fivetran_id
🔑creative_id
url
shape
type
We have added a new table,
VIDEO
, with the following fields:_fivetran_id
🔑creative_id
url
shape
duration
We have added a new table,
CALL_TO_ACTION
, with the following fields:_fivetran_id
🔑creative_id
text
type
We have added a new table,
LAYOUT
, with the following fields:_fivetran_id
🔑creative_id
text
For more information, see the Criteo ERD.
Docebo
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
AUDIENCE | |||||
table | New Table | AUDIENCE | |||
AUDIENCE_LABLES | |||||
table | New Table | AUDIENCE_LABELS | |||
AUDIENCE_SET_RULE | |||||
table | New Table | AUDIENCE_SET_RULE | |||
AUDIENCE_USER | |||||
table | New Table | AUDIENCE_USER | |||
CHANNEL_ITEM | |||||
column | Deprecated Column | language | |||
column | New Column | languages | |||
COURSE | |||||
column | Deprecated Column | language | |||
column | New Column | languages | |||
COURSE_ENROLLMENT | |||||
column | Deprecated Column | completed | |||
column | Deprecated Column | enrolled | |||
column | Deprecated Column | in_progress | |||
column | Deprecated Column | not_started | |||
column | Primary Key Change | username | username 🔑 | Added to composite primary key | |
column | New Column | first_name | |||
column | New Column | last_name | |||
DATEWISE_INSTRUCTOR | |||||
column | Primary Key Change | course_id 🔑 | Added to composite primary key | ||
column | Primary Key Change | fivetran_id 🔑 | Added to composite primary key | ||
column | Primary Key Change | session_id 🔑 | Added to composite primary key | ||
EXTERNAL_TRAINING_ADDITIONAL_FIELD | |||||
column | Primary Key Change | external_training_id | external_training_id 🔑 | Added to composite primary key | |
GAMIFICATION_BADGE | |||||
table | New Table | GAMIFICATION_BADGE | |||
GAMIFICATION_LEADERBOARD | |||||
table | New Table | GAMIFICATION_LEADERBOARD | |||
GAMIFICATION_LEADERBOARD_POSITION | |||||
table | New Table | GAMIFICATION_LEADERBOARD_POSITION | |||
MANAGER_SUBORDINATE | |||||
table | New Table | MANAGER_SUBORDINATE | |||
MANAGER_SUBORDINATE_RELATION | |||||
table | New Table | MANAGER_SUBORDINATE_RELATION | |||
SESSION | |||||
column | Primary Key Change | course_id | course_id 🔑 | Added to composite primary key | |
column | Primary Key Change | fivetran_id 🔑 | Added to composite primary key | ||
SESSION_ADDITIONAL_FIELD | |||||
column | Deprecated Column | session_id | |||
column | Primary Key Change | course_id 🔑 | Added to composite primary key | ||
column | Primary Key Change | fivetran_id 🔑 | Added to composite primary key | ||
SESSION_ENROLLMENT | |||||
column | Deprecated Column | evaluatoravatar | |||
column | Deprecated Column | evaluatorfirstname | |||
column | Deprecated Column | evaluatorlastname | |||
column | Deprecated Column | evaluatorusername | |||
column | Primary Key Change | _fivetran_id 🔑 | New primary key | ||
column | New Column | evaluator_avatar | |||
column | New Column | evaluator_firstname | |||
column | New Column | evaluator_lastname | |||
column | New Column | evaluator_username | |||
SESSION_EVENT | |||||
column | Primary Key Change | session_id | session_id 🔑 | Added to composite primary key | |
column | Primary Key Change | course_id 🔑 | Added to composite primary key | ||
column | Primary Key Change | fivetran_id 🔑 | Added to composite primary key | ||
SESSION_INSTRUCTOR | |||||
column | Primary Key Change | course_id 🔑 | Added to composite primary key | ||
column | Primary Key Change | fivetran_id 🔑 | Added to composite primary key | ||
SKILL | |||||
table | New Table | SKILL | |||
SUBORDINATE_MANAGER_TYPE | |||||
table | New Table | SUBORDINATE_MANAGER_TYPE | |||
USER_ASSOCIATED_SKILL | |||||
table | New Table | USER_ASSOCIATED_SKILL | |||
USER_FIELD | |||||
table | New Table | USER_FIELD | |||
USERS | |||||
column | Deprecated Column | subscription_record_id | |||
column | Deprecated Column | user_id 🔑 | No longer primary key | ||
column | Deprecated Column | username | |||
column | New Column | actions | |||
column | New Column | authenticator_app_pair_date | |||
column | New Column | avatar | |||
column | New Column | confirmed | |||
column | New Column | country | |||
column | New Column | create_by_admin | |||
column | New Column | creation_date | |||
column | New Column | currently_logged_users_count | |||
column | New Column | date_format | |||
column | New Column | email_validation_status | |||
column | New Column | encoded_username | |||
column | New Column | expiration_date | |||
column | New Column | expired | |||
column | New Column | field_1111 | |||
column | New Column | fullname | |||
column | Primary Key Change | id 🔑 | New primary key | ||
column | New Column | is_manager | |||
column | New Column | lang_code | |||
column | New Column | languages | |||
column | New Column | last_access_date | |||
column | New Column | last_update | |||
column | New Column | level | |||
column | New Column | multi_domains | |||
column | New Column | name | |||
column | New Column | newsletter_optout | |||
column | New Column | newsletter_optout_date | |||
column | New Column | request_on | |||
column | New Column | send_notification | |||
column | New Column | status | |||
column | New Column | timezone | |||
column | New Column | uuid | |||
column | New Column | version |
Dropbox Sign
TO_ADDRESS
and FROM_ADDRESS
tables, which are combined entities of breakout tables from the SELF_MAILER
, LETTER
, POSTCARD
, and CHECK
tables. We are also implementing separate breakout tables for these entities.Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CHECK (new table name: CHECKS) | |||||
table | Rename Table | CHECK | CHECKS | Renamed because check is a reserved keyword. | |
CHECK_FROM_ADDRESS | |||||
table | New Table | CHECK_FROM_ADDRESS | |||
CHECK_TO_ADDRESS | |||||
table | New Table | CHECK_TO_ADDRESS | |||
FROM_ADDRESS | |||||
table | Deprecated Table | FROM_ADDRESS | Data now available in the POSTCARD_FROM_ADDRESS , CHECK_FROM_ADDRESS , LETTER_FROM_ADDRESS , and SELF_MAILER_FROM_ADDRESS tables. | ||
LETTER_FROM_ADDRESS | |||||
table | New Table | LETTER_FROM_ADDRESS | |||
LETTER_TO_ADDRESS | |||||
table | New Table | LETTER_TO_ADDRESS | |||
POSTCARD_FROM_ADDRESS | |||||
table | New Table | POSTCARD_FROM_ADDRESS | |||
POSTCARD_TO_ADDRESS | |||||
table | New Table | POSTCARD_TO_ADDRESS | |||
SELF_MAILER_FROM_ADDRESS | |||||
table | New Table | SELF_MAILER_FROM_ADDRESS | |||
SELF_MAILER_TO_ADDRESS | |||||
table | New Table | SELF_MAILER_TO_ADDRESS | |||
TO_ADDRESS | |||||
table | Deprecated Table | TO_ADDRESS | Data now available in the POSTCARD_TO_ADDRESS , CHECK_TO_ADDRESS , LETTER_TO_ADDRESS , and SELF_MAILER_TO_ADDRESS tables. |
Employment Hero
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
SUPERANNUATION_DETAIL | |||||
column | Primary Key Change | employee_id 🔑 | employee_id | No longer primary key. | |
column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
TAX_DECLARATION | |||||
column | Primary Key Change | employee_id 🔑 | employee_id | No longer primary key. | |
column | Primary Key Change | organisation_id 🔑 | organisation_id | No longer primary key. | |
column | Primary Key Change | _fivetran_id 🔑 | New primary key. |
Facebook Ads
We have added a new column, picture
, to the AD_VIDEO_HISTORY
table.
We have added a new prebuilt report, MARKETING_MIX_MODELING
. The report fetches data on the adset level and contains the spend
and impressions
metrics. See Facebook's Marketing Mix Modeling documentation for more information.
Fivetran Platform Connector
We have made the following changes to the INCREMENTAL_MAR
table:
- Deprecated the
connector_id
column, which contains the connector name; - Added a new column,
connector_name
.
The ROLE
table has the connector_types
column, which creates a many-to-many relationship between the CONNECTOR_TYPE
and ROLE
tables. We added a new bridge/join table, role_connector_type
that has the connector_type
and role_id
columns to make this relationship more intuitive.
We have added a new column, connector_id
, to the RESOURCE MEMBERSHIP
table. It contains the connector ID (like the existing integration_id
column). Existing connectors now have both columns, connector_id
and integration_id
, while new connectors created after July 10, 2024 only have the connector_id
column.
The DESTINATION
table has the type
column, which contains the deployment type (Fivetran
or HVR
). For new connectors created after July 10, 2024 this column is replaced with the deployment_type
column.
See our Fivetran Platform Connector ERD for more information.
Genesys
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CAMPAIGN_INTERACTION | |||||
table | Deprecated Table | CAMPAIGN_INTERACTION | We are deleting the table as the implementation of the combined table incorrect. | ||
CAMPAIGN_INTERACTION_INTERACTING | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
CAMPAIGN_INTERACTION_PENDING | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
CAMPAIGN_INTERACTION_PREVIEWING | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
CAMPAIGN_INTERACTION_PROCEED | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
CAMPAIGN_INTERACTION_SCHEDULED | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
QUEUE | |||||
table | Deprecated Table | QUEUE | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_BULLS_EYE_RING_EXPANSION_CRITERIA | |||||
table | Deprecated Table | QUEUE_BULLS_EYE_RING_EXPANSION_CRITERIA | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_BULLS_EYE_RING_MEMBER_GROUP | |||||
table | Deprecated Table | QUEUE_BULLS_EYE_RING_MEMBER_GROUP | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_BULLS_EYE_RING_SKILL_TO_REMOVE | |||||
table | Deprecated Table | QUEUE_BULLS_EYE_RING_SKILL_TO_REMOVE | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_CONDITIONAL_GROUP_ROUTING_RULE | |||||
table | Deprecated Table | QUEUE_CONDITIONAL_GROUP_ROUTING_RULE | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_CONDITIONAL_GROUP_ROUTING_RULE_GROUP | |||||
table | Deprecated Table | QUEUE_CONDITIONAL_GROUP_ROUTING_RULE_GROUP | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_EMAIL_ADDRESS_AUTO_BCC | |||||
table | Deprecated Table | QUEUE_EMAIL_ADDRESS_AUTO_BCC | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_EMAIL_ADDRESS_ROUTE_SKILL | |||||
table | Deprecated Table | QUEUE_EMAIL_ADDRESS_ROUTE_SKILL | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_MEMBER_GROUP | |||||
table | Deprecated Table | QUEUE_MEMBER_GROUP | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
QUEUE_ROUTING_RULE | |||||
table | Deprecated Table | QUEUE_ROUTING_RULE | We are deleting the table as the implementation of the combined table was causing data integrity issue. | ||
ROUTING_QUEUE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_BULLS_EYE_RING_EXPANSION_CRITERIA | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_BULLS_EYE_RING_MEMBER_GROUP | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_BULLS_EYE_RING_SKILL_TO_REMOVE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_CONDITIONAL_GROUP_ROUTING_RULE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_CONDITIONAL_GROUP_ROUTING_RULE_GROUP | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_EMAIL_ADDRESS_AUTO_BCC | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_EMAIL_ADDRESS_ROUTE_SKILL | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_MEMBER_GROUP | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
ROUTING_QUEUE_ROUTING_RULE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_BULLS_EYE_RING_EXPANSION_CRITERIA | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_BULLS_EYE_RING_MEMBER_GROUP | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_BULLS_EYE_RING_SKILL_TO_REMOVE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_CONDITIONAL_GROUP_ROUTING_RULE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_CONDITIONAL_GROUP_ROUTING_RULE_GROUP | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_EMAIL_ADDRESS_AUTO_BCC | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_EMAIL_ADDRESS_ROUTE_SKILL | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_MEMBER_GROUP | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. | |||
USER_QUEUE_ROUTING_RULE | |||||
table | New Table | This is the new table having the data from the combined table after we un-combined it. |
GitLab
commit_id
column being null
for some records.Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
PROJECT_BRANCH | |||||
column | Rename Column | default | defaults | ||
column | Primary Key Change | project_id 🔑 | project_id | No longer primary key. | |
column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
PROJECT_BRANCH_PARENT_ID | |||||
column | Deprecated Column | project_branch_commit_id 🔑 | No longer primary key. | ||
column | Primary Key Change | project_branch_fivetran_id 🔑 | Added to primary key. | ||
PROJECT_JOB | |||||
column | Rename Column | tag | tags | ||
PROJECT_RELEASE_ASSET_LINK | |||||
column | Deprecated Column | project_release_commit_id 🔑 | No longer primary key. | ||
column | Primary Key Change | project_release_fivetran_id 🔑 | Added to primary key. | ||
PROJECT_RELEASE_ASSET_SOURCE | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Deprecated Column | project_release_commit_id 🔑 | No longer primary key. | ||
column | New Column | project_release_fivetran_id | |||
PROJECT_RELEASE_EVIDENCE | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Deprecated Column | project_release_commit_id 🔑 | No longer primary key. | ||
column | Primary Key Change | project_release_fivetran_id 🔑 | Added to primary key. | ||
PROJECT_RELEASE_MILESTONE | |||||
column | Deprecated Column | project_release_commit_id 🔑 | No longer primary key. | ||
column | Primary Key Change | project_release_fivetran_id 🔑 | Added to primary key. | ||
PROJECT_RELEASE_PARENT_ID | |||||
column | Deprecated Column | project_release_commit_id 🔑 | No longer primary key. | ||
column | Primary Key Change | project_release_fivetran_id 🔑 | Added to primary key. | ||
PROJECT_REPO_TAG | |||||
column | Primary Key Change | project_id 🔑 | project_id | No longer primary key. | |
column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
PROJECT_REPO_TAG_PARENT_ID | |||||
column | Deprecated Column | project_repo_tag_commit_id 🔑 | No longer primary key. | ||
column | Primary Key Change | project_repo_tag_fivetran_id 🔑 | Added to primary key. |
Google Analytics 4 Export
We have added support for item parameters data. To support this feature, we have added columns of the form param_*
, to the ITEM
table. If you created the connector before July 24, 2023, we sync the data into the ITEM_PARAMS
table. Be sure to re-sync the connector to backfill the historical data or contact Fivetran Support to re-sync it for you.
Google Calendar
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CALENDAR_LIST | |||||
column | Rename Column | primary | is_primary |
Gorgias
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
TICKET_CUSTOM_FIELD | |||||
table | New Table |
Greenhouse
We have made the following schema changes for connectors created on or after July 18, 2024:
- Added the
primary_email_address
column in theUSERS
table - Removed the
is_primary
column from theUSER_EMAIL
table - Renamed the
TAG
table toTAGS
- Renamed the
end
column toends
in theSCHEDULED_INTERVIEW
table - Renamed the
from
andto
columns in theEMAIL
table tofroms
andtos
- Renamed the
default
andfrom
columns in theEMAIL_TEMPLATE
table tois_default
andfroms
GRIN
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CAMPAIGN | |||||
table | New Table | CAMPAIGN | |||
CAMPAIGN_COMPENSATION | |||||
table | New Table | CAMPAIGN_COMPENSATION |
Helpscout
We have made the following schema changes for new connectors created on or after July 31, 2024:
- Renamed the
order
column toorders
in theMAILBOX_WORKFLOW_HISTORY
table
Jotform
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
TEAM | |||||
table | New Table | ||||
TEAM_ASSET | |||||
table | New Table | ||||
TEAM_MEMBER | |||||
table | New Table |
Khoros Care
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
COMBINED_REPORT | |||||
column | Rename Column | language | languages |
Lever
We have made the following schema changes for connectors created on or after July 27, 2024:
Added the following tables:
FEEDBACK_FORM_SCORE_CARD_SUB_FIELD
FEEDBACK_FORM_TEMPLATE_FIELD
POSTING_FORM_SCORE_CARD_SUB_FIELD
POSTING_FORM_TEMPLATE_FIELD
PROFILE_FORM_SCORE_CARD_SUB_FIELD
PROFILE_FORM_TEMPLATE_FIELD
REFERRAL_FORM_SCORE_CARD_SUB_FIELD
REFERRAL_FORM_TEMPLATE_FIELD
Removed the
SCORE_CARD_SUB_FIELD
andTEMPLATE_FIELD
tablesRenamed the
USER
table toUSERS
Renamed the primary key
tag
totags
in theOPPORTUNITY_TAG
andPOSTING_TAG
tables
LinkedIn Ad Analytics
LinkedIn has deprecated the approximate_unique_impressions
field and replaced it with approximate_member_reach
in the following tables:
AD_ANALYTICS_BY_CAMPAIGN
AD_ANALYTICS_BY_CREATIVE
AD_ANALYTICS_BY_CREATIVE_WITH_CONVERSION_BREAKDOWN
MONTHLY_AD_ANALYTICS_BY_MEMBER_COMPANY
MONTHLY_AD_ANALYTICS_BY_MEMBER_COMPANY_SIZE
MONTHLY_AD_ANALYTICS_BY_MEMBER_COUNTRY
MONTHLY_AD_ANALYTICS_BY_MEMBER_INDUSTRY
MONTHLY_AD_ANALYTICS_BY_MEMBER_JOB_FUNCTION
MONTHLY_AD_ANALYTICS_BY_MEMBER_JOB_TITLE
MONTHLY_AD_ANALYTICS_BY_MEMBER_REGION
MONTHLY_AD_ANALYTICS_BY_MEMBER_SENIORITY
LinkedIn Company Pages
LinkedIn has deprecated the following tables:
PAGE_STATISTIC_BY_REGION
- replaced byPAGE_STATISTIC_BY_GEO
PAGE_STATISTIC_BY_COUNTRY
- replaced byPAGE_STATISTIC_BY_GEO_COUNTRY
REGION
COUNTRY
Mention
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
ALERT_LANGUAGE | |||||
column | Rename Column | language 🔑 | languages 🔑 | ||
ALERT_PREFERENCE | |||||
column | Primary Key Change | _fivetran_id 🔑 | New primary key. |
Mixmax
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
MEETING_TYPE_DAY | |||||
column | Deprecated Column | day | |||
column | Deprecated Column | enabled | |||
column | Deprecated Column | end_time | |||
column | Deprecated Column | index 🔑 | We now use the _fivetran_id column as the primary key. | ||
column | Deprecated Column | start_time |
Monday.com
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
ACTIVITY_LOG | |||||
column | Primary Key Change | board_id | board_id 🔑 | Added to primary key. | |
BOARD | |||||
column | Rename Column | permissions | permission | ||
COLUMN_VALUE | |||||
column | Deprecated Column | additional_info | No longer supported by the source app API. | ||
column | New Column | archived | |||
column | Primary Key Change | board_id 🔑 | Added to primary key. | ||
column | New Column | checked | |||
column | New Column | date | |||
column | New Column | description | |||
column | New Column | direction | |||
column | New Column | display_value | |||
column | New Column | duration | |||
column | New Column | from_date | |||
column | New Column | hour | |||
column | New Column | icon | |||
column | New Column | index | |||
column | New Column | is_done | |||
column | New Column | label | |||
column | New Column | label_style_border | |||
column | New Column | label_style_color | |||
column | New Column | minute | |||
column | New Column | number | |||
column | New Column | rating | |||
column | New Column | running | |||
column | New Column | settings_str | |||
column | New Column | started_at | |||
column | New Column | symbol | |||
column | New Column | time | |||
column | New Column | to_date | |||
column | New Column | update_id | |||
column | New Column | updated_at | |||
column | New Column | visualization_type | |||
column | New Column | width | |||
COLUMN_VALUE_ITEM_ID | |||||
table | New Table | COLUMN_VALUE_ITEM_ID | |||
COLUMN_VALUE_MIRROR_ITEM | |||||
table | New Table | COLUMN_VALUE_MIRROR_ITEM | |||
COLUMN_VALUE_TAG | |||||
table | New Table | COLUMN_VALUE_TAG | |||
ITEM_SUBSCRIBER | |||||
column | Primary Key Change | board_id 🔑 | Added to primary key. | ||
PERSON_TEAM | |||||
table | New Table | PERSON_TEAM | |||
REPLY | |||||
column | New Column | created_at | |||
TIME_TRACKING_HISTORY | |||||
column | Primary Key Change | board_id 🔑 | Added to primary key. |
Mux
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
ASSET_PLAYBACK | |||||
table | New Table | ASSET_PLAYBACK | |||
LIVE_STREAM_PLAYBACK | |||||
table | New Table | LIVE_STREAM_PLAYBACK | |||
PLAYBACK | |||||
table | Deprecated Table | PLAYBACK | |||
SPACE | |||||
table | Deprecated Table | SPACE | |||
SPACE_BOARDCAST | |||||
table | Deprecated Table | SPACE_BOARDCAST |
NetSuite SuiteAnalytics
We have added the _fivetran_index
column as a primary key column to the amortizationScheduleRecurrence
table.
Orbit
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
MEMBER_ACTIVITY | |||||
column | New Column | attribute_type | |||
MEMBER_ACTIVITY_IN_AN_ORGANIZATION | |||||
column | New Column | attribute_type | |||
WORKSPACE_ACTIVITY | |||||
column | New Column | attribute_type |
Outreach
To improve sync performance, we have deprecated the bodyText
field in the MAILING
table because the bodyHtml
field holds the same content. We are gradually rolling out this change to existing connectors.
Pardot
We have added a new table, EXTERNAL_ACTIVITY
. For more information, see Pardot's API documentation for the external-activites
endpoint.
We will gradually roll out this change to all connectors. The table can be selected by selecting the toggle in the setup form. Refer to Pardot's setup guide for more information.
Pinterest Organic
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
PIN_ANALYTIC_DAILY_METRIC | |||||
column | Primary Key Change | date | date 🔑 | Added to composite primary key | |
column | Deprecated Column | index 🔑 | No longer primary key | ||
USER_ACCOUNT_ANALYTIC_DAILY_METRIC | |||||
column | Deprecated Column | _fivetran_id 🔑 | No longer primary key | ||
column | Primary Key Change | date | date 🔑 | Added to composite primary key | |
column | Primary Key Change | end_date | end_date 🔑 | Added to composite primary key | |
column | Primary Key Change | start_date | start_date 🔑 | Added to composite primary key | |
column | Primary Key Change | user_account_id | user_account_id 🔑 | Added to composite primary key | |
USER_ACCOUNT_ANALYTICS | |||||
column | Primary Key Change | user_account_id | user_account_id 🔑 | Added to composite primary key |
Ramp
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
TRANSACTION_ACCOUNTING_CATEGORY | |||||
column | Primary Key Change | transaction_id | transaction_id 🔑 | Added to primary key. | |
column | Primary Key Change | index 🔑 | New primary key. | ||
TRANSACTION_DISPUTE | |||||
column | Primary Key Change | transaction_id | transaction_id 🔑 | Added to primary key. | |
TRANSACTION_POLICY_VIOLATION | |||||
column | Primary Key Change | transaction_id | transaction_id 🔑 | Added to primary key. |
Rootly
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
INCIDENT | |||||
column | New Column | in_triage_at |
Salesforce Marketing Cloud
We have added a new table, SMS_MESSAGE_TRACKING
to sync data from the SMSMessageTracking data view.
We have added the following new tables to support MobilePush:
MOBILE_PUSH_DETAIL_EXTRACT
PUSH_MESSAGE
PUSH_APPLICATION
We have added the following new tables to support Chat Messaging Data Extract:
CHAT_TRACKING
CHAT_INBOUND_MESSAGE_LOG
CHAT_POTENTIAL_UNSUBS
OTT_REGISTRATION
Security Journey
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
ENROLLMENT | |||||
column | Rename Column | all | alls |
ShipStation
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
SHIPPING_PROVIDER | |||||
column | Rename Column | primary | is_primary |
Shopify
We have added two new columns, company_id
and company_location_id
, to the ORDER
table. Be sure to re-sync the ORDER
table to backfill the data for these columns or contact our support team to re-sync it for you.
Square
We have added the following new tables:
BANK_ACCOUNT
CUSTOM_ATTRIBUTE_DEFINITION
GIFT_CARD
GIFT_CARD_ACTIVITY
GIFT_CARD_CUSTOMER
MERCHANT
MERCHANT_CUSTOM_ATTRIBUTE
Stripe
We have added the following new tables to support upcoming invoices:
UPCOMING_INVOICE
UPCOMING_INVOICE_ACCOUNT_TAX_ID
UPCOMING_INVOICE_CUSTOM_FIELD
UPCOMING_INVOICE_LINE_ITEM
UPCOMING_INVOICE_LINE_ITEM_PRORATION_DETAILS_CREDITED_ITEM
UPCOMING_INVOICE_LINE_ITEM_TAX_RATE
UPCOMING_INVOICE_TAX_RATE
We have added the following new tables to support Quote:
QUOTE
QUOTE_LINE_ITEM
QUOTE_COMPUTED_UPFRONT_LINE_ITEM
QUOTE_TAX_RATE
We have added a new table, TAX_AMOUNT
, to store data for all Stripe tax amount and categories.
We have added a new table, CREDIT_NOTE_LINE_ITEM_TAX_RATE
, to store the tax rate ID applied to the credit note line item.
We have added a new table, INVOICE_ACCOUNT_TAX_ID
, to store the account tax ID related to the invoice.
We have added a new table, INVOICE_LINE_ITEM_PRORATION_DETAILS_CREDITED_ITEMS
, to store details for the proration credited items.
We have added the following new columns to the CREDIT_NOTE
table:
amount_shipping
effective_at
out_of_band_amount
shipping_cost_amount_subtotal
shipping_cost_amount_tax
shipping_cost_amount_total
shipping_cost_shipping_rate
subtotal_excluding_tax
total_excluding_tax
We have added two new columns, amount_excluding_tax
and unit_amount_excluding_tax
, to the CREDIT_NOTE_LINE_ITEM
table.
We have added the following new columns to the INVOICE
table:
account_country
account_name
amount_shipping
application
automatic_tax_enabled
automatic_tax_status
effective_at
from_invoice_action
from_invoice_invoice
last_finalisation_error_*
latest_revision
on_behalf_of
paid_out_of_band
payment_setting_default_mandate
payment_setting_payment_method_options.*
payment_setting_payment_method_types
rendering_amount_tax_display
rendering_pdf_page_size
shipping_cost_amount_subtotal
shipping_cost_amount_tax
shipping_cost_amount_total
shipping_cost_shipping_rate
shipping_details_address_*
shipping_details_name
shipping_details_phone
subtotal_excluding_tax
test_clock
total_excluding_tax
We have added two new columns, amount_excluding_tax
and unit_amount_excluding_tax
to the INVOICE_LINE_ITEM
table.
We have added two new columns, test_clock
and unit_amount_decimal
, to the INVOICE_ITEM
table.
We have removed the following columns from the INVOICE
table:
billing
date
finalized_at
We now sync the data of these discontinued columns to other columns in the INVOICE
table. Use the following columns:
collection_method
forbilling
created
fordate
status_transitions_finalized_at
forfinalized_at
Teads
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
REPORT_BUDGET | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | broweser | browser | ||
column | Rename Column | line_iten_name | line_item_name | ||
REPORT_DISPLAY_PROGRESS | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | line_iten_name | line_item_name | ||
REPORT_LUMEN | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | line_iten_name | line_item_name | ||
REPORT_MOAT | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | line_iten_name | line_item_name | ||
REPORT_SCOPE | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | line_iten_name | line_item_name | ||
REPORT_VIDEO | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | line_iten_name | line_item_name | ||
REPORT_VIDEO_PROGRESS | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | We've changed the way we calculate the primary key. | |
column | Rename Column | line_iten_name | line_item_name |
Teamwork
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CALENDAR_EVENT | |||||
column | Rename Column | end | end_at | ||
column | Rename Column | where | at_where | ||
TASK | |||||
column | Rename Column | order | orders |
TikTok Ads
We have added a new field, asset_ownership_status
, to the PIXEL
table.
We have added a new field, custom_event_type
, to the PIXEL_EVENT
table.
We have added new metrics to our basic prebuilt reports.
Reports:
AD_REPORT_DAILY
AD_REPORT_HOURLY
AD_REPORT_LIFETIME
ADGROUP_REPORT_DAILY
ADGROUP_REPORT_HOURLY
ADGROUP_REPORT_LIFETIME
CAMPAIGN_REPORT_DAILY
CAMPAIGN_REPORT_HOURLY
CAMPAIGN_REPORT_LIFETIME
Metrics:
Shop Event Metrics:
cost_per_onsite_initiate_checkout_count
cost_per_onsite_on_web_cart
cost_per_onsite_on_web_detail
cost_per_onsite_shopping
onsite_initiate_checkout_count_rate
onsite_initiate_checkout_count
onsite_on_web_cart_rate
onsite_on_web_cart
onsite_on_web_detail_rate
onsite_on_web_detail
onsite_shopping_rate
onsite_shopping_roas
onsite_shopping
total_onsite_initiate_checkout_count_value
total_onsite_on_web_cart_value
total_onsite_on_web_detail_value
total_onsite_shopping_value
value_per_onsite_initiate_checkout_count
value_per_onsite_on_web_cart
value_per_onsite_on_web_detail
value_per_onsite_shopping
Page Event Metrics:
cost_per_on_web_subscribe
on_web_subscribe_per_click
on_web_subscribe
total_on_web_subscribe_value
value_per_on_web_subscribe
Toggl Track
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
USERS | |||||
column | Primary Key Change | id 🔑 | id | No longer primary key. | |
column | Primary Key Change | user_id | user_id 🔑 | Added to primary key. | |
USERS_GROUP | |||||
column | Deprecated Column | users_id 🔑 | No longer primary key. | ||
column | Primary Key Change | user_id 🔑 | New primary key. |
Trello
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
BOARD | |||||
column | Rename Column | desc | description | ||
CARD | |||||
column | Rename Column | desc | description |
UserVoice
We have renamed the USER
table to USERS
in the schema for UserVoice connectors created on or after July 11, 2024:
Workday HCM
We have added the following new tables:
JOB_REQUISITION_INCOMING
JOB_REQUISITION_ADDITIONAL_LOCATION
JOB_REQUISITION_ADDITIONAL_JOB_PROFILE
JOB_REQUISITION_ADDITIONAL_JOB_POSTING_LOCATION
JOB_REQUISITION_ALLOWANCE_PLAN
JOB_REQUISITION_BONUS_PLAN
JOB_REQUISITION_CALCULATED_PLAN
JOB_REQUISITION_CERTIFICATION
JOB_REQUISITION_CERTIFICATION_SPECIALTY
JOB_REQUISITION_CERTIFICATION_SUBSPECIALTY
JOB_REQUISITION_COMMISSION_PLAN
JOB_REQUISITION_COMPENSATION
JOB_REQUISITION_COMPETENCY
JOB_REQUISITION_CUSTOM_ORGANIZATION
JOB_REQUISITION_DEFAULT_ASSESSMENT_TEST
JOB_REQUISITION_DOCUMENT_FIELD
JOB_REQUISITION_EDUCATION
JOB_REQUISITION_LANGUAGE
JOB_REQUISITION_LANGUAGE_ABILITY
JOB_REQUISITION_MERIT_PLAN
JOB_REQUISITION_ORGANIZATION
JOB_REQUISITION_PAY_PLAN
JOB_REQUISITION_PERIOD_SALARY_PLAN
JOB_REQUISITION_POSITION
JOB_REQUISITION_RESPONSIBILITY
JOB_REQUISITION_ROLE_ASSIGNMENT
JOB_REQUISITION_ROLE_ASSIGNEE
JOB_REQUISITION_SKILL
JOB_REQUISITION_STOCK_PLAN
JOB_REQUISITION_TRAINING
JOB_REQUISITION_WORK_EXPERIENCE
JOB_REQUISITION_UNIT_ALLOWANCE_PLAN
JOB_REQUISITION_UNIT_SALARY_PLAN
LINKED_JOB_REQUISITION
To sync these tables, you must enable the security domains necessary for the Recruiting module. We are gradually rolling out these changes to all the existing connectors.
Zendesk Chat
We have made the following schema changes for connectors created on or after July 23, 2024:
- Renamed the
timestamp
column totimestamps
in theCHAT_HISTORY
table - Renamed the
timestamp
column totimestamps
in theCHAT
table - Renamed the
timestamp
column totimestamps
in theENGAGEMENT
table - Renamed the
tag
primary key column totags
in theCHAT_TAG
table
Zendesk Support
We have added the following new tables:
AGENT_CHANNEL_HISTORY
AGENT_MAX_CAPACITY_HISTORY
AGENT_STATUS_HISTORY
AGENT_UNIFIED_STATUS_HISTORY
AGENT_STATUS_TYPE
AGENT_STATUS_TYPE_GROUP
We are gradually rolling out this change to all existing connectors.
Improvements
ActiveCampaign
We have changed the sync strategy for the CONTACT
table. We now re-import this table and its child tables once a week to capture updates and deletes.
Amazon DynamoDB
We have limited the number of requests we issue for the permissions granted to Fivetran's IAM role. During a sync, if your connector's Schema Change Handling option is set to Allow columns
or Block all
, we no longer check the Fivetran role's access to tables you have excluded by revoking their permissions. If you have already granted access to these tables, trigger a schema reload to include them in your sync. Learn more in our DynamoDB excluding source data documentation.
Azure Cosmos DB for MongoDB
Our Azure Cosmos DB for MongoDB connector is now generally available. Read our Azure Cosmos DB connector documentation.
BigCommerce
We have made the following changes to the Schema tab for connectors created on or after July 19, 2024:
- We display all table names in lowercase
- We display all the tables, including the empty tables
- We no longer support table-level selection or deselection for syncing
BigQuery
Our BigQuery connector is now generally available.
Read our BigQuery connector documentation.
Bitly
We have changed the sync strategy for the BITLINK
table. We now re-import this table and its child tables to capture updates and deletes.
Box
We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.
Braintree
We have upgraded our Braintree connector from version 3.19.0 to 3.29.0 of the Braintree API. For more information about the changes and deprecations, see Braintree API's changelog.
Braze
We now support user profile exports configured with Google Cloud Storage. For more information, see our Braze documentation.
Brightcove
We have changed the sync strategy for the following tables. During historical syncs and initial syncs, we now sync historical data only up to 2004-01-01T00:00:00Z
.
ANALYTICS_REPORT
,LIVE_ANALYTICS_TIME_SERIES_CCU_DATA_POINT
LIVE_ANALYTICS_TIME_SERIES_FINGERPRINT_COUNT_DATA_POINT
LIVE_ANALYTICS_TIME_SERIES_SECOND_VIEWED_DATA_POINT
LIVE_ANALYTICS_TIME_SERIES_VIDEO_IMPRESSION_DATA_POINT
LIVE_ANALYTICS_TIME_SERIES_VIDEO_VIEW_DATA_POINT
Checkout.com
We now support priority-first sync for the following tables and their child tables:
BALANCE_REPORT
CUSTOMER
DISPUTE
FINANCIAL_ACTION_REPORT
INSTRUMENT
PAYMENT
PAYMENT_ACTION
PAYOUT_REPORT
REPORT
Clari
We have changed the sync strategy for our Clari connector. We now incrementally sync the following tables and their child tables:
FIELD
FORECAST_ENTRY
TIME_FRAME
TIME_PERIOD
USERS
During every incremental sync, we also sync the historical and future forecasting data for these tables. The incremental syncs for these tables contribute towards your MAR.
ClickHouse Cloud
You can now configure your ClickHouse Cloud destination using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
ClickUp
We have changed our sync strategy for the TASK
and TIME_ENTRY
tables and their child tables. Instead of weekly, we now perform a monthly re-import for these tables.
CockroachDB
We now sync TIME and TIMETZ columns to your destination as STRING values. Learn more in our CockroachDB type transformation and mapping documentation.
commercetools
We now support priority-first sync for the following tables and their child tables:
CART
CUSTOMER
INVENTORY
ORDERS
PAYMENT
PRODUCT
Convex
You can now configure your Convex connector using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
Criteo
Our Criteo connector can now sync creatives and ads data. For more information, see Criteo's creatives documentation.
Cvent
We now incrementally sync the ENROLLMENT
table and its child tables.
We no longer capture deletes for the following tables and their child tables:
ATTENDEE_INSIGHT
ATTENDEE
CARD_TRANSACTION
EMAIL
EVENT_QUESTION
EVENT
MEETING_REQUEST
SPEAKER
SURVEY
Dropbox
We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.
Eventbrite
We have changed the authentication method for our Eventbrite connector. We now use private token instead of OAuth to authenticate the Eventbrite connector. Be sure to re-authenticate your Eventbrite connector using private token. For more information, see our Eventbrite documentation.
Facebook Ads
We have upgraded our Facebook Ads connector to version 19.0 of the Facebook API. For more information, see Facebook's summary of Graph API v19.0 and Marketing API v19.0.
We now support the following breakdowns in our custom report tables:
video_asset
coarse_conversion_value
fidelity_type
hsid
is_conversion_id_modeled
postback_sequence_index
redownload
skan_campaign_id
We now support the following fields in our custom report tables:
website_purchase_roas
ad_click_actions
ad_impression_actions
auction_bid
auction_competitiveness
auction_max_competitor_bid
catalog_segment_actions
catalog_segment_value_mobile_purchase_roas
catalog_segment_value_omni_purchase_roas
catalog_segment_value_website_purchase_roas
cost_per_15_sec_video_view
cost_per_2_sec_continuous_video_view
cost_per_ad_click
cost_per_dda_countby_convs
cost_per_one_thousand_ad_impression
created_time
dda_countby_convs
instagram_upcoming_event_reminders_set
interactive_component_tap
place_page_name
qualifying_question_qualify_answer_rate
video_play_retention_0_to_15s_actions
video_play_retention_20_to_60s_actions
video_play_retention_graph_actions
video_time_watched_actions
wish_bid
We have deprecated the following fields in our custom report tables:
cost_per_estimated_ad_recallers
estimated_ad_recall_rate
gender_targeting
labels
location
unique_actions
unique_clicks
unique_ctr
unique_inline_link_click_ctr
unique_inline_link_clicks
unique_link_clicks_ctr
unique_outbound_clicks
unique_outbound_clicks_ctr
action_converted_product_id
Fivetran Platform Connector
The Fivetran Platform connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
GitHub
The GitHub connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
Google Ads
We've added the option to disable skipping empty account reports. This feature is enabled by default for all connectors. Now, you can also manually toggle it On or Off on the connector setup form.
See our Skip Empty Reports documentation for further details.
Google Drive
We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.
Greenhouse
We have made the following changes to the Schema tab for connectors created on or after July 18, 2024:
- We display all table names in lowercase
- We display all the tables, including the empty tables
- We no longer support table-level selection and deselection for syncing
Guru
We have changed the sync strategy of the connector. We no longer re-import the following tables weekly to capture deletes:
EVENT
TASK
Helpscout
We have made the following changes to the Schema tab for connectors created on or after July 31, 2024:
- We display all table names in lowercase
- We display all the tables, including the empty tables
- We no longer support table-level selection or deselection for syncing
Helpshift
We have changed the sync strategy of the connector. We no longer re-import the following tables weekly to capture deletes:
ANALYTIC_AGENT
ANALYTIC_CUSTOM_BOT
ANALYTIC_CUSTOM_BOT_STEP
ANALYTIC_FAQ
ANALYTIC_ISSUE
ANALYTIC_OPEN_ISSUE
ANALYTIC_SUPPORT
ISSUE
Ironclad
We have made the following changes to the sync strategy for our Ironclad connector:
We now incrementally sync the following tables and their child tables to capture new records:
WORKFLOW
WORKFLOW_PARTICIPANT
WORKFLOW_REVIEWER
WORKFLOW_SIGNER
We now re-import the following tables and their child tables to capture updates and deletes:
GROUPS
RECORD
SCHEMA
USERS
WORKFLOW_SCHEMA
Previously, we re-imported all the tables during every sync.
Klaviyo
You can set the limit on how much of the historical data you want to pull for the EVENT
table. To do that, select the preferred range from the drop-down menu in the setup form.
Learn more in our Klaviyo documentation.
Lever
We have made the following changes to the Schema tab for connectors created on or after July 27, 2024:
- We display all table names in lowercase
- We display all the tables, including the empty tables
- We no longer support table-level selection or deselection for syncing
- The connector will sync only the Opportunity endpoint and its child endpoints
Loop
We have changed the sync strategy for the ADVANCED_SHIPPING_NOTICE
table. We no longer re-import the table and its child tables to capture deletes.
Luma
We have changed the sync strategy for the EVENT
table. We no longer re-import the EVENT
tables and its child tables to capture deletes.
Mandrill
We've removed the Template Labels filtering option from the connector configuration. This change applies to all new connectors created after June 20, 2024.
MariaDB
We now support version 10.11 of MariaDB. Learn more in MariaDB's Changes and Improvements in MariaDB 10.11 documentation.
All new MariaDB connectors now support Fivetran Teleport Sync for tables without primary keys. Learn more in our MariaDB Fivetran Teleport Sync documentation.
Marketo
You can now set the historical sync time frame for the following tables:
ACTIVITY_*
LEAD_SEGMENT
SEGMENT
DELETED_PROGRAM_MEMBERSHIP
OPPORTUNITY_MEMBERSHIP
LIST_MEMBERSHIP
MERGED_LEAD
To support this enhancement, we have added a new drop-down menu, Historical Sync Time Frame, to the connector setup form.
Materialize
You can now configure your Materialize Cloud destination using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
Microsoft Dynamics 365 Business Central
Our Microsoft Dynamics 365 Business Central connector is now available in BETA.
Read our Microsoft Dynamics 365 Business Central connector documentation.
Microsoft Dynamics 365 Finance and Operations
Our Microsoft Dynamics 365 Finance and Operations connector is now generally available. Read our Microsoft Dynamics 365 Finance and Operations connector documentation.
Mixpanel
We now support Service Accounts authentication for Mixpanel connectors. We support this authentication method to handle Mixpanel's deprecation of the Project Secret authentication method. We recommend that you use the Service Accounts authentication method for both new and existing connectors.
Monday.com
We have changed the sync strategy for the ACTIVITY_LOG
table. We now incrementally sync the table.
MotherDuck
You can now configure your MotherDuck destination using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
MySQL
All new MySQL connectors now support Fivetran Teleport Sync for tables without primary keys. Learn more in our MySQL Fivetran Teleport Sync documentation.
NetSuite SuiteAnalytics
We have fixed a bug where we didn’t sync some of the records for the amortizationScheduleRecurrence
table.
Ometria
- We now incrementally sync the
CONTACT
table.
Opsgenie
We have changed the sync strategy for the ALERT
table. We now incrementally sync the ALERT
table to capture new records and updates. We no longer capture deletes for the ALERT
table. Previously, we used to re-import the table.
Pardot
We have added a new field, Historical Sync Limit, to the connector setup form. This allows you to select the time range for which historical data should be synced. The default value is ALL_TIME
. For an existing connector, you can edit the connection details and set the time frame value. We have also added support for the timeframe_months
field for connectors created using the Create a Connector endpoint. For more information, see our REST API config.
The historical sync limit only applies to the following tables:
EMAIL
LIST_MEMBERSHIP
VISITOR_ACTIVITY
VISITOR_PAGE_VIEW
For more information, see our Pardot documentation.
PlanetScale
You can now configure your PlanetScale connector using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
Productboard
We have changed the sync strategy for the NOTE
table. During initial syncs and historical syncs, you can now sync data for this table dating back to 2014.
Propel
You can now configure your Propel Cloud destination using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
Qualtrics
We have deprecated API key-based authentication to connect to Qualtrics. Connectors using this authentication method will still continue to work properly. However, you can re-authorize your connection in the Fivetran Setup tab to use OAuth authentication. To connect using OAuth authentication, see our Qualtrics Setup instructions documentation.
The Qualtrics connector now supports Standard and Advanced authentication methods.
Reddit Ads
You can now configure the time zone for custom reports. Reports can now either be synced according to your Reddit Ads account's time zone or using a custom time zone.
Sailthru
You can now use your own S3 bucket to sync Sailthru Connect data. Previously, you had to use Fivetran's S3 bucket. To support this enhancement, we have added two new fields, S3 Bucket and Role ARN, to the setup form. We are gradually rolling out this improvement to all existing connectors.
Salesforce
We have upgraded our Salesforce connector from version 60.0 to 61.0 of the Salesforce REST API. Learn more about the changes in Salesforce's changelog. We are gradually rolling out this change to all existing connectors.
We now support AWS Private Link for Salesforce. This feature is in GA and is available only for Business Critical accounts.
Salesforce Marketing Cloud
We have added a new field, Historical Sync Time Frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. The default value is ALL_TIME
. For an existing connector, you can edit the connection details and set the time frame value. We have also added support for the historic_sync_time_frame
field for connectors created using the Create a Connector endpoint. For more information, see our REST API config.
The historical sync limit only applies to the following tables:
CHAT_MESSAGING_DETAIL_EXTRACT
EVENT
MOBILE_PUSH_DETAIL_EXTRACT
SMS_MESSAGE_TRACKING_DATA_VIEW
SAP ERP on HANA
We have made the following improvements to our SAP ERP on HANA connector.
SNC support
We added support for Secure Network Communications (SNC), the SAP's proprietary encryption/decryption tool. SAP supports both a certificate-based authentication and user/password authentication combined with SNC.
This update introduces changes in the connector setup form, including a dropdown to select one of the available SNC modes (No SNC, SNC with certificate, or SNC with certificate and user/password).
Additionally, we have introduced a Direct connection method, which is only available for the SNC with certificate or SNC with certificate and user/password modes. The combination of No SNC mode with the Direct connection is not allowed due to security concerns.
It is still possible to use an SSH tunnel with any of the SNC modes (including No SNC).
Data type mapping update
We've updated the mapping of the FLTP
SAP data type from FLOAT to DOUBLE.
For more information, see our SAP ERP on HANA documentation and SAP ERP on HANA setup guide.
SFTP
We have added the Magic Folder Mode functionality to our SFTP connector. For connectors created after July 22, 2024, you can now opt to sync files as unique tables within a schema in your destination. You can either select Magic Folder or Merge Mode as your sync strategy, in the connector setup form. For more information, see our setup instructions and REST API configuration.
SharePoint
We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.
SingleStore
You can now configure your SingleStore destination using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.
SQL Server
We can now sync tables without primary keys using Fivetran Teleport Sync. The feature is in Beta.
We now support syncing the JSON data type if you use change tracking or Fivetran Teleport Sync as your incremental sync method. See all supported data types in our SQL Server documentation.
Stripe
We now capture data of the archived prices in the PRICE
table. Previously, we captured data only for the active prices in this table.
Tempo
We have changed the sync strategy for the TIMESHEET_APPROVAL
table. During historical syncs and initial syncs, we now sync only the last 183 days' worth of data for this table.
UserVoice
We have made the following changes to the Schema tab for UserVoice connectors created on or after July 11, 2024:
- All table names now appear in lowercase.
- We now display all tables in the schema, including the empty tables.
- We no longer support table-level selection or deselection for new UserVoice connectors.
When I Work
We no longer re-import the PAYROLL
and SCHEDULED_SHIFT_BREAK
tables.
WorkdayFinancialManagement
Our Workday Financial Management connector is now available in BETA.
Read our Workday Financial Management documentation.
Zendesk Chat
We have made the following changes to the Schema tab for connectors created on or after July 23, 2024:
- We display all table names in lowercase
- We display all the tables, including the empty tables
- We no longer support table-level selection and deselection for syncing