Since visitors can easily match multiple segment definitions, you need to take care when setting your priority order or you may have experiences with very little traffic, or you may not be showing the most relevant experience to the right set of visitors.

Mutiny will automatically ensure your experiences don't conflict with one another. A visitor can only see one experience per type on any page. You can manage the priority by using the "Manage priority" button on the app "Website" tab.

Components, and On-page personalizations are all prioritized independently. Within any category, you can drag and drop the segment cards to reorder the priority. The first on the list is the highest priority experience.

Redirects always take first priority and cannot run concurrently to Component or Page personalizations. If you have a redirect experience running for an audience, it will always take precedence over any other experience type.

Components like banners, side pops and surveys are prioritized against one another and a visitor will only see the highest priority components segment they qualify for. This is to keep your visitor experience very high and not bombard site visitors with banners, side pops and overlay modals.

The one exception to this is exit intent modals. Exit intent modals will run concurrently to other component types because there is no visual conflict since it is only triggered when a user exits your site, not on page landing.

On page personalized experiences will be mutually exclusive to one another, but will automatically be concurrent to components. That means a visitor can see their highest priority matched personalized page and their highest priority matched personalized component.

Mutiny keeps your experiences mutually exclusive and relies on priority order to ensure that your visitors have the personalized experience you intend for them. If you want an experience to be concurrent within it's experience type category (Page or Component), you can choose to make the experience concurrent. Note that this will make the experience concurrent to all other experiences.

We generally recommend against doing this, because there is no control for conflicts. However, there are strategic reasons you may want to do this, like making a change to a navigation item in one experience when you know for sure no other experiences are personalizing that given element. You can find more information on running concurrent experiences here.

In general, you should have your smallest and most targeted experiences as top priority. If these segments are too low on your priority list, you run the risk of very little traffic seeing those experiences. For example, if you have an All Traffic segment as first priority, no one will ever see any other experiences on those pages.

In practice, this might look like ordering a target account segment first, then your industry vertical segments, then your company size segments and finally any all traffic experiences.

If you have more faith in accuracy of some data sources over others, you can choose to make those a higher priority. For example, maybe you have some experiences targeting customers using first party data, and some inferring they are a customer because they have viewed documentation on your site. You would want to prioritize your first party data segment over the behavioral inference segment.

A final lens you should use when considering your experience priority is your company's strategic priorities. What are your highest priority audiences? Which are your highest performing segments?

Remember to also look at your experiment results - these might make a case for a bump in priority as well!

Don't be a stranger

If you have any questions, we’re here to help! Please feel free to contact us at any time, either through intercom chat or via support@mutinyhq.com.