Using a different carrier? See Package Tracking.
Introduction
LSO (Lone Star Overnight) is a regional parcel carrier in the US Southwest. Zembula reads LSO tracking from the same tracking service LSO's own tracking site uses. You don't need an LSO account, key or password for it, so there is nothing to create or paste.
Zembula sends LSO only the tracking number. It never creates shipments or changes anything at LSO.
This guide covers connecting LSO in the Zembula platform and using it in your content.
Who can do this
You don't need an LSO account or key to connect LSO.
In Zembula, only account Admins can connect LSO. Other users can open the Package Tracking page, but they can't change it.
Before you go live
Each time an image with LSO tracking loads, Zembula asks LSO for the latest scans. So each email open can make a call to LSO.
LSO doesn't publish this tracking service as a public API, so it can change without notice. If it changes, LSO tracking can stop showing until Zembula updates the connection.
When LSO doesn't know a tracking number, it takes several seconds to answer. The image waits up to five seconds and then loads with no tracking. If many opens in a short time carry numbers LSO doesn't know, LSO tracking can stop showing for a few minutes, for real numbers too. Send only real LSO tracking numbers.
Talk to your Zembula team before you use LSO tracking in a large send.
Connect LSO in Zembula
You don't need any LSO account details, so there's nothing to paste.
In the Zembula platform, open Data Sync → Integrations and select the Data integrations tab.
Click Set up on the Package Tracking tile. If Package Tracking is already set up, the button reads Open instead.
If Package Tracking is off, click Turn on. The page shows Setting up the builder source… and then Use INTERFACES › Package Tracking in the builder.
Under Carriers, click Add on the LSO row.
The row reads LSO needs no account details — connect it to add it to your tracking. Click Connect.
The LSO row then reads Connected — starts answering within the hour.
If order data is live for Package Tracking, the LSO row reads Connected — waiting: carriers and order data can't run together until the next release. To switch, click Use LSO instead and confirm. This turns order data off and LSO on. Content that sends only an order ID then shows your fallback.
To stop using LSO, click Disconnect on the LSO row.
Try it
Add INTERFACES › Package Tracking to a draft image in the builder, turn on Simulate, and preview it with an LSO tracking number. If a number you know is real shows no tracking, check that your content sends the carrier.
The Status section at the bottom of the Package Tracking page also lists anything that needs attention.
Using LSO in your content
Send each package's tracking number in tracking_number and its carrier in carrier. Zembula doesn't work out the carrier from the tracking number, so always send the carrier.
A carrier value goes to LSO when it contains LSO as a word, or Lone Star, in any case. For example: LSO, lso, LSO Ground, LSO_PRIORITY, Lone Star Overnight or LONE_STAR_OVERNIGHT. LSO must stand on its own: LSOExpress doesn't go to LSO.
Send one LSO tracking number. Zembula removes spaces and commas from it before it asks LSO.
What shoppers see
Status: the stage of LSO's latest scan, such as In Transit, Out for Delivery or Delivered. A scan Zembula can't classify reads In Transit.
Latest scan: the most recent scan LSO reports when the image loads, with its city. Scan times show in US Central time.
Estimated delivery: the date in LSO's latest "Scheduled for" scan. It reads Scheduled Delivery, or Rescheduled Delivery when LSO moved the date. Zembula drops it when a newer delay, exception or missed-delivery scan arrives. After delivery it reads Delivered, with the time of the delivery scan.
Tracking link: the package's tracking page on lso.com.
No manage delivery link: LSO doesn't give one, so the manage delivery link stays empty.
When LSO has no scans for a number yet, Tracking.API.error reads not_found, so your content can show a fallback. A number LSO doesn't recognize at all usually returns no tracking data, not not_found. Base your fallback on Tracking.status having no value, not only on not_found.
Zembula never reads the street address or ZIP code a package is delivered to, or the name of the person who signed. A delivery scan, or a missed-delivery scan, can show the city and state of the delivery address.
Additional resources