Include or exclude dimension values in Data Views

Transcript

Hey, everybody. It’s Doug. In this video, I want to show you a cool feature when you are configuring components while setting up a Data View in Customer Journey Analytics. And so, we’re going to talk about configuring dimensions, so down here, and over on the right-hand side rail here, this INCLUDE EXCLUDE VALUES. And so let me go ahead and click on that. And this is a really cool configuration feature that is not available in Adobe Analytics, but we’re happy to include it in Customer Journey Analytics. And the concept is somewhat simple. It’s really just a filter of your data. But the fact that you can set it up during the configuration gives you some really cool use cases. And so, I’m going to go over a few of these. However, first, I do want you to notice that, you know, when you turn this on, Set include/exclude values, by default, it will be off. But when you turn that on, and you get these other things to appear, you’ll be able to add as many rules as you want. As you can see there, I can add rules and I can take them away, et cetera. But you’ll see here the Match is if all criteria are met or if any criteria are met, so basically a boolean AND and a boolean OR here for when you have multiple criteria. Doesn’t really matter if you have just one. It doesn’t matter which one of those you select, of course. But you can see here that I’ve got this Page Title selected. And so, really, just these page names or these page titles, which ones do I want to include or exclude in my Data View? So if I go over here, I can see the different criteria available: Contains a phrase or a term or all terms, you know. It’s got all these different items here. It can equal it exactly. It can does not equal, starts with, ends with, you know. So, this is basically your includes, like contains and things like that, and your excludes, which is like does not contain any term or phrase, et cetera. Now, before I go into some use cases, I do want to show you because you might be wondering yourself how does this differ from the filter in a freeform table? So let me jump over to a project, okay? And I have a freeform table here with page titles, and you’ve got this filter right here. So, if I click on Page Title, and if I go into advanced, it will look pretty familiar: if all criteria are met, if any criteria are met. Once again, AND and OR. And as I drop this down, contains a phrase, it’s really those same things. And so, what’s the difference? Why can’t I just do it here instead of doing it in the Data View? Well, you can, but keep a couple things in mind. First of all, if you do it in your table, it’s really only going to affect that table. And so that’s, of course, very helpful when you are actually in your project and you need to edit what is in your table and, you know, leave only, let’s say, you know, only put category pages in here or something like that. But if you want to be able to set that up ahead of time for your end users, see, what we’re talking about, if I go back over to the Data View, is setting up the Data View ahead of time so that your analysts have things available to them. So let me give a couple use cases where that can maybe be helpful. Let’s say I had a bunch of different error pages, or pages that would come up, you know, if different errors happen on the site, I could duplicate this, right? So I could say Page Title, duplicate that. So maybe I’ll just go ahead and do that. I scroll to the top, and I got Page Title 2, and I could come into the COMPONENT SETTINGS and say Error Pages. It’d be funny if I had an error in the spelling. Okay, Error Pages. And then when I go down to include or exclude, it has to contain the phrase, you know, Error:, or something like that. And, you know, that’s, of course, if all of my page titles that are error pages start with that. But you see it gave me a completely different component. So, when your analysts are going through the components, they can have very quick access to this subset of pages that are just error pages, so it makes it very easy for them. And that, of course, goes out beyond pages, right? So if you have any of your dimensions that you would want to take a subset and make it its own dimension to be easily used, you know, maybe it’s clientid and maybe you duplicate that, and you have certain clients that are in a certain region. So, you have something like southwest clientids or something like that, right? So it would make a completely different dimension that would be easy for your end users to grab and put into a report. And don’t forget that it’s not only for our freeform table but it would apply to other visualizations like the flow or fallout visualizations as well. Okay, here’s another use case. Let me jump back over to the project. Let’s say that I notice that I’ve got some pages in here that weren’t supposed to show up. Maybe they were doing some testing or something like that, and it’s, you know, they’re pages that shouldn’t show up in here, or items, again, any kind of items that shouldn’t show up. And I’m going to pretend for a minute that these prd pages are not supposed to be in there, and I’ve got a bunch of 'em. I kind of go out through here, and I’m like, “Oh no, those prd pages are showing up in here, clogging up my really cool report. I don’t want them in there.” So in this case I don’t really need a new dimension to be a subset of my pages. I just kind of need to clean up my pages. So, I’ll go back to the Data View, and I make sure I have my Page Title selected right there, and then I can say in my Criteria, Does not contain prd.

And in fact, if I don’t know if there might be uppercase or lowercase prd, I can also deselect that one so it’s not case sensitive. And that way, you can take out all of the prd pages from the overall page title component. And, once again, this would apply to any of your dimensions. And so if you need to kind of, you know, remove items out of a dimension that shouldn’t be in there when your analysts are going into the data, or, again, the first use case where you want to make some new components that might be a subset of a larger one, then that’s very helpful too. Anyway, I hope that gives you an idea of some of the great things you can do with this include/exclude feature in Customer Journey Analytics. Good luck. - -