Experience

An experience is a concrete thing a visitor sees — a specific page version, component, algorithm, or merchandising rule. This step connects each audience variant to the experience built for it. Until you map experiences, a variant is only a traffic share and a set of audience values. Mapping gives each audience something to actually receive.

​

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 audience variant.

The column header for each variant shows the audience it serves, so you can see who receives what 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 audience variant needs at least one experience mapped to it.

​

Publishing on Start

Starting an experiment prompts you to publish the associated records. The experiment only begins after you confirm.

​

What’s Next

• View Experiment Results