Below is a list and description of the dynamic tags that can be generated from the system based on a number of factors including event/activity, customer and transaction details. Please review the tags carefully. By default, we’ve already added the key tags to your ticket layouts.
| TAG NAME | DESCRIPTION |
|---|---|
| General | |
| Registration link | Please ignore this tag- it is not applicable to layouts |
| Date | Represents the order confirmation date in D/M/YYYY format. E.g. 8/11/2019 |
| Time | Represents order confirmation time in H:MM TT format. E.g. 5:44 PM |
| Order Summary | Please ignore this tag- it is not applicable to layouts |
| Confirmation Number | This is a unique confirmation number for the order. E.g. 10694 |
| Password | Please ignore this tag- it is not applicable to layouts |
| Please ignore this tag- it is not applicable to layouts | |
| Name | Please ignore this tag- it is not applicable to layouts |
| Business Registered Trading Name | Represents the organisation’s name from company details page |
| Special Note | Please ignore this tag- it is not applicable to layouts |
| Terms and Conditions | Represents the company’s Term and Conditions from the General Setting page |
| Company ABN | Represents the company’s Tax ID number from company details page E.g. 11111111111 |
| Company Phone Number | Represents the company’s phone number from the company details page E.g. 02 1234 5678 |
| Company Website | Represents the company’s Website address from the company details page E.g. http://company.com.au |
| Company Support Email | Represents the company’s Support Email from the company details Page E.g. support@company.com |
| Company Email Address | Represents the company’s Email from the company details Page E.g. company@gmail.com |
| Login Link | Please ignore this tag- it is not applicable to layouts |
| Trans Date | Extended version of date of order confirmation date in D/M/YYYY format. E.g. 8/11/2019 |
| Trans Time | Extended version order confirmation time in H:MM TT format. E.g. 5:44 PM |
| Payment Method | Represents form of payment E.g. Cash, Credit Card etc. |
| Continue Shopping URL | Please ignore this tag- it is not applicable to layouts |
| Order Note | Add a note against an order that can be then be visually displayed |
| Parent Order Confirmation Number | This relates to a refund and exchange and is the original order number. By default, this is not added to the confirmation email as the customer/patron will receive their new reference number. |
| Waitlist Thankyou Message | This is the message that is sent to the customer after they join the waitlist. |
| Waitlist Detail | The name of the waitlist. |
| Waitlist message | This is what you want to tell the customer about the waitlist. |
| Waitlist For | This is the event/activity that the waitlist relates too in reference to event line 1. It ignores event line 2. |
| Waitlist Customer | This is the customers name associated with the waitlist. |
| Business Public Name | This name can be used to populate onto your confirmation emails and other areas if you prefer to not display the default ‘Business Registered Trading Name/Company. |
| Customer Full Name | This is the complete name of the customer (first name, surname) as one tag rather than 2 separate tags. |
| Zoom Webinar Confirmation Details | This will display your Online Zoom Webinar details on the confirmation email the customer will receive including the Zoom Event Name, headline text and descriptions. Customers will also have a clear ‘JOIN NOW’ button to join the webinar. |
| Events | |
| Event Line 1 | This tag represents the name of the event/activity from event build step1. E.g. The Wiggles |
| Event Line 2 | This tag represents a second line for the event, especially when the name of event/activity is long from event build step1. E.g. The Wiggles on tour with Dorothy the Dinosaur |
| Venue/Location Name | Represents Venue or Location name where event/activity is going to take place E.g. ABC Theatre |
| Venue Street Address | Represents Venue’s address E.g. 280 pitt street, Sydney, NewSouthWales AUSTRALIA 2000 |
| Venue Phone 1 | Represents Venue’s phone number E.g. 02 9999 9999 |
| Venue Phone 2 | Represents Venue’s alternative phone number E.g. 02 1111 1111 |
| Venue Email | Represents venue’s Email Address E.g. Inquary@abctheater.com |
| venue Website | Represents Venue’s website E.g. https://abctheater.com.au |
| Free Text Line 1 | Represents additional information of the event which you can setup from event build step:1 E.g. ABC Theatre presents |
| Free Text Line 2 | Represents additional information of the event which you can setup from event build step:1 E.g. Sponsored by |
| Free Text Line 3 | Represents additional information of the event which you can setup from event build step:1 E.g. Please bring your photo ID |
| Free Text Line 4 | Represents additional information of the event which you can setup from event build step:1 E.g. Directed by |
| Session Day of Week Short | Represents session start day in DDD format E.g. Tue |
| Session Day of Week Long | Represents session start day in DDDD format E.g. Tuesday |
| Session Date Short | Represents session start date in D/M/YYYY format E.g. 8/11/2019 |
| Session Start Date/Time | Represents session start date and time as one tag i.e. 8 July 2020, 7.30 am. |
| Session Start Time | Represents session start time in HH:MM TT format E.g. 06:50 PM |
| Event Start Day of Week Short | Represents event start day in DDD format E.g. Sun. |
| Event Start Day of Week Long | Represents event start day in DDDD format E.g. Sunday |
| Event Start Date Short | Represents event start date in D/M/YYYY format E.g. 8/11/2019. Tip: If the event has multiple dates/times, this tag will simply print the first date no matter what date was purchased. |
| Event Start Date Long | Represents event start date in D/MMM/YYYY format E.g. 8 Nov 2019. Tip: If the event has multiple dates/times, this tag will simply print the first date no matter what date was purchased. |
| Event Start Time | Represents event start time in HH:MM TT format E.g. 06:50 PM |
| Event End Day of Week Short | Represents event end day in DDD format E.g. Sun |
| Event End Day of Week Long | Represents event end day in DDDD format E.g. Sunday |
| Event End Date Short | Represents event end date in D/M/YYYY format E.g. 8/11/2019 |
| Event End Date Long | Represents event end date in D/MMM/YYYY format E.g. 8 Nov 2019 |
| Event End Time | Represents event end time in HH:MM TT format E.g. 06:50 PM |
| Open Pass End Date Short | Represents open pass end date in D/M/YYYY format E.g. 8/11/2019 |
| Open Pass End Date Long | Represents open pass end date in D/MMM/YYYY format E.g. 8 Nov 2019 |
| Open Pass End Time | Represents open pass end time in HH:MM TT format E.g. 06:50 PM |
| Ticket Type Name | Represents Ticket type name E.g. Adult, Child, Student, Concession etc. |
| Ticket Price | Represents the price of ticket exclude fees E.g. 40.00, 50.35 |
| Event Confirmation Number | This is an unique confirmation number. E.g. 10695- please note, you can simply use the default confirmation number tag above instead |
| Ticket Fee | Represents the per ticket fee charged for each ticket/item purchased E.g. 1.50 |
| Transaction Fee | Represents transaction fee charged once per order E.g. 1.00 |
| Payment Fee | Represents payment fee E.g.. credit card surcharge E.g. 0.50 |
| Ticket ID | This is an unique ticket Id number for each ticket/item purchased which is the same number used as the barcode number r. E.g. 201911060644458535 |
| TicketPrice TicketFee | Represents the total amount of ticket price and ticket fee E.g. (TicketPrice-40) + (TicketFee-2) = (TicketPrice TicketFee-42) |
| Transaction Sales Channel | Represents the name of transaction sales channel E.g. Walk-up, Online, Telephone etc. |
| Reporting Code | The reporting code assigned to the event. |
| Delivery Method | Represents form of delivery E.g. Post, E-ticket, Email Confirmation etc. |
| Delivery Fee | Represents delivery fee E.g.. a mail charge fee for sending an item through the postal service E.g. 1.50 |
| Price Level | Represents different price levels which define in pricing template E.g. General Admission, VIP etc. |
| Section Label | Represents the section label of a seating plan E.g. Upper, Middle, Balcony etc. |
| Row Label | Represents the row label of a seating plan E.g. A, AA, AB etc. |
| Seat Label | Represents the seat label of a seating plan E.g. 1, 2, 30 etc. |
| Booth Label | Represents the booth label of a seating plan. This option is currently not available |
| Door Name | Represents the door name E.g. Door A, Door B, Main Entrance etc. |
| No. of Items in Order | Please ignore this tag- it is not applicable to layouts |
| Total Amount | Please ignore this tag- it is not applicable to layouts |
| Area | Represents the area of the venue, E.g.. C1, C2, Upper, Lower. Once you click on an area, you can then select sections etc. This option is currently not available |
| Table Label | This is the table label i.e A, B. |
| Seat Desc | This is the description added against a seat such as Wheelchair only. You can add seat descriptions via Manage Venues/Manage Holds, Step 3: Seat Description/Seat View. |
| TH1 | This is the first field of Ticket Holder Information. THI allows you to collect customer/patron information for each ticket being purchased. For example, if four tickets are being purchased, it will ask for all four customer’s/patron’s details. This can be particularly handy for festivals where it’s required that each attendee have their details printed on each ticket – or if it’s an over age function, it’s possible to have a date of birth printed on each ticket. By default, this feature is turned off. |
| TH2 | This is the second field of Ticket Holder Information. THI allows you to collect customer/patron information for each ticket being purchased. For example, if four tickets are being purchased, it will ask for all four customer’s/patron’s details. This can be particularly handy for festivals where it’s required that each attendee have their details printed on each ticket – or if it’s an over age function, it’s possible to have a date of birth printed on each ticket. By default, this feature is turned off. |
| TH3 | This is the third field of Ticket Holder Information. THI allows you to collect customer/patron information for each ticket being purchased. For example, if four tickets are being purchased, it will ask for all four customer’s/patron’s details. This can be particularly handy for festivals where it’s required that each attendee have their details printed on each ticket – or if it’s an over age function, it’s possible to have a date of birth printed on each ticket. By default, this feature is turned off. |
| TH4 | This is the fourth field of Ticket Holder Information. THI allows you to collect customer/patron information for each ticket being purchased. For example, if four tickets are being purchased, it will ask for all four customer’s/patron’s details. This can be particularly handy for festivals where it’s required that each attendee have their details printed on each ticket – or if it’s an over age function, it’s possible to have a date of birth printed on each ticket. By default, this feature is turned off. |
| TH5 | This is the fifth field of Ticket Holder Information. THI allows you to collect customer/patron information for each ticket being purchased. For example, if four tickets are being purchased, it will ask for all four customer’s/patron’s details. This can be particularly handy for festivals where it’s required that each attendee have their details printed on each ticket – or if it’s an over age function, it’s possible to have a date of birth printed on each ticket. By default, this feature is turned off. |
| Ticket Number Customer | When building an event, under step 3: Schedule Editor, on the right hand side, click ‘Options’ to locate the Ticket Number field. This allows you to enter a starting and ending number that can be printed or displayed on your ticket layouts (eticket and printed layouts). Against the order, each ticket is also marked with the number allocated. If you work with promoters or external parties that sell tickets for you and you need to track the number range, i.e. Outlet A will receive tickets 1-50 and Outlet B 51-100, if the outlets do not sell all the quantity, you will easily be able to identify what hasn’t been sold and refund them back into your system to be sold again. |
| Customer ID | The customer who purchase the event, voucher etc., their unique customer id number that allows you to find them without having to type in their full details in customers and accounts. |
| Title | Title of the person who purchased the event, voucher etc., E.g. Mr, Mrs etc. |
| First Name | First name of the customer who purchased the event, voucher etc. E.g. Sam |
| Preferred Name | Preferred name of the customer who purchased the event, voucher etc. |
| Middle Name | Middle name of the customer who purchased the event, voucher etc. E.g. Peter |
| Last Name | Last name of the customer who purchased the event, voucher etc. E.g. Brown |
| Email address of the customer E.g. sam.brown@gmail.com | |
| Alternate Email | Alternate email address that the customer can be contacted on E.g. sam77@gmail.com |
| Mobile | Mobile/Cell number of the customer E.g. 123456789 |
| Work | Work phone number of the customer E.g. 987654321 |
| Home | Home number of the customer E.g. 02 1234 5678 |
| Fax | Fax number of the customer E.g. 123 456 7899 |
| Billing Address Line 1 | Billing address of the customer E.g. Level 5 |
| Billing Address Line 2 | If the billing address is long, line 2 can be used |
| Billing Address Line 3 | If the billing address is long, line 3 can be used |
| Billing Suburb/Town/City | This is the suburb/town/city E.g.. Sydney |
| Billing State/Province | This is the state/province E.g. NSW |
| Billing Country | This is the billing country E.g.. Australia |
| Billing Zip | This is the billing Zip/Postal Code E.g.. 2000 |
| Mailing Address Line 1 | Represents the Mailing address of the customer if its different from Billing address E.g. Level 8 |
| Mailing Address Line 2 | If the mailing address is long, line 2 can be used |
| Mailing Address Line 3 | If the mailing address is long, line 3 can be used |
| Mailing Suburb/Town/City | This is the Suburb/Town/City E.g.. Sydney |
| Mailing State/Province | This is the State/Province E.g. NSW |
| Mailing Country | This is the mailing country E.g.. Australia |
| Mailing Zip | This is the mailing Zip/Postal Code E.g.. 2000 |
| Profile Picture | Please ignore this tag- it is not applicable to layouts |
| Password | Please ignore this tag- it is not applicable to layouts |
| Date of Birth | Represents the Date of Birth of the customer in D/M/YYYY format E.g. 18/5/1990 |
| Age Range | Age range of the customer E.g. 18 to 30 |
| Age | Age of the customer E.g. 25 |
| Gender | Gender of the customer e.g. Male, Female |
| Company Name | Represents the company name that the customer belongs too |
| Position/Title | Position of the customer who purchased event, voucher etc. E.g. Manager |
| ABN | Represents the Customer’s ABN number E.g. 12345678910 |
| Website | Represents the customers website address if they have one |
| Date Created | Date when customer was created in the system in DD/MMM/YYYY format E.g. 01 Nov 2019 |