User Properties Overview
What are user properties?
User Properties are fields you send to Appcues from your product about your users. They are the “adjectives” that describe your users. Examples include things like Name, Email Address, Company, Role, Created Date, etc.
Why send user properties to Appcues?
One of the powerful features of Appcues is the ability to very specifically target users based on who they are or where they are in their customer lifecycle. For example, you may want to target “new marketing admins”, for which you would need to know “created date”, “role”, and “team”. All of these are User Properties you can send to Appcues.
How do I send User Properties?
Check out the Sending User Properties Guide (Developer) document.
Where can I see which User Properties I’m sending?
They’re all listed on the Events and Properties page in Settings. At least one user needs to have been identified with a particular User Property to have the property show on this page.
You can also see User Properties on a certain page in your app if you Open the Appcues Debugger.
Which User Properties should I send?
Here’s a set of recommendations to start sending first. You can add more later as needed, but (as you probably know) developer time can be hard to come by.
Installation plan template
To make it easy to figure out what user properties (and events!) you want to send to Appcues, we created an installation plan template. Click here to make a copy of the template. If you choose to create an installation plan, you can share it with the developer(s) that will install Appcues so they know exactly what data you need!
Recommended / Necessary
|User ID||Required to identify a user, must be present for Appcues to function.|
|First Name||For personalizing content.|
|Last Name||Also for personalizing content (but more optional).|
|Email Address||Can be used for various identification.|
|Created Date (user)||For knowing how long a user has been using your product.|
|Company Name||For personalizing content.|
|Plan Type||Example: trial, paid. Used for lifecycle targeting.|
|Plan Tier||Example: standard, enterprise.|
|Role||Example: admin, standard. However you differentiate permissions.|
Additional / Optional
|Team||Example: marketing, sales. Or any other way you segment your users.|
|Location||Example: state, zip, country, etc (use multiple properties). Target on where your customer lives.|
|Version||If users can be on different version of your application they may need to see different content.|
|Beta User / Feature Flags||To communicate with users who have access to certain features.|
|Language||For multi-language applications.|
|Renewal Date||To remind users to renew. This is generally an account level property that is added to each user.|