Skip to main content
All CollectionsContentExperiences
Introduction to Experiences
Introduction to Experiences

Experiences let you create and manage journeys across your website and messages to give consistency across channels and touchpoints.

Updated over a month ago

Experiences allow you to quickly manage content within Slots as a group, helping to ensure coordinated messaging. You can tailor multiple pieces of website content for each Experience, as well as message content, for a consistent cross-channel experience.

You can control who sees each Experience using Experience rules. The rules, such as the date and time, or specific criteria for when different content should be shown, can be configured once for the whole Experience, rather than individually for each Slot – saving you time and increasing your efficiency.

Learn more in Use marketing rules.

Example use cases:

  • Different website and email messaging for first time visitors and new shoppers.

  • Different website and email messaging for Black Friday or a flash deal.

  • Different website and email messaging for your VIP shoppers.

  • Different website and email messaging for those that have shown a preference for a particular category, for example, Menswear vs Womenswear.

  • Showing all visitors a June promotion experience, and showing extra content to your VIP shoppers.
    You can do this by showing more than one Experience to some shoppers. Learn more in the section Using multiple Experiences.

  • Experiences build on top of Slots and SmartBlocks. Using Experiences is faster and more synchronised to use than Slot Rules on their own.


How Experiences interact with existing Site Editor set up or Slot Rules

When you migrate the account to use Experiences for an existing Site Editor setup, the existing setup is moved into a Migrated Site Config Experience. This can then be prioritized or adjusted against any new Experiences you create.

Existing slot rules can be used alongside experience rules. Each Slot processes rules based on the setup within the Slot Rules page, which can contain both Experience and non-Experience rules.


Definitions

Experience

An experience you want to give your consumers. An Experience can be made up of:

  • Personalization of one or many web pages with the Site Editor.

  • Email content, controlled by a Slot rule to show particular content depending on the Experience.

  • Experience rules within Web or Email Slots to show selected SmartBlocks when on an Experience, ensuring all content is co-ordinated in messaging.

Experience rule set

A set of rules that determine when a person is shown each Experience.

Learn more in Use marketing rules.

Experience priority order

Only impacts Experiences with Site Editor configurations.

A shopper can be assigned to more than one Experience. Some Experiences can be shown simultaneously without any conflict, for example, one experience which only changes the header, and another which changes the footer. However, when there is a Site Editor content clash between Experiences, the priority order is used to determine which should be shown

Learn more in the section Using multiple Experiences.

Takeover

Only impacts Experiences with Site Editor configurations.

An Experience can be set to takeover all others, meaning that only content from that experience is used.

Learn more in the section Using multiple Experiences.


Migrate your account to use Experiences

Before you start

If you're on a legacy account type which doesn’t have Experiences fully enabled by default, you need to migrate your account to use the feature.

Before migrating your account, you’re able to create new Experiences and use some features, but not all features are available, and you aren’t able to put any Experiences live.

⚠️ You can only migrate your account once and it is not reversible, you must be aware of the impact of this before proceeding.

Impact of migrating

Migrating your account merges your existing Site Editor configuration into a Migrated Site Config Experience.

It also creates an Experience Rule that results in the new Migrated Site Config being the one that is shown to your visitors. Therefore, your website continues to display the same content.

After the migration, you can still access the Site Editor from the left hand navigation, but this now has a menu at the top to select which Experience you want to edit. This is also accessible from within an Experience using the Edit Site button. Versions for each Experience Site Editor can be viewed using the Content History button.

If your Site Editor does not contain any inserted content, when the migration is complete, a new Default Experience is still created, but is empty.

If you’re unsure about going ahead with the migration, or have any questions, contact our Support team.

To migrate your account:

  1. Expand the User menu and go to Settings > System Configuration.

  2. Select Migrate to Experiences.

  3. Select MIGRATE ACCOUNT.


Reporting

There are 3 areas where you can view how Experiences are performing:

  • Within the Experience you can view how many users are seeing content for the Experience over time.

  • Within a Person history report, you can see which Experience a person has been assigned to, under the Experience panel.

  • Within the Comparison report, you can see data against each Experience on the Experience tab.


    In the Comparison report, each purchase is attributed to content using the last click (product only) attribution model. Every Experience that caused a SmartBlock/Slot to be shown then receives the attributed purchase value. This includes both Experiences that place content through the Site Editor and Experiences that place content through Slot Rules.

    Purchases can be attributed to multiple Experiences. For example, if a person is assigned two Experiences, and both Experiences caused the SmartBlock/Slot they clicked on to display — based on the Slot Rules and/or Site Editor placement — then both Experiences have the purchase value attributed to them.

Why does my Experience tab in the Comparison report not show any data?

For the system to start logging data against an Experience, there needs to be some content that is being displayed as part of the Experience. If there is no content being displayed as part of the Experience, then no data is recorded.

Did this answer your question?