Skip to main content


DX Engine An API-first Experience Engine that provides the right content the right customer at the right time, in every context.

DX Graph The Graph data store that houses entities along with their relationships

Experience API The API interface to the DX Engine that takes in the user's context as an input and responds with relevant content assembled from multiple backend content repositories in real-time.

Customer Identity Graph Conscia has the ability to take customer data from multiple back-end applications such as CRMs, online user database, behavioural data, etc and create an identity graph that can be shared across your martech stack.

Content Graph Conscia can sync content from one or more back-end repositories and create a centralized graph of all content. Conscia also provides tools to non-technical users to enrich, classify, validate, relate and distribute this content to destination platforms.

Headless Experience Management In traditional WebCMSes, content and experience are closely tied together. Headless CMSes keep content and presentation logic neatly separated. This, however, can create a divide between marketing and digital teams as it is difficult for marketing and product teams to visualize what the content will look like on a specific touchpoint or surface. Conscia creates a bridge between IT and Business by providing a headless way of managing experiences, empowering Marketing to control what the user should see while providing the much required guardrails that IT is comfortable with.

Experience Studio A GUI for non-technical users that provides a semantic view of all data loaded into Conscia along with tools to enrich data and power experiences.

Intel An AI and Analytics Engine that holds large amounts of data and provides advanced analytics and machine learning.

Data Collections A set of data or content records belonging to the same logical entity. For example, you may have a collection of customers, products, promotions, vendors, etc.

Master This is the golden record of a given entity created by stitching data from multiple sources. For example, Customer data may come from CRM, Surveys, Online Form Submissions, ESPs, Social Media profiles, etc. When you stitch this data together to create a single customer profile, the result is a master record.

Experience Since Conscia is a headless platform, an experience may refer to a page, a mobile application screen, an email template, or even a chatbot interface.

Component A renderable or logical component of the Experience is referred to as an Experience Component. An example of a renderable component is the hero banner on a home page, whereas a logical component may govern the layout of the overall page experience.

Experience Rules The DX Engine exposes an interface for business users to create a set of rules that determine what content should be displayed to what user in what context.

Taxonomy Taxonomies are one of the most powerful features of the DX Graph. It is exactly what the name suggests i.e a classification hierarchy with logical criteria set at every node that defines how a target data set should be mapped to it. For instance, in the ecommerce use case, product classification can be modelled as a taxonomy and you can specify the conditions a product must meet for it to belong to this product category.

Source Collections Source Data is the data you sync into Conscia to be managed and enriched.

Master Collections Suppose you have movie, actor and theater data as your source collections. You may create a Master colection of Movie records by connecting the underlying source collections such that each movie record has the list theaters playing the movie, the list of actors, and number of number of actors.