Dimensions

Ordinal of the carrier delivery attempt on a shipment: 1, 2, 3 or 4+, read from attempted and delivered scans. Splits delivery outcomes into first-attempt success versus redelivery.

Proof-of-delivery method recorded at the carrier's delivered scan: signature, photo, PIN code, parcel locker, access point or none. One value per shipment, read from Order Management, not a web event.

Carrier-reported reason a shipment stalled or failed in transit: weather, address issue, damaged, recipient unavailable, held at facility. Used to split failed deliveries by root cause.

The specific geographic address or coordinates where goods are delivered to the customer. It is used to track and optimize delivery routes and logistics operations.

Stage of the shipping message sent to a customer: shipped, out_for_delivery, delivered, delayed or delivery_exception. Sent as notification_type on notification_open; channel is a separate field.

Delivery Promise Date is the delivery date, or earliest-to-latest date window, committed to the customer at checkout and stored on the order, captured as delivery_promise_date (ISO 8601 date, with delivery_promise_earliest_date and delivery_promise_latest_date when the promise is a window) on add_shipping_info and purchase, and frozen at the value in force when the order is placed. It is the baseline that Shipment On-Time Delivery Rate measures actual delivery against, so operations, customer service and checkout teams can analyse promise accuracy by delivery option, fulfilment node and destination without confusing it with the carrier's later estimated delivery date, the actual delivered date or the shipping method purchased.

The geographic area where deliveries are made, categorized by predefined regions to optimize logistics operations.

Delivery SLA Status classifies each shipment as Early, On Time or Late by comparing the carrier delivery scan with the delivery promise date. Open shipments are In Transit or At Risk until the promise date passes.

Home delivery slot the customer books at checkout, stored as a governed label such as "Morning 08-12" or "Evening 18-21". Ship-to-home orders only; store pickup slots are classified by Pickup Window.

Device category is the form-factor class of the device behind an event or session (desktop, mobile, tablet or smart TV), resolved at collection time from the User-Agent string and User-Agent Client Hints and exposed as device.category in GA4 and as Mobile Device Type (XDM device.type) in Adobe Analytics. It is the main breakdown for finding device-level gaps in add-to-cart, checkout completion and order conversion, and it guides mobile checkout UX investment and device bid adjustments in paid media.

Express Checkout Method records which accelerated wallet checkout a shopper launched to place an order (apple_pay, google_pay, shop_pay, paypal_express, amazon_pay or other_express), or none when the order went through the merchant's standard multi-step checkout, captured as the express_checkout parameter on begin_checkout, add_payment_info and purchase. Where Payment Method describes the tender that settled the order, this dimension describes the checkout path, so it is the breakdown used to size how much revenue skips the address, shipping and payment forms, and to see how each wallet converts compared with standard checkout.

Facet value a shopper selects in product-list faceted navigation (Nike, Red, UK 10, 4 stars & up), always read with its filter_type. Captured as filter_value on the filter_apply event.

Financing Method classifies the primary funding source a buyer uses for a residential property purchase (Cash, Conventional, Jumbo, FHA, VA, USDA, Seller Financing, Other or Unknown), following the RESO Data Dictionary BuyerFinancing vocabulary rolled up to HMDA loan-type conventions. It lets brokerage, marketing and finance teams compare lead-to-offer conversion, contract fall-through, days to close and commission revenue by financing type, so they can steer lender partnerships, campaign mix and pipeline forecasts.

The default channel grouping of the earliest recorded session for a user within the attribution lookback window, persisted at user level so that every later event, order and revenue amount can be attributed back to how that customer was originally acquired. It is the backbone dimension for first-touch acquisition reporting and for separating marketing-sourced growth from organic and direct demand.

The basis on which an order qualified for free shipping: Threshold Met, Promotion, Member Benefit or Not Eligible. It records the offer the platform applied; Shipping Tier records service level and speed.

Fulfillment Method records the customer-visible way an order is handed over — BOPIS (buy online, pick up in store), curbside pickup, ship-to-store, ship-to-home or same-day delivery — captured at the shipping step and frozen on the completed order, making it the anchor that stitches the digital order to its offline pickup or delivery leg and the primary slice for every BOPIS and omnichannel KPI. It is deliberately narrower than Shipping Tier, which describes delivery speed and the service level the customer paid for (Standard, Expedited, Overnight), and than Fulfillment Strategy, which describes the backend sourcing decision (store-ship-from, dark store, regional distribution centre); those two are maintained as separate catalog rows and Fulfillment Method never carries their values.

Fulfillment Strategy classifies how each order line or split fulfillment unit is sourced and handed to the customer (Ship from DC, Ship from Store, Same-Day Delivery from Store, BOPIS, Curbside Pickup, Ship to Store, Drop Ship or Third-Party Fulfillment), as assigned by the order management system. It is the retailer-side execution path behind the shopper-selected Fulfillment Method and the standard breakdown for comparing omnichannel fulfillment cost, speed, cancellations and on-time performance.

Whether a gift option (gift wrap, gift message or gift receipt) was chosen at checkout, reported per order as true, false or (not set). Gift orders need different packing, pricing display and return handling.

The self-service help-center or knowledge-base article a customer viewed, keyed on a stable article ID with the title as label. Breaks down self-service views and support contact rates by article.

Industry classification of the B2B buyer account: the NAICS sector (or the SIC code / CRM industry picklist value mapped to NAICS) held on the company record in the CRM and the B2B commerce platform (Salesforce B2B Commerce Account, Adobe Commerce B2B Company, Shopify B2B Company), inherited by every buyer user, session and order tied to that account. It is the standard firmographic breakdown for comparing revenue, conversion, order value and retention across the verticals a B2B storefront sells into, and it drives sector-specific pricing, assortment and account-based marketing decisions.

The exact keyword or phrase a user enters into an on-site or in-app search function. This dimension categorizes search interactions by the user's expressed intent and is used to analyze content/product discoverability, navigation effectiveness, and demand signals within owned digital properties.

Item Category is the top level of the merchandise hierarchy on every product in the GA4 items[] array (item_category, with item_category2 to item_category5 for deeper levels), matching the Adobe Analytics product-string category and the Shopify and Salesforce Commerce catalog category. Merchandising uses it to compare item views, add-to-carts, units and item revenue across departments, and it reconciles with finance reporting only when the value comes from the product master for the item_id rather than the page breadcrumb.

The coupon code applied to a single line item, sent as coupon inside the GA4 items[] array on cart, checkout and purchase events. Order-level codes belong to the Coupon Code dimension, not this one.

Last Purchase Recency Band groups each customer by the number of calendar days between their most recent completed order and the analysis date, using default bands of 0-30, 31-90, 91-180, 181-365 and 366+ days plus No purchase for registered customers who have never ordered. It is the standard recency cut behind Klaviyo and Shopify win-back and lapsed-customer segments and the 12-month active-customer convention, and it measures elapsed time only, leaving the churn decision to the business's churn definition and lifecycle labels to Customer Status.