Adobe Customer Journey Analytics Developer Expert flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

CJA connection

A configuration object that maps one or more AEP datasets into a single data source for CJA, defining the person identifier and contributing event and lookup data.

Event dataset role

A dataset whose rows become fact records in CJA, contributing to event counts and metrics. Lookup datasets enrich dimensions but do not add rows.

Lookup dataset join

A dataset joined to event data on a shared key to add dimension attributes. Failed joins yield no-value rows rather than dropping events.

Backfill window

The period during which late-arriving or corrected records are re-ingested into a connection. Data older than the window is not automatically refreshed.

Person ID namespace

The identity namespace (default ECID) used by a connection to link events into a person timeline. It must be consistent across all datasets in the connection.

Dataset retention dependency

CJA can only query rows still retained in the AEP data lake. Dataset retention policy, not CJA, governs how long data remains queryable.

Data view purpose

A container that defines dimensions, metrics, segments, and calculated metrics over a connection. One connection can back multiple data views.

Component visibility toggle

A data view setting that hides a field from the component rail without deleting it. Hidden components remain available to existing projects.

Metric attribution setting

A per-metric data view setting controlling how credit is allocated across touchpoints. Changing it affects all reports using that metric.

Dimension persistence

A data view setting that determines how a dimension value carries forward across events or visits, such as last touch or first touch.

Session definition

A data view setting defining session timeout and background event handling, which governs visit-based metrics like visits and bounces.

Component ID stability

The internal identifier, not the display name, links a component to saved projects. Renaming a component does not break references.

Stitching

The process of combining events from multiple datasets into one person timeline using a shared identifier, enabling cross-device and cross-channel reporting.

Field-based stitching

A stitching method that links events using a high-confidence identifier such as an authenticated user ID present in the datasets.

Graph-based stitching

A stitching method that uses the AEP identity graph to resolve identities across datasets, linking events through shared identity namespaces.

Stitching lookback

The time window within which events are stitched. Older events require a re-stitch operation, which is costly and time-limited.

People versus visits

People counts distinct stitched identities, while visits counts sessions. Visits can exceed people because one person may have multiple sessions.

Derived field

A rule-based dimension computed at query time, such as marketing channel. Changing the rule reclassifies historical data on the next query.

Identity mapping consistency

Datasets must map the same identity namespace consistently. An ECID in one dataset and a CRM ID in another without a linking field will not stitch.

Freeform row limit

The maximum rows displayed per breakdown in a freeform table, configurable in table settings. Higher limits increase query time and load.

Panel versus table segment

A panel-level segment filters all visualizations in the panel. A table-level segment filters only that table's data.

Calculated metric nesting

Calculated metrics may reference other calculated metrics, but circular references are rejected at save time by the platform.

Fallout visualization

A Workspace visualization showing drop-off across ordered touchpoints. It supports up to ten touchpoints per step in a defined path.

Anomaly detection baseline

Anomaly detection compares observed values to an expected range derived from the metric's attribution model and historical data.

Project sharing permissions

Workspace project access is separate from data view permissions. A user needs both to view a shared project and its underlying data.

Governance label propagation

Data governance labels applied in AEP propagate to CJA and can block a field from use as a dimension or metric.

Privacy request handling

Access and delete requests are processed at the AEP dataset level. CJA reflects deletions after lake records are removed.

Consent filtering

CJA does not automatically exclude opted-out users. Consent and opt-out flags must be captured in the schema and filtered via segments.

Row-level data filter

A data view control restricting which rows a user can see. It is enforced at query time and is not visible to the user.

Missing dimension value

Usually caused by a schema mapping gap or a failed lookup join, not a data view configuration error. Check dataset mapping first.

Non-additive metric

A metric such as people or visits whose breakdown rows do not sum to the total, because distinct counting or attribution prevents simple addition.

Audit trail

AEP records dataset and connection changes in audit logs. CJA component changes appear in the Admin console audit trail.