Best Practices
Feature Chaser
Learn how to harness the power of Formbricks to gather targeted user feedback on specific features. Dive deep into creating, triggering, and publishing the Feature Chaser survey to enhance your product with actionable insights for specific users.
Following up on specific features only makes sense with very targeted surveys. Formbricks is built for that.
Save, and move over to where the magic happens: The “Audience” tab.
Please follow our Actions manual for an in-depth description of how Actions work.
Purpose
Product analytics never tell you why a feature is used - and why not. Following up on specific features with highly relevant questions is a great way to gather feedback and improve your product.Formbricks Approach
- Trigger survey at exactly the right point in the user journey
- Never ask twice, keep your data clean
- Prevent survey fatigue with global waiting period
Overview
To run the Feature Chaser survey in your app you want to proceed as follows:- Create new Feature Chaser survey at app.formbricks.com
- Setup a user action to display survey at the right point in time
Formbricks Widget running? We assume that you have already installed the Formbricks Widget in your web app. It’s required to display messages and surveys in your app. If not, please follow the Quick Start Guide (takes 15mins max.)
1. Create new Feature Chaser
If you don’t have an account yet, create one at app.formbricks.com Click on “Create Survey” and choose the template Feature Chaser:
2. Update questions
The questions you want to ask are dependent on your feature and can be very specific. In the template, we suggest a high-level check on how easy it was for the user to achieve their goal. We also add an opportunity to provide context:
Save, and move over to where the magic happens: The “Audience” tab.
3. Set up a trigger for the Feature Chaser survey:
Before setting the right trigger, you need to identify a user action in your app which signals, that they have just used the feature you want to understand better. In most cases, it is clicking a specific button in your product. You can create Code Actions and No Code Actions to follow users through your app. In this example, we will create a No Code Action. There are two ways to track a button:- Trigger by Inner Text: You might have a button with a unique text at the end of your feature e.g. “Export Report”. You can setup a user Action with the according
Inner Textto trigger the survey, like so:
- Trigger by CSS Selector: In case you have more than one button saying “Export Report” in your app and only want to display the survey when one of them is clicked, you want to be more specific. The best way to do that is to give this button the HTML
id=“export-report-featurename”and set your user action up like so:
Please follow our Actions manual for an in-depth description of how Actions work.
4. Select Action in the “When to ask” card
5. Last step: Set Recontact Options correctly
Lastly, scroll down to “Recontact Options”. Here you have full freedom to decide who you want to ask. Generally, you only want to ask every user once and prevent survey fatigue. It’s up to you to decide if you want to ask again, when the user did not yet reply:
7. Congrats! You’re ready to publish your survey 💃
Formbricks Widget running? You need to have the Formbricks Widget installed
to display the Feature Chaser in your app. Please follow this tutorial (Step
4 onwards) to install the widget.