1. Help Center
  2. Target Visitors

Create Custom Segments

THIS ARTICLE WILL HELP YOU:

Segments 

Segments are a group of visitors that qualify for some Audience conditions (such as location, the device used to access the site, the hour of the day, and any other user behaviors) and can be used at a later time for targeting. Visitors in a specific segment are likely to behave or purchase in the same way. Thus, you can create segments by defining audience conditions that allow Convert Experiences to determine which segment a visitor qualifies for and run the appropriate variation.

Segments also have the capability of being tracked separately in every experiment run after the visitor has qualified for the segment or programmatically assigned to.

Subsequent Visits

A segment basically allows a visitor to qualify for an audience on subsequent visits even if they do not meet the audience conditions. That is why we call segments persistent. This means that if a visitor qualifies for such an audience in the first visit, he will continue to qualify for that audience every time he visits the page. If he visited multiple times, sometimes meeting the conditions and sometimes not, he will keep seeing the experiment.

You need to attach a segment to visitors before they are bucketed in an experiment, for that segment to be tracked separately within that experiment. 

Not attached to any experiment

You can also create an Audience that you would signal as a segment and not attach to any experiment. Users which match the audience will be put on this segment, even if this audience has not been added to any experience. Later on, you can use this segment in an experience and use already bucketed visitors on to it.

Project Level

Segments are evaluated at the project level, so any visitor that reaches a page with the project tracking code and matches the Audience conditions designated as a Segment will be added to it.

Saved segments of a project can be used on other experiments as well.

How do I create a Segment?

You can enable an Audience for segmentation by following one of the two methods described below.

Using Experience Summary

Go to the Experience Summary and create a new Audience; when saving it, you will have the option to mark it as a Segment. 

 

 

Using Audiences

Select the Audiences tab and add an Audience. When saving it, you will have the option to save it as a Segment.

 

 

Content Conditions

Once you check Segmentation for an Audience, Content conditions will become available to use:

 

Tip
  1. If you need to do targeting based on visitor data, use Audience Conditions.
  2. If you need to do targeting based on page content, use the Site Area.
  3. If you want to create a persistent group of visitors, your can use page content Conditions and/or visitor data Conditions, configured in the Audience Conditions. Content conditions are available only when the Audience is checked as a Segment.
 

Number of Segments 

The number of Segments you can have at one time depends on your Convert plan limits.  If you have used the maximum, you can delete a segment and create a new one if needed.

Remove a Visitor from a Segment

At the moment, it is not possible to remove a visitor from a Segment once added. However, if you do not want to make an experience persistent, then you should look at our Transient Audiences.

GDPR Warning Message

If the Segmentation feature is enabled, this could be interpreted by Privacy Authorities in Europe that data subjects might be identified. Therefore a warning was added to inform users when segmentation is enabled for at least one audience. You can find here the screens where this warning appears.


Creating Custom Segments Based on Triggered Goals

Key Consideration

  • Goal Attachment to Experience:
    • For a goal to trigger a segment, the goal must be associated with an experience. Without this attachment, the goal cannot activate the segment.

Common Issues and Solutions

  1. Segment Triggering Before Experiment Bucketing:

    • Ensure that the segment triggers before the experiment is bucketed (fired for the first time). If the segment is not triggered beforehand, it may not appear in the report.
  2. Goal Triggering in Page View:

    • The goal must trigger in a page view before the segment rules are expected to be matched. Otherwise the Triggered Goal condition would not result in returning true.
  3. Goals and Experiment Segmentation:

    • Goals are triggered only for experiments. Therefore, you cannot define a segment based on a goal fired within the same experiment. This setup would result in the segment never being triggered, and hence, not appearing in the reports.

Example Scenario

If a goal is triggered multiple times within an experience but segmented reports show no data, consider the following:

  • Ensure the segment triggers before the experiment is bucketed.
  • Verify that the goal triggers in a page view before the segment rules are matched.
  • Avoid defining a segment within the same experiment based on goals fired for that experiment.

Conclusion

To create effective custom segments based on triggered goals:

  • Attach goals to experiences.
  • Trigger segments before experiments are bucketed.
  • Ensure goals trigger in page views before matching segment rules.
  • Avoid defining segments within the same experiment based on goals fired within that experiment.

By adhering to these guidelines, you can ensure accurate reporting of your custom segments and avoid common issues.

 

keyword: segmentation segment