event

Attribute Name	Data Type	Description
ID	string	The unique identifier of the event.
TenantID	int	The unique identifier of the client environment.
SourceSystemID	string	The unique identifier of the upstream source system.
SourceSubSystemID	string	The unique identifier of the source sub-system.
Cookie	string	The unique identifier of the person triggering the event. For web or app-related events, use an actual cookieID or mobiledeviceID of the visitor, prefixed with an indication of the source system. This attribute is used only for web or app-related events.
SessionID	string	The unique identifier of the session.
Variables	string	It keeps DeviceType, Browser, OperatingSystem, BrowserType values (Unparsed Channel Info, and UserAgent) Acquia splits and assigns to the corresponding column.
Type	string	The type of the event. Standard email event values for this attribute are: `emailSend` `emailOpen` `emailClick` `emailBounce` `emailSubscribe`, `emailUnsubscribe` Standard web event values for this attribute are: `productBrowsed` `categoryBrowsed` `onsiteSearch` `cartUpdated` `checkout` You can also use custom event values. To configure them, contact Acquia Support. The following are some examples of custom event values: `emailNotSent` `brandBrowsed` `recommendationClicked` `directMailSend` `marketingCall` `smsClick` `surveyFilled`
Category	string	The category of the event.
Subtype	string	This attribute stores the type of bounce for email bounce events. For example, hard or soft.
EventTimeStamp	string	The date and time at which the event occurred.
SourceCustomerNumber	string	The unique identifier of the customer that triggered the event. Note that you must provide one of the following two identifiers for CDP to load the events in the platform: Email SourceCustomerNumber
CustomerID	string	The unique identifier of the customer.
Email	string	The email address of the customer that triggered this event. Note that you must provide one of the following two identifiers for Acquia CDP to load the events in the platform: Email SourceCustomerNumber Those should additionally tie to actual records in the Customer feeds that you send to CDP. Otherwise, the events will not be loaded.
Language	string	The language of the webpage where the event was triggered. This attribute is applicable mostly to web events. Accept-Language: en-US,en;q=0.9,tr;q=0.8
IPAddress	string	The IP address from where the event was triggered.
Referer	string	This attribute stores the URL of the page that leads the visitor to the current page on which the event was triggered. This attribute is applicable to only web events.
Country	string	The country from which the event was triggered.
OS	string	The device OS from where the event was triggered.
Georegion	string	The geo-region from where the event was triggered.
Geocity	string	The geo-city from where the event was triggered.
GeoPostalCode	string	The geo-postal code from where the event was triggered.
GeoLatitude	string	The geo-latitude from where the event was triggered.
GeoLongitude	string	The geo-longitude from where the event was triggered.
GeoAreaCode	string	The geo-area code from where the event was triggered.
GeoOrganization	string	The geo-organization from where the event was triggered.
GeoContinent	string	The geo-continent code from where the event was triggered.
SourceListNumber	string	The identifier of the list number of the event.
LinkName	string	The link name of the event.
URL	string	This attribute stores the URL of the current page where this event was triggered. This attribute is applicable to only web events.
SourceMessageNumber	string	The message that triggered this event for the customer. For email events: this is the message that was sent, opened, clicked, or bounced that lead to the subscription or unsubscription of the customer. For other marketing campaigns, such as email and SMS, this is the message that was sent, or that was viewed by the customer and on which the event was triggered. This is important for reporting and tying events to the marketing efforts that triggered them.
MessageID	string	The unique identifier of the message.
BodyType	string	The body type of the email campaign. For example, HTML and Text.
Anonymous	boolean	The purpose of the column is to identify the known and unknown events but Event tables keep only the known events so the column is not used.
SourceProductNumber	string	The identifier of the product tied to the event. This attribute is applicable to web events.
ProductID	string	The unique identifier of the product.
SourceProductCategoryNumber	string	The identifier of the category tied to the event. This attribute is applicable to web events.
ProductCategoryID	string	The unique identifier of the product category.
BrandId	string	The unique identifier of the brand.
SourceTransactionNumber	string	The identifier of the transaction tied to the event. This attribute is applicable to web events.
TransactionID	string	The unique identifier of the transaction associated with the event.
ContainerId	string	The container ID of the event.
SegmentId	string	The unique identifier of the segment.
UserClient	string	This is the client used when the event was triggered. This is applicable for web-like events where differentiating between the website and a mobile application is relevant for marketing campaigns. This is automatically populated when you use the CDP JS SDK on your website. However, you must populate the value when using the Tracker API. The possible values are: A for applications such as mobile applications B for browser U for unknown
CustomerState	string	Lead prospect customer.
Browser	string	The browser on which the event was triggered. This is applicable for web events. This is automatically populated when you use the CDP JS SDK on your website. However, you must populate the value when using the Tracker API.
BrowserType	string	The browser type on which the event was triggered. This is applicable for web events. This is automatically populated when using the JS SDK but you should populate it when using the Tracker API (if you need to use it later for marketing campaigns). The list of standard values supported by CDP is MOBILE_BROWSER, WEB_BROWSER, ROBOT, UNKNOWN, TOOL.
OperatingSystem	string	The operating system of the device on which the event was triggered. This is applicable for web events. This is automatically populated when you use the CDP JS SDK on your website. However, you must populate the value when using the Tracker API.
DeviceType	string	The type of device used to trigger the event. This is applicable for web events. This is automatically populated when you use the CDP JS SDK on your website. However, you must populate the value when using the Tracker API. The supported values are: COMPUTER: for laptops and desktops. MOBILE: for mobile phones. TABLET: for tablets. GAME_CONSOLE: for game consoles. DMR: for digital media receivers. WEARABLE: for wearable devices. UNKNOWN: for the rest.
RowCreated	timestamp	The time when the event was first triggered.
RowModified	timestamp	The time when the event was last modified.
Batch	string	When the promotion was last modified in CDP. This is used for bucketing the ingestion of records into CDP.
Domain	string	The name of the domain on which the event was triggered. This is applicable for web events. This is automatically populated when you use the CDP JS SDK on your website. However, you must populate the value when using the Tracker API.
SearchTerm	string	The term that was used during an onsite search event.
Source	string	The source(file name) of the data, which is auto-assigned by CDP.
RealtimeRequestNumber	string	A unique identifier(guid) that is assigned by the KAFKA consumer. All records that are in the same payload/message share the same RRN. It is not for the records that are loaded.
RowProcessed	timestamp	The time when the record was processed by CDP.

Loading...

Did not find what you were looking for?