Expand my Community achievements bar.

Interested in becoming an Adobe Analytics Champion? Join us on May 15 at 9 am PT, and learn how to become a 2025 Adobe Champion.
SOLVED

Profile dataset components attribution (Costumer journey analytics CJA)

Avatar

Level 1

We are working on a client that has a profile dataset available in CJA. As part of our analysis tasks, we want to know the subscriptor statement (actived or canceled) at a given snapshot.

 

However, when we set the report, we are observing that when a profile dimension is used for a specific event, CJA returns multiple value if user has multiple values during along the time, acting as a list var. But when using the same dimension but on the event dataset, attribution is as we expected and only shows the last value known.

 

Data with profile dimension 

Person IDTimestampEvent typesuscription state (profile dataset)
A01/10/2024order upgradeactive
A01/10/2024order upgradecanceled
B01/10/2024order canceledactive
B01/10/2024order canceledcanceled

 

Data with event dimension

Person IDTimestampEvent typesuscription state (event dataset)
A01/10/2024order upgradeactive
B01/10/2024order canceledcanceled

 

Is this a expected behaviour or is it caused by a wrong implement?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @JavierMa6 ,

In CJA the profile datasets ideally work as lookups against the Person ID and like any lookup dataset these should return the most recent value of the lookup field in the Profile Dataset (Profile dataset is separate and unrelated to an AEP Real-Time Customer Profile).

In your example, the first table containing data from profile dataset seems to be be returning multiple  values for "subscription state" attribute which doesn't seem correct. I'd expect this table to return one row per Person ID with "subscription state" column showing the most recent value recorded in Profile Dataset for that Person ID.

I believe what you expect is correct and there seems to either incorrect implementation, some timing issue in data ingestion to CJA or some other CJA working concept that is causing it.

If you go through below links these also suggest that profile lookups should return only the most recent value for a given attributes,

A Guide to Understanding Adobe Customer Journey Analytics Lookup Datasets

How to Leverage Event, Lookup, and Profile Datasets in Adobe Customer Journey Analytics

Profile dataset from AEP into CJA

brian_au or bryan_skelton might be able to help you with this.

Cheers!

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @JavierMa6 ,

In CJA the profile datasets ideally work as lookups against the Person ID and like any lookup dataset these should return the most recent value of the lookup field in the Profile Dataset (Profile dataset is separate and unrelated to an AEP Real-Time Customer Profile).

In your example, the first table containing data from profile dataset seems to be be returning multiple  values for "subscription state" attribute which doesn't seem correct. I'd expect this table to return one row per Person ID with "subscription state" column showing the most recent value recorded in Profile Dataset for that Person ID.

I believe what you expect is correct and there seems to either incorrect implementation, some timing issue in data ingestion to CJA or some other CJA working concept that is causing it.

If you go through below links these also suggest that profile lookups should return only the most recent value for a given attributes,

A Guide to Understanding Adobe Customer Journey Analytics Lookup Datasets

How to Leverage Event, Lookup, and Profile Datasets in Adobe Customer Journey Analytics

Profile dataset from AEP into CJA

brian_au or bryan_skelton might be able to help you with this.

Cheers!

Avatar

Level 1

Hi,

 

Thanks for your answer.

 

I was wrong when I assumed suscription state was unique for each profile. Suscription is a dimension within an array so it is normal to have different values at a given timestamp.

 

regards