You must be on our CXDP account package to access this feature.
Any event data you import to Dotdigital is stored as an Insight data collection for use in segmentation and personalization.
Events
Each event must be associated with an existing contact within Dotdigital. You can use any contact identifier type you want, including Custom identifiers.
Each event has:
| Field | Description |
|---|---|
| type | The notional type of the event which is displayed on the contact's timeline on the Single customer view. |
| id | A unique ID for the event, for example, a GUID. |
| eventTimestamp | The UTC date and time the event occurred in ISO 8601 format. |
| timelineDetails.summary | A description of the event to be shown in the contact's timeline on the Single customer view. |
| eventData | The actual data for the event as a JSON object. |
Insight data for events
We create a contact-scoped Insight data collection for each event type raised.
The collection name is the event's type, with any non-alphanumeric characters replaced by _ .
The type of an event must not conflict with the existing standard types of:
- cartInsight
- catalog
- consentInsight
- easyEditorExtensions
- nostoEmailCampaigns
- orders
- productCategories
- webInsight
- wishList
For example:
"Holiday booking" becomes "Holiday_booking"
The Insight data collection type is event
The structure of the records in the collection:
| Field | Data type | Description |
|---|---|---|
| id | string | The unique ID of the event. |
| event | string | The event type. |
| created_date | string | The time and date in UTC ISO-8601 format that the event occurred. |
| event_data | object | The event data. |
You can use these Insight data collections of events in your segment rules and for personalization using Liquid script. Learn more in our Help Centre.