Acquia DAM (Widen) - OpenText TeamSite Authoring Services Integration and Automation

Common Integration Use Cases Between Acquia DAM (Widen) and OpenText TeamSite Authoring Services

Acquia DAM (Widen) and OpenText TeamSite Authoring Services complement each other well in enterprise digital experience operations. Acquia DAM serves as the centralized source of approved brand assets, while TeamSite manages structured web content creation, workflow, and publishing. Integrating the two platforms helps marketing and digital teams reuse approved assets efficiently, reduce manual file handling, and maintain brand consistency across web properties.

1. Centralized asset delivery from Acquia DAM into TeamSite page authoring

Data flow: Acquia DAM to OpenText TeamSite Authoring Services

Marketing teams can browse and insert approved images, logos, videos, and documents stored in Acquia DAM directly into TeamSite page templates and content blocks. This eliminates the need to download, re-upload, or duplicate assets in the CMS.

• Reduces time spent searching for the right asset
• Ensures only approved, current brand assets are used on the website
• Supports faster page creation for campaigns, product launches, and seasonal updates

2. Automated asset metadata sync for web content governance

Data flow: Acquia DAM to OpenText TeamSite Authoring Services

Asset metadata such as title, description, campaign name, product line, usage rights, and expiration date can be synchronized into TeamSite to support content governance and compliance. This is especially useful when web teams need to understand asset restrictions before publishing.

• Improves control over licensed or time-sensitive media
• Helps prevent expired or region-restricted assets from being published
• Supports structured content tagging and search within TeamSite

3. Asset approval and publishing workflow alignment

Data flow: Bi-directional

When a new asset is approved in Acquia DAM, a notification or status update can trigger content authors in TeamSite to use the approved version in a web page or campaign module. Conversely, if a web page requires a new image or document, TeamSite users can initiate an asset request back to the DAM team for creation or approval.

• Aligns creative approval with web publishing timelines
• Reduces bottlenecks between design, marketing, and web operations
• Creates a more transparent handoff between asset management and content publishing teams

4. Campaign landing page assembly using DAM-managed creative assets

Data flow: Acquia DAM to OpenText TeamSite Authoring Services

For product launches, promotions, or regional campaigns, TeamSite authors can assemble landing pages using approved banners, hero images, videos, and downloadable collateral from Acquia DAM. This supports rapid campaign deployment while preserving brand consistency across markets.

• Speeds up launch of campaign microsites and landing pages
• Enables reuse of approved creative across multiple web properties
• Supports distributed marketing teams working across regions or business units

5. Dynamic asset updates on published web pages

Data flow: Acquia DAM to OpenText TeamSite Authoring Services

When a file is updated in Acquia DAM, such as a refreshed product image, revised brochure, or new logo version, TeamSite can reference the latest approved asset automatically or through a controlled update process. This reduces the risk of outdated content remaining live on the website.

• Minimizes manual replacement work for web teams
• Ensures published pages reflect the latest approved brand materials
• Improves consistency across multiple pages and sites using the same asset

6. Regional and partner-specific content distribution

Data flow: Acquia DAM to OpenText TeamSite Authoring Services

Acquia DAM portals can provide region-specific or partner-approved assets to TeamSite authors responsible for localized websites. This is valuable when different markets require different imagery, language variants, or regulatory disclosures.

• Supports localization and market-specific web publishing
• Reduces the risk of using assets not approved for a given geography
• Improves collaboration between central brand teams and local web teams

7. Usage analytics feedback loop for content optimization

Data flow: OpenText TeamSite Authoring Services to Acquia DAM

Performance data from TeamSite pages, such as click-through rates, downloads, or engagement by asset type, can be fed back into Acquia DAM analytics. Marketing teams can then identify which images, videos, or documents perform best and prioritize similar assets in future campaigns.

• Improves asset selection based on real web performance
• Helps creative teams understand which content drives engagement
• Supports data-driven decisions for future asset production

8. Controlled asset request and creation workflow from web content teams

Data flow: OpenText TeamSite Authoring Services to Acquia DAM

When web authors need a new asset that is not yet available, TeamSite can route an asset request to Acquia DAM workflows for creation, review, and approval. This creates a structured intake process instead of ad hoc email requests or file sharing.

• Improves request tracking and accountability
• Reduces delays caused by informal asset handoffs
• Ensures new assets are created with the correct format, metadata, and approval status

Together, Acquia DAM and OpenText TeamSite Authoring Services create a more efficient content supply chain by connecting approved digital assets with structured web publishing workflows. The result is faster content delivery, stronger brand governance, and less operational friction across marketing and digital teams.