Iterable Events Reference

UltraCart pushes activity to your Iterable project server-to-server, in real time. There is no storefront pixel or tag to install: once your API key is saved, UltraCart sends each event directly to Iterable's API as it happens. This page lists every event UltraCart can send, when it fires, and which configuration setting controls it, so you can build Journeys and segments against them.

Where to see events

Every send is written to your integration log with the Iterable event name as the action label:

Operations → Reporting → Integration Logs

Filter the Action column by an event name (for example updateCart or refund) to see every time UltraCart pushed that event. In Iterable, the same events land on the shopper's user profile and in their event history, where they become Journey triggers and segmentation criteria.

Events at a glance

Event (Iterable name)	Fires when	Controlled by
Purchase (purchase)	An order is placed, including a subscription signup and every rebill	On whenever the integration is configured
Shipment (fulfilled)	An order ships	On whenever the integration is configured
Reviews (trackReviews)	An order ships (review-request data)	On whenever the integration is configured
Order Updated (orderUpdated)	An order is edited, or its status changes	Send Order Updated Events
Refund (refund)	A refund is issued on an order	Send Refund Events
Cart Abandoned (updateCart)	A cart is classified as abandoned	Send Return Cart Events
Auto Order lifecycle (uc_autoorder_*)	A subscription is created, renewed, paused, resumed, cancelled, a rebill fails, or a single item changes	Send Auto Order Lifecycle Events

The core commerce events (purchase, shipment, reviews) flow as soon as the integration is configured with a valid API key and the order has a valid email; they are not individually toggled. The remaining events each have their own checkbox on the Iterable configuration screen, so you can turn off any category you do not use.

Cart abandonment and the auto order (subscription) lifecycle each have their own detailed page: see Iterable Abandoned Cart Integration and Iterable Auto Order (Subscription) Events.

---

Purchase (purchase)

UltraCart's most important event. It is a native Iterable commerce event, so it populates the shopper's purchase history and revenue in Iterable automatically.

Fires when: an order is placed. This includes a one-time order, the first order of a new subscription (signup), and every subscription rebill.

Useful fields:

• Order ID, order total, subtotal, shipping and handling, discounts, and currency
• Each item: SKU, name, price, quantity, categories, product image URL, and product page URL
• subscription — true when the order is part of a subscription (auto order)
• rebill — true when the order is a renewal rather than the original signup order

Build with it: post-purchase flows, receipts and thank-you emails, revenue reporting, and first-order-versus-renewal branching (using the subscription and rebill flags). See Iterable Auto Order (Subscription) Events for how those flags behave and how to keep one-time buyers out of subscriber journeys.

Shipment (fulfilled)

Fires when: an order ships. The event is an order-level snapshot: it carries the full order and all tracking numbers on the order at the time it fired. If an order ships in more than one shipment, the event refreshes to the latest fulfillment state rather than creating duplicates.

Useful fields:

• Order ID and all tracking numbers for the order
• Each item: SKU, name, price, quantity, categories, image and product page URL
• subscription / rebill flags (same meaning as on the purchase event)

Build with it: "your order has shipped" notifications with tracking links, and delivery-based follow-ups.

Reviews (trackReviews)

Fires when: an order ships. It carries the data needed to request product reviews for what the shopper bought.

Useful fields: the ordered items (SKU, name, categories) and a review token used to build a review link.

Build with it: post-delivery review-request campaigns.

Order Updated (orderUpdated)

One event covers both order edits and status changes, with an updateType field so your Journey can branch on what happened.

Fires when: an order is edited (items or address changed) or its status transitions — for example to on hold, completed, rejected, fraud review, or pending clearance.

Controlled by: the Send Order Updated Events checkbox.

Useful fields:

• updateType — items_changed, address_changed, or status_changed
• For status changes: previous status, new status, a status reason, and the current order total
• For edits: previous and new totals, the updated item list, and the shipping address

Build with it: status-driven messaging (for example, an "order on hold — action needed" email), and confirmations when an order is edited.

Shipment transitions are intentionally not routed here — a shipment is its own fulfilled event (above), so you wire shipping notifications to fulfilled, not to orderUpdated.

Refund (refund)

Fires when: a refund is issued against an order (full or partial).

Controlled by: the Send Refund Events checkbox.

Useful fields:

• Original order ID and original order total
• Refund amount, refund type (full / partial), and a refund reason
• The refunded items (SKU, quantity, amount) for item-level refunds
• Remaining order total after the refund

Build with it: refund confirmation emails and post-refund win-back or feedback flows.

Cart Abandoned (updateCart)

Fires when: UltraCart classifies a shopper's cart as abandoned, after the delay you set with the Abandon cart after setting.

Controlled by: the Send Return Cart Events checkbox.

This event has a dedicated walkthrough — including how to build the recovery Journey and use the return-to-cart link — on the Iterable Abandoned Cart Integration page.

Auto Order (Subscription) lifecycle (uc_autoorder_*)

When you sell subscriptions (auto orders), UltraCart sends a family of lifecycle events — created, renewed, paused, resumed, payment failed, cancelled, and single-item changes — so you can build welcome, renewal, dunning, and win-back journeys.

Controlled by: the single Send Auto Order Lifecycle Events checkbox (it covers the whole family).

These events, the subscription / rebill flags, and the Only Flag Subscription For Physical Items option are all covered on the Iterable Auto Order (Subscription) Events page.