eCommerce events

Overview

This article lists all eCommerce events supported by the ConvertPlus shopping cart.

The ConvertPlus cart caters to the following Web Metrics solutions:

  • Google Universal Analytics

  • Google Tag Manager (with Universal Analytics)

  • Adobe Dynamic Tag Manager

  • Google Analytics 4

  • Google Tag Manager (with GA4)

Each solution handles enhanced events triggered by the ConvertPlus Cart differently. Because each Web Metrics solution prefers its data arranged in a particular way, the document describes each web solution separately, alongside a distinct section for the custom cartUpdated event.

The parameters below are used to track eCommerce events triggered by the ConvertPlus and InLine carts.

Availability

Merchant tracking is available for all 2Checkout accounts.

eCommerce events grouped by Web Metric

Google Universal Analytics

The Google Universal Analytics DataLayer differs from Google Tag Manager and Adobe's Dynamic Tag Manager in that it is an array of arrays. Each event pushed in the DataLayer is an array with various indexes, based on the type of the triggered event:

  • The first element of the array determines the type of payload added to the DataLayer (it can either be event or config).

  • The second element of the array determines the sub-type of the first element.

  • The third element is an object with the actual data/payload.

Event
Triggered by
Notes
Example

begin_checkout

LOAD_CART (load-cart)

- the item’s price is the item’s net discounted price, taken from the item’s key named itemNetDiscountedPrice - the item’s price should not be calculated with the item’s quantity - the item’s coupon key is only present if a coupon is applied - the order’s coupon key is only present if an order coupon is applied

```json

[

"event",

"begin_checkout",

{

} ]

The event key will always be populated with the cartUpdated value as this is the name of the custom event. Alongside the event key, you can find any number of custom keys; their names and values vary and depend on the action the user performed in the cart.

The ConvertPlus shopping cart implements an event buffer.

When a shopper performs an action in the cart, the cart triggers many internal events that can lead to many small updates. To prevent the DataLayer from being spammed by unnecessary small updates, the event buffer collects events within a short time window (1 second at the time of writing), keeps only the newest values, and releases them in bigger chunks.

The custom keys used by the cartUpdated event are as follows:

Event
Triggered by
Values
Notes
Example

PAGE_NAME

- LOAD_CART (load-cart) - LOAD_PAGE (load-page) - PLACE_ORDER (place-order:success)

- checkout - finish - retry

```json

{ "PAGE_NAME": "finish" }

Last updated

Was this helpful?