Events

Captures every confirmed removal of one or more product units from the cart, aligned to GA4 remove_from_cart and Adobe scRemove. Source event for Cart Removals and cart-edit analysis.

Records a reserve-and-collect request once the store system accepts it, confirming the hold and returning a reservation_id; no online payment. Rejected requests are not recorded; collection is order-pickup.

Return Initiated fires when a customer successfully submits a return request against a completed order through the self-service returns portal (Shopify, Salesforce Commerce Cloud, Loop, Narvar), carrying the order reference, the returned line items, the stated reason, the return method and the requested resolution (refund, exchange or store credit). It is the authoritative numerator input for return rate and the leading signal of revenue at risk, reported by initiation date well before the downstream Refund Issued event confirms the financial reversal.

Standard select_content event with content_type = search_suggestion, fired when a shopper picks a query, product or category from the search typeahead. A typed query submitted without a pick is a Site Search.

Session Start is the automatically collected event that opens a visit, firing on the first interaction a user has with the site or app after the inactivity timeout has elapsed. Every session-scoped acquisition report is counted from it — channel grouping, source/medium, campaign and landing page for the visit are resolved from the traffic context present on this event, and all downstream browsing, cart and purchase activity is attributed to the session it creates.

Measures each explicit customer, partner, or agent action that starts a shipment-booking workflow or creates a new booking draft. It captures booking intent and shipment context at initiation, regardless of whether the booking is subsequently completed, abandoned, rejected, or cancelled.

This event tracks notifications sent to customers when their shipment is delayed, capturing the impact on customer experience and operational efficiency.

E-commerce specialisation of Notification Open: fires when a customer opens a transactional shipping-lifecycle message (shipping confirmation, out for delivery, delivered, pickup ready or delay) sent by email, SMS or push, as recorded by the ESP or push provider and stitched to the originating order through transaction_id. It is the base engagement signal for post-purchase communications and shows whether delivery updates actually reach customers before they contact support or check order status themselves.

Records each successful display of shipment-tracking details to a customer or authorized business user, including the shipment's latest status, delivery estimate, carrier, and exception state. It measures tracking engagement at the event, session, user, shipment, and channel levels so teams can identify repeat status checks, delivery concerns, and gaps in tracking-data freshness.

Site Search is the standard search event, recorded each time a shopper executes a query against the storefront's internal product search, whether by submitting the search box, pressing enter or selecting an autocomplete suggestion. It carries search_term, search_type, search_source and search_results_count, and it is the single source for Site Searches, Internal Search Term, Zero-Results Search Rate and Search-to-Purchase Conversion Rate. It is the canonical search event; Property Search is its Real Estate variant, which keeps the same search event and adds location and radius parameters.

Custom sort_apply event, fired when a shopper changes the sort order of a product listing or search results page. It is the sort counterpart of filter_apply (Filter Applied).

Subscription Start captures the moment a customer activates a paid recurring commerce plan — subscribe-and-save, replenishment, curated box or paid membership — at the point the first billing authorization succeeds and a subscription contract comes into existence. It deliberately excludes email and newsletter opt-ins that reuse the same unified subscribe event in the acquisition sub-domain: a row qualifies only when it carries a subscription_id and a recurring charge, so list growth is never counted as commerce revenue.