What Are Liquid Tags (and How Can You Use Them on TicketingHub?)

Ever wanted to personalize every email or ticket your customers receive—without rewriting the whole thing each time? That's exactly where Liquid Tags shine. This guide is for TicketingHub users who want to send smart, dynamic messages that pull real-time information from each booking.

Whether you're welcoming guests by name, changing messaging based on language, or tweaking details depending on the day of the week, Liquid Tags help you automate the process while keeping it personal. No coding knowledge is required.

What Exactly Is a Liquid Tag?

Liquid Tags are placeholders—tiny pieces of code that automatically insert personalized information from a customer's booking into your emails, tickets, or automated messages.

For example, if you write:

Hello {{ customer.first_name }}, your tour is confirmed!

Your customer will receive:

Hello Carl, your tour is confirmed!

Important: All Liquid tags in TicketingHub use double curly braces {{ }} for output variables, and {% %} for logic. Always use this format — do not use single braces { }.

Note on AI tools: If you ask ChatGPT, Gemini, or another AI assistant to write Liquid tag templates, the syntax they suggest may not match TicketingHub's implementation. Always use the tag list on this page as your reference.

Types of Liquid Tags You Can Use

TicketingHub supports two main types of Liquid Tags:

Output Tags

These display specific booking details like names, dates, and product information.

Hello {{ customer.first_name }}, your tour on {{ booked_for_date }} is confirmed.

Logic Tags

These allow you to create rules and display different content depending on conditions — like the booking language, ticket type, or day of the week.

{% if order.language == "fr" %}
  Bonjour ! Merci pour votre réservation.
{% else %}
  Hello! Thank you for your booking.
{% endif %}

How to Activate Liquid Tags

Liquid Tags are not enabled by default on every account. Here's how to turn them on:

1. Go to a specific product in your TicketingHub dashboard.
2. Navigate to the Emails tab.
3. Open any email template.
4. Look for the Liquid Tags toggle in the top-right corner of the email editor.
5. Enable it — you'll now see the full tag editor and be able to use any tag from the list below.

If you don't see the toggle, contact support and we'll activate it for you.

Where to Use Liquid Tags in TicketingHub

Liquid Tags work inside product email templates, including: Confirmation Emails, Reminder Emails, Cancellation Emails, and Abandoned Booking Emails.

Note: Not all variables are available in every email type. For example, some tags that work in Confirmation Emails are not available in Proforma Invoice Emails. If a tag appears not to be rendering, the variable may not be supported in that specific email context. Contact support to confirm.

Customize by Language

If you have international and local customers, you can tailor your messaging based on the language selected at booking.

Update: The {{ order.language }} variable now correctly captures the language your customer chose in the booking widget. Your conditional language logic will work reliably across all new bookings.

{% if order.language == "es" %}
  ¡Hola! Gracias por tu reserva.
{% elsif order.language == "fr" %}
  Bonjour ! Merci pour votre réservation.
{% else %}
  Hello! Thank you for your booking.
{% endif %}

Personalize by Ticket Type

Want to give special messages to VIPs or students? Use conditional tags to customize based on ticket type.

{% if order.ticket_type == "VIP" %}
  Welcome VIP! Enjoy your complimentary welcome drink.
{% elsif order.ticket_type == "Student" %}
  Don't forget to bring your student ID.
{% else %}
  Thanks for booking! Please arrive on time and enjoy the tour.
{% endif %}

Change Meeting Point Based on the Day of the Week

If your meeting location changes on certain days, you can set up a rule to display the correct info automatically.

{% assign weekday = booked_for_date | date: '%a' %}
{% if weekday == 'Mon' %}
  Please meet at our annex building.
{% else %}
  Please meet at our main office.
{% endif %}

Multi-Language Emails: Advanced Examples

Many operators run tours for international audiences. Here are ready-to-use templates for common multi-language setups.

Hebrew (Right-to-Left):

{% if order.language == "he" %}
<p style="direction: rtl; text-align: right;">
  שלום {{ customer.first_name }}! תודה על ההזמנה שלך.<br>
  <strong>פרטי המוצר:</strong> {{ product.name }}
</p>
{% else %}
  Hello {{ customer.first_name }}! Thank you for your booking.
{% endif %}

Japanese / English Bilingual:

{% if order.language == "ja" %}
  こんにちは {{ customer.first_name }} 様。ご予約ありがとうございます。
  ツアー名：{{ product.name }}
{% else %}
  Hello {{ customer.first_name }}, thank you for your booking.
  Tour: {{ product.name }}
{% endif %}

Pro Tip: You can combine all those conditions — ticket type, language, and day — in a single message. TicketingHub's Liquid Tag engine makes personalized communication effortless.

Where Liquid Tags Do NOT Work

Liquid Tags are supported in email templates only. They will not render in the following locations:

• Widget success message field (the confirmation text shown on screen after booking)
• Custom question labels
• Product description fields

If you need to show personalised information after booking, the best approach is to direct customers to their confirmation email.

Why Use Liquid Tags?

Because they help you:

• Automatically personalize customer messages with real booking data
• Send emails in your customers' own language without maintaining separate templates
• Avoid manual edits and reduce human error
• Show accurate, dynamic info for each booking — meeting points, pickup times, guide details, and more

Full List of Supported Liquid Tags

The following tags are supported in TicketingHub email templates. Tags with a note have specific behaviour to be aware of.

Order & Booking

{{ reference }}
{{ order.reference }}
{{ order.language }}         — Language selected by the customer in the booking widget.
{{ order.referral_code }}
{{ order.checkout_url }}
{{ booked_for_date }}
{{ size }}                   — Number of people in the booking.
{{ group_booking }}
{{ questions_with_answers }}
{{ extra_names }}
{{ amount }}                 — Total amount of the booking.

Voucher

{{ voucher }}                — Note: currently displays the order reference number. A dedicated
                               voucher code variable is in development. Until then, use
                               {{ reference }} if you need the booking reference.

Product

{{ product.name }}
{{ product.address.name }}
{{ product.address.building }}
{{ product.address.street }}
{{ product.address.city }}
{{ product.address.region }}
{{ product.address.postal_code }}
{{ product.address.country }}
{{ product.address.google_maps_url }}
{{ product.formatted_address }}

Season, Variant & Option

{{ season.name }}
{{ variant.name }}
{{ tier_names }}
{{ option.name }}
{{ option.time }}

Customer

{{ customer.first_name }}
{{ customer.last_name }}
{{ customer.full_name }}
{{ customer.company }}
{{ customer.email }}

Attendee

{{ attendee.first_name }}
{{ attendee.last_name }}
{{ attendee.full_name }}
{{ attendee.company }}
{{ attendee.email }}

Pickup

{{ pickup.location }}
{{ pickup.time }}
{{ pickup.note }}
{{ pickup.map }}

Supplier

{{ supplier.name }}
{{ supplier.logo }}
{{ supplier.logo_url }}
{{ supplier.website }}
{{ supplier.telephone }}
{{ supplier.email }}

Guide

{{ guide.name }}
{{ guide.first_name }}
{{ guide.last_name }}
{{ guide.telephone }}

Channel & Reseller

{{ channel.name }}
{{ reseller.name }}

Other

{{ notes }}
{{ manage_booking_url }}
{{ smartwaiver_url }}

Common Mistakes to Avoid

1. Using single braces instead of double braces

Wrong:   { customer.first_name }
Correct: {{ customer.first_name }}

2. Mixing up product and tour in variable names

Wrong:   {{ tour.name }}
Correct: {{ product.name }}

TicketingHub uses product — this is the most common syntax error we see.

3. Trusting AI-generated tag syntax

ChatGPT and Gemini may suggest liquid tag formats that don't match TicketingHub's implementation. Always cross-reference with the list on this page.

4. Using liquid tags in unsupported fields

Tags only render inside email templates. They will not work in the widget success message field or product description fields.

5. Variable unavailable in that email type

Some variables are only available in specific email types. If a tag isn't rendering, the variable may not be supported for that email context. Contact support to confirm.

Liquid Tags Made Simple

Liquid Tags might sound technical, but once you get the hang of them, they're a total game-changer. They're perfect for busy operators who want to automate communication without losing that personal touch.

And if you're ever unsure about how to structure a tag, we're here to help — just reach out!

Updated on: 11/04/2026