Klaviyo Integration Flow Triggers and Filters
The Klaviyo & Malomo Integration gives users powerful ways to trigger personalized emails based on their order's shipment status. First, check out our quick video to learn how to build a flow off of Malomo data in Klaviyo. Next, review the events below that are available to trigger emails.
How to Build a Flow off Malomo Data in Klaviyo
Malomo Event Metrics
With an active Malomo integration in your Klaviyo account, these event metrics become available for Flows:
METRIC | DESCRIPTION |
|---|---|
| Shopify records a new order placed by a customer. |
| Shopify records a new shipment on an order and that shipment registers in the Malomo platform. |
| The carrier registers a new shipment status with Malomo. |
| Malomo identifies a problem with an order or shipment. |
| Loop records a new return shipment and that shipment registers in the Malomo platform. |
| The carrier registers a new shipment status for a Loop return package with Malomo. |
Shipment Statuses
With an active Malomo integration in your Klaviyo account, the statuses below become available as Flow Triggers in the Malomo: ShipmentUpdateReceived event metric. The statuses are also available for merchants with an active Loop integration in the Malomo: ReturnShipmentUpdateReceived event metric.
METRIC | DESCRIPTION |
|---|---|
| A shipping label was created but the carrier has not yet taken possession of the shipment. |
| The shipment is in the carrier’s possession and is en route to its destination. |
| The shipment is currently on its last mile and is en route to the destination address. |
| The local delivery vehicle has reported the package was delivered. |
| The shipment was not successfully delivered and is en route back to sender. |
| The delivery has been cancelled typically by either the seller or recipient. |
| The shipment is available for pickup from the carrier’s facility such as a post office. |
| The shipment could not be delivered. |
| An unknown delivery error occurred. |
| The carrier doesn’t know the current status of the shipment. |
PROBLEM TYPES
With an active Malomo integration in your Klaviyo account and an active Problem Orders feature, these problem types become available as Flow Triggers in the Malomo: OrderIssueCreated metric:
METRIC | DESCRIPTION |
|---|---|
| An order that has been created but has not been fulfilled in the specified time frame.* |
| An order that has been fulfilled or is in transit and has not received a scan update in the specified time frame. * |
| This event is created based on the carrier status of “failure”, meaning the shipment could not be delivered.** |
| This event is created based on the carrier status of “return_to_sender”, meaning the shipment could not be delivered and is en route back to the sender.** |
*For FulfillmentStalled and ShipmentStalled, the default stalled timeframe is set to 72 hours with Saturdays and Sundays excluded. You may change this in the configuration panel at any time. Please note that the change is not retroactive, and will apply only to new orders placed after updating your settings.
** In Klaviyo, the ShipmentDeliveryAttemped and ShipmentReturnToSender serves the same purpose as the Malomo: ShipmentUpdateReceived metric paired with the failure or return_to_sender status. Enabling this problem type will not overwrite any flows based on the existing event.
Important Notes for Problem Orders:
At this point, the “Stalled” flag is not a real-time status. It is added to an order once the stalled criteria are met, and is not removed.
Unless you exclude Saturdays and/or Sundays from the Stalled logic, you will notice a spike in Stalled orders created on Sundays and Mondays, as most carriers are not scanning packages throughout the weekend.
Due to the point above, we recommend that you take some time to understand the effects of your chosen configurations before building any customer-facing automations.