OpenText Active Community - Trading Grid - Optimizely Integration and Automation

Common Integration Use Cases Between OpenText Active Community - Trading Grid and Optimizely

• Partner issue resolution linked to digital experience testing
  When trading partners report portal or transaction issues in OpenText Active Community - Trading Grid, case details can be pushed to Optimizely to correlate problems with recent A/B tests or personalization changes. This helps digital and operations teams quickly identify whether a new experiment is affecting partner login, order submission, or document access flows.
• Partner portal content updates driven by community feedback
  Feedback, questions, and recurring support topics from Trading Grid communities can be sent to Optimizely to inform content optimization on partner-facing pages. Teams can use this input to test revised instructions, onboarding content, or navigation paths that reduce partner confusion and improve task completion rates.
• Personalized partner communications based on community activity
  Activity in OpenText Active Community - Trading Grid, such as issue severity, partner segment, or participation in specific discussion groups, can feed Optimizely personalization rules. This enables targeted messaging on partner portals, such as showing relevant announcements, training content, or escalation guidance to the right trading partners.
• Experimenting with partner onboarding journeys
  OpenText Active Community - Trading Grid can provide operational insights into onboarding bottlenecks, while Optimizely runs experiments on onboarding pages, document submission steps, and help content. The integration supports continuous improvement of partner activation workflows by testing which journey changes reduce setup time and support requests.
• Document and policy change communication optimization
  When new trading policies, compliance documents, or process updates are shared in OpenText Active Community - Trading Grid, Optimizely can be used to test how those updates are presented in the partner experience. Teams can compare different layouts, calls to action, or content structures to improve document adoption and reduce missed acknowledgements.
• Segmented partner engagement campaigns
  Partner segmentation data from Trading Grid, such as region, product line, or transaction volume, can be synchronized to Optimizely for targeted experimentation. Marketing, partner success, and operations teams can test different portal banners, announcements, or resource recommendations for each segment to improve engagement and responsiveness.
• Closed-loop optimization for partner self-service
  Usage patterns and unresolved topics from OpenText Active Community - Trading Grid can be sent to Optimizely analytics workflows to identify where self-service content is failing. Optimizely can then test alternative page structures, search prompts, or help widgets, creating a feedback loop that reduces partner support dependency and improves portal efficiency.