Pre Requisites: Completed Shopify <> Malomo Integration, Completed Tracking Page Onboarding.
Set up Time: 15-20 Minutes
...
Complete the following procedure to set up the integration for Malomo and Attentive.
Set up the integration
Complete the following steps to set up the integration:
...
You now have access to a set of Malomo event triggers, which can be used to create journeys and insert Malomo data into them. 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.
Review or Set your Default Tracking Page URL
Attentive uses the Default Tracking Page URL set in the Malomo Dashboard to share your live tracking page with your customer. To review this page, go to Malomo > Account > Overviewandlook for the Default Tracking Page URL section. If this section is blank, please add in the full URL of your live tracking page. If you have multiple live tracking pages, please select the page you would like to assign as the default tracking experience.
To learn more about setting or reviewing your default tracking page, check out this article.
Inform customers on their Order Status using Attentive Journeys
After the integration is connected, you can create a custom journey in Attentive using the custom events from Malomo. Users can configure their journeys to communicate in real-time to customers where their order is in the shipping lifecycle.
Available Journey Triggers with Malomo
Anchor | ||||
---|---|---|---|---|
|
When a trigger is fired (when a Malomo event occurs), an active Attentive automation for that trigger must also exist in your account in order for SMS notifications to be sent.
Event name | 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. |
| A shipping label was created and has been registered in the carrier’s system. However, the carrier has not yet taken possession of the shipment. |
| Only the first scan event when the shipment is in the carrier’s possession and is en route to its destination. |
| The shipment is in the carrier’s possession and is en route to its destination. |
| Only the first scan event when the shipment is currently on its last mile and is en route to the destination address. |
| 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 is available for pickup from the carrier’s facility such as a post office. |
| The shipment was not successfully delivered and is en route back to sender. |
| A delivery was attempted but the shipment could not be delivered. |
| The delivery has been canceled typically by either the seller or recipient. |
| An unknown delivery error occurred. |
| An order that has been created but has not been fulfilled in the specified time frame within our Problem Orders feature. |
| An order that has been fulfilled or is in transit and has not received a scan update in the specified time frame within our Problem Orders feature. |
*Please note, we do not recommend triggering off of InTransit
or OutforDelivery
, as the journey may trigger multiple texts to your customer. Please use our Malomo: ShipmentFirstInTransit
and Malomo: ShipmentFirstOutForDelivery
triggers instead.
Available Properties with Malomo
Anchor | ||||
---|---|---|---|---|
|
To link customers to your custom tracking page, we recommend using the { order_url}
tag once you've set your Default Tracking Page URL. You can also build your tracking URL with the {order_id}
tag, such as this: www.brandname.mymalomo.com/xxxxx/?_m_id={order_id}
We also recommend using the {order_number}
property to give customers a reference point. The following table lists the available custom events and properties:
Event name | Properties |
|
|
|
|
|
|
|
|
|
**Please note, we do not recommend triggering a status off of InTransit, as the journey will trigger multiple texts to your customer. Our system receives the InTransit status on every scan event received between PreTransit and OutForDelivery.
| |
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|