Do you have a web application/SaaS and want your customers/users to be able to send you better feedback and feature requests? You can use Feedbucket for that!
By default, Feedbucket will show all feedback to everyone. This is obviously not what you want when it comes to your users. You do not want User A to see the feedback submitted by User B.
To get it so users only see their own feedback there are a few updates that we have to do.
{warning} When we have configured your project to use User Feedback, you will get an error alert before completing step 2 & 3 below. This is normal.
Set your users Name & Email - When submitting feedback through Feedbucket we need a name and an email of the person submitting feedback. Called a Reporter. With user feedback you already know your users name and/or email so you should set this automatically so the user do not have to do it. This is done by adding a Javascript config object like below (Watch the video for me in depth discussion about this.):
// Add this to every page where you have Feedbucket installed.
<script>
window.feedbucketConfig = {
reporter: {
name: "User A",
email: "user-a@yourwebsite.com"
}
}
</script>Add a unique token to every user - This might be the most confusing part. By just doing the above your users would still be able to see eachothers feedback. We need some way to uniquely identify each user and we do this with a token. This can be anything from your database of users like for example a uuid if you have it. Another option is to use a hash of for example the users email + created_at timestamp. You could also create a new column in your database for your users like feedbucket_token or something. There are multiple ways to do this but what you want is to have a token for each user that you will set. This token will not change for that user. You then update the feedbucketConfig object from the step before to be like this:
// Add this to every page where you have Feedbucket installed.
<script>
window.feedbucketConfig = {
reporter: {
name: "User A",
email: "user-a@yourwebsite.com",
token: "super-secret-token-for-user-a"
}
}
</script>{warning} Do not use a regular auto increment ID as a token (for example
1234). Users could then easily change this and start seeing feedback from user users. The token should be unique to your user but should not be able to be guessed.
User A will no longer see the feedback that User B and User C submitted, and vice versa. You can handle the feedback just like normal either from within Feedbucket Adin or in one of your integrations.When you have Feedbucket on your on product you probably want to brand the widget in your own colors, add your own logo, remove the Powered by Feedbucket, etc. Take a look at Branding to see how this works.
What plan is needed for User Feedback?
To use User Feedback you need to have our Business plan.