Mutiny gives you full control over when experiences should show to a specific user. In addition to experience priority, you can also choose to have experiences run concurrently.

Setting experiences to run concurrently

To mark an experience as concurrent, select the meatball menu next to the segment card in the experience priority modal and select "Concurrent?".

What is a 'concurrent' experience?

Concurrent experiences run at the same time as all other experiences, regardless of experience priority. If you have a visitor who qualifies for more than one segment on the same page, you can choose whether or not that customer should see the personalizations from both experiences.

For example, you may have experiences on your homepage that are live for both a startup segment and a B2B segment. There will be visitors to your homepage that are coming from a B2B startup and would qualify for both audiences. In the priority modal, you can select whether these experiences should run concurrently or which should take priority if you want to keep the experiences separate.

When to choose to run concurrently

If you are personalizing different elements on your page in each experience, you can choose to run your experiments concurrently.

If you are personalizing the same elements on your page in each experience, you should not run your experiments concurrently. There is no guarantee which experience's modifications will be shown and you will not have control over the user experience for visitors that are part of both segments.

Let's take a look at a few examples -

Scenario 1

You change the headline in both your experiences. You should not run these experiments concurrently because you won't have assurance of which headline visitors from B2B startups will see.

You should either choose which personalization should take precedence and set the priority accordingly, or create a composite segment where you can fully customize the experience for the visitors in both segments.

Scenario 2

You change the headline in your startup experience and you change your logo bar in your B2B experience. You should run these experiences concurrently because there will be no conflict in personalized modifications.

Scenario 3

You want to change the CTA in your navigation site-wide and you want to personalize your homepage content. To do this, you create an experience on the homepage and an experience on your 'about' page where you apply condition rules to apply the personalization to every page on your site. In your 'about' page experience, you configure your CTA personalization. Because you want this to apply to your homepage, as well, you should run the CTA experience concurrently.