User and filter definitions within mtribes.*
This article details User and filter definitions within mtribes.
|User||An identified/known/non-anonymous user (signed-in).|
|Visitor||An anonymous user (non-signed in).|
Key user insights
|Active user||User has had an event (identify/sdk) within the last 30 days; x < 30 days.|
|New||User has had their first ever event within the last 30 days.|
|At risk||User has not had an event within the last 30 days, but has had an event within the last 60 days; 30 < x < 60 days.|
|Lost||User has not had an event within the last 60 days; x > 60 days.|
|Date property||Applies to anonymous||Source of truth||Definition|
||When the system first recognizes any user through any path, a record is created. CreatedAt is the time of record creation.|
||When the system first recognizes a non-anonymous user through the identified event, JoinedAt is set to the current time. However, if the user was created through the management API, this value can be set to whatever the caller desires. At a later point in time, this property can also be overridden through the management API.|
||When the system first recognizes a non-anonymous user through any path, KnownAt is set to the current time.|
|LastActiveAt / LastSeen||Y||
||When a new identify event is available for any user, LastActiveAt is set to the current time regardless of whether the record already exists.|
- Where BOTH DataPipeline and User service are listed, both maintain their own copy of the date. This will lead to slight differences in date.
- Where ONLY User service is listed, DataPipeline needs to open the identify event, find the property AND save the property to its record.