Adobe Real-Time CDP Developer Expert flashcards
Adobe Real-Time CDP Developer Expert · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- XDM schema class
- The base structure of a schema, such as XDM Individual Profile or XDM ExperienceEvent, that defines the core fields and determines which field groups can be added.
- Field group
- A reusable, versioned collection of schema fields that can be added to schemas sharing a compatible class, enabling consistent modeling across datasets.
- Dataset
- The ingestion and storage unit in Adobe Experience Platform; it references one schema and is the target for batch or streaming data and lifecycle controls.
- Streaming ingestion
- Near real-time data ingestion via the Streaming Ingestion API or Edge Network, where records are validated against the schema and written to a dataset.
- Batch ingestion
- Ingestion of files (JSON, Parquet, CSV) through the Data Ingestion API or sources connectors, processed as dataflow runs with per-batch success or failure reporting.
- Primary identity
- A schema field marked as identity and designated primary, required for Profile-enabled datasets so records can be stitched into profiles via the identity graph.
- Union schema
- An aggregated view of all fields across datasets sharing a class, used by Profile and segmentation to query attributes regardless of source dataset.
- Schema type immutability
- Field data types cannot be changed after data is ingested; a new field or dataset is required, so types must be validated before enabling ingestion.
- Identity namespace
- A declared identifier type such as ECID, Email, or CRM ID that labels identity fields and determines how the identity graph links records.
- Identity graph
- The service that links identities across namespaces into a single profile, creating edges from identityMap fields present on ingested records.
- Merge policy
- Rules that decide which attribute value wins when multiple source records conflict, using timestamp ordering, dataset precedence, or attribute-based selection.
- Profile fragment
- A single ingested record that contributes attributes to a profile; the profile is the union of fragments stitched together by identity graph edges.
- Default merge policy
- The timestamp-ordered merge policy applied when no schema or segment override is specified, where the most recently ingested attribute value wins.
- Profile lookup API
- An API that returns merged profile attributes and edge projections, showing the merge policy applied and the winning values for a profile.
- Sandbox identity isolation
- Identities are scoped per sandbox; the same namespace value in different sandboxes does not resolve to the same profile.
- Streaming segment
- A segment evaluated continuously as records are ingested, emitting near real-time qualification events to downstream streaming destinations.
- Batch segment
- A segment evaluated on a schedule against the Profile union schema, producing membership used by batch file exports to destinations.
- Segment qualification states
- The membership states realized (entered), exited (left), and existing, stored in the segmentMembership object on the profile.
- Activation mapping
- The configuration that maps XDM profile attributes and identity namespaces to destination fields, determining which identifiers and attributes are exported.
- Destination dataflow
- The configured pipeline that exports segment membership or profile data to a destination, run on a schedule or triggered by qualification events.
- Batch destination export
- Export of segment membership as files such as CSV or Parquet to cloud storage, typically on a schedule via a destination dataflow run.
- Streaming destination
- A destination that receives segment qualification events continuously in near real-time, pushing identifiers and attributes as profiles enter or exit segments.
- Segment criteria field requirement
- Segment criteria must reference fields present in the union schema; if a referenced field is missing, the segment evaluates as empty.
- Data usage labels
- Labels such as C1-C12, I1-I2, and S1-S2 applied to schema fields and datasets that policies use to restrict data use in segments and destinations.
- Consent policy
- A policy evaluated against the consent field group, such as collect.val and share.val, that controls whether data can be used at activation time.
- Privacy Service
- The service that processes access and delete requests by identity namespace and value, tracked by job ID and applied to datasets and Profile.
- Data lifecycle expiration
- A dataset setting that deletes records after a retention period; expiration jobs run on a schedule and are irreversible once executed.
- Policy enforcement point
- A point such as segmentation, destination activation, or dataset query where policies are evaluated and violations block the action with an error.
- Attribute-based access control
- Access control using labels and roles to restrict dataset and field visibility, including field-level labels that can hide PII from users.
- Audit logs
- Records of governance actions such as label changes, policy edits, and access, retained for compliance review and traceability.
- Privacy delete request
- A request submitted to Privacy Service with an identity namespace and value that removes matching data from datasets and Profile, subject to dataset type.
- Data usage policy
- A rule that combines data usage labels with marketing actions to determine whether a dataset or field may be used for a given purpose.