OpenText TeamSite - LiveSite Content Services - iconik Integration and Automation

Common Integration Use Cases Between OpenText TeamSite - LiveSite Content Services and iconik

1. Publish approved video assets from iconik to LiveSite pages

Data flow: iconik ? OpenText TeamSite - LiveSite Content Services

Media teams can manage, tag, and approve video assets in iconik, then push selected assets or asset references into LiveSite for use on websites, landing pages, and campaign microsites. This ensures only approved, brand-safe media is exposed to customers while content teams can assemble pages without manually handling files.

• Reduces duplicate asset handling
• Speeds up campaign publishing
• Improves governance over customer-facing media

2. Use iconik metadata to drive personalized content experiences

Data flow: iconik ? OpenText TeamSite - LiveSite Content Services

Asset metadata from iconik, such as campaign, region, product line, language, or rights status, can be synchronized into LiveSite to support dynamic content selection. LiveSite can then render the most relevant media based on audience segment, geography, or page context.

• Enables more targeted digital experiences
• Supports regional and multilingual content delivery
• Improves content relevance without manual page duplication

3. Surface content usage and campaign context back into iconik

Data flow: OpenText TeamSite - LiveSite Content Services ? iconik

When LiveSite publishes or updates a page using a media asset, usage details can be sent back to iconik so media teams know where assets are deployed. This gives teams visibility into which videos or rich media are live, which campaigns they support, and when they need to be refreshed or retired.

• Improves asset lifecycle management
• Helps avoid expired or outdated media on live pages
• Supports faster campaign cleanup and replacement

4. Trigger content updates when new media versions are approved

Data flow: iconik ? OpenText TeamSite - LiveSite Content Services

When a new version of a video or rich media asset is approved in iconik, an integration can notify LiveSite to update the corresponding page component or content reference. This is useful for product launches, regulatory updates, and seasonal campaigns where media changes must be reflected quickly across digital properties.

• Reduces manual page maintenance
• Shortens time to publish updated media
• Helps maintain consistency across channels

5. Centralize approval workflows for marketing and content operations

Data flow: Bi-directional

iconik can serve as the media collaboration and approval workspace, while LiveSite manages final content assembly and publishing. Integration can pass approval status, review comments, and publish readiness between teams so content operations, legal, and marketing work from a shared process instead of disconnected tools.

• Improves cross-team coordination
• Creates clearer approval checkpoints
• Reduces publishing delays caused by email-based reviews

6. Reuse rich media across multiple digital properties

Data flow: iconik ? OpenText TeamSite - LiveSite Content Services

Organizations often need the same video asset on corporate sites, product portals, and regional microsites. By integrating iconik with LiveSite, teams can maintain one governed media source and reuse it across multiple experiences while LiveSite handles contextual rendering and placement.

• Eliminates redundant asset copies
• Ensures consistent branding across properties
• Simplifies updates when source media changes

7. Track rights, expiration, and compliance for published media

Data flow: iconik ? OpenText TeamSite - LiveSite Content Services

iconik can store rights and expiration metadata for media assets, and LiveSite can use that information to prevent expired content from being displayed. This is especially valuable for licensed footage, partner content, and regulated industries where media usage must be controlled.

• Reduces compliance risk
• Prevents expired assets from remaining live
• Supports audit-ready media governance

8. Improve campaign launch coordination between media and web teams

Data flow: Bi-directional

For major launches, media teams can prepare assets in iconik while web teams build pages in LiveSite. Integration can synchronize asset readiness, publish status, and launch dependencies so both teams know when content is ready for deployment. This helps coordinate complex launches across multiple markets and channels.

• Improves launch readiness visibility
• Reduces last-minute content bottlenecks
• Supports faster, more reliable campaign execution