Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form below and we will reply as soon as possible.

  • Appcues Certifications & Training
  • Contact Us
  • Home
  • User Experiences
  • Use Cases

Build Guide - Product Feedback Slideout

Updated at November 28th, 2022

Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form with the details about the help content you'd like to see.

  • Installation & Developers
    Installing Appcues Installing Appcues Mobile API & Data Troubleshooting Extras
  • User Experiences
    Web Experiences Building Web Experiences Building Mobile Experiences Customization & Styling Targeting Studio Troubleshooting Use Cases FAQ
  • Mobile
    Installation & Overview Building Mobile Experiences Mobile Analytics Troubleshooting Mobile Use Cases
  • Account Management
    Subscription Users & Data
  • Analytics
    Experience and Event Analytics Data
  • Best Practices
    Use Cases Pro Tips PLG FAQ
  • Integrations
    Integration Documents Use Cases Resources
  • Post-mortem
    System Incidents
+ More

Table of Contents

Building the Slideout 1. Launch the Appcues Builder to create a new flow 2. Create a Slideout step 3. Add a 'Text' block to communicate to your end-users 4. Add a 'Rating' block for feedback gathering 5. Change the button text Setting a Theme Targeting the correct users

Difficulty level: Intermediate

 

Feedback from your users is a key component of knowing whether you're heading in the right direction with product updates and new features. A feedback flow that we can create in Appcues can look like this: 

A feedback flow should be:

  • Explicit and one-topic in the content you're asking for feedback about
  • Contain an easily understood rating or open-ended question
  • Respect the user's time (they came to your product to do something else) by being concise

Let's walk through building a simple feedback flow. We'll cover:

  • Building the slideout
  • Setting the Theme
  • Targeting the correct users

Building the Slideout

Let's begin by creating the actual content.

1. Launch the Appcues Builder to create a new flow

There are multiple ways to create a new flow, one is from the flows page in the Appcues studio by clicking the 'Create a Flow' button or through the Appcues Chrome Extension.

  1. from the Appcues Studio Flows page:
  2. from the Appcues Chrome Extension:

2. Create a Slideout step

Once in the Appcues Builder, start by adding a Slideout group and using any template you wish:

3. Add a 'Text' block to communicate to your end-users

Give the flow some context or text introduction. Because we have event targeting we are able to say "Looks like you recently built a flow", and you can give short context in the same way—all depending on your preference!

 

4. Add a 'Rating' block for feedback gathering

This will contain both the question you want to ask the user as well as the numerical rating block. Set the numerical limit to your preference and add a label. In this example, we've set our limit to 4.

You can also edit the rating text under the numbers.

5. Change the button text

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 flow 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 within your account settings in the Appcues Studio. If you're interested in seeing what user properties we recommend sending to Appcues, check out this User Properties Overview doc.

The targeting below is for example purposes, yours will be different. For this flow, we wanted to target a very specific set of users.

  1. They needed to be customers
  2. They needed to have completed their Onboarding (we don't want new users seeing it)
  3. They needed to have recently completed the action we're asking about (in this case, having built a flow)
  4. We didn't want to show it to everyone (because we're running multiple surveys and that might inundate a user with flows)

Here's how we did it, explained below.:

 

For the first and second conditions, we used our Segments for Customers and Steadystate users.

Third condition is the Session Randomizer property, which each user gets during each session and changes with each new session. It's on a 100-point scale, so we're trying to target about 40% of users that meet all the other criteria. 

Fourth, we'll show this flow if the user has "Clicked create new flow" in the past 4 days. This is an event we send to Appcues from a button click in our application and is how we know they did the activity we're asking about.

Lastly, and this is icing, we didn't want to show a user multiple surveys in a short period of time. We created a specific Segment so users won't see more than one survey per day. 

That's it! You can use Test Mode to see what your slideout will look like in a live environment and publish your flow when you're ready.

Need some extra support? Shoot us an email at support@appcues.com and we'll be happy to help.

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Event Triggering
  • Forms & Surveys
  • Studio: Events and Properties Page Overview
  • NPS Overview
Appcues logo

Product

Why Appcues
How it works
Integrations
Security
Pricing
What's new

Use cases

User Onboarding Software
Feature Adoption Software
NPS & Surveys
Announcements
Insights
Mobile Adoption

Company

About
Careers
we're Hiring

Support

Developer Docs
Contact

Resources

The Appcues Blog
Product Adoption Academy
GoodUX
Case studies
Webinar Series
Made with Appcues
Appcues University

Follow us

Facebook iconTwitter icon greyLinkedin iconInstagram icon
© 2022 Appcues. All rights reserved.
SecurityTerms of ServicePrivacy Policy
Expand