This section describes configuring segmentation when using the ContextHub. If you are using the Client Context functionality, please see the relevant documentation for configuring segmentation for Client Context.
Segmentation is a key consideration when creating a campaign. See Managing Audiences for information on how segmentation works and key terms.
Depending on the information you have already collected about your site visitors and the goals you want to achieve, you will need to define the segments and strategies needed for your targeted content.
AEM allows you to easily personalize your users' experience. It also allows you to verify the results of your segment definitions.
The Audiences console is used to manage segments for ContextHub or Client Context as well as audiences for your Adobe Target account. This documentation covers managing segments for ContextHub. For Client Context segments and Adobe Target segments, please see the relevant documentation.
The Segment Editor allows you to easily modify a segment. To edit a segment, select a segment in the list of segments and click the Edit button.
Using the components browser you can add AND and OR containers to define the segment logic, then add additional components to compare properties and values or reference scripts and other segments to define the selection criteria.
The following components are available out-of-the-box and allow you to group comparisons and references together for boolean evaluation. They can be dragged from the components browser to the editor.
The following segment comparisons are available out-of-the-box to evaluate segment properties. They can be dragged from the components browser to the editor.
||Compares a property of a store to a defined value
|Property-Property||Compares one property of a store to another property
|Property-Segment Reference||Compares a property of a store to another referenced segment
|Property-Script Reference||Compares a property of a store to the results of a script
|Segment Reference-Script Reference||Compares a referenced segment to the results of a script
null < 30 // will return true
Therefore when creating a segment, you should select a data type whenever the types of compared values are known. For example:
When comparing the property profile/age, you already know that the compared type will be number, so even if profile/age is not set, a comparison profile/age less-than 30 will return false, as you would expect.
You can combine comparisons and references to scripts and other segments using the OR and AND containers (see Creating a New Segment) to define the exact scenario for selecting this segment.
When the entire statement evaluates to true then this segment has resolved. In the event of multiple segments being applicable, then the Boost factor is also used. See Creating a New Segment for details on the boost factor.
The segment editor does not check for any circular references. For example, segment A references another segment B, which in turn references segment A. You must ensure that your segments do not contain any circular refernces.
In the New ContextHub Segment, enter a title for the segment as well as a boost value if required and then tap or click Create.
Double-click on or tap the configure option of the new reference or segment to edit the specific parameters. In this example, we are testing for people in San Jose.
Always set a Data Type if possible to ensure that your comparisons are evaluated properly. See Comparisons for more information.
Add more components as required. You can formulate boolean expressions using the container components for AND and OR comparisons (see Using AND and Or Containers below). With the segment editor you can delete components not needed anymore, or drag them to new positions within the statement.
Using the AND and OR container components, you can construct complex segments in AEM. When doing this, it helps to be aware of a few basic points:
- The top level of the definition is always the AND container that is initially created. This cannot be changed, but does not have an effect on the rest of your segment definition.
- Ensure that the nesting of your container makes sense. The containers can be viewed as the brackets of your boolean expression.
The following example is used to select visitors who are considered in our prime age group:
Male and between the ages of 30 and 59
Female and between the ages of 30 and 59
You start by placing an OR container component within the default AND container. Within the OR container, you add two AND containers and within both of these you can add the property or reference components.
Once the segment has been defined, potential results can be tested with the help of the ContextHub.
- Preview a page
- Click the ContextHub icon to reveal the ContextHub toolbar
- Select a persona that matches the segment you created
- The ContextHub will resolve the applicable segments for the selected persona
For example, our simple segment defintion to identify users in our prime age group is a simple segment definition is based on the age and gender of the user. Loading a specific persona that matches those criteria shows if that the segment is successfully resolved:
All traits are resolved immediately, though most only change on page reload.
Such tests can also be performed on content pages and in combination with targeted content and related Activities and Experiences.
If you have set up an activity and experience using the prime age group segment example above, you can easily test your segment with the activity. For details about setting up an activity, please see the related documentation on authoring targeted content.