Sitecore - Brandfolder Integration and Automation

Common Integration Use Cases Between Sitecore and Brandfolder

1. Centralized brand asset delivery to Sitecore pages

Flow: Brandfolder ? Sitecore

Marketing teams store approved images, videos, logos, and campaign graphics in Brandfolder, then publish selected assets into Sitecore for use across web pages, landing pages, and microsites. This ensures Sitecore authors always pull from a controlled asset library rather than uploading local copies.

• Reduces duplicate asset storage and version drift
• Ensures only approved brand assets are used on customer-facing pages
• Speeds up web content creation for marketing teams

2. Automated asset updates for campaign and product content

Flow: Brandfolder ? Sitecore

When a campaign image, banner, or product visual is updated in Brandfolder, the latest approved version can automatically sync to Sitecore content components that reference it. This is useful for time-sensitive promotions, seasonal campaigns, and product launches where visual consistency matters.

• Eliminates manual replacement of outdated assets
• Supports faster campaign refreshes across multiple pages
• Reduces the risk of publishing expired or noncompliant content

3. Brand-approved asset selection within Sitecore authoring workflows

Flow: Brandfolder ? Sitecore

Content authors in Sitecore can browse or search Brandfolder directly to select approved assets during page creation. This gives editors access to the right files, metadata, and usage guidance without leaving the CMS environment.

• Improves author productivity
• Helps non-design teams choose the correct asset variant
• Supports governance through embedded brand rules and metadata

4. Publishing Sitecore content references back to Brandfolder for campaign governance

Flow: Sitecore ? Brandfolder

When Sitecore pages, landing pages, or campaign modules are finalized, key content references such as page thumbnails, hero images, or approved creative can be pushed back into Brandfolder as part of the campaign record. This creates a centralized archive of what was actually published.

• Provides a single source of truth for campaign assets and outputs
• Supports auditability and brand compliance reviews
• Makes it easier to reuse successful creative in future campaigns

5. Metadata synchronization for better asset discoverability

Flow: Bi-directional

Brandfolder asset metadata such as campaign name, product line, region, language, and usage rights can be synchronized with Sitecore content tags and taxonomy fields. This allows Sitecore teams to filter and reuse assets based on business context, while Brandfolder retains richer content governance information.

• Improves search and filtering across both platforms
• Aligns content structure between DAM and CMS teams
• Supports regional and multilingual content operations

6. Product launch content alignment between DAM and web experience

Flow: Brandfolder ? Sitecore

For product launches, Brandfolder can serve as the repository for approved product imagery, packaging shots, and launch creative, while Sitecore consumes those assets to build launch pages and campaign microsites. This ensures the web experience always reflects the latest approved product visuals.

• Accelerates launch execution across marketing and web teams
• Reduces inconsistencies between product marketing and digital channels
• Supports coordinated launch governance across departments

7. Asset usage tracking and content governance

Flow: Sitecore ? Brandfolder

Usage data from Sitecore, such as which assets are placed on high-traffic pages or campaign landing pages, can be sent to Brandfolder to help teams understand asset performance and reuse patterns. This helps brand and marketing teams prioritize which creative to refresh, retire, or repurpose.

• Improves visibility into asset value and usage frequency
• Supports content lifecycle management
• Helps teams make data-driven creative decisions

8. Cross-team workflow for asset approval and web publishing

Flow: Bi-directional

Brandfolder can manage the approval status of creative assets, while Sitecore can consume only assets marked as approved for web use. If an asset is rejected or replaced in Brandfolder, the corresponding Sitecore content can be flagged for review or update before publication.

• Creates a controlled approval path from design to web publishing
• Reduces compliance and brand risk
• Improves collaboration between creative, marketing, and web operations teams