In this article, we’re listing down some of the most important property types that ZetaHub supports.
String
- Holds – any single string of data
- Constraints – none enforced
- Activity Name – not used
- Activity Attr Name – not used
- Example Uses
- first_name
- user_id
- favorite_color
- zip_code
Number
- Holds – any single numeric data
- Constraints – max value: 9007199254740991 (enforced by JavaScript), generally this data type should only be used for values when you want to be able to do math or number logic on them.
- Activity Name – not used
- Activity Attr Name – not used
- Example Uses
- age
- latitude
Date
- Holds – any single date data
- Constraints – ISO8601 format
- Activity Name – not used
- Activity Attr Name – not used
- Example Uses
- birth_date
- sign_up_date
- purchase_date
List
- Holds – multiple data points, collected from activity attributes
- Constraints
- can hold strings, numeric, and dates
- List mgmt tools have to be turned on in a per user basis
- Ability to sum/average/etc. within the segmentation tool is turned on in the UI on a user by user basis
- To upload lists via .csv file, you can replicate the same user into multiple rows with the value of the list property being different for each of the rows. For example, if you want to add the values, Harvard, Stanford, MIT into a list property called schools, you should first create this property and mark it of type list, then upload the file with three rows, where the user_id, email, first_name, last_name etc is all same but the schools property has the three different values.
- Activity Name – used (ie. purchase)
- Activity Attr Name – used (ie. order_total)
- Example Uses
- order_totals (can be used to calculate LTV, AOV, etc)
- shopping_cart_items (used to hold all items currently in your shopping cart)
Counter
- Holds – a single integer, automatically increments on a specified activity
- Constraints – unknown
- Activity Name – used (ie. purchase)
- Activity Attr Name – not used
- Example Uses
- order_count (counts every purchase activity for each user)
- view_count (count every view activity for each user)
Last Occurrence
- Holds – a single date value, automatically updates on a specified activity
- Constraints – ISO8601 format
- Activity Name – used (ie. purchase)
- Activity Attr Name – not used
- Example Uses
- last_purchase (date of last purchase activity for each user)
- last_view (date of last view activity for each user)
Recur Date Every Year
- Holds – a single month/day date value (with the year)
- Constraints
- ISO8601 format
- Use the full date including year
- When segmenting select your user property and use the “within last”, “within next”, “not within last”, or “not within next” operators
- Activity Name – not used
- Activity Attr Name – not used
- Example Uses
- renewal_date
- birthday
Recur Date Every Month
- Holds – a single day date value (without the month and year)
- Constraints
- ISO8601 format
- Use the full date including month and year
- When segmenting select your user property and use the “within last”, “within next”, “not within last”, or “not within next” operators
- Activity Name – not used
- Activity Attr Name – not used
- Example Uses
- billing_date
- payment_reminder_date