Capture cart events

This is for:

Developer

This article explains how to capture cart update events and send the information to Coveo along with the product information using the Coveo UA library.

When to send a cart event

Anytime the content of a cart is modified by a user, a cart event must be sent to Coveo, together with the product information payload. Cart content modifications may include the addition or removal of products, or changes in quantity of existing products in the cart. Depending on your site’s design, cart events can be triggered from different pages, such as:

  • From a page which shows the current content of a visitor's shopping cart

  • From an individual product’s detail page (PDP)

  • From a search results page

  • From a listing page

  • From a recommendations component

Warning

You must send an additional click event if the cart is directly modified from the search results page, listings page or recommendations component.

The following image is from the cart page view of the online sporting goods store Barca Sports, which provides users with the ability to modify the contents of their cart by increasing or decreasing the quantity of items. Minimally, you would want to log product information and the quantity added or removed in the product data payload. We calculate quantity as the increase or decrease in value, and not the new total amount. For example, if a client changes the quantity of the item in cart from 1 to 2, the quantity to pass in the cart event is 1.

Barca cart view

Capture a cart modification event using Coveo UA library commands

When the content of a cart is modified, you must run the following javascript code which contains Coveo UA library commands.

coveoua('ec:addProduct', {
    'id': 'SP00579_00009', 1
    'name': 'Whitetraveler DryBag',
    'category': 'Accessories/Bags/Drybags',
    'price': 96, 2
    'quantity': 1, 3
});

coveoua('ec:setAction', '<ACTION_TYPE>'); 4
coveoua('send', 'event'); 5
1 Add product data payload
2 The currencyCode for the item’s price is set as a global field when initializing the analytics library
3 The number of units added by this event
4 Set the action type
5 Send the event

Add product data payload

The ec:addProduct command includes the relevant product data in the event you’re about to send. In this case the product dataset contains the product id, name, category, price and quantity.

Cart product dataset requirements

The following table lists the fields sent along with the event and the solutions that leverage them. Search, Listings, and Recs columns refer to whether the ML that powers those solutions needs those data points. The Reporting column is for general reporting purposes that encompasses all solutions. For more information on these fields, including other recommended and optional fields that can be sent, refer to the Product fields reference.

Field Priority Search Listings Recs Reporting

id

Required

check

check

check

check

name

Required

check

category

Required

check

check

check

check

quantity

Required

check

check

price

Required

check

check

check

check

brand

Recommended

check

check

check

check

group1

Recommended

check

check

check

check

variant

Recommended

check

  1. Only needed when you need to setup ML to recommend at the group level.

Note

When you structure your items with product grouping, ensure you add the group field to the product dataset in all sent events.

Using the recommended approach for product data, you would find, for example, "ec_item_group_id": "001" and "productid": "001-red" in the product dataset payload. The group can be represented by any string as long as it’s consistent, in other words, the same value 001, is used on the different products in the group.

Refer to Product data fields reference for more information.

Set the action type

The ec:setAction command is used to specify which <ACTION_TYPE> is to be performed on this data. In the case above, we want to add the product data payload. To capture when there’s a decrease in cart items, you would use remove.

Send the event

Finally, the send command sends an event with a given payload to the Coveo analytics endpoint.

Sending an additional click event

When managing cart modifications events, with Coveo-powered components, adding products to the cart directly from search results, product listings, or recommendation carousels requires sending two events:

  1. Click event

  2. Cart modification event

Each query, whether it generates search results, displays product listings, or showcases recommendations, has a unique searchUid associated with it. For precise attribution of cart modifications, it’s crucial to include this searchUid in the click event. This click event is then sent along with the cart modification event.

When you send click events using Headless or Atomic, you don’t need to worry about including the searchUid in the event. This process is handled automatically for you.

Coveo UA library

However, if you’re using the Coveo UA library to log click events, you’ll need to pass the searchUid value in the payload of the click event.

For information on extracting the searchUid, see Extract the searchUid.

The following example showcases a function that sends a click event using the Coveo UA library, followed by a cart modification event:

