List of tracking events

List of tracking events

Customer Data Platform (CDP) provides the list of tracking events to help you seamlessly track and analyze visitor activities through a set of web events.

Acquia WebTag provides a default list of events that must be implemented on your website to enable CDP to capture and track visitor activities throughout the visitors' journey.

Event types

The following are types of tracking events:

• Default events: Acquia recommends you to implement the following list of tracking events to enrich CDP data:

  Event type	Use cases
  login	Description: Tracks the visitors who log in to your website so that you can understand user engagement and return frequency. Trigger the event: When the visitor logs in to your site. Expected payload: One event with at least a customer identifier, SourceCustomerNumber or Email.
  productBrowsed	Description: Tracks the products viewed by visitors so that you can get insights into product popularity and visitor preferences. Trigger the event: When the visitor views the details of a product either on a product detail page or through a Quick View functionality. Expected payload: One event for each product viewed with a Targets set that includes the productId attribute set.
  categoryBrowsed	Description: Tracks the product categories viewed by visitors so that you can identify popular categories or those categories attracting repeat visits. Trigger the event: When the visitor views a specific product category page. Expected payload: One event for each category viewed with the SourceProductCategoryNumber attribute set.
  cartUpdated	Description: Tracks the content of the shopping cart of visitors so that you can monitor updates to the carts and capture purchasing intent through product additions or removals. Trigger the event: When an item is added or removed from the cart, or when the cart is cleared. CDP does not consider the quantity in the cart for each item. CDP considers an item “added” if its quantity in the cart is greater than 0, and considers it “removed” if the quantity is 0. Expected payload: One event per cart update with as many Targets as the number of distinct products in the cart, with the corresponding SourceProductNumber attribute set. To represent a cart that is cleared, send a unique cartUpdated event with one single Target that has the SourceProductNumber attribute set to NULL.
  checkout	Description: Tracks the orders placed by visitors so that you can capture completed purchases and understand buying behavior and transaction volume. Trigger the event: When the visitor pays and confirms the transaction. Expected payload: One event for the checkout with or without a Transaction, with the appropriate fields set (SourceTransactionNumber), and any number of Targets for the related TransactionItems, that is, products included in the transaction, with the appropriate fields set (SourceTransactionItemNumber).
  onsiteSearch	Description: Tracks the search terms used by visitors so that you can capture initiated searches and understand product interest, improve search functionality, and analyze trending keywords. Trigger the event: When the visitor starts a search on your website. Expected payload: One event with the SearchTerm attribute set.
  logout	Description: Tracks the visitors who log out of your website so that you can measure session lengths and understand engagement frequency. Trigger the event: When the visitor logs out of their account on your website. Expected payload: One event with or without a customer identifier (SourceCustomerNumber or Email).

• Custom events: Custom events can be added if default events are too limited to capture specific visitor behaviors for enhancement in CDP.

  To add custom events, contact Acquia Support.

Trigger the event: When the visitor views a specific product category page.

Expected payload: One event for each category viewed with the SourceProductCategoryNumber attribute set.