CJA lookups for lookup and profile data

With CJA Lookups on lookup and profile data, users can utilize deeper relationships between data elements, such as person to account in B2B use cases. In this video, we cover how to add lookup data to lookup and profile datasets and how to plan out and map your key fields. Note, if there is a one to many relationship between the key and the lookup value, the most recent value will be used.

For detailed documentation, visit Dataset types and Add account-level data as a lookup dataset.

Transcript

Hello, I’m Erica Angle, principal product manager for Adobe Analytics. Today I’m going to showcase customer journey analytics, support for lookup data and lookup and profile data sets. As we add more types of data to CGA, the data relationships become more complex and require more options to define the relationships between different data set elements so that reporting and analysis work properly.

In this example, I work for a company with a large B2B marketing team. They would like to understand how people on certain marketing lists, or that are part of specific opportunities, are consuming digital content. I’ve created a group of five data sets in Adobe Experience Platform to structure my B2B marketing data. Let’s take a quick look. I’m going to select data assets under Data management and filter for my data sets.

So you can see I’ve structured each data set to have a specific schema and made sure to understand the relationships between each data set. So let’s take a look at those relationships. I made a little diagram to help me visualize how these relationships should work together. So I’ve got my event data and my profile data. These are standard CK elements. And then coming off of my event data and want to create a lookup that ties together the event person key to the marketing list member person key. And then the marketing list member has both a person key and a list key in it, which means I can do a secondary lookup to bring in the marketing list information tied to each marketing list ID. So we’ve got a two tier lookup off of events, and then further off of the profile data, I wanted to bring in the opportunities for each person. And so I’m tying together a person key in the profile to the person key and the opportunity person relationship table.

Let’s take that now into create and build a connection. For the connections. I’ve already built the connection. So let’s take a look at how I did that. I can come into edit Connections and I’ll see those five data sets that we were looking at in the diagram. We’ve got our activity and person data. And then let’s see how we would tie in the marketing list member to that event. Data. When you bring in that lookup data for event the same way that it has in CGA, or you’re going to define your key element within this data set, which is marketing list member person key. And then you’re going to match that key to your event data set. So if I bring this in here and do a little search, you can see the person key appears in multiple data sets. But for this relationship to work properly we want to use the source key from the event data set.

And then that establishes that relationship going down to a lookup on a lookup. We’re going to bring in this marketing list information. In this case the lookup key is a marketing list key which is found in both this data set which is a marketing list data set. Here, and the matching key which is found in the marketing list member data set. So I have selected that here and we can apply that relationship. So now I’ve built a lookup and a lookup on a look up against my event data to bring in the relationship between person and opportunity person. When I bring that opportunity person data in, when you use the key of the person key source key from the opportunity person data set and match that against the person key source key that’s in the profile.

Just like that. Once all my relationships are set up, I can double check them. Utilizing the table within connections to see the relationship between the key and the matching key, and what the person ideas for the activity and person tables as well. Once the connection is all set up and looking good, we can let that data flow into data views and from there into workspace.

So I’ve built a relatively simple workspace here to showcase some of the relationships. So this is our event and profile data. And the relationship between that. So you can see there’s people’s names and interesting moments are events that occurred for each person. Then looking at the lookup on profile. So this is the opportunity data brought in against profile. There’s opportunities bundle and Bogo and a person role that was brought in from the opportunity person table primary and support. So that’s also that relationship is looking good.

Then moving on to the lookup on the event data. Got a marketing list member and a marketing list name. So a person name and a marketing list name. And finally the lookup on the lookup which brings in that additional marketing list information. I’ve got a description of each marketing list and tying that all the way back to the person associated with each marketing list. Now I’m ready to bring together a new report for my marketing team that showcases how people in certain marketing lists are utilizing digital content.

recommendation-more-help
a05d7212-fdba-4b70-a337-d5897f329c68