The following attributes come "out-of-the-box" with Userflow. Use attributes in auto-start conditions, targeting/segmentation, and event tracking.
To create a new attribute:
Select Settings > Attributes from the sidebar.
Click New attribute.
Complete the details, and click Create attribute.
Userflow Attributes
Category | Display Name | Field Key | Data Type | Description |
|---|---|---|---|---|
User |
|
| User's email address | |
User | First Seen |
|
| When the user was first seen by Userflow |
User | Last Seen |
|
| When the user was last seen by Userflow (the latest user interaction) |
User | Name |
|
| User's full name |
User | Signed Up |
|
| When the user first signed up in your app |
Company | Company First Seen |
|
| When a member of the company was first seen by Userflow |
Company | Company Last Seen |
|
| When a member of the company was last seen by Userflow |
Company | Company Name |
|
| Company's name |
Company | Company Signed Up |
|
| When the company was first signed up in your app |
Event | Announcement Comment |
|
| Userflow announcement comment |
Event | Announcement ID |
|
| Userflow announcement |
Event | Announcement Name |
|
| Userflow announcement name |
Event | Announcement Reaction |
|
| Userflow announcement reaction |
Event | Announcement Version ID |
|
| Userflow announcement version |
Event | Announcement Version Number |
|
| Userflow announcement version number |
Event | Assistant Conversation |
|
| Userflow Adoption Agent conversation |
Event | Assistant ID |
|
| Userflow Adoption Agent |
Event | Assistant Message |
|
| Userflow Adoption Agent message |
Event | Assistant Message Rating |
|
| Userflow AI message rating |
Event | Assistant Message Scale Max |
|
| Max possible CSAT score |
Event | Assistant Message Scale Rating |
|
| CSAT rating |
Event | Assistant Name |
|
| Userflow Adoption Agent name |
Event | Assistant Version ID |
|
| Userflow Adoption Agent version |
Event | Assistant Version Number |
|
| Userflow Adoption Agent version |
Event | Banner ID |
|
| Userflow banner |
Event | Banner Name |
|
| Userflow banner name |
Event | Banner Session ID |
|
| Banner session |
Event | Banner Version ID |
|
| Banner version |
Event | Banner Version Number |
|
| Banner version |
Event | Checklist ID |
|
| Userflow checklist |
Event | Checklist Name |
|
| Userflow checklist name |
Event | Checklist Session ID |
|
| Checklist session |
Event | Checklist Start Reason |
|
| Why checklist started |
Event | Checklist End Reason |
|
| Why checklist ended |
Event | Flow ID |
|
| Userflow flow |
Event | Flow Name |
|
| Userflow flow name |
Event | Flow Session ID |
|
| Flow session |
Event | Flow Start Reason |
|
| Why flow started |
Event | Flow End Reason |
|
| Why flow ended |
Event | Flow Step Name |
|
| Flow step |
Event | Flow Step Number |
|
| Flow step number |
Event | Page URL |
|
| URL where event happened |
Event | Text Answer |
|
| Free-form response |
Event | Number Answer |
|
| Numeric response (NPS, ratings) |
Event | List Answer |
|
| Multi-select answers |
Event | Viewport Width |
|
| Browser width |
Event | Viewport Height |
|
| Browser height |
How date attributes populate
First Seen / Last Seen (
first_seen_at/last_seen_at) are set automatically by Userflow. First Seen is stamped the first time a user is identified; Last Seen updates on each later identify/interaction. You don't send these.Signed Up (
signed_up_at) is supplied by you — pass it in youruserflow.identify()call as an ISO 8601 datetime string (for example,new Date(...).toISOString()). If you don't send it, it stays empty.
Querying these dates
Use them anywhere attribute conditions appear — segments, auto-start conditions, and analytics filters — with operators like "is before / is after / in the last N days". Example: a segment of users last seen more than 30 days ago (useful for re-engagement) filters on last_seen_at "is before" 30 days ago.
Attribute limits
Userflow enforces three hard limits on attributes. They apply to user and company attributes alike.
Limit | Value |
|---|---|
Attributes per user or company | 1,500 |
Characters per attribute value | 5,000 |
Characters per attribute name | 100 |
List attributes are measured as a whole. The 5,000-character limit is the combined length of every item in the list, not the length of each item. A list of 200 codes at 30 characters each comes to 6,000 characters and will hit the limit, even though no single item is anywhere near it.
If you are modelling something that grows over time, such as a per-user entitlements or permissions list, size it against these numbers before you build on it.