Once the Malomo x Loop integration is enabled, you will have access to a set of new Malomo return event triggers, which can be used to create personalized notifications in your connected apps like Klaviyo, Attentive, and Postscript
🚨 Please note, the new Malomo event triggers will only be available in Klaviyo at the initial beta launch. Attentive and Postscript events will be released shortly.
Loop Return Events
METRIC | DESCRIPTION |
|---|---|
Malomo: ReturnShipmentCreated | Loop records a new return shipment and that shipment registers in the Malomo platform. |
Malomo: ReturnShipmentUpdateReceived | The carrier registers a new shipment status for a Loop return package with Malomo. |
Return Shipment Statuses
These statuses become available as Flow Triggers in the Malomo: ReturnShipmentUpdateReceived metric in Klaviyo.
METRIC | DESCRIPTION |
|---|---|
pre_transit | A shipping label was created but the carrier has not yet taken possession of the shipment. |
in_transit | The shipment is in the carrier’s possession and is en route to its destination. |
out_for_delivery | The shipment is currently on its last mile and is en route to the destination address. |
delivered | The local delivery vehicle has reported the package was delivered. |
return_to_sender | The shipment was not successfully delivered and is en route back to sender. |
cancelled | The delivery has been cancelled typically by either the seller or recipient. |
available_for_pickup | The shipment is available for pickup from the carrier’s facility such as a post office. |
failure | The shipment could not be delivered. |
error | An unknown delivery error occurred. |
unknown | The carrier doesn’t know the current status of the shipment. |
Please note, each trigger is created on the first instance that the event is received from Malomo, so it may take up to 24 hours for all of the Malomo triggers to be listed