Two Datasets
Aampe needs two datasets to function- A table of users along with important user properties. Any properties included will be available within the audience builder.
- A table of user events. This table powers agentic learning and is also available within the audience builder.
User Properties
Following is the data model Aampe uses to store properties about users.| Column Name | Data Type | Description |
|---|---|---|
| contact_id | String | A unique user identifier |
| country | String | Required |
| <property_1> (e.g language) | … | … |
| <property_n> (e.g subscription_status) | ||
| push_token | String (Optional) | Token of the user that will be used to send out push-messages, if different from contact_id |
| phone_number | String (Optional) | Number to be used to send out SMS and whatsapp messages, if different from contact_id |
| email_address | String (Optional) | Email of the user that will be used to send out email messages, if different from contact_id |
See this page for industry-specific examples of user attributes
Events
| Column Name | Data type | Description |
|---|---|---|
| contact_id | String | A unique user identifier |
| timestamp | Timestamp | The timestamp of when the event happened in UTC |
| event_name | String | An event name corresponding to the event that was triggered |
| event_instance_id | String (Optional) | An event identifier |
| timezone | String (Optional) | Local timezone of the user/event - locale |
| metadata | JSON (Optional) | Any useful data points about the event |
See this page for industry-specific examples of events and event properties