Event data
When segmenting by an event or browsing event data, you first choose the event type (subgroup), then specific fields for that type. The subgroups that display for selection are the event types that your organization sends to Sitecore CDP through the Stream API. Event types can include standard or custom event types that your organization sends to Sitecore CDP.
After you select a subgroup, additional fields for the selected event type (subgroup) display. This can include core fields as well as additional event data that is sent to Sitecore CDP using the "ext" object. This enables you to pass additional event data to Sitecore CDP and segment by that data or view its details.
Event types include, and are not limited to, the following. Your company might have additional custom event types:
-
Add
-
Add Consumers
-
Add Contacts
-
Checkout
-
Confirm
-
Identity
-
Order Checkout
-
Payment
-
Purchase
-
Search
-
Tracking
-
Update
-
View
Data availability in segments
Sitecore CDP runs a nightly processing service that provides the most recent guest data to segments. The service runs at 00:00 UTC. This means that any data used to create a segment is based on data up to the last time the service ran. For example, if you create a segment of customers with abandoned carts, Sitecore CDP will include customers with abandoned carts up to 00:00 UTC. Any customers with abandoned carts after this time will be available for segments when the service runs again at 00:00 UTC.
The daily processing service can also affect when certain values display in the segment builder for selection. For example, if you want to create a segment that uses a new event type named ADD_TO_WISHLIST, it won't display as a value for selection in the UI until you have at least one guest with an ADD_TO_WISHLIST event that was raised before the last processing service ran, 00:00 UTC.
The following table includes some of the fields that are available for use in event-based segmentation or the data browser feature for the selected event type. The available fields depend on the type of event selected. In addition, your organization might have additional fields.
|
Attribute |
Description |
Example |
|---|---|---|
|
Channel |
The channel on which the event was captured. |
"WEB", "MOBILE_WEB", "MOBILE_APP" |
|
Currency |
The organization’s currency code associated with the event. |
"EUR", "NZD", "USD" |
|
Language |
The language of the event. |
"EN", "FR", "DE" |
|
Page |
The webpage where the event was captured. |
"trending_styles" |
|
Point of Sale |
The point of sale associated with the event. |
"myretailsite.com", "bestretailsite.co.uk" |
|
Created At |
The date and time when the event was captured. |
"Is in the past 7 days" |
|
Date of Birth |
For identity events, the date of birth of the guest included in the event. |
1975-01-01T00:00 |
|
|
The email address of the guest included in the event. | |
|
First Name |
For identity events, the first name of the guest included in the event. |
Alexis |
|
Last Name |
For identity events, the last name of the guest included in the event. |
Barry |
|
Gender |
For identity events, the gender of the guest included in the event. |
unknown |
|
Payment Type |
The type of payment associated with the event. |
CARD |
|
Status |
The status of the event. |
PURCHASED |
|
Category |
For tracking events, the status of the event. Possible values are EXECUTED and FAILED. |
EXECUTED |