The XDM Registry operationalizes Adobe’s Experience Data Model and other industry-standard schemas or customer-extended schemas. Working with a standard data model brings direct value to customers because they don’t have to label, transform, and match their fields for every individual operation. The XDM Registry also gives an overview of available vendor extensions for the various standard schemas and industry-specific use cases and verticalized solutions. A customer can create their own unique data model (Customer Data Model) according to their business needs, either by creating their own schemas or by extending the available standard schemas already available in the XDM Registry.
The central Catalog Service tracks and organizes metadata for the data stored in Adobe Experience Platform. As such, it contains references to all available datasets, connections to streaming sources, connectors to external systems, and the states of all datasets in the platform. This central service updates the state of datasets and new batches of data as they come in. One of the first operations is to create a new dataset, based on an XDM Schema, before using the Ingestion Service to bring the actual data into the platform. The catalog service also takes care of the data lineage.
Using the Catalog Service API, create a new dataset and query Experience Platform to discover what data is in the platform, what state it’s in, and how much data has been processed. Then, get its XDM schema, find out what systems or processes have acted on it, understand the state of individual datasets, and more.
Data Ingestion services
Adobe Experience Platform provides two main modes of ingesting data: batch and streaming. Batch ingestion lets you import data in bulk, from any number of datasources and through any connection you define. You can import batch data by either uploading it through the API, or through available out-of-the-box connectors in Adobe Experience Platform. The ingestion service accepts Apache Parquet or CSV files. During ingestion, the data is validated against the schema of the target dataset. Multiple batches can be added to a single dataset.
Streaming data can be picked up from the data pipeline, which can be populated by Adobe Solutions or externally through the Data Collection Service API.
Data Usage Labeling & Enforcement
Adobe Experience Platform not only allows you to aggregate all data from associated Adobe Experience Cloud solutions, but allows you to ingest data from any other source, including commercial databases, third-party solutions, and more. Managing this data requires data governance, such as cataloging the data by its source and type, as well as tracking and enforcing any restrictions on its use.
The Data Usage Labeling & Enforcement (DULE) Framework, built into Experience Platform, enables data stewards to analyze internal Adobe Experience Cloud data and data coming from any external sources at the connection, dataset, or individual field level and apply labels to it that allow the DULE Policy Service to calculate whether any given data usage request is compliant with the laws, contractual restrictions, or corporate policies governing its use. This activates the data for use by marketers, who, through the seamless integration of DULE with Adobe’s marketing solutions, can get immediate feedback on any data usage request, comply with policy, and customize their marketing actions to use the data accordingly. The DULE Framework is also accessible through APIs that enable developers to apply DULE labels programmatically and query the DULE Policy Service for data governance decisions, thereby enabling third-party developers to integrate their applications with DULE governance.
The platform is an open system. Datasets available in the platform can be read and exported. The Data Access Service provides a single point of access to the available datasets. The Data Access Service, in turn, depends on the Catalog Service to discover data sets and retrieve them from the Experience Platform’s data store. Using the Data Access API in conjunction with the Catalog Service API, developers can access data on any level—connection, dataset, or individual records—to extract it, transform it, or store it in a third-party system for further use, reference, and analysis.
Unified Profile Service
The Unified Profile Service is the central service to activate the audiences that are developed within Adobe Experience Platform. As multiple datasets come into the platform and are transformed, eventually they will be consumed by the Profile service. Based on the Customer Data Model (consisting of schemas in XDM and third-party schemas), the service creates an aggregated real-time view of the consumer and allows you to inspect individual consumer profile attributes. Using segment definitions, the profile can return an audience that meets the segment criteria by stitching together the multiple data points coming from multiple datasets. The Unified Profile Service also supports individual point lookups to understand the preferences of a consumer and deliver the right experience. The Unified Profile Service will be consumed by Adobe Solutions, but is also available for integration into third-party activation solutions.