This document covers the configuration of segmentation as used with the Client Context. To configure segments with ContextHub using the touch UI, please see Configuring Segmentation with ContextHub.
Segmentation is a key consideration when creating a campaign. See Segmentation glossary 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.
These segments are then used to provide a visitor with specifically targeted content. This content is maintained in the Campaigns section of the website. Teaser pages defined here can be included as teaser paragraphs on any page and define which visitor segment the specialized content is applicable for.
AEM allows you to easily create and update segments, teasers, and campaigns. It also allows you to verify the results of your definitions.
You can Edit each segment to specify a Title, Description and Boost factor. Using the sidekick you can add AND and OR containers to define the Segment Logic, then add the required Segment Traits to define the selection criteria.
Each segment has a Boost parameter that is used as a weighting factor; a higher number indicates that the segment will be selected in preference to a segment with a lower number.
The following logic containers are available out-of-the-box and allow you to construct the logic of your segment selection. They can be dragged from the sidekick to the editor:
The following segment traits are available out-of-the-box; they can be dragged from the sidekick to the editor:
| IP Range
||Defines a range of IP addresses that the visitor can have.
| Page Hits
||How often the page has been requested.
| Page Property
||Any property of the visited page.
| Referral Keywords
||Keywords to match with information from the referring website.
| Segment Reference
||Reference to another segment definition.
| Tag Cloud
||Tags to be matched with those from the pages visited.
| User Age
||As taken from the user profile.
| User Property
||Any other information that is available in the user profile.|
You can combine these traits using the boolean operators OR and AND (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.
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.
Properties with the _i18n suffix are set by a script which is a part of personalization's UI clientlib. All UI-related clientlibs are loaded on author only since the UI is not needed on publish.
Therefore when creating a segment with such properties is it normally necessary to rely on browserFamily for instance instead of browserFamily_i18n.
You can construct complex segments in AEM. 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 either:
Male and between the ages of 16 and 65
Female and between the ages of 16 and 62
As the main operator is OR you need to start with an OR Container. Within this you have 2 AND statements, for each of these you need an AND Container, into which you can add the individual traits.
Once the segment has been defined, potential results can be tested with the help of the Client Context:
- Select the segment to be tested.
- Press Ctrl-Alt-C to open the Client Context, which shows the data that has been collected. For testing purposes you can Edit certain values, or Load another profile to see the impact there.
- Depending on the traits defined, the data available for the current page may or may not match the segment definition. The status of the match is shown underneath the definition.
For example, a simple segment definition can be based on the age and gender of the user. Loading a specific profile shows that the segment is successfully resolved:
All traits are resolved immediately, though most only change on page reload. Changes to mouse position are visible immediately, so useful for testing purposes.
Such tests can also be performed on content pages and in combination with Teaser components.
Mouseover on a teaser paragraph will show the segments applied, whether they currently resolve and therefore, why the current teaser instance has been selected: