You can use any information about the order that your ticketing system exposes via its API.
crowdEngage combines all the orders for a customer so that you only send one message per customer rather than one message per order. Some fields are calculated automatically.
Orders
Orders are held in a list called orders. You'll need to loop through this list to insert information for each order.
-
order.id
Tickets
Tickets are held in a list called tickets. You'll need to loop through this list to insert information for each ticket.
-
ticket.barcode
-
ticket.seat
-
ticket.area
-
ticket.full_seat_name
-
ticket.top_level_seating_plan_name
-
ticket.seat_information
-
ticket.price_band_name
For example:
Your seats are as follows:{% for ticket in order.tickets %}
{{ ticket.full_seat_name }}
{% endfor %}
Other fields
You can also include information about attributes, payments, refunds, order items, deliveries, and more. They might be a little tricky, just let us know what you need, and we’ll give you a hand!
Blank fields
Be aware that fields might well be blank if they aren't required in your ticketing system! If you want to avoid this, you could use an if/else statement to check whether the field is blank or not before you use it.