Customize Workevo to be about your customers
A default installation of Workevo will allow you to answer important questions about your user base quickly. But sometimes you want answers to questions specific to your users and products. You can send accurate Workevo data to your user base in two ways: custom user properties and events. Below, we will share some best practices examples to help you customize Workevo about your users.
Custom user attributes are data that you send us about your users. Various events; Specific actions that your users perform in your product.
For example, if you have a project management tool:
- The custom user attribute you submit may be the same as the project number that the user-created or the name of their package.
- While an event can tell you when your users upgrade their packages.
You can send any custom user properties you want to Workevo. Custom user attributes are ideal for helping you answer questions like:
- How much? For example, which users pay you more than $ 10 per month?
- What is your name? for example, show me a list of all users whose job title is Marketer
- Is it true or false? For example, which users have used my calendar feature? (calendar feature = true) and which users are hiding? (calendar feature = false)
- What day? For example, which registered users will end on September 1?
You may have questions specific to your user base. Therefore, you should submit Workevo whatever your custom user properties need to answer them. And you should only send data that capture meaningful information about your users (like their monthly spend, the number of teammates they've added or their subscription date ended).
You may have questions specific to your user base. Therefore, you should submit Workevo whatever your custom user properties need to answer them. And you should only send data that capture meaningful information about your users (like their monthly spend, the number of teammates they've added or their subscription date ended).
Here are a few common examples we find that you may be inspired by:
Project created - If you own a project sharing tool, you'll want to know which users (and how many) users have or haven't created a project yet. This data tells you who needs help to succeed with that feature.
To find out users who have not created a project, filter the user list to show to all people with 0 projects created:
Calendar feature - You may want to see a list of all users who have used your Calendar feature on the last day. This will be a valuable group to request feedback.
Job title - You may want to see a list of all marketers who use your product. You can tell this specific user group about your new analytics feature.
Monthly Spending - You may want to find out which users are spending more than $ 50 per month on their subscriptions. This will be a great group to give a thank you gift for.
Here's how you will filter your user list for that:
Uploaded songs - How many users have uploaded more than 80 songs, for example, out of 100 possible songs? If someone is going to the limit, they will be an excellent candidate to upgrade, so you should let them know about your plan of 500 songs.
Download ebook - Which users have downloaded your latest ebook? This favorite content group might be interested in your latest blog post writing on a similar topic.
Purchased products - Maybe you want to know who bought more than five products from your store. You can then give this group a gift for their loyalty as future purchase discounts.
Remember, these are just a few examples. You can send Workevo any data that makes sense to you to understand your users better.
You can add descriptions for any custom attributes you create in Workevo. This will help both you and your teammates remember your custom meaning. Here is how to do it.
To track specific actions a user takes in your product, you should send events to Workevo. Events tell you the first time your users performed an action (for example, when an upgrade was registered), the last time they took that action (for example, the last time they exported PDF) and the total the time they take action (like the number of times a particular feature is used). If you are looking for inspiration, you can see our guide to using events here.