Phrase - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between Phrase and OpenText Core Digital Asset Management

Phrase and OpenText Core Digital Asset Management complement each other well in global content operations. Phrase manages translation workflows, linguistic consistency, and multilingual content delivery, while OpenText Core DAM centralizes approved digital assets such as images, videos, documents, and brand files. Together, they help teams localize assets faster, reduce manual handoffs, and keep global content aligned across markets.

1. Send approved DAM assets to Phrase for localization

Direction: OpenText Core Digital Asset Management to Phrase

When marketing or product teams approve source assets in OpenText Core DAM, those assets can be automatically sent to Phrase for translation of embedded text, captions, metadata, file names, or associated copy. This is useful for campaigns, product launches, and regional content updates where creative assets must be localized before release.

• Reduces manual export and upload steps
• Speeds up multilingual campaign production
• Ensures translators work from the latest approved source asset

2. Return localized asset metadata and translations back to DAM

Direction: Phrase to OpenText Core Digital Asset Management

After translation is completed in Phrase, localized metadata, alt text, captions, and related text fields can be pushed back into OpenText Core DAM. This allows regional teams to search, filter, and publish assets in their local language without recreating records manually.

• Improves asset discoverability across markets
• Keeps multilingual metadata synchronized
• Supports faster reuse of approved localized assets

3. Localize product launch and campaign asset packages

Direction: Bi-directional

For global launches, OpenText Core DAM can provide the master creative package, while Phrase manages translation of all supporting text elements such as banners, social copy, product claims, and legal disclaimers. Once translated, the localized content can be associated back to the correct asset versions in DAM for regional distribution.

• Supports coordinated launch execution across countries
• Helps marketing teams maintain brand consistency
• Reduces delays caused by disconnected creative and translation workflows

4. Translate asset descriptions and alt text for accessibility and SEO

Direction: OpenText Core Digital Asset Management to Phrase

Organizations often store image descriptions, alt text, and usage notes in DAM. These fields can be sent to Phrase for translation so that localized websites and digital channels can publish accessible, search-friendly content in each target language.

• Improves accessibility compliance in multiple languages
• Supports localized SEO performance
• Ensures consistent terminology across digital channels

5. Manage multilingual video and rich media localization workflows

Direction: OpenText Core Digital Asset Management to Phrase and back to OpenText Core Digital Asset Management

For video and rich media assets, OpenText Core DAM can store source files, subtitles, transcripts, and version references. Phrase can translate subtitles, voiceover scripts, and on-screen text. The localized files can then be returned to DAM for regional publishing or handoff to downstream video platforms.

• Streamlines subtitle and transcript localization
• Supports version control for media assets
• Helps teams manage multiple language variants from one source

6. Synchronize brand-approved terminology across asset libraries

Direction: Bi-directional

Phrase can maintain approved terminology and translation memory for brand language, while OpenText Core DAM stores the approved source assets and related usage guidance. Integrating the two helps ensure that product names, campaign slogans, and regulated phrases remain consistent across all asset descriptions and localized content.

• Reduces terminology drift across regions
• Improves brand and legal consistency
• Supports repeatable localization for recurring campaigns

7. Trigger localization workflows when new assets are tagged for global use

Direction: OpenText Core Digital Asset Management to Phrase

When a new asset is tagged in OpenText Core DAM as global, multilingual, or region-specific, the integration can automatically create a localization job in Phrase. This is especially valuable for teams managing frequent content updates, where translation requests need to start as soon as assets are approved.

• Automates intake of translation requests
• Shortens turnaround time for global content teams
• Reduces dependency on manual coordination between marketing and localization teams

8. Publish market-ready localized assets to regional teams

Direction: Phrase to OpenText Core Digital Asset Management

Once translation is complete in Phrase, the localized content can be delivered back to OpenText Core DAM and organized by language, market, or campaign. Regional teams can then access the correct approved version for use in local websites, email campaigns, retail channels, or partner portals.

• Improves governance over localized content distribution
• Gives regional teams faster access to approved assets
• Supports scalable global content operations