Traits are pieces of information you know about a user or a group that are included in an Identify call or a Group call. These could be demographics like age or gender, or account-specific like plan or setup.
User traits
As a general rule, you should attach as traits all the information that you can use to classify and segment your users.
These are the most common user traits we've seen:
emailrolestaffadminindustrysource_of_sign_upsubscription_status
These traits are very useful to segment your audiences in any way you want. In this case for example, we're looking at founders that signed up to June thanks to word of mouth.
By sending the right traits you'll be able to answer questions like:
Are product managers more likely to retain compared to founders?
Where are most of my signups coming from? Is social media bringing more traffic than word of mouth?
How many of my paying customers are from a B2B company? How many from a B2C company?
Reserved traits
June has reserved some custom traits (based on Segment reserved traits) that have semantic meanings for users, and will handle them in special ways, like showing the right information at the right place in the product.
Trait | Type | Description |
| String | Email address of a user |
| String | Full name of a user. |
| String | First name of a user |
| String | Last name of a user |
| String | URL to an avatar image for the user |
💡 userId and anonymousId are both required as part of the identify call when you submit the traits above.
Group traits
You can apply the same principle and attach important pieces of information to your groups as well. Again, as a general rule you should attach as traits all the information that you can use to classify and segment your groups.
These are the most common company traits we've seen:
industrycompany_sizecompany_stagesubscription_statussetup_completedintegrations_installed
For example, you can see all the traits that we're tracking:
In most cases, traits are almost static e.g they don't change value often. However, it's also possible to have dynamic traits which get updated on the basis of a specific behavior. For example, in the image above, traits such as loaded_report_count_last_30_days or monthly_event_count get updated once a day by a cron job that runs in the back end.
Note: You can also add user or company traits manually from our UI. This is very useful to qualify your latest signups and make sure that the ones with higher potential have priority. In our case, the tier trait can take the following values depending on the size of the business and industry: 0 (super high priority), 1 (high priority), 2 (mid priority) and 3 (low priority).
Reserved traits
June has reserved some custom traits (based on Segment reserved traits) that have semantic meanings for users, and will handle them in special ways, like showing the right information at the right place in the product.
Trait | Type | Description |
| String | Full name of a group. |
💡 groupId and userId are both required as part of the group identify call when you submit the traits above.