Build Guide - Regular - User Testing
Removing friction from a user's experience with your product is often about proper design. Unfortunately, as you get closer to how the feature works you also get further away from whether it's usable to the general population, and that's where User Testing comes in.
This flow will automate reaching your target users and scheduling time with. We'll cover:
The final product of your slideout will look something like this when we're done:
Building the slideout
Let's begin by creating the actual content.
First, launch the Flow Builder to create a new flow
There are multiple ways to create a new flow, one is from the flows page in your dashboard by clicking the green Create a Flow button:
Create a Slideout step
Once in the Flow Builder, start by creating a Slideout:
Add a text block
Give the flow some context. Use the voice of your brand and be clear and concise with what the flow is asking.
Add a calendar scheduling link
We use Calendly but any scheduling app will work since we're simply linking out to it. Check out the Growth Lab guide to creating a Calendly event to use with this flow.
Remove the default button now that you have the custom link button. The option is in the slideout settings.
Setting a Theme
See the Themes page if you haven't already set a theme for your Appcues content.
If you have a Theme you're ready to use, make sure this modal is using it:
Targeting the correct users
To be able to target you'll need the applicable User Properties being sent to Appcues. You can see what you're sending on the "Events and Properties" tab of the Settings section. And recommended User Properties to send are in the User Properties Overview doc.
The targeting below is for example purposes, yours may be different. For this flow, we wanted to target a very specific set of people.
- They needed to be customers
- They needed to have completed their Onboarding (we don't want new users seeing it)
- We wanted to ask them later in their session, so set a minimum pageview count
- We also wanted to only show to a portion of users, so we added the Randomizer criteria.
Here's how we did it, explained below:
First, we used our Segment for Steadystate users (creating a Segment). This includes users on accounts where they have installed our script and the user is at least 40 days old.
Second (and optional), Session Pageviews is a field Appcues automatically tracks. In cases where users aren't regularly logged out this may not reset between actual usage. It's also not necessary for a good experience.
Third (also optional), the session randomizer works by giving your user a number between 0 and 99 for the session, where "50" would target about half. You don't want to dry up your potential user testers in one round, so only showing to a subset of users future proofs your ability to get user testers down the road.
When you're ready you can use Test Mode to see what your modal will look like and publish your flow when you're ready. And remember, you don't need to wait to build all the content you're hoping to build to set this flow live; and you can always iterate on each flow once you know how your users are interacting with them.
Have an awesome feedback form or survey to share? Need some extra support? Shoot us an email at firstname.lastname@example.org and we'll be happy to help.