Fivetran Release Notes

We have upgraded the Google Ads connector to version 26 of the Google Ads API.

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

• advance_booking_window_max_days
• advance_booking_window_min_days
• length_of_booking_max_days
• length_of_booking_min_days
• start_date_range_end_date
• start_date_range_start_date
• start_day_of_week
• user_set_dates_type

Google Ads replaced its hotel-specific ad group bid modifier criteria with vertical-agnostic ones that apply across travel verticals. As a result, we no longer populate the following columns in the AD_GROUP_BID_MODIFIER_HISTORY table. Use the replacement columns instead. Existing data in the deprecated columns is preserved.

Deprecated column Replacement column hotel_advance_booking_window_max_days advance_booking_window_max_days hotel_advance_booking_window_min_days advance_booking_window_min_days hotel_check_in_date_range_end_date start_date_range_end_date hotel_check_in_date_range_start_date start_date_range_start_date hotel_check_in_day_day_of_week start_day_of_week hotel_date_selection_type user_set_dates_type hotel_length_of_stay_max_nights length_of_booking_max_days hotel_length_of_stay_min_nights length_of_booking_min_days

We no longer support the customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled field in custom reports because Google Ads removed it. We replace it automatically with the customer.conversion_tracking_setting.enablement_setting field. Your report gets a new conversion_tracking_setting_enablement_setting column that reports the account-level enhanced conversions status, and we no longer populate the conversion_tracking_setting_enhanced_conversions_for_leads_enabled column. Existing data in that column is preserved. To see the status inherited from a manager account when you use cross-account conversion tracking, add the customer.conversion_tracking_setting.effective_enablement_setting field to your report.

The following fields are now available in custom reports:

• ad_group_criterion.require_eu_political_advertising_declaration
• asset.business_message_asset.line_info.line_id
• asset.business_message_asset.sms_info.country_code
• asset.business_message_asset.sms_info.phone_number
• asset_group.final_url_suffix
• asset_group.tracking_url_template
• asset_group.url_custom_parameters
• campaign.lift_measurement_config
• campaign.pmax_campaign_settings.local_services_pmax_campaign_settings.listing_id
• campaign_criterion.require_eu_political_advertising_declaration
• customer.conversion_tracking_setting.effective_enablement_setting
• customer.conversion_tracking_setting.enablement_setting
• local_services_lead.campaign

Original source

You can now choose Saturday or Sunday for table maintenance on your Databricks destination on AWS or Azure. To support this enhancement, we have added a VACUUM Day drop-down menu to the destination setup form. The selected day applies to both VACUUM and OPTIMIZE operations. Existing destinations retain their maintenance day unless you change it. The drop-down menu is visible when the Disable VACUUM operations toggle is set to OFF. For more information, see our Databricks table maintenance documentation.

Original source

Meta has deprecated the ids query parameter in the Graph API. Starting with Graph API v26.0, requests that use ids to fetch multiple objects at once return an error. As of October 27, 2026, this change starts applying to all remaining supported Graph API versions. For more information, see Meta's announcement.

The connector previously used the ids parameter to fetch some metadata entities in groups. We now request each entity individually, still grouped into batch requests. This change keeps your syncs working.

As a result, the connector sends more requests to the Facebook API during syncs. Syncs that fetch a large number of metadata entities may take longer. No action is required on your part.

Original source

On October 15, 2026, we are introducing a unified Fivetran Activations experience with the following improvements:

• Source-based navigation: Manage activations and syncs by source. Previously, activations were organized by individual syncs. The redesigned interface groups syncs by each unique source-to-destination path, similar to how we organize tables within Fivetran connections. You can more easily find individual activations, trial status, and settings.
• Unified access controls: Fivetran Users & Permissions replaces the separate Census access model. The Fivetran access model supports SCIM provisioning, team management, and more granular permissions. Learn more in our Role-Based Access Control documentation.
• Activations API V2: Use the new API version to support source-based management and unified access controls. Learn more in the API V2 documentation. We will retire Activations API V1 on January 15, 2027. If you still use API V1, you must migrate to API V2 before then.

As part of the move to Fivetran Users & Permissions, Workspaces are now deprecated. We will retire Workspaces on January 15, 2027.

Original source

We've added smart_plus_creative_id to the SMART_PLUS_AD_CREATIVE_INFO table.

We've added a new prebuilt report, CREATIVE_MATERIAL_REPORT_DAILY, which tracks per day performance metrics for individual creative materials used in Smart+ ad campaigns. The CREATIVE_MATERIAL_REPORT_DAILY table's primary keys are:

• advertiser_id
• smart_plus_ad_id
• main_material_id
• stat_time_day

The new prebuilt report offers standard creative performance metrics, including impressions, clicks, spend, video engagement, conversions, and social engagement (likes, comments, shares, follows, profile visits).

Original source

Fivetran is gradually moving all dbt projects to automatic patch version updates. We run each moved project on the latest supported patch release of its dbt minor version, the same way we run projects with the Automatically use latest patch version toggle enabled.

For example, a moved project that uses dbt 1.9.4 runs on the latest 1.9 patch release. Patch releases contain bug and security fixes for the same minor version.

For moved projects, the dbt project setup form doesn't show the Automatically use latest patch version toggle, and the dbt Core Version drop-down menu shows only minor versions.

You don't need to take any action. Your projects keep their current minor version. To move a project to a newer minor version, select it in the dbt Core Version drop-down menu.

Original source