.png){kind=logo}
1235
Events
There are 13 different events during post-purchase that LateShipment.com can send to Klaviyo via the LateShipment.com<>Klaviyo integration. These are:
- LS-Shipped - When a package is picked up by the shipping carrier
- LS-In-Transit - When a package is in-transit with the carrier.
- LS-In-Transit Delays - When a package is delayed in transit.
- LS-FailedDelivery - When delivery for a package was attempted, but unsuccessful.
- LS-OutforDelivery - When a package is out for delivery.
- LS-Delivered - When a package is delivered.
- LS-ReturnInitiated - When a return is approved and when a return is initiated.
- LS-ReturnApproved - Return request reported has been approved.
- LS-ReturnRejected - Return request reported has been denied.
- LS-ReturnReceived -Returned item received at the warehouse.
- LS-ReturnIntransit - Return shipment is in transit.
- LS-StoreCreditissued- A store credit has been issued for the return.
- LS-RefundInitiated - A refund request has been processed for the item returned.
Events are saved as custom metrics within the corresponding customer's Klaviyo profile.
Payloads:
By default, each event contains the following fields in its payload:
-
trackingnumber
-
shipdate
-
estimateddate
-
ordernumber (Shopify order number)
-
customername
-
lsstatus (Current status of the shipment)
-
trackinglink (Link to the customized tracking page)
-
carriertype (Name of the shipping carrier used)
-
variantid (Variant ID to use along with {% catalog %} block.)
All fields are strings (or an array of strings) unless otherwise noted.
The different Event Variables that can be used in your email templates:
-
trackingnumber
-
shipdate
-
estimateddate
-
ordernumber (Shopify order number)
-
customername
-
lsstatus (Current status of the shipment)
-
trackinglink (Link to the customized tracking page)
-
carriertype (Name of the shipping carrier used)
-
variantid (Variant ID to use along with
{% catalog %}block.)
Here is an example syntax for using an event variable in an email template:
<table width="100%">
<tr>
<th colspan="3" style="text-align:left;">
YOUR TEXT HERE
</th>
</tr>
{% for item in event.Items %}
<tr>
{% catalog item.variantid integration='shopify' %}
<td style="text-align:center;padding:8px;" width="30%">
<img alt="{{ catalog_item.title }} - {{ catalog_item.variant.title }}" src="{{ catalog_item.variant.featured_image.full.src|default:catalog_item.featured_img
What can I do with these events?
There are two general ways merchants can leverage the LateShipment.com <> Klaviyo integration:
- Recreate LateShipment.com's Post Purchase notifications using Klaviyo
- Create custom post-purchase flows and segments.
1. Recreate LateShipment.com's Post Purchase notifications using Klaviyo.
This integration will allow you to fully customize the event triggers and emails that are deployed from LateShipment.com and customize them using Klaviyo.
To complete this, you will need to customize flows and emails for LateShipment.com's existing flows and emails in Klaviyo.
- Click here to see the full list of LateShipment.com notification flows and event triggers
- You can build the emails yourself using Klaviyo's drag-and-drop block editor. Examples of existing LateShipment.com flows can be found here.
- Once your flows are approved and live, don't forget to head back to your LateShipment.com account to enable the triggers.
2. Create Custom Flows and Segments
This integration will also allow you to use LateShipment.com's Post Purchase data to create custom flows and segments to provide your customers with a more personalized experience. Some sample use cases include:
- Sending a different confirmation email based on the value of the product, sale promotions, etc.
- Creating unique in-transit delays and packages suspected lost flows for customers.
