top of page

See DXO in Action!

Here, you will find everything you need to understand how Conscia's DXO works.

DX Engine

Zero Code API Orchestration Engine

The DX Engine can connect to any backend via a Universal API Connector, chain API calls, stitch and transform data and execute business logic.   Popular Use Cases: Omnichannel Personalization and a centralized Backend-for- Frontend for all channels.

DX Graph

An API First Data Layer

Every large enterprise organization is struggling with a mix of home-grown, legacy and modern data sources that must be integrated to create a unified experience.  The DX Graph creates a persistent, API first, data layer on top of your existing data sources and democratizes the ability to transform, load, discover, relate, validate, enrich, and govern data in a centralized, self-service user interface.

Omnichannel Personalization

with any CMS or DAM

We've created recipes that showcase how Conscia can connect to any headless CMS, DAM or Commerce Engine to offer omnichannel personalization as a service to our customers.   This includes Contentful, Contentstack,, Storyblok, AgilityCMS, Cloudinary, and many others.

DXO Recipes

See how Conscia's DXO addresses some of the most common  orchestration use cases.

Orchestration Recipe

Stitching Data from Multiple Data Sources

In this recipe, we will show you how to use the DX Engine to stitch data from multiple sources. We will use GitHub Gists to store different parts of a product detail page. We will then use the DX Engine to fetch the data from the Gists and stitch it together into a single JSON object.

Orchestration Recipe

Merge Two Data Sources into a Single Data Model

In this recipe we will merge content items from the CMS with product records from a commerce engine in order to populate product pages, whether a Product Detail Page (PDP), Product Listing Page (PLP), landing page, or anywhere products are featured with extended information. 

Orchestration Recipe

Handling Recursion and Nesting Hierarchies

Many third-party APIs provide access to hierarchical data one level at a time. This scenario is common in generating website navigation elements or similar hierarchical structures when the API provider does not offer a comprehensive hierarchy endpoint.  Where an API does not offer a direct way to retrieve an entire hierarchy, Conscia enables the implementation of recursive logic through the use of Sub Components in the DX Engine. 

Orchestration Recipe

Checkout Orchestration

Before you convert a Commercetools cart to an order, you must specify a shipping address. Logically, you must add line items (produts and quantities) to the cart. You can implement a Conscia Orchestration Component based on this recipe to implement both of these functions, or any function that updates a Commercetools cart.

Orchestration Recipe

Logging with Datadog

Observability and monitoring is an essential part of any enterprise tech stack. Most of our customers use one of the enterprise monitoring and analytics tools such as Datadog and Dynatrace to collect, search, and analyze log data.  This recipe shows how the DX Engine can write logging messages to Datadog as an example.

Orchestration Recipe

Order Fulfillment with SMS Notifications

In the following recipe, we will walk through a flow where a merchant has marked an order fulfilled through their Order Management System (OMS). Conscia is listening for a webhook from the OMS, and marks the commerce order fulfilled and sends an SMS notification to the shopper letting them know their order is on the way. We will use Twilio and Elastic Path Commerce Cloud APIs as well as a Postman call to simulate a webhook event from an OMS.

bottom of page