Docs

Notification Merge Tag Reference

Every [Tag] you can put in a Pickup, Delivery, Driver or Smart ETA notification template, which ones are available where, and where the substitution silently fails.

Published

A merge tag is a bracketed placeholder, like [CustomerName], that you type or click into a notification template. When Zippykind sends the message it replaces the tag with the real value for that ticket. This page lists every tag the platform substitutes, which notification tabs and channels each one is offered on, and the specific places substitution does not happen even though the tag looks like it should work.

How to insert one

Open any trigger's EDIT button on the Pickup, Delivery, Driver or Smart ETA Notifications tab. Each of the SMS, Mobile Push and Email boxes has its own Available Tags dropdown next to it; choosing a tag inserts it, spaced with a leading and trailing space, at your cursor. The dropdown only lists the tags that make sense for the trigger and channel you opened — opening the Photo trigger shows [Photo] in the list, opening Assign Ticket on the Driver tab does not.

On the Free Plan, the dropdown still inserts the tag but a warning toast tells you tags are not available on that plan — because, as covered below, the Free/Trial plan does not run tag substitution on customer-facing email at all.

The standard set — Pickup, Delivery and Driver Notifications, every channel

  • [TicketID] — the ticket's id.
  • [CustomerName] — the customer's name on the ticket.
  • [CustomerPhoneNumber] — the customer's phone number. Not offered on Driver Notifications templates.
  • [CustomerAddress] — the delivery address.
  • [DeliveryDateTime] — the ticket's delivery date and time, formatted for the account's time zone.
  • [DeliveryDateTimeWindow] — the delivery window, if the ticket has one: the "deliver after" time through the delivery date and time.
  • [ProductPickupName], [ProductPickupPhone], [ProductPickupAddress] — the pickup location's contact name, phone and address, where the driver collects the order.
  • [TicketDescription] — the ticket's description field.

Customer-only set — Pickup and Delivery Notifications, not Driver

  • [DriverName], [DriverPhone] — the assigned driver's name and phone. Available on Pickup and Delivery templates. The tag dropdown does not offer these two on Driver Notifications templates, but the underlying substitution does run there too, so typing them in by hand on a driver template works.
  • [TrackingLink] — the link to the customer's live tracking page.
  • [TrackingReceipt] — the link to the delivery tracking receipt / details page.
  • [TrackingToken] — the raw tracking token used to build those two links.

Email-only set

  • [ExternalCustomerNumber], [ExternalOrderId], [ExternalInvoiceNumber] — ids from your own system, when the ticket carries them. Offered in the Email tag list, not SMS or Push.
  • [AllPhotos] — every photo already on the ticket's history at the moment the email is sent, rendered inline as images with view links. Because it reflects whatever exists in the history right then, it renders empty on an early trigger like Ticket Created and fills in as the driver adds photos.

Trigger-specific tags — only offered, and only substituted, on their matching trigger

  • [Notes] — the driver's note text. Substituted only when the underlying option key is DELIVERY_NOTES or DELIVERY_UPDATE_NOTES — see the gap below.
  • [Signature] — the link to the captured signature image. Offered on the Signature trigger.
  • [Photo] — the link to the single photo just captured. Offered on the Photo trigger.
  • [SignLink] — the contactless signing link. Offered on the Contactless Signature trigger.
  • [StopsAway] — how many stops away the driver is. Offered only on the Smart ETA tab, and only substituted for a Smart ETA trigger; it has no meaning anywhere else.

Where substitution silently fails — read this before you rely on Notes

Three gaps are worth knowing about, all found by reading the send code rather than the UI:

  • Pickup Notifications → Notes does not fire at all. The code that decides whether to send a first-note notification always checks the Delivery tab's Notes switch, whatever the ticket's transaction type. Full detail in Pickup Notifications explained.
  • Pickup Notifications → Update Notes sends, but [Notes] in its template is not replaced. That trigger correctly reads the Pickup tab's own switch and template, but the code that fills in the [Notes] placeholder only runs for the DELIVERY_NOTES and DELIVERY_UPDATE_NOTES keys. A Pickup > Update Notes template containing [Notes] sends the customer the literal text "[Notes]" instead of the driver's edited note. Leave [Notes] out of that one template, or describe the update without quoting it.
  • Customer-facing email tags need a paid plan. On Pickup and Delivery Notifications, the whole block of email tag substitution is skipped for a Free or Trial account — every [Tag] in the email body is sent to the customer exactly as written, brackets and all. This is why the Email column header on those tabs already carries a popover telling free-plan accounts to open a support case to have email notifications enabled.

Two tags the code substitutes that the dropdown never offers

[PickUpDateTime] and [CompanyName] are replaced by the send code on every trigger, but neither appears in any Available Tags dropdown. [PickUpDateTime] currently resolves to the same value as [DeliveryDateTime]. [CompanyName] resolves to your account's site title in a driver notification, but to an empty string in a customer-facing Pickup or Delivery notification — so putting [CompanyName] in a customer template removes that text rather than filling it in. Safer to spell your company name out directly in a customer template instead of relying on this tag.