OpenText TeamSite - LiveSite Content Services - Marq Integration and Automation

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

1. Brand-Compliant Campaign Content Publishing

Data flow: Marq - OpenText TeamSite - LiveSite Content Services

Marketing teams can create approved campaign assets in Marq, such as banners, landing page visuals, product sheets, and promotional graphics, then publish them directly into TeamSite for use across websites and portals. This reduces manual handoffs between design and web teams and helps ensure that only brand-approved content is delivered to customer-facing channels.

Business value: Faster campaign launches, fewer version control issues, and consistent brand presentation across digital properties.

2. Dynamic Web Page Asset Updates

Data flow: Marq - OpenText TeamSite - LiveSite Content Services

When marketing updates a brochure, infographic, or event asset in Marq, the revised version can be pushed into TeamSite and rendered automatically on relevant pages. This is useful for frequently changing content such as product collateral, seasonal promotions, and event materials.

Business value: Reduces web maintenance effort and ensures visitors always see the latest approved content.

3. Personalized Content Assembly for Customer Portals

Data flow: Bi-directional

TeamSite can deliver personalized page experiences while Marq supplies modular content assets that can be reused across audience segments, regions, or product lines. TeamSite can also send performance or audience context back to inform which Marq templates and content variants should be produced next.

Business value: Improves relevance of digital experiences and supports more targeted content operations.

4. Sales Enablement Content Distribution

Data flow: Marq - OpenText TeamSite - LiveSite Content Services

Sales and field marketing teams can author pitch decks, one-pagers, and proposal inserts in Marq, then publish approved versions to TeamSite for distribution through partner portals or internal sales hubs. TeamSite can present the right collateral based on product, region, or customer segment.

Business value: Speeds access to approved sales materials and reduces the use of outdated collateral.

5. Multi-Channel Content Reuse Across Web and Print-Ready Assets

Data flow: Marq - OpenText TeamSite - LiveSite Content Services

Organizations can use Marq to create reusable content blocks and design templates that are then surfaced in TeamSite for web publishing. The same approved content can support both digital experiences and print-ready or downloadable assets, improving consistency across channels.

Business value: Increases content reuse, lowers production cost, and improves governance across channels.

6. Regional Content Localization Workflow

Data flow: OpenText TeamSite - LiveSite Content Services - Marq

TeamSite can identify pages or content elements that require localization and send them to Marq for regional adaptation. Local teams can update language, imagery, and market-specific messaging in Marq, then return the localized assets to TeamSite for publishing.

Business value: Accelerates localization cycles and helps regional teams maintain control without compromising central governance.

7. Event and Webinar Promotion Asset Management

Data flow: Marq - OpenText TeamSite - LiveSite Content Services

Marketing teams can create event invitations, registration graphics, speaker cards, and follow-up assets in Marq, then publish them into TeamSite for use on event landing pages and promotional microsites. Updates to event details can be synchronized quickly across all customer-facing touchpoints.

Business value: Improves coordination between campaign teams and web teams while reducing manual updates.

8. Content Approval and Publishing Governance

Data flow: Bi-directional

Marq can serve as the content creation and approval environment for marketing assets, while TeamSite acts as the controlled publishing layer for live digital experiences. Approval status, asset metadata, and publishing readiness can be exchanged between the platforms to enforce governance before content goes live.

Business value: Strengthens compliance, reduces publishing risk, and creates a clearer workflow between content creators and web operations.