There are several ways to set custom data in FullStory. Each of them can take a unique set of properties. For instance, a custom field is one that you define that FullStory saves, displays, and that can be used in search.
For example, pricingPlan_str
is a custom field, as you can see by the formulation of its name: all custom field names have an underscore and suffix. More specifically, custom fields must be named using the pattern ident_type, where ident is a sequence of alphanumeric characters A-Z, a-z, or 0-9 and type is a short suffix that denotes the type of the field, which can be any of these. Custom field names must start with an alphabetic character (A-Z or a-z).
See more examples below:
Type suffix | Meaning | Example |
---|---|---|
str |
string |
{ "nickname_str": "boo" } |
int |
integer |
{ "PasswordResets_int": 49 } |
real |
real |
{ "amtAbandonedInCart_real": 3.84 } |
date |
date in ISO-8601 UTC format |
{ "initialSignupDate_date": |
bool |
boolean |
{ |
strs |
list of strings |
{ |
ints |
list of integers |
{ |
reals |
list of reals |
{ |
dates |
list of ISO-8601 UTC format dates |
{ |
bools |
list of booleans |
{ |

Learn more about common troubleshooting tips for custom user data.