Customer Journey Analytics lets you build, manage, share, and apply powerful, focused audience filters to your reports. Filters let you identify subsets of persons, sessions or events based on characteristics or interactions. Filters are designed as codified audience insights that you can build for your specific needs, and then verify, edit, and share with other team members.
Filters can be based on:
See Create filters for the various options available to create filters. You then build, modify, and save the definition of a filter in the Filter builder. Alternatively, you can create quick filters using the Quick filter bulder. And you can also generate filters from visualizations in Workspace, for example using the Fallout visualization.
You use the Filters manager to manage filters.
Especially, as an administrator, the proper planning of filters improves the chances that the filters are used. Consider the following when planning filters:
Audience: Who will use your filters? Ensure you provide a good filter description so the audience understands:
What is this filter useful for?
When should I use this filter?
Scope: Which Filter container best represents the data you are after? Use the smallest container possible.
Components: Decide which components to include in the filter definition, and against which values the conditions should validate.
Process: Consider an approval process for your filter. There is no approval workflow in Customer Journey Analytics but you can still organize a process to determine whether you approve a filter or not.
Modularity: Define filters with modularity in mind. So, the users of your filters can easily stack filters to create powerful new filters.
You can create three types of filters:
Quick filters allow you to explore data easily within a given Workspace project, without the need of creating a filter in the Filter Builder. You define your filter within the Workspace interface directly. See Quick filters for more information.
Regular filters let you identify data (persons, sessions, events) based on one or more conditions. If more than one conditions, you use logical operators like And and Or to define the filter further. You can use containers to group conditions and build more complex filters. See Filter builder for more information.
You must have the Select package to create cross-channel sequential filters. Contact your administrator if you’re unsure what Customer Journey Analytics package you have.
Sequential filters let you identify data (persons, sessions, events) based on navigation (page views across your site, interactions with scenes in your mobile app, or using a menu on a set-top box). Sequential filters help you identify, for example, what a person likes and what a person avoids. You use the Then logical operator to define a sequential filter. See Sequential filters for more information.
Filters are based on a Person-, Session-, and Event-level hierarchy using a nested container model. The nested containers allow you to define conditions between and within the containers.
Person | ||
Session | ||
Event |
For Adobe Analytics users:
A filter sets conditions to filter persons, sessions or events based on conditions. For example, conditions to filter persons based on person characteristics and navigation traits. To further breakdown the data, you can filter on specific sessions, page view events, screen taps, menu choices on a set-top box, and more. But also filter on attributes that you have ingested from a CRM or loyalty system. The Filter builder provides a simple interface to build these subsets and apply conditions in nested, hierarchical Person, Session, or Event containers.
The container architecture employed in the Filter builder defines Person as the outermost container. The container contains overarching data specific for the person across sessions and events like page views, mobile application screens, or menu screens on a set-top box. A nested Session container lets you set rules to break down the person’s data based on sessions. A nested Event container lets you break down person information based on individual interactions. Each container lets you report across a person’s history, interactions broken down by sessions, or break down individual events.
The Person container includes every session and every event for the persons that qualify for the condition specified in the container. When you define a filter with a simple condition like Page Name equals Checkout
, then the Person container resolves to:
Checkout
.As the most broadly defined container, reports generated at the Person container level returns events and sessions for all persons that qualify for the filter. The Person container is the most susceptible to change based on defined date ranges.
Person containers can include values based on a person’s overall history:
The Session container lets you identify page interactions or mobile app interactions, campaigns, or conversions for a specific session. The Session container is the most commonly used container because it captures behaviors for the entire session once the rule is met. The Session container also lets you define which sessions you want to include or exclude in building and applying a filter. When you define a filter with a simple condition like Page Name equals Checkout
, then the Session container resolves to:
Checkout
is visited.The session container can help you answer the following questions:
Session containers include values based on events per session:
Data views in Customer Journey Analytics let you determine how long a session lasts, but also when a new session should be created. For example, you can define a new mobile app session based on every time a user launches your mobile app. See Session settings for more information.
The Event container defines which page, mobile application, or other type of events that you would like to include or exclude from a filter. It is the most narrow of the containers available to let you identify specific clicks, page view, taps on button in a mobile app where a condition is true. The Event container lets you view a single tracking code, or isolate behavior within a particular area of your mobile app. You may also want to pinpoint a specific value when an action occurs, such as the marketing channel when an order was placed. When you define a filter with a simple condition like Page Name equals Checkout
, then the Event container resolves to:
Checkout
.Event containers include value-based, single page breakdowns for:
Logic Group enables you to group conditions into a single sequential filter checkpoint. As part of the sequence, the logic defined in the container identified as Logic Group is evaluated after any prior sequential checkpoint and before any following sequential checkpoint. See Logic Group for more information.
When creating containers within other containers, you are actually creating a filter within a filter. The following logic is applied to nested containers:
When you nest a filter within a filter (for example, you drag a filter from the Components panel onto your filter definition), a container is created with a copy (not a reference) of the dragged filter definition.