# Activities

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.

You can upload one or more of these tables:

* Online activities (customer in login area on your website / click in email)
* Inbound activities (customer calls call center, letters and emails from customer)
* Outbound activities (print mailings, catalogs, calls from a call center)
* Payment activities (customer pays an invoice, receives a dunning level, is referred to collections)

{% hint style="info" %}
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.
{% endhint %}

<table><thead><tr><th width="162">Field Name</th><th width="125">Data Type</th><th>Example</th><th>Description</th></tr></thead><tbody><tr><td>*customer_id</td><td>string</td><td>e131498</td><td>The Customer ID; Unique identifier used for merging all tables.</td></tr><tr><td>*activity_timestamp</td><td>date</td><td>2015-01-13</td><td>Date and (optionally) Time of the Transaction</td></tr><tr><td>*activity_type</td><td>string</td><td>CartAdd<br>CartCancel</td><td>Used to generate patterns for the most common types.</td></tr><tr><td>activity_subtype</td><td>string</td><td>Trousers Black<br>4RTR3022DS</td><td>Can be used to generate additional patterns.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.crossengage.io/predictions-platform/data-model/activities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.