**Here are the steps to connect Klaviyo with TrackingMore:** 1. Sign up for Trackingmore account 2. Make sure you have an active Klaviyo account 3. In Klaviyo, go to Account > Settings > API Keys > Public API Key, copy the public API key 4. In TrackingMore, paste in the klaviyo public API key and click "Connect" to set up this intergration 5. Once you enter your Klaviyo API Key, you can use TrackingMore event metrics to trigger a flow. Trackingmore Events are coming with **CurrentStatuses** & **Sub-Statuses** for each shipment, which are powerful segmentation triggers for Klaviyo Flows. (example below) Variable name: `CurrentStatus` | CurrentStatus | Description | | :------------ | :------------ | | notfound | Package tracking information is no available yet | | transit | Courier has picked up package from shipper, the package is on the way to destination | | pickup | Also known as "Out For Delivery", courier is about to deliver the package, or the package is wating for addressee to pick up | | delivered | The package was delivered successfully | | expired | No tracking information for 30days for express service, or no tracking information for 60 days for postal service since the package added | | undelivered | Also known as "Failed Attempt", courier attempted to deliver but failded, usually left a notice and will try to delivery again | | exception | Package missed, addressee returned package to sender or other exceptions | Variable name: `Substatus` | Substatus | Description | | :------------ | :------------ | | delivered001 | Package delivered successfully | | delivered002 | Package picked up by the addressee | | delivered003 |Package received and signed by addressee | | delivered004 | Package was left at the front door or left with your neighbour | | undelivered001 | Address-related issues | | undelivered002 | Receiver not home | | undelivered003 | Impossible to locate the addressee | | undelivered004 | Undelivered due to other reasons | | exception004 | The package is unclaimed | | exception005 | Other exceptions | | exception006 | Package was detained by customs | | exception007 | Package was lost or damaged during delivery | | exception008 | Logistics order was cancelled before courier pick up the package | | exception009 | Package was refused by addressee | | exception010 | Package has been returned to sender | | exception011 | Package is beening sent to sender | | pickup001 | The package is out for delivery | | pickup002 | The package is ready for collection | | pickup003 | The customer is contacted before the final delivery | | transit001 | Package is on the way to destination | | transit002 | Package arrived at a hub or sorting center | | transit003 | Package arrived at delivery facility | | transit004 | Package arrived at destination country | | transit005 | Customs clearance completed | Below is an example flow we recommend:  Available data inside of the Klaviyo events: | Property name | Template tag | Example | | :------------ | :------------ | :------------ | | CarrierCode | {{ event.CarrierCode }} | dhl | | TrackingCode |{{ event.TrackingCode }} | RA123123123CN | | OrderNumber | {{ event.OrderNumber }} | #12345 | | CurrentStatus |{{ event.CurrentStatus }} | Delivered | | Substatus | {{ event.Substatus}} | delivered001 | | ExpectedDeliveryDate | {{ event.ExpectedDeliveryDate }} | 2021/10/22 | | LastestCheckpointTime | {{ event.LastestCheckpointTime }} | 2021/10/22 21:16 | | TransitTime | {{ event.TransitTime }} | 7 | | OrderEmail | {{ event.OrderEmail}} | test@gmail.com | | OrderPhone | {{ event.OrderPhone }} | +4478 2989 2347 | | OriginalCountryCode | {{ event.OriginalCountryCode }} | GB | | DestinationCountryCode | {{ event.DestinationCountryCode}} | GB |