Skip to main content
An experience is a concrete thing a visitor sees — a specific page version, component, search algorithm, or merchandising rule. This step connects your abstract variants to those real objects. Until you map experiences, variants are only percentages. Mapping gives each group something to actually experience.

​
Add an Experience

Click Add Experience(s) and choose a type.
Only records that already have variants appear for selection. Variants are authored in the module the record belongs to, not here — so create them before you reach this step. Each type can be added once. Selected types are removed from the dropdown.

​
Map Variants

Adding a type opens a selection dialog. Search for the records you want, filter by content model where available, and add one or more. Each added row then gives you two things to set:
  1. A Version — defaults to the published version, or the latest version if none is published.
  2. A variant mapping — which internal variant of that record maps to which experiment variant.
The column header for each variant shows its traffic allocation, so you can see the split while you map.

​
Key Considerations

  • Web pages must be enabled to act as web pages.
  • Visibility of algorithms and merchandising rules depends on your plan. If your plan does not include Discovery, those types will not appear.
Every experience must have a version and a variant mapping before the experiment can start. You can save an incomplete mapping, but you cannot launch with one.
Starting an experiment prompts you to publish the associated records. The experiment only begins after you confirm.

​
What’s Next