Start with the event.
| Alert | When it helps |
|---|---|
| First detection | Know that the network has detected the activated label. |
| Not detected | Hear about a detection gap after your chosen interval, followed by recovery when a new detection arrives. |
| Tracking ending | See that the included tracking period is approaching expiry. |
| Detected near a place | Receive an update from a qualifying detection inside a chosen area. |
| Detected away from a place | Receive an update from a qualifying outside detection after an inside detection. |
For a place alert, choose an area.
Search for the address, confirm the place, and choose a radius in feet or miles. Use an area that matches the site you care about. A warehouse campus may need a different radius from a small office.
Location reports have uncertainty. Shipzik checks the reported accuracy area before treating a detection as clearly inside or outside your chosen radius. An ambiguous detection does not establish a crossing.
Choose who needs to know.
Send each alert to the account owner, selected account members, or outside email recipients. For example, your operations team can receive detection-gap alerts while a customer receives updates near their destination.
New accounts start with first-detection and tracking-ending alerts on, and not-detected alerts off. Account defaults can be changed for future activations; individual trackers have their own alert settings.
Read the alert as a detection.
Shipzik does not infer a departure from silence. An away alert requires a qualifying outside detection after an inside one. A near alert is not proof of delivery, and a gap is not proof that an item is lost.
Detections depend on network receivers and surroundings. Use History to review the location and alert events together.
Learn how to share tracking with a customer or how labels work.