activity
The activity table is used to simulate historical activity for a participant. Each row in the activity table describes the unique combination of a participant and all dates for which that participant has been active.
Table Schema
| Name | Type | Description |
|---|---|---|
| personid | VARCHAR |
Internal identifier to specify a unique instance of a person. This column is used to partition data tables in the Bulk Data API and should be included on all table joins. Use personid to join to tables in other models within the Bulk Data API. |
| participantkey | VARCHAR |
Internal identifier to specify a unique instance of a participant in an RKStudio project. Key relationship with the participant table. |
| activitykey | VARCHAR |
Primary key. A unique, auto-generated internal identifier to specify a unique daily instance of participant activity. |
| date | TIMESTAMP |
The date of the activity for this participant. |
| dayssincelast | INTEGER |
The number of days between the last known date this Participant was active and this activity date. For an activity date of today, this value is exactly equal to the number of days between last activity date of the Participant and today. For all other dates, the value is smaller than the number of days between the last activity date and today. |
| incompletetasks | INTEGER |
The number of incomplete tasks that were open as of this activity date. |
| retainedanyoflast3 | BOOLEAN |
True if the participant responded to the at least one survey issued to them out of the last 3 on this date. |
| retainedanyoflast5 | BOOLEAN |
True if the participant responded to the at least one survey issued to them out of the last 5 on this date. |
| retainedindenominator | BOOLEAN |
True if the participant should be considered in the denominator for retention on this activity date based on their consent date. |
| retainedlast | BOOLEAN |
True if the participant responded to the last survey issued to them on this date. |
