As a long-time user of Adobe Analytics, I would like to be able to fully analyze my user's behavior within CJA. CJA data views can consist of one data set or several data sets, but as I understand it the concept a 'web visit' is being expanded and re-labeled a 'session' within CJA. It seems obvious that if the data set has a 'time series' component, then the concept of 'sequencing' applies.
As such, I propose that we add, at the AEP identity level, the ability for AEP to automatically add in both an 'Event Hit Depth' and 'Session Number' dimension to be used in our CJA data views. For example, let's assume a PERSON went to a company's website (on day 1), bought something at the company's retail store (on day 2) and called the company's customer service hotline (on day 3).
Assuming all data is in AEP and all data sources are connected via that 'identify' feature of AEP, then AEP should be able to define the 'Session Number' based on all the known data in AEP and should be able to determine and correctly sequence all the 'event' data per the time series timestamp within a single ‘session’.
For example,
Web Data Set:
Day 1 - time stamp 1 - user on the website home page --- AEP should be able to set 'Session Number' dimension = 1 (based on all data in known AEP) & should be able to set ‘Event Hit Depth’ dimension = 1 (based on all the event data for that session)
Day 1 - time stamp 2 - user on website product page --- AEP should be able to set 'Session Number dimension = 1 & Event Hit Depth dimension = 2
then
Retail Data Set
Day 2 - time stamp 3 - user's retail POS transaction --- AEP should be able to set 'Session Number' dimension = 2 & Event Hit Depth dimension = 1
then
Call Center Data Set
Day 3 - time stamp 4 - user's call center data -- AEP should be able to set 'Session Number' dimension = 3 & Event Hit Depth dimension = 1
It's all about establishing a 'session start time' and then classifying sessions based on the sequence of those timestamps and similarly within a data set's 'session' using the 'event time stamp' to classify the 'Event Hit Depth' based on the sequence of those time stamps, which I suspect can only be done at the ‘Identity’ level, after all the data gets ingested and gets ‘processed’.
Being able to sequence user's behavior across data sets ONLY within the 'flow diagram' visual simply isn't good enough; not for our Enablement Teams, not for our QA Teams, and definitely not good enough for our Analysis & Insights teams.