Comment on page
Create content entries representing personalizations and experiments.
Experiences in your Content Source
Experiences are a way to customize and tailor the content that is served to your users. Both types, Experiments and Personalizations, are based on the same fundamentals and evaluated equally. This page discusses the basic evaluation process. If you would like to learn more about how to configure Experiments and Personalizations, have a look at the following pages:
In order to know what baseline content should be switched with a personalized variant, content needs to be "mapped". In order to map your content, Ninetailed conveniently provides the
Ninetailed Experiencecontent type directly within your Content Source. The mapping of a single baseline entry and one or multiple variants creates a "component" and links it to an Experience.
Baseline content is content that is served to your users by default without using any Experiences. In Experiments, this is also referred to as the "control" group. Naturally, this is the content that is switched with a variation when rendering an Experience to a user. Any type of content can serve as a baseline for multiple Experiences. Naturally, only a single Experience can be displayed in the end, which depends on the priority of Experiences.
A variant entry is content that is created to either test the performance of that variant or to serve a more personalized experience to your users.
A single entry (e.g. a CTA on your homepage) can be part of multiple Experiences. Naturally, only a single content entry can be displayed at a time for each component. For this, Ninetailed provides a priority feature, letting you choose the order of your Experiences on a component-level.
For each individual component, Ninetailed evaluates whether the user is eligible for the Experience with the highest priority (top of the list). If the user is not fulfilling the Audience requirement or is not allocated due to traffic allocation, Ninetailed evaluates the next Experience for that component.
Priority of Experiences
Example: For your homepage hero, you are running multiple Experiences: An Experiment that is shown to an Audience with a specific UTM parameter, and an Experiment that shows an alternative hero image. In your hero component, you have set up your Experiences in a way that the "No heroes" Experiment is prioritized. In this case, if a visitor satisfies both Audiences, only the "No heroes" Experiment will be shown.
If an Experience with an "All Users" Audience is configured to have the highest priority, all Experiences with a lower priority would not be served to anyone. It is good practice to rank more specific Experiences higher.