AEP Datasets don't merge in CJA

Question

Hi Team,

We have one Dataset in AEP ‘Webevent ” which doesn’t have any Primary Identifier and data is pushed using Identitymap.

Another Dataset “Online Transaction” has the hashedEmail as the Primary Identifier

There is another dataset “Customer Profile”, This dataset has hashedEmail as the Primary Identifier .This dataset is not merging with “Webevent” and Online Transaction”dataset in CJA dataview.

We can see the fields of “Webevent” and Online Transaction”datasets are merging in CJA and showing up as one dimension however ““Customer Profile” fields are not merging with Webevent” and Online Transaction”datasets

When I see field I mean , lets say “userId” field is present in above all 3 datasets and have same schema field path in all 3 datasets.
userId from “Webevent” and Online Transaction”datasets are merging in CJA dataview and we can see it in CJA also. It is showing a single dimesion but dataset source is both "Webevent" and "Online Transaction"
However a new component 69459540021cba3a1255c8e5.userId is getting added in CJA dataview when I drag the field from "Customer Profile" and we can see it as separate component in CJA also .

Is there anything someone can advise here ?
Our expectation is userId from all 3 datasets should have been merged into single dimension.

Vinay_Chauhan · Answer

This is expected behavior in CJA and is driven by dataset type, not schema alignment.

In CJA, fields from event datasets (Webevent and Online Transaction) can merge into a single dimension when they share the same identity and are resolved at event time. However, profile or lookup datasets like Customer Profile do not merge their fields with event datasets, even if the field name and schema path are identical.

Customer Profile attributes are treated as lookup components and therefore appear as separate, dataset-qualified dimensions in CJA. They enrich events but do not participate in field-level merging.

If a single merged dimension is required, the field must be present on the event datasets themselves or joined via lookup logic rather than relying on profile datasets.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded