Tracking page

Last updated: September 4, 2026

The tracking page is the branded, public web page your customer opens from a link in their delivery notification to watch their order in real time. It's the customer-facing window onto a running delivery: a live map, the current delivery status, an ETA, and the driver and proof-of-delivery details — all under your logo, your colors, and your business info. It's what the customer sees for the life of the delivery, and you design it here in the portal with a live preview before any customer ever opens one.

You don't build a tracking page per delivery. You configure it once, at the organization level, and that one setup is what every customer's page draws from. The public page each customer opens is a separately hosted surface — you configure it here; Nash renders it for the customer. Change a setting in the portal and it applies to the pages your customers open from then on.

What you set up here

The editor gives you a live phone-and-desktop preview with a phase switcher, so you can see the pre-dispatch and live-delivery views exactly as a customer would, on mobile or desktop, as you work. Within it you control:

  • Appearance and branding — your logo, brand color and theme, the page language, and a "Powered by Nash" toggle. See Brand your tracking page.
  • Page components — the substance of what the customer sees, each turned on or off: the map, pickup and dropoff location, dropoff ETA, proof of delivery, live driver location, driver and provider info, package and reference IDs, the event timeline, the recipient's last name and phone, your organization name, and more. See Customize your tracking page.
  • Pre-dispatch tracking — an optional screen, with a message you write, shown before a driver is assigned. See Show tracking before dispatch.
  • Feedback — a thumbs up/down form, with your own title and reason options, shown to the customer after delivery. See Collect delivery feedback.
  • Footer and business details — your website and social handles.

Some richer capabilities — a Delivery Activity feed and an embedded AI tracking assistant on the page — are premium extras whose availability varies by organization. If you want them, reach out to Nash.

How the customer reaches the page

A customer almost always reaches their tracking page through a link inside a notification — the tracking-link variable dropped into a message that fires as the delivery moves. That means configuring the page and configuring who gets told about it are two separate jobs: this object is the page itself; the messages that carry its link live in the Customer notifications object. Set up one without the other and a customer can end up with a page nobody links to, or updates with nowhere to click through to.

What you can do

One thing to carry through all of it: Nash dispatches the delivery, and a provider or your own fleet carries it out. The tracking page reflects the driver's location and status as Nash surfaces them from whoever's actually delivering — it isn't Nash performing the delivery.