To improve model and forecasting quality, you can upload additional tables that contain specific activities and interactions with your customers. These tables must each contain at least a unique customer ID, a timestamp, and an activity type. Additionally, an activity_id can be passed that links the activity to a specific action. However, this data is not required for an initial well working model and is therefore optional.
Note
In order to make use of these activities in the modelling process, it is important that they are stored in the so-called event format (just like transactions). This means that each row in an activity table describes exactly one 'event' at a time with a customer.
| Field Name | Data Type | Example | Description |
|---|---|---|---|
| *customer_id | String | e131498 | The Customer ID; Unique identifier used for merging all tables. |
|
*activity_timestamp |
Date |
2010-12-21 |
Date and (optionally) Time of the Transaction |
| *activity_type | String | CartAdd CartCancel |
Used to generate patterns for the most common types. |
|
activity_subtype |
String | Trousers Black 4RTR3022DS |
Can be used to generate additional patterns. |