const logClickAndAddToCart = (result) => {
    coveoua('send', 'click',{ 1
      actionCause: 'documentOpen',
      anonymous: true,
      documentPosition: 1,
      documentTitle: result.title,
      documentUrl: result.clickUri,
      originLevel1: 'Search',
      searchQueryUid: engine.state.search.response.searchUid, 2
      sourceName: result.raw.source,
      customData: {
          contentIDKey: 'permanentid',
          contentIDValue: result.raw.ec_productid,
      },
    });

    coveoua('ec:addProduct', { 3
      'id': result.raw.ec_productid,
      'name': result.raw.ec_name,
      'brand': result.raw.ec_brand,
      'category': result.raw.ec_category,
      'price': result.raw.ec_price,
      'quantity': 1,
    });

    coveoua('ec:setAction', 'add');
    coveoua('send', 'event');
}
1 Send a click event using the Coveo UA library, specifying the required payload fields.
2 Extract the value of the searchUid field from the Headless engine to ensure correct attribution.
3 Capture a cart modification event by adding the product payload, setting the action type, and sending the event.
Note

If you’re currently pairing the searchUid with the cart event, we suggest transitioning to the above-described approach of sending a click event alongside a cart event.

The added advantage of this method is two-fold. First, it provides a more exact representation of clickthrough rates, especially for stores that have 'add to cart' buttons on their listing pages. Second, it bolsters the efficacy of our machine learning models, as these models leverage click events as valuable data points.

We will continue to support pairing the searchUid with the cart event for existing implementations, however we recommend transitioning to the above-described approach of sending a click event alongside a cart event.

coveoua('ec:addProduct', {
    'id': '037212201_DKBL',
    'name': 'backland 120',
    'category': 'sport/ski_mountaineering/boots',
    'price': 447.20,
    'list': 'coveo:search:<QUERY-SEARCH-UID>', 1
    'quantity': 1
});
coveoua('ec:setAction', '<ACTION_TYPE>');
coveoua('send', 'event');
1 <QUERY-SEARCH-UID> must be replaced with the value of the searchUid that generated the search result list or listing page from which the product was added to the cart.

For information on how to extract the searchUid, see Extract the searchUid.

Set the action type

The ec:setAction command is used to specify which <ACTION_TYPE> is to be performed on this data. In the case above, we want to add the product data payload. To capture when there’s a decrease in cart items, you would use remove.

Send the event

Finally, the send command sends an event with a given payload to the Coveo analytics endpoint.

Cart event validation

When the cart event is logged, use the developer tools for client-side request verification to inspect your visit to ensure everything done using the UI is captured as a set of consistent and coherent events properly mapped to their Coveo UA parameters. This must occur after the implementation is applied.

Inspect the cart event through the network browser and ensure it satisfies the following:

Barca cart view network browser

1 The client ID (cid) is consistent with other events sent on the page.

2 The currency matches what’s being displayed to the visitor.

3 Confirm the event is an addition (add) or removal (remove) from cart.

4 Category values should use / to represent hierarchies and use | to represent multiple values.

5 The product ID matches what’s set in the catalog (same is true if sending group and variant).

6 The quantity reflects the change in cart items (for example, if a visitor already has a product in their cart and they add another 2 identical items, this will take the total amount in the cart to 3, so quantity in the event is set to 2).

Note

Adding to cart directly from a search results page, listings or recs carousel should also send an additional click event with a search ID that matches that of the corresponding search.

Event field data mapping

The following table shows how the client-side fields are mapped to parameters in the analytics request sent to Coveo UA. You need to ensure this information is properly passed in the payload.

Field name Description Parameter

currencyCode

The currency of the product being purchased

cu

id

Identifier for the base product

pr1id

category

The product category

pr1ca

price

The price shown to the user (including discounts)

pr1pr

brand

The product brand

pr1br

name

The product name

pr1nm

group

The product group ID

pr1group

variant

The exact SKU of the variant selected

pr1va

quantity

Quantity added or removed

pr1qt

For a complete list of parameters that can be sent in the event, see ​​Log Collect events.

Note

Parameters such as pr1ca can be more generally referred to as prNca, where N represents an interaction involving more than one product.