The Digital Experience Orchestration Engine (DX Engine) orchestrates data and content from any backend system based on business logic configured and executed by its embedded rules engine in real-time.
Here are the key capabilities and features of the DX Engine:
Orchestration as a Service
Conscia is completely agnostic of your frontend and sits in the cloud as an API-accessible orchestration engine, deployed on the Edge to optimize query performance and reduce latency. This means that you do not need to manage any infrastructure for the orchestration layer for your composable stack. Your frontend rendering layer, either Client Side Rendering or Server Side Rendering, can make a single API call to the DX Engine and receive all the data and content required to display an experience on any channel or touchpoint.
This also allows you to avoid writing glue code or custom business logic in your frontend layer. Writing glue code in your front end couples your backend to your front-end. This logic is not re-usable on other front-end frameworks and channels. Conscia abstracts the business logic from your frontend and makes it accessible from any client via the Experience API.
Zero-Code API Orchestration
Conscia achieves zero-code orchestration by providing a unified API layer that connects multiple backend systems, such as CMS, CRM, CDP, and DAM, without requiring any custom code or complex integrations. Conscia orchestrates data and content between systems and leverages real-time decisioning to intelligently connect the dots between various backend APIs.
Intuitive, Business User Control Over Experience Logic
The DX Engine comes with a native Decision/Rules Engine that is exposed to the business users via an intuitive UI where they can configure experience rules i.e who should see what content when and where. With this centralized UI, Conscia returns control back in the hands of business users to control personalization and A/B testing for all your channels and touch points, not just your website.
Maximize Your Investments in Your Existing Tech Stack
When your content and data is siloed in legacy backend systems such as ERPs, PIMs, CMSs, CRMs etc, Conscia creates an API-first, modernized Data Layer on top of these existing applications to power modern, composable experiences. In other words, Conscia accelerates the journey from legacy and monolithic systems to a composable architecture without having to decommission these systems.
Understand How Your Experiences Are Performing
Track behavioural signals as your customer interacts with your content and experiences and use powerful insights offered by Conscia to determine how best to optimize your customer experience for every customer.
Understand How Your Backends Are Performing
Since the DX Engine is sitting in the middle of your frontend and backend, it logs every call it receives from the client side as well as the response that is received from the various backends. These logs are available for further analysis. This log contains essential information about API performance, response failures, etc so that you can gain full visibility into the status of your entire composable stack.
Here is how Conscia fits into your overall Digital Experience Stack.
When the calling client to the DX Engine is for a UI-based application, it is important to understand that the DX Engine is Front-End Agnostic. Each Component delivers a JSON response. DX Engine components do not deliver any markup - the manner in which the front end renders itself is not a concern of the DX Engine. You can think of a DX Engine Component as a data source for a front-end visual components.
For instance, if you have a header banner visual Component on the frontend, the DX Engine Component is simply providing the data and content necessary to render that visual Component on the front end. A DX Engine Component connects to a backend API such as a headless CMS, a DAM or a Commerce Engine and sources data directly from that backend in real-time based on the experience logic configured by your IT/Marketing teams.