v1.5.0 dbt_social_media_reporting

PR #35 includes the following updates:

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.

Full Changelog: v1.4.0...v1.5.0

v1.4.0 dbt_social_media_reporting

PR #34 includes the following updates:

Documentation

• Updates README with standardized Fivetran formatting

Under the Hood

Upstream Dependency Changes

• Increases the required Linkedin Pages package to version 1.2.0

Full Changelog: v1.3.1...v1.4.0

v1.3.1 dbt_social_media_reporting

PR #33 includes the following updates:

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.

Full Changelog: v1.3.0...v1.3.1

v1.3.0 dbt_social_media_reporting

PR #30 includes the following updates:

Bug Fix

• Adds explicit string casting for page_id, page_name, post_message, and post_url fields across all platform reporting models (social_media_reporting__facebook_posts_reporting, social_media_reporting__instagram_posts_reporting, social_media_reporting__linkedin_posts_reporting, social_media_reporting__twitter_posts_reporting) to ensure consistent data types.

Under the Hood

• Updates social_media_reporting__youtube_videos_reporting to include the platform field in the group by statement in order to maintain consistency with other platform reporting models.

Full Changelog: v1.2.0...v1.3.0

v1.2.0 dbt_social_media_reporting

PR #29 includes the following updates:

Features

• Increases the required dbt version upper limit to v3.0.0.

Full Changelog: v1.1.0...v1.2.0

v1.1.0 dbt_social_media_reporting

PR #27 includes the following updates:

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.

Full Changelog: v1.0.0...v1.1.0

v1.0.0 dbt_social_media_reporting

PR #23 includes the following updates:

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.

Full Changelog: v0.7.0...v1.0.0

v0.7.0 dbt_social_media_reporting

PR #20 includes the following updates for Instagram Business:

Schema/Data Changes

5 total changes • 1 possible breaking changes

Data Model	Change type	Old name	New name	Notes
social_media_reporting__instagram_posts_reporting	Modified Columns	impressions	impressions	Instagram has deprecated the *_impressions metrics in favor of *_views. To maintain compatibility with the downstream social_media_reporting__rollup_report model, these columns are now coalesced into a single impressions field, with *_views taking precedence. This change may slightly affect reported values for some media types. See the DECISIONLOG for details.
instagram_business__posts	New Columns		carousel_album_shares, carousel_album_views, story_shares, story_views, video_photo_shares, video_photo_views, reel_views
instagram_business__posts	Deprecated Columns	carousel_album_impressions, carousel_album_video_views, story_impressions, video_photo_impressions, video_views, reel_plays		Retained for backward compatibility but will be removed in a future release
stg_instagram_business__media_insights	New Columns		carousel_album_shares, carousel_album_views, story_shares, story_views, video_photo_shares, video_photo_views, reel_views
stg_instagram_business__media_insights	Deprecated Columns	carousel_album_impressions, carousel_album_video_views, story_impressions, video_photo_impressions, video_views, reel_plays		Retained for backward compatibility but will be removed in a future release

Updates

• The schema changes align with the April 2025 and December 2024 Fivetran Instagram Business connector updates:
  • Deprecated metrics are retained for backward compatibility but will be removed in a future release.
  • See the Instagram API documentation for more detail on the updated fields.

Under the Hood

• Updated the consistency test to only include columns present in both dev and prod, ensuring that the consistency test can run with what is common.
• Moved default var definitions in-line within models instead of defining them in the package’s dbt_project.yml to prevent conflicts with a user’s own dbt_project.yml, aligning with practices used in other packages.
• Standardized the syntax of the get_staging_files macro to match conventions used across other packages.

Full Changelog: v0.6.0...v0.7.0

v0.6.0 dbt_social_media_reporting

PR #16 includes the following updates:

Breaking Change: Addition of Youtube Analytics

• We have added Youtube Analytics as a platform in this package via the youtube__video_report model from the dbt_youtube_analytics package.
  • For Quickstart users, this is enabled/disabled automatically based on the presence of youtube_analytics data.
  • For other users, this is enabled by default. However, if you are not using the Youtube Analytics connection, you may disable it by following these steps in the README or by including the configuration shown below in your dbt_project.yml file:

vars:
    social_media_rollup__youtube_enabled: False

models:
    youtube_analytics:
        enabled: false
    youtube_analytics_source:
        enabled: false

Documentation

• Added Quickstart model counts to README. (#15)
• Corrected references to connectors and connections in the README. (#15)

Under the Hood

• Updated Copyright and README format.
• Updated comparison__rollup_report validation test to correctly reference _social_media_dev.
• Added table variables for the upstream Youtube Analytics package in the quickstart.yml.

Full Changelog: v0.5.0...v0.6.0

v0.5.0 dbt_social_media_reporting

Upstream Breaking Changes (Twitter Organic)

PR #12 from the upstream dbt_twitter_organic_source package includes the following breaking change updates:

• The source defined in the src_twitter_organic.yml file has been renamed from twitter_organic to twitter to align with the default schema name used by the upstream Fivetran connector.
  • If you're referencing sources from the upstream Twitter Organic packages, please update your source references as needed. See below for the full scope of source changes.

New Source Reference	Old Source Reference
"{{ source('twitter','account_history') }}"	"{{ source('twitter_organic','account_history') }}"
"{{ source('twitter','organic_tweet_report') }}"	"{{ source('twitter_organic','organic_tweet_report') }}"
"{{ source('twitter','tweet') }}"	"{{ source('twitter_organic','tweet') }}"
"{{ source('twitter','twitter_user_history') }}"	"{{ source('twitter_organic','twitter_user_history') }}"

• The default schema name has been modified from twitter_organic to now be twitter to more closely align with the default schema name generated by the Fivetran connector. Please be aware if you were leveraging the previous default schema then you will need to update the twitter_organic_schema variable accordingly.
• All identifier variables in the src_twitter_organic.yml file have been renamed. If you’re using any of these in your project, please update them accordingly. The changes include:
  • Prepending twitter_organic_* has been updated to twitter_* to align with the schema change.
  • The spelling of *_identifer has been corrected to *_identifier.

New Identifier Variable Name	Old Identifier Variable Name
twitter_account_history_identifier	twitter_organic_account_history_identifer
twitter_organic_tweet_report_identifier	twitter_organic_organic_tweet_report_identifer
twitter_tweet_identifier	twitter_organic_tweet_identifer
twitter_twitter_user_history_identifier	twitter_organic_twitter_user_history_identifer

Under the Hood

• Consistency validation for integration tests has been added for the social_media_reporting__rollup_report model. (PR #11)
• Updated the maintainer PR, Issue, Feature Request, and Config templates to resemble the most up to date format. (PR #11)
• Renamed the Twitter Organic seed files to allow for more testing functionality. (PR #11)
• Addition of a section tag within the README so the model descriptions may be accessible within the Fivetran UI for Quickstart. (PR #10)

Full Changelog: v0.4.0...v0.5.0