Release Notes

August 2026

We've updated the following quickstart data model packages to add DuckDB as a supported destination:

Expand to see full list

Ad Reporting to version v2.7.3
Amazon Ads to version v1.3.1
Amazon Selling Partner to version v0.5.1
Amplitude to version v1.4.1
App Reporting to version v1.3.2
Apple App Store to version v1.3.2
Apple Search Ads to version v1.3.1
Asana to version v1.4.1
AWS Cloud Cost to version v0.4.1
Facebook Ads to version v1.5.1
Facebook Pages to version v1.3.1
Fivetran Platform Connector to version v2.5.3
GitHub to version v1.4.1
Google Ads to version v1.4.1
Google Analytics 4 Export to version v0.7.2
Google Play to version v1.3.1
Greenhouse to version v1.4.1
HubSpot to version v1.9.2
Instagram Business to version v1.2.1
Intercom to version v1.7.1
Iterable to version v1.5.1
Jira to version v1.10.2
Klaviyo to version v1.4.1
Lever to version v1.3.1
LinkedIn Ad Analytics to version v1.3.1
LinkedIn Company Pages to version v1.5.1
Mailchimp to version v1.3.2
Marketo to version v1.4.1
Microsoft Advertising to version v1.3.1
Microsoft Dynamics 365 CRM to version v0.4.1
Mixpanel to version v0.17.1
NetSuite SuiteAnalytics to version v1.7.1
Pardot to version v1.4.1
Pendo to version v1.4.1
Pinterest Ads to version v1.3.1
Qualtrics to version v1.3.1
QuickBooks to version v1.9.1
Recharge to version v1.5.2
Recurly to version v1.5.1
Reddit Ads to version v1.5.1
Sage Intacct to version v1.4.1
Salesforce to version v2.4.1
Salesforce Marketing Cloud to version v0.6.1
SAP to version v0.8.1
ServiceNow to version v1.0.2
Shopify to version v1.9.2
Shopify Holistic to version v1.3.1
Snapchat Ads to version v1.3.1
Social Media Reporting to version v1.6.2
StackAdapt to version v0.2.1
Stripe to version v1.10.1
TikTok Ads to version v1.4.1
Twilio to version v1.4.1
Unified RAG to version v0.3.1
Workday HCM to version v1.0.3
X Ads to version v1.3.1
X Organic to version v1.2.1
Xero to version v1.6.1
YouTube Analytics to version v1.2.1
Zendesk Support to version v1.7.1
Zuora to version v1.4.1

June 2026

v1.7.0

Schema/Data Change

2 total changes • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
(Breaking) `stg_intercom__tag`, `stg_intercom__company_tag_history`, `stg_intercom__contact_tag_history`, `stg_intercom__conversation_tag_history`	Changed data type	integer	string	Casts `tag_id` as a string so joins succeed regardless of source type.
`stg_intercom__company_history`, `stg_intercom__company_tag_history`, `stg_intercom__contact_company_history`	explicit data type cast	source data type	string	Casts `company_id` as a string for consistent join keys.

Bug Fix

Resolves a Database Error in intercom__company_enhanced (and other tag-joined models) caused by mismatched tag_id data types. The fix casts all ID join keys to string in staging. See the Schema/Data Change table above.

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

January 2026

v1.6.0

Documentation

Updates README with standardized Fivetran formatting.

Under the Hood

In the quickstart.yml file:
- Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
- Adds supported_vars for Quickstart UI customization.

v1.5.0

Schema/Data Change

3 total changes • 2 possible breaking change

Data Model(s)	Change type	Old	New	Notes
`intercom__conversation_enhanced` `intercom__conversation_metrics`	New field		`conversation_assignee_id`	The ID of the user assigned to the conversation. This column is an alias of `assignee_id` from `stg_intercom__conversation_history` model. If you also persist `assignee_id` using the `intercom__conversation_history_pass_through_columns` variable, ensure it uses a different alias to avoid duplicate column errors.
`intercom__conversation_enhanced` `intercom__conversation_metrics`	New field		`is_assignee_admin`	Boolean field indicating whether the conversation assignee is an admin user, determined by joining `assignee_id` with the admin table. Returns `false` if conversation is unassigned or assigned to a non-admin user
`intercom__conversation_enhanced` `intercom__conversation_metrics` `stg_intercom__conversation_history`	Deprecated field	`assignee_type` or `conversation_assignee_type`	Marked as [DEPRECATED]	The `assignee_type` field is no longer supported by Intercom's API. Use `is_assignee_admin` instead to determine if an assignee is an admin

Under the Hood

Updated intercom__admin_metrics to filter conversations using is_assignee_admin boolean instead of the deprecated conversation_assignee_type = 'admin' string comparison
Enhanced intercom__conversation_enhanced with a left join to the admin table to determine admin assignee status
Updates to the integrity and consistency validation tests to ensure accurate testing of model changes between versions.

October 2025

v1.1.0

Bug Fixes

Performance optimization: Refactored int_intercom__conversation_part_events for customers with large intercom__conversation_part_history source tables:
- Consolidated redundant CTEs and eliminated unnecessary joins to reduce compute load and memory usage for larger source tables.
- Implemented single window function pass instead of multiple subqueries.
- Replicate IGNORE NULLS logic with first_value() window functions using custom ordering (case when condition then 0 else 1 end) to prioritize relevant events and naturally skip null values.
Data accuracy fix: Corrected the last_close_by_author_id window function logic that was incorrectly using ascending order instead of descending order, causing it to return the same value as first_close_by_author_id. The fix ensures proper chronological ordering to capture the actual last close event author.

Under the Hood

Created consistency and integrity tests for intercom__conversation_enhanced to validate that the above changes do not impact end model values.