Adobe Experience Platform

Dataset

Dataset in AEP

A dataset is the container where AEP stores records conforming to an XDM schema. It can receive batch or streaming data and feed downstream services.

When it applies: It appears when separating sources, retention cycles, permissions, and operating uses. Not every ingestion needs the same dataset or should feed Profile.
What it is confused with: A dataset does not define fields by itself or resolve identities. It is also not a profile: it stores records interpreted by other services.
Architecture consequence: Dataset boundaries affect traceability, deletion, monitoring, and Profile load. Design them around contracts and lifecycles, not only connectors.

Related concepts

Data governance reaches analysis too
What data usage labels do in Customer Journey Analytics, what enabled policies block, and what happens to data views and exports.
Fix the data or fix the report?
A misclassified channel can be fixed at source, during ingestion or in CJA. Compare who receives the correction and what happens to historical data.
The purchase is in AEP. Where does it go missing in CJA?
Trace a purchase missing from CJA through the dataset, connection, historical import, data view and filters before loading the data again.