Home | Connectors | OpenText Decision Service | OpenText Decision Service - Adobe Experience Manager Sites Integration and Automation

OpenText Decision Service - Adobe Experience Manager Sites Integration and Automation

Integrate OpenText Decision Service Business Transaction Management and Adobe Experience Manager Sites Artificial intelligence (AI) apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between OpenText Decision Service and Adobe Experience Manager Sites

1. Personalized content eligibility and offer selection

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service ? Adobe Experience Manager Sites

AEM Sites captures visitor attributes such as account type, region, industry, or campaign source and sends them to OpenText Decision Service to determine which content variant, banner, or offer the visitor is eligible to see. The decision service applies centralized business rules, then returns the approved content choice back to AEM for rendering.

Business value: Marketing teams can change eligibility rules without code changes, while digital teams maintain consistent personalization across web pages and landing pages.

2. Dynamic lead routing from web forms

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service

When a prospect submits a form on an AEM Sites page, the submission is sent to OpenText Decision Service to determine the correct next action, such as assigning the lead to sales, routing to a partner, or sending to a nurture journey. The decision can use rules based on geography, product interest, company size, or compliance constraints.

Business value: Improves lead response times, reduces manual triage, and ensures leads are routed according to current business policies.

3. Content governance based on customer or account rules

Data flow: OpenText Decision Service ? Adobe Experience Manager Sites

OpenText Decision Service evaluates whether a user or account is allowed to access specific content, such as regulated product information, pricing pages, or region-specific documentation. AEM Sites uses the decision response to show, hide, or restrict access to pages and assets.

Business value: Supports compliance, reduces the risk of publishing restricted content to the wrong audience, and centralizes access rules outside the CMS.

4. Campaign content selection by business segment

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service ? Adobe Experience Manager Sites

AEM Sites sends campaign context such as page type, visitor segment, or product category to OpenText Decision Service. The service returns the best content package, call to action, or message variant based on business rules for each segment. AEM then assembles the page dynamically.

Business value: Enables faster campaign execution, more precise targeting, and consistent message governance across multiple digital properties.

5. Approval-driven publishing decisions

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service

Before a page, landing page, or content update is published in AEM Sites, the publishing request is evaluated by OpenText Decision Service against approval rules such as legal review status, product launch readiness, market authorization, or expiration dates. The decision service returns approve, hold, or reject outcomes.

Business value: Reduces publishing errors, enforces governance, and helps marketing and compliance teams work from the same rule set.

6. Regional content and pricing rule enforcement

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service ? Adobe Experience Manager Sites

AEM Sites sends visitor location, language, and account context to OpenText Decision Service to determine which regional content, pricing disclaimer, or product message should be displayed. The decision engine applies rules for country-specific regulations, tax disclosures, or market-specific promotions.

Business value: Ensures customers see the correct localized experience while reducing the operational burden of maintaining separate rule logic in the CMS.

7. Case or service escalation from digital experiences

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service

When a customer uses a support page, product selector, or self-service form in AEM Sites, the interaction is sent to OpenText Decision Service to determine whether the issue should be handled through self-service, routed to a service team, or escalated to a case management process. Rules can consider urgency, product tier, or customer value.

Business value: Improves customer service routing, reduces unnecessary escalations, and aligns digital experiences with operational policies.

8. A/B test decisioning with business rule control

Data flow: Adobe Experience Manager Sites ? OpenText Decision Service ? Adobe Experience Manager Sites

AEM Sites can send visitor or session data to OpenText Decision Service to determine which approved test variant should be shown. Unlike purely statistical testing, the decision service can enforce business constraints such as excluding certain customer groups, limiting exposure by region, or prioritizing regulated content.

Business value: Gives marketing teams controlled experimentation while protecting against rule violations and inconsistent audience treatment.

How to integrate and automate OpenText Decision Service with Adobe Experience Manager Sites using OneTeg?