Mutiny will automatically ensure your experiences don't conflict with one another. By default, a visitor can only see one experience per type on any page. Since visitors can easily match multiple segment definitions, you'll need to pay attention to your experience 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.
You can manage the priority by clicking the "Manage priority" button from the segment and experience overview page. You'll also be prompted to set experience priority when you launch a new experience.
Managing priority
Component, Page and Redirect experiences are prioritized independently. You can choose between these using the tabs at the top of the priority modal.
Within each experience type, you can drag and drop the segment cards by selecting the meatball button on the left. You can also move a segment card to the top by selecting "Move to top". The first on the list is the highest priority experience.
Redirects
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
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.
Page
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.
Priority considerations
When deciding on your experience priority, you may want to keep these things in mind.
Segment size
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.
Highest trust
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.
Strategic importance
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!
FAQs
Can I run two experiences at the same time?
Yes, Mutiny supports running experiences concurrently to each other. Click here to learn more.
Comments
0 comments
Please sign in to leave a comment.