Implementing Opt-In/Opt-Out User Preferences
Empower users by enabling them to select their level of engagement with various features and to modify these preferences as their needs evolve with customizable opt-in/opt-out preferences using Jimo.
User Type: Website Visitors
Domain: Digital Platforms
Jimo Feature Used: Surveys & Segmentation
Aspect: Adoption
The Challenge:
Users often seek a balance between receiving helpful guidance and maintaining an uncluttered, streamlined platform experience. The key challenge is to respect user preferences while ensuring they have the option to engage with valuable platform features as desired.
The Solution:
Jimo's "Surveys" & "Segments" features address this challenge head-on by offering:
Surveys: Quickly gather user preferences with simple questions. It's like asking your users directly what they enjoy and what they could do without on your platform.
Segments: Take what you've learned from the surveys and group users accordingly. This way, everyone gets more of what they love and less of what they don't, making every user's experience feel just right.
Step-by-step Guide:
Planning Your Survey:
Let's keep this super simple: it's all about what your users want to see (or not). Imagine a one-step wonder where users quickly hit 'Yes' or 'No' on the stuff they care about, like tutorials or heads-ups on new features.
In our example, we will go for a general preference request we can use on an onboarding flow.
To ask for preferences you have to choose your approach: show stuff, hide stuff, or maybe even a quick 'What's your take?' kind of question. 🤔
Here, we'll use an open question to give more freedom to the user, but you can choose an "accept all" by default approach to drive more engagement in your communications.
Last thing but the most important, you'll have to make sure users can change their minds later. Think of somewhere handy to trigger back this survey, so they can switch things up whenever they feel like it. Easy peasy!
To handle that issue easily, let's ask our tech team to prepare a spot in our settings where we can embed a link or a manual trigger.
Using a Template:
Based on your planning, choose a template that aligns with your request goals. Many surveys are using multiple-choice questions in our Templates.
In our case, we need one with a single step. We'll adapt the "Ask users where did the users find you" template, there's just a few modifications to do and we can keep the thank you step as it is.
Customize the selected template to fit your platform's unique features and branding.
You can start by defining the overall look of your survey, themes are here to help.
We're focusing on one main question, so let's keep the survey tidy. Position the snippet where it feels natural, ditch any extra bits like labels that we don't need, and fine-tune the multiple-choice options to fit our 'Yes or No' vibe.
To get users more involved, why not throw in something eye-catching? A cool media piece or a friendly face in a profile block can make all the difference in drawing users in. 🌟
In our example, we'll only use a generic visual to make the snippet more visible to the user.
Designing the Experience:
You have to define an engaging request based on your approach and design 2 buttons accordingly.
We used our title to emphasize the feelings of the user and answer options that clarify the outcome. We advise you to also use a CTA that allows the user to confirm his action.
It's important to add a closing step to thank your users, acknowledge their engagement, and confirm that you'll respect their choice.
It's the perfect occasion to show them where they can trigger back this survey to change their preferences. Use a media block, a CTA, or keep it simple like below with an embedded link.
Target & Publish:
Utilize Jimo's user-friendly builder and target settings to set up your survey, defining rules for its initiation (e.g., user's first login, navigation to a particular section).
Trigger
To finalize your first draft, start with the most practical way for you to trigger, it will help you test.
The default trigger is perfect for testing from a single URL starting point.
If your team has prepared a spot such as a button or a simple icon in the settings, you can use an on-click trigger.
In that case, you won't be able to push this survey to users, you'll have to use a public URL. But your users will be able to access the setting whenever they want by clicking on the element you've selected.
If you want to make this request an extension of your onboarding flow, we advise you to work with your product and tech teams to choose which action within your app concludes the first overview or login funnel to ask for preferences and set up a manual trigger accordingly.
You can set up this trigger at the end of your configuration, it overrides the other triggers and, makes the Where field useless, so it may slow down your testing.
To set up this trigger you'll just have to paste
window.jimo.push(['do', 'boosted:trigger', [{ evolutionId : "<YourExperienceID>" }]])in your code where you can identify that your user is ready to define his preferences.
Where
Use the "Where" setting to specify the URLs or app sections where the survey should be triggered. Avoid using Everywhere without a manual Jimo initialization, it will prevent triggering your survey on login pages or other bad timings.
To maintain a focused onboarding experience, you might start with a single page and expand as needed based on user feedback and journey mapping.
In our example, we will use filtered URLs to trigger the onboarding from multiple pages that the user might visit on their first connection to catch his preferences from the start as a conclusion to his onboarding. It will also nudge him to explore and manage his settings. (We also added our testing environment to the domains.)
Who
Define your target audience within Jimo's settings, ensuring that the tour reaches the right users at the right time.
If you used an advanced trigger or filtered URLs that make your onboarding reachable only via a specific action on a few pages. To make sure you don't bother your already onboarded users, we advise setting a segment on the fly based on the date of creation of the user.
Otherwise, using the default trigger and where field can be relevant but make this Who section the most important. You may define segments based on the general engagement or based on the completion of other preexisting experiences.
Use segmentation to tailor the request to different user groups, such as new sign-ups or users who have not yet seen any other experiences.
You can use a few default attributes but segmentation will be limited if you don't first identify your users. Also, make sure that if you identify your user only target the ones that are identified.
For the most accurate way to identify new users, we advise you to get in touch with your tech team to set up a custom attribute manually or via our integrations.
When
You can schedule the tour to trigger, but in the case of this preference, it's the recurrence and priority that matter the most.
Usually, we want any experience related to onboarding, like this survey, to be among the first ones triggered. So you need to have your rate limiting set to the 1st or 2nd highest priority on the list.
With a recurrence, you can remind and confirm user preferences regularly.
In our case, we'll set it to repeat twice a year to prevent overwhelming our users. But it can be valuable for you to synchronize this value with other recurrent communication such as monthly product updates.
Testing and Refinement:
Test the all URLs you need to start your preference request survey from in the test bar of the Where field.
You can preview your Survey while editing or use a test link once in the settings.
Here's a tip: Use a Team segment to test in real conditions while keeping it hidden from your users.
Conduct user testing with a small group to collect feedback on the tour's clarity, engagement, and overall effectiveness by doing a few live onboarding demos.
Launch and Analytics Monitoring:
Deploy the optimized survey, ensuring functionality across different devices and platforms.
Monitor the experience's performance through Jimo's analytics, focusing on user engagement and completion rates.
Refine the survey based on feedback, adjusting content, pacing, and interactive elements as needed. Categorize your communication to segment on more detailed user preferences.
In our example, we'll divide preferences into 3 categories: Adoption, Education & Discovery.
There are 2 options to implement this update.
Add a new step to your Survey, with a condition so it can be reached only by users who agreed to the previous step.
It might be more engaging to directly use a multiple-choice step to let the user check the categories he's interested in.
Integration of a Segmentation:
Based on survey responses, segment users into groups according to their preferences. This segmentation allows for personalized user journeys, displaying only the content and features each user opts to engage with.
In our example, a single segment is sufficient. We need to apply this segment to all experiences to make sure to exclude opt-out users.
Utilize the segmentation data to customize the visibility of tutorials, announcements, and other features according to user preferences, enhancing the overall user experience.
You can use the survey results to segment on the fly or apply the newly created segment to any experience you want to respect the user preferences.
Benefits:
Enhanced User Satisfaction: By providing users with control over their platform experience, you increase overall satisfaction and engagement.
Flexibility: Users appreciate the ability to adjust their preferences over time, ensuring their interaction with the platform remains aligned with their current needs.
Simplified User Experience: This approach reduces clutter for users who prefer a more streamlined platform, improving usability and focus.
Conclusion:
The "Implementing Opt-In/Opt-Out User Preferences" use case demonstrates a creative application of Jimo's Surveys feature to enhance user control and satisfaction. By allowing users to personalize their interaction with your platform, you foster a more engaging, user-friendly environment that respects individual preferences.
Last updated
