Release Notes

August 2026

v1.6.1

Feature Update

Updates Quickstart to surface the connector-level models that Social Media Reporting does not already build, so you can enable them directly from Quickstart:

v1.6.2

Feature Updates

Adds DuckDB as a supported destination.

June 2026

v1.6.0

Schema/Data Changes (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when not using the union connections of the same type feature)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) {connector_name}_sources variables for more robust union data configuration. The old {connector_name}_union_schemas and {connector_name}_union_databases variables will still be supported. See the README for specific details.

Upstream Dependency Changes

Increases the required Facebook Pages package to version 1.3.0
Increases the required Instagram Business package to version 1.2.0
Increases the required Twitter Organic package to version 1.2.0
Increases the required LinkedIn Pages package to version 1.4.0
Increases the required YouTube Analytics package to version 1.4.0

February 2026

v1.5.0

Schema/Data Change (--full-refresh required after upgrading)

21 total changes • 13 of which are breaking in the form of materialization updates

Data Model(s)	Change type	Old	New	Notes
`stg_linkedin_pages__organization` `stg_linkedin_pages__organization_ugc_post` `stg_linkedin_pages__post_content` `stg_linkedin_pages__share_statistic` `stg_linkedin_pages__ugc_post_history` `stg_linkedin_pages__ugc_post_share_statistic` (as well as the upstream tmp models for each model)	Materialization	Table	View	Breaking: These staging models are now views. Upon full refresh, the package will automatically drop the tables and recreate them as views. However, we recommend reviewing your schema and manually dropping any remaining staging models materialized as tables as they will no longer be updated in favor of the materialized views.
`linkedin_pages__posts`	Renamed column	`ugc_post_id`	`post_id`	Breaking: Column renamed to reflect that the model now includes both UGC posts and shares.
`social_media_reporting__rollup_report`	Data expansion	UGC posts only	UGC posts + shares	Linkedin Pages data will now includes both UGC posts and LinkedIn shares.
`social_media_reporting__linkedin_posts_reporting`	Data expansion	UGC posts only	UGC posts + shares	Linkedin Pages data will now includes both UGC posts and LinkedIn shares.
`linkedin_pages__posts`	Data expansion	UGC posts only	UGC posts + shares	Model now includes both UGC posts and LinkedIn shares.
`linkedin_pages__posts`	Added column		`content_type`	Indicates whether the post is from 'ugc' (UGC post) or 'share' (LinkedIn share).
`stg_linkedin_pages__organization_share`	New model			Mapping table between organizations and shares.
`stg_linkedin_pages__share_content`	New model			Content of shares (articles, images, polls, text).
`stg_linkedin_pages__share_history`	New model			Version history of shares with metadata.
`stg_linkedin_pages__share_share_statistic`	New model			Mapping between shares and share statistics.

Under the Hood

Added seed files for new LinkedIn data sources, as well as designed column types to ensure no data type confusion errors.

January 2026

v1.3.1

Bug Fix

Fixes double-counting of Instagram impressions in social_media_reporting__instagram_posts_reporting. Fivetran's Instagram Connector populates multiple fields with the same value for certain media types (CAROUSEL_ALBUM and VIDEO/Reels). Previously, the model summed all view metrics, which counted impressions twice. The fix takes video_photo_views or video_photo_impressions, which is the basis for both carousel_album and reel impressions/views.

v1.4.0

Documentation

Updates README with standardized Fivetran formatting

Under the Hood

Upstream Dependency Changes

Increases the required Linkedin Pages package to version 1.2.0

November 2025

v1.1.0

Schema/Data Change

1 total change • 0 possible breaking change

Data Model(s)	Change type	Old	New	Notes
`social_media_reporting__rollup_report`	Deprecated Column (Facebook Pages only)	`impressions`	`impressions`	The impressions field for Facebook Pages has been deprecated as of November 2025 and persists in the upstream package. The field remains active and relevant for all other platforms. An alternative solution will be provided in a future release.

Documentation

Updated YAML documentation to note the deprecation of the impressions field for the Facebook Pages platform, clarifying it will not be populated following November 2025.

Under the Hood

Updates to the comparison__rollup_report consistency test.

August 2025

v1.0.0

dbt Fusion Compatibility Updates

Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
- Removed all dbt_utils.unique_combination_of_columns tests.

Under the Hood

Updated conditions in .github/workflows/auto-release.yml.
Added .github/workflows/generate-docs.yml.