Adobe RT-CDP Business Practitioner Pro key terms

A unified, continuously updated record assembled from many source systems that merges identity-linked data into a single view of each customer for segmentation and activation.

A stored map of relationships between identifiers, showing which email, device, loyalty number, or CRM ID belong to the same person so records can be stitched together.

A labeled category that defines what a given identifier represents, such as Email, ECID, or a custom CRM ID, and controls how that value is matched across datasets.

The single identifier chosen to represent a profile when multiple identities are linked; it anchors the merged record and is used as the profile key.

The process of linking identifiers from separate datasets into one graph so events and attributes collected under different IDs resolve to a single profile.

A declarative data model describing the structure, fields, and data types of a dataset, built from reusable classes and field groups so ingested data is standardized.

The base component of a schema that defines the core behavior of the data it describes, such as a profile record class or an experience event class.

A reusable bundle of schema fields that can be added to multiple schemas, encouraging consistent definitions for concepts like consent, demographics, or commerce details.

A time-stamped record of an action or observation tied to an identity, such as a page view or purchase, typically modeled with an event class schema.

A container that holds ingested data conforming to a single schema, and the unit to which dataflows write and from which profiles and audiences draw data.

A configured pipeline that moves data from a source into a dataset, tracking run history, status, and any partial or failed batches along the way.

A prebuilt integration that pulls or receives data from an external system such as cloud storage, a CRM, or an analytics platform into the platform.

Loading data in scheduled or on-demand files rather than continuously, where each upload is processed as a discrete batch and evaluated against the schema.

Continuously receiving individual records or small payloads through an endpoint or connector so data becomes available for profile and segmentation with minimal delay.

A configuration that determines how data from multiple datasets is combined when building a profile, including which datasets take precedence and how timestamps are resolved.

The ordering within a merge policy that decides which dataset's attribute values win when conflicting values arrive for the same profile field.

A saved rule set that describes which profiles qualify for an audience, expressed through attributes, events, or logical combinations evaluated against profile data.

A group of profiles that meet a segment definition's criteria, which can be evaluated on a schedule or in real time and then sent to destinations.

Evaluating audience membership as new data arrives so profiles enter or exit a segment within moments, rather than waiting for a scheduled batch run.

Evaluating audience membership on a recurring schedule against the full profile store, producing updated segment membership at defined intervals.

Evaluating segment rules at the point of experience delivery, such as on a web page, using locally available data for immediate personalization decisions.

A configured connection to an external system, such as an ad platform or marketing tool, where audiences and profile attributes are exported for use.

The process of sending audience membership and associated profile attributes to a destination so the receiving system can target or suppress those individuals.

A dataflow that carries a selected audience to a specific destination, with its own schedule, identity mapping, and run history for monitoring.

Configuring which profile identifiers and attributes are exported to a destination, and how they correspond to the fields the receiving platform expects.

Tags applied to schemas and fields that classify data sensitivity and contractual restrictions, which policies then use to control where data may flow.

A rule that combines a governance label with a permitted or restricted action, determining whether data with that label can be used for a given purpose.

Automatic checking of usage policies at points like audience creation or destination activation, blocking or warning when data would be used against its labels.

A recorded customer preference about data collection and use, such as opt-in for marketing, stored as profile attributes and honored during activation.

The repository where ingested datasets are stored in their schema-conforming form, queryable for analysis independently of whether they feed the profile.

A dataset whose schema and configuration allow its data to be used to build unified profiles, as opposed to being stored only for query and analysis.

A partial record contributed by one dataset for one identity; fragments are joined by the identity graph and merge policy to form the unified profile.

The final assembled customer record after fragments are combined, showing merged attributes, identities, and audience memberships for a single person.

The interface used to search for and inspect an individual profile, including its attributes, linked identities, events, and current audience memberships.

An isolated partition of the platform containing its own schemas, datasets, profiles, and destinations, used to separate environments or teams.

A permission system assigning users to roles that grant specific capabilities and access to particular sandboxes and data resources.

Practices for keeping profile data accurate and current, including deduplication, expiry of stale records, and correction of identity or attribute errors.

The recorded outcome of an ingestion or activation attempt, showing success, partial success, or failure along with error details used for troubleshooting.