OpenText Lens - Data Visibility - Marq Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and Marq

OpenText Lens - Data Visibility helps organizations discover, classify, and assess unstructured content across repositories, while Marq is typically used to create and manage branded content and marketing materials at scale. Together, they can support controlled content creation, governance, and reuse of approved assets across business teams.

• Approved content discovery for Marq template creation

  Data flow: OpenText Lens - Data Visibility to Marq

  Use OpenText Lens to identify high-value, approved, and frequently used documents such as product sheets, policy documents, or sales collateral stored across file shares and content repositories. Feed the approved source content into Marq so marketing and operations teams can convert it into reusable templates and standardized content blocks. This reduces duplicate effort and ensures Marq templates are built from governed, current materials.

• Sensitive content screening before publishing in Marq

  Data flow: OpenText Lens - Data Visibility to Marq

  Before content is imported into Marq for external use, OpenText Lens can scan repositories to detect confidential, regulated, or obsolete content. Only content that passes governance rules is promoted into Marq for campaign, sales, or partner-facing materials. This lowers the risk of publishing outdated pricing, restricted customer data, or noncompliant language.

• Content cleanup prior to brand asset migration

  Data flow: OpenText Lens - Data Visibility to Marq

  When organizations consolidate marketing assets into Marq, OpenText Lens can identify redundant, duplicate, and obsolete files across legacy repositories. Teams can use these findings to decide which assets should be migrated, archived, or retired before loading content into Marq. This improves migration quality and prevents clutter from being carried into the new environment.

• Governed reuse of source documents in campaign production

  Data flow: OpenText Lens - Data Visibility to Marq

  OpenText Lens can surface authoritative source documents such as compliance-approved product descriptions, legal disclaimers, and regional messaging variants. Marq teams can then reuse these approved inputs when assembling localized brochures, email assets, or presentation materials. This creates a controlled workflow that reduces manual rewriting and keeps messaging consistent across teams.

• Retention and archive alignment for expired marketing content

  Data flow: Marq to OpenText Lens - Data Visibility

  As campaigns end and assets become obsolete in Marq, metadata or exported content can be sent to OpenText Lens for review against retention and governance policies. OpenText Lens can help identify which files should be archived, deleted, or retained for audit purposes. This supports content lifecycle management and reduces storage and compliance risk.

• Audit support for regulated content production

  Data flow: Bi-directional

  OpenText Lens can provide visibility into the origin, classification, and sensitivity of source materials used in Marq. Marq can return usage details such as which templates or campaigns used specific assets. Together, this creates an audit trail for regulated industries that need to prove approved content was used in customer communications, investor materials, or public-facing documents.

• Cross-functional content governance workflow

  Data flow: Bi-directional

  Legal, compliance, and information governance teams can use OpenText Lens to flag content that requires review before it is made available in Marq. Marketing teams can then work in Marq only with content that has been cleared, while any newly created assets can be sent back for periodic review. This establishes a repeatable approval process that balances speed with control.

• Regional content standardization and localization control

  Data flow: OpenText Lens - Data Visibility to Marq

  OpenText Lens can identify the latest approved regional documents, translations, and policy references across repositories. Marq can then use these as the controlled source for localized content production. This helps global teams avoid using outdated regional variants and ensures local marketing materials remain aligned with corporate standards.