Brandfolder - LionBridge Integration and Automation

Common Integration Use Cases Between Brandfolder and Lionbridge

1. Automated Translation of Approved Brand Assets

Data flow: Brandfolder → Lionbridge

When marketing teams finalize campaign assets in Brandfolder, the approved files, captions, and supporting metadata can be sent to Lionbridge for translation and localization. This is useful for banners, product launch graphics, social media kits, and regional campaign materials that must be adapted for multiple markets.

• Reduces manual handoff between brand and localization teams
• Speeds up multilingual campaign delivery
• Ensures only approved, on-brand assets are translated

2. Localized Asset Return to Brandfolder for Regional Teams

Data flow: Lionbridge → Brandfolder

After translation is completed, localized versions of copy, subtitles, or region-specific asset variants can be returned to Brandfolder and stored alongside the source asset. Regional marketing teams can then access the correct language version from a single source of truth.

• Improves discoverability of localized content
• Prevents duplicate file storage across teams and regions
• Supports reuse of approved translations across future campaigns

3. Multilingual Metadata and Tag Translation for Better Searchability

Data flow: Brandfolder → Lionbridge → Brandfolder

Brandfolder asset metadata such as titles, descriptions, tags, and usage notes can be sent to Lionbridge for translation and then written back into Brandfolder. This makes assets easier to search and filter for local teams working in their native language.

• Improves asset findability in regional markets
• Supports consistent naming conventions across languages
• Reduces time spent manually localizing asset metadata

4. Localization Workflow Triggered by New Campaign Asset Uploads

Data flow: Brandfolder → Lionbridge

When a new campaign asset is uploaded to a designated Brandfolder collection, the integration can automatically create a translation job in Lionbridge. This is especially valuable for recurring product launches, seasonal promotions, and global brand campaigns with tight deadlines.

• Removes manual request creation for localization teams
• Creates a repeatable workflow for global content operations
• Helps teams meet launch dates across multiple regions

5. Translation Status Tracking for Cross-Team Visibility

Data flow: Lionbridge → Brandfolder

Lionbridge translation status updates can be pushed back into Brandfolder so marketing, product, and regional teams can see whether an asset is pending, in progress, reviewed, or completed. This gives stakeholders visibility without needing to check separate systems.

• Improves project tracking and accountability
• Reduces status update emails and manual follow-ups
• Helps teams coordinate launch readiness by market

6. Localization of Product and Packaging Assets for Global Markets

Data flow: Brandfolder → Lionbridge → Brandfolder

Brandfolder can serve as the repository for product packaging artwork, compliance graphics, and regulatory visuals that require language adaptation for different countries. Lionbridge translates the required text elements, and the localized versions are stored back in Brandfolder for downstream use by design, legal, and regional teams.

• Supports global product rollout and packaging updates
• Reduces risk of using outdated or untranslated artwork
• Helps maintain compliance across markets

7. Reuse of Approved Translations Across Future Asset Versions

Data flow: Bi-directional

Brandfolder can store source assets and their localized variants, while Lionbridge can leverage previously approved translations for recurring phrases, disclaimers, and campaign copy. This creates a more efficient translation process for repeated content such as taglines, legal text, and product descriptors.

• Improves translation consistency across campaigns
• Reduces localization cost and turnaround time
• Supports brand voice consistency in every market