OpenText DAM (OTMM) - Wix Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Wix

OpenText DAM (OTMM) is well suited for managing high-value digital assets such as product images, marketing media, museum collections, and broadcast content, while Wix is designed for quickly building and maintaining customer-facing websites with flexible no-code and low-code tools. Integrating the two platforms helps organizations keep website content current, reduce manual asset handling, and ensure approved media is consistently published across digital properties.

1. Automated publishing of approved product images to Wix product and landing pages

Data flow: OpenText DAM (OTMM) to Wix

When product images are approved in OTMM, they can be automatically pushed to Wix product pages, category pages, or campaign landing pages. This is especially useful for retail, manufacturing, and distribution teams that need to keep web content aligned with the latest product releases, packaging updates, or seasonal promotions.

• Marketing teams avoid manually downloading and re-uploading images
• Web content stays aligned with the latest approved assets
• Reduces risk of outdated or non-compliant product imagery appearing online

2. Centralized management of campaign assets for Wix marketing microsites

Data flow: OpenText DAM (OTMM) to Wix

Campaign banners, hero images, promotional videos, and event visuals stored in OTMM can be published directly to Wix microsites and campaign pages. This supports faster launch of time-sensitive campaigns and ensures that all web assets come from a controlled source of truth.

• Campaign managers can launch pages faster with pre-approved assets
• Brand consistency is maintained across multiple campaign sites
• Asset reuse is improved across regions, products, and promotions

3. Bi-directional asset metadata synchronization for web governance

Data flow: Bi-directional between OpenText DAM (OTMM) and Wix

Asset metadata such as campaign name, product SKU, usage rights, expiration date, and language can be synchronized between OTMM and Wix. OTMM remains the master for asset governance, while Wix can return usage context such as page placement, campaign association, or publish status.

• Improves visibility into where assets are used on the website
• Supports rights management and content expiration controls
• Helps marketing and compliance teams track approved usage

4. Automated updates of museum and heritage collection media on public exhibit pages

Data flow: OpenText DAM (OTMM) to Wix

Museums and heritage organizations can store collection images, exhibit videos, and archival media in OTMM and publish selected assets to Wix exhibit pages or digital collections portals. When curators update descriptions, replace images, or retire content, the website can be refreshed automatically.

• Curatorial teams manage assets centrally without web editing dependency
• Public-facing exhibit pages remain accurate and current
• Supports richer digital storytelling with controlled media delivery

5. Video distribution for brand, event, and broadcast content on Wix sites

Data flow: OpenText DAM (OTMM) to Wix

Marketing, corporate communications, and media teams can use OTMM to manage event recordings, brand videos, and short-form or long-form broadcast assets, then publish selected versions to Wix pages. This is useful for embedding video galleries, event recap pages, or campaign storytelling sections on the website.

• Ensures only approved video versions are published
• Reduces storage duplication and manual file handling
• Improves speed of publishing multimedia-rich web experiences

6. Website asset request workflow from Wix to OpenText DAM (OTMM)

Data flow: Wix to OpenText DAM (OTMM)

When website editors or regional teams need a new image, localized banner, or updated product photo, a request can be initiated from Wix and routed into OTMM for review, approval, and fulfillment. This creates a controlled intake process for asset creation and replacement.

• Web teams can request assets without emailing creative teams
• Requests are tracked through a structured approval workflow
• Improves turnaround time and accountability for content updates

7. Localization and regional website content distribution

Data flow: OpenText DAM (OTMM) to Wix

For organizations operating multiple regional websites in Wix, OTMM can distribute localized versions of product images, campaign visuals, and promotional videos to the correct site or page based on market, language, or brand rules. This is valuable for global marketing and distributed channel teams.

• Supports consistent brand execution across regions
• Reduces manual localization errors
• Enables faster rollout of market-specific web content

8. Asset usage tracking and retirement based on website lifecycle

Data flow: Wix to OpenText DAM (OTMM)

Wix can send asset usage information back to OTMM, such as which images or videos are currently live, which pages they support, and when they are no longer in use. OTMM can then flag assets for review, archival, or retirement based on campaign end dates or content lifecycle rules.

• Helps reduce clutter in the DAM repository
• Supports governance for expired campaigns and outdated product content
• Improves operational control over digital asset lifecycle management