Email Merge Tags

Last updated June 20, 2026

Email Merge Tags

Merge tags are placeholders wrapped in double curly braces — for example, {{client_first_name}} — that auto-fill with real client, trip, and booking data when an email is sent. Write them directly into your email template body or subject line, or insert them from the variable picker (the { } button) in the template editor.

Available Tags

Client

TagWhat it fills
{{client_name}}Client's full name
{{client_first_name}}First name
{{client_last_name}}Last name
{{client_preferred_name}}Preferred / nickname, if set
{{client_email}}Client's email address
{{client_phone}}Client's phone number

Trip

TagWhat it fills
{{trip_name}}Name of the trip
{{destination}}Destination
{{start_date}}Trip start date
{{end_date}}Trip end date
{{departure_date}}Departure date
{{return_date}}Return date
{{total_price}}Total trip price
{{deposit_amount}}Deposit amount

Payment

TagWhat it fills
{{amount}}Amount currently due
{{balance_due}}Remaining balance
{{due_date}}Payment due date
{{payment_type}}Type of payment (deposit, final payment, etc.)
{{deposit_due_date}}Deposit due date
{{final_payment_date}}Final payment due date

Booking

TagWhat it fills
{{booking_supplier}}Supplier or cruise line
{{booking_confirmation}}Confirmation or reservation number
{{booking_type}}Type of booking (flight, hotel, cruise, etc.)

Cruise

TagWhat it fills
{{ship_name}}Name of the ship (e.g., "Wonder of the Seas")
{{stateroom_category}}Stateroom category (e.g., "Balcony", "Ocean View")
{{stateroom_number}}Assigned cabin number
{{embarkation_port}}Port of departure
{{disembarkation_port}}Port of arrival / turnaround
{{cruise_length}}Length of the sailing (e.g., "7 nights")

Agent & Agency

TagWhat it fills
{{agent_name}}Your full name
{{agent_email}}Your email address
{{agent_phone}}Your phone number
{{agent_title}}Your title or role
{{agency_name}}Your agency's name
{{agency_phone}}Your agency's phone number
{{website}}Your agency's website URL
{{clia_number}}Your agency's CLIA number

Links

TagWhat it fills
{{portal_url}}Personalized link to the client's travel portal
{{documents_list}}Formatted list of the trip's documents

Cruise Details

The six cruise tags — {{ship_name}}, {{stateroom_category}}, {{stateroom_number}}, {{embarkation_port}}, {{disembarkation_port}}, and {{cruise_length}} — pull from the cruise booking attached to the trip.

For reservation number, sailing date, and cruise line, use the standard tags {{booking_confirmation}}, {{start_date}} / {{departure_date}}, and {{booking_supplier}} respectively — these already resolve from the booking record.

Populating the data

Cruise tags only fill when the underlying booking has cruise-specific data. There are two ways to populate it:

AI import (recommended): Open the trip and use Import Booking to paste or upload a cruise confirmation. JourneyFuse extracts ship name, stateroom category, cabin number, embarkation port, and disembarkation port automatically from the confirmation document. Cruise length is derived from the sailing dates.

Manual entry: Open the booking, scroll to the cruise section of the booking form, and fill in:

  • Ship Name
  • Stateroom Category
  • Cabin Number
  • Embarkation Port
  • Disembarkation Port

Cruise length is calculated automatically from the booking's start and end dates — no separate field needed.


Where Merge Tags Work

Merge tags resolve reliably in two places:

  • Saved email templates — tags fill when the template is loaded into a compose window tied to a client and trip.
  • Automated / Journey emails — tags fill at send time from the trip and booking context attached to the automation step.

A tag typed directly into a one-off compose email is not guaranteed to fill — the compose window may not have enough context to resolve all tags. For cruise-specific tags in particular, put them in a saved template or an automation step rather than a manual compose email.

If a tag has no data — for example, {{ship_name}} on a non-cruise trip, or a field that was never filled in — it renders as empty rather than showing the raw {{tag}} text to the client.


Related