Merge Tags are transaction-specific data/code that you can insert into your HTML Email and Ticket Templates. This could be data such as event name, customer name, ticket specifics, etc.
There are different kinds of Tags depending on the data that you want to include - for more info about Merge Tags and how to add them to your templates, see the Merge Tags help article here.
Here is the full list of Tags that are available for you to choose for your Templates:
1. GLOBAL TAGS
a) Transaction Info - data that is generic across the transaction:
| Data Point | Tag | Example Usage | Example Value |
|---|---|---|---|
| Customer First Name | CUSTOMER.FNAME | {{ CUSTOMER.FNAME }} | Steve |
| Customer Last Name | CUSTOMER.LAST_NAME | {{ CUSTOMER.LAST_NAME }} | Rogers |
| Customer Email | CUSTOMER.EMAIL_ADDRESS | {{ CUSTOMER.EMAIL_ADDRESS }} | cap@avengers.com |
| Reference number | TRANSACTION.REFERENCE | {{ TRANSACTION.REF }} | 3f9855eccf974196ba14a5759e3d8747 |
| Transaction Total | TRANSACTION.TOTAL | {{ TRANSACTION.GROSS }} | 289.00 |
| Transaction Tax | TRANSACTION.TAX | {{ TRANSACTION.TAX }} | 9.00 |
| Transaction Created At | TRANSACTION.CREATED_AT | {{ TRANSACTION.CREATED_AT }} | Sat 17 April, 10:10 AM |
b) Organisation Info - data related to your Organisation in Line-Up:
| Data Point | Tag | Example Usage | Example |
|---|---|---|---|
| Name | ORGANISATION.NAME | {{ ORGANISATION.NAME }} | ACME Theatres |
| Image | ORGANISATION.IMAGE | {{ ORGANISATION.IMAGE }} | acme_logo.jpg |
| Email Address | ORGANISATION.EMAIL_ADDRESS | {{ ORGANISATION.EMAIL_ADDRESS }} | boxoffice@acemtheatres.com |
| Full Address | ORGANISATION.FULL_ADDRESS | {{ ORGANISATION.FULL_ADDRESS }} | 10 King Road, Godalming, Surrey, GU7 5DA, UK |
| Street Address | ORGANISATION.ADDRESS_STREET | {{ ORGANISATION.ADDRESS_STREET }} | 10 King Road |
| Town Address | ORGANISATION.ADDRESS_TOWN | {{ ORGANISATION.ADDRESS_TOWN }} | Godalming |
| City Address | ORGANISATION.ADDRESS_CITY | {{ ORGANISATION.ADDRESS_CITY }} | Surrey |
| Postcode Address | ORGANISATION.ADDRESS_POSTCODE | {{ ORGANISATION.ADDRESS_POSTCODE }} | GU7 5DA |
| Country Address | ORGANISATION.ADDRESS_COUNTRY | {{ ORGANISATION.ADDRESS_COUNTRY }} | UK |
| Currency Symbol | ORGANISATION.CURRENCY_SYMBOL | {{ ORGANISATION.CURRENCY_SYMBOL }} | £ |
| Currency | ORGANISATION.CURRENCY | {{ ORGANISATION.CURRENCY }} | GBP |
2. LOOP TAGS
a) Transaction Item
Here are the transaction items available to you and an example of the loop you might create to place the values in:
| Data Point | Loop example |
|---|---|
| TICKETS | {% for ticket in TRANSACTION.TICKETS %}{% endfor %} |
| DELIVERY_METHODS | {% for delivery_method in TRANSACTION.DELIVERY_METHODS %}{% endfor %} |
| PAYMENTS | {% for product in TRANSACTION.PRODUCTS%}{% endfor %} |
| PRODUCTS | {% for payment in TRANSACTION.PAYMENTS %}{% endfor %} |
b) Transaction Item - Ticket
The following values are available for TICKETS, to be placed inside a loop, e.g.: {% for ticket in TRANSACTION.TICKETS %} {% endfor %}:
| Data Point | Tag | Example Usage | Example Value |
|---|---|---|---|
| Ticket Face Value | FACE_VALUE | {{ ticket.PRICE_VALUE }} | 100.00 |
| Ticket Tax | TAX | {{ ticket.TAX }} | 20.00 |
| Ticket Gross | GROSS | {{ ticket.GROSS }} | 120.00 |
| Ticket Created At (Order date and time) | CREATED_AT | {{ ticket.CREATED_AT }} | 17/11/2028 09:00pm |
| Ticket Discount Name | DISCOUNT.PRICE.NAME | {{ ticket.PRICE.DISCOUNT.NAME }} | CHRISTMAS2028 |
| Ticket Discount Amount | DISCOUNT.PRICE.AMOUNT | {{ ticketPRICE..DISCOUNT.AMOUNT }} | 10.00 |
| Ticket Discount Type | DISCOUNT.TYPE | {{ ticket.DISCOUNT.TYPE }} | Fixed |
| Ticket Band Name | BAND_NAME | {{ ticket.BAND_NAME }} | Band A |
| Ticket Variant Name | VARIANT_NAME | {{ ticket.VARIANT_NAME }} | Adult |
| Ticket Seat Group | SEAT_GROUP | {{ ticket.SEAT_GROUP }} | Stalls |
| Ticket Seat | SEAT | {{ ticket.SEAT }} | A1 |
| Ticket Seat Type | SEAT_TYPE | {{ ticket.SEAT_TYPE }} | Restricted View |
| Ticket Event Name | EVENT.NAME | {{ ticket.EVENT.NAME }} | Hamlet |
| Ticket Event Image | EVENT.IMAGE | {{ ticket.EVENT.IMAGE }} | yorick.png |
| Ticket Event Short Description | EVENT.SHORT_DESCRIPTION | {{ ticket.EVENT.SHORT_DESCRIPTION }} | A modern retelling of Shakepeare’s classic. |
| Ticket Event Venue Name | EVENT.VENUE_NAME | {{ ticket.EVENT.VENUE_NAME }} | ACME Theatre |
| Ticket Event Venue Address | EVENT.VENUE_ADDRESS | {{ ticket.EVENT.VENUE_ADDRESS }} | 1 Stanley Road, London, W1 8AG |
| Ticket Event Interval Time | EVENT.INTERVAL_TIME | {{ ticket.EVENT.INTERVAL_TIME }} | 15 |
| Ticket Event Run Time | EVENT.RUN_TIME | {{ ticket.EVENT.RUN_TIME }} | 120 |
| Ticket Performance Start Date | PERFORMANCE_START_DATE | {{ ticket.PERFORMANCE_START_DATE }} | 01/09/2028 |
| Ticket Performance Start Time | PERFORMANCE_START_TIME | {{ ticket.PERFORMANCE_START_TIME }} | 7:30 pm |
| Ticket Performance End Time | PERFORMANCE_END_TIME | {{ ticket.PERFORMANCE_END_TIME }} | 9:30 pm |
| Ticket Performance End Date | PERFORMANCE_END_DATE | {{ ticket.PERFORMANCE_END_DATE }} | 01/09/2028 |
| Ticket Barcode | BARCODE | {{ ticket.BARCODE }} | aoj4fi8k7Nb4v2A2H1SK2 |
| Ticket Barcode Image | BARCODE_IMAGE | {{ ticket.BARCODE_IMAGE }} | aoj4fi8k7Nb4v2A2H1SK2.png |
c) Transaction Item - Ticket - Price Adjusters
Within ticket transaction items, you can access data related to price adjusters on that ticket. This can be achieved by placing another loop within your TRANSACTION.TICKETS loop, e.g. {% for ticket in TRANSACTION.TICKETS %} {% for PRICE_ADJUSTER in ticket.PRICE_ADJUSTERS %} {{ YOUR TAG HERE }} {% endfor %} {% endfor %}:
| Data Point | Loop Example |
|---|---|
| Ticket Price Adjuster | {% for adjuster in ticket.ADJUSTERS %} {% endfor %} |
Price Adjuster Tags - to be placed within the loops above:
| Data Point | Tag | Example Usage | Example |
|---|---|---|---|
| Price Adjuster Name | NAME | {{ adjuster.NAME }} | Inside 1 |
| Price Adjuster Description | DESCRIPTION | {{ adjuster.DESCRIPTION }} | In-depth description of adjuster |
| Price Adjuster External | EXTERNAL |
{% if adjuster.EXTERNAL %} {{ adjuster.NAME }} {% endif % } |
In the example to the left, we’re saying if there are any external adjusters, then show the name of the external adjuster. |
| Price Adjuster Rate Type | RATE_TYPE | {{ adjuster.RATE_TYPE }} | FIXED |
| Price Adjuster Rate | RATE | {{ adjuster.RATE }} | 1.50 |
d) Transaction Item - Delivery Method
The following values are available for DELIVERY_METHODS, to be placed inside a Loop, e.g.: {% for delivery_method in TRANSACTION.DELIVERY_METHODS %} { % endfor %}:
| Data Point | Tag | Example Usage | Example Value |
|---|---|---|---|
| Delivery Method Name | METHOD_NAME | {{ delivery_method.NAME}} | Postage |
| Delivery Method Description | DESCRIPTION | {{ delivery_method.DESCRIPTION }} | Tickets sent by first class post |
| Delivery Method Price | PRICE | {{ delivery_method.PRICE }} | 1.63 |
| Delivery Method Tax | TAX | {{ delivery_method.TAX }} | 0.32 |
| Delivery Method Gross | GROSS | {{ delivery_method.GROSS }} | 1.95 |
| Delivery Method Created At (Order date and time) | CREATED_AT | {{ delivery_method.CREATED_AT }} | 17/11/2028 09:00pm |
| Delivery Method Image | IMAGE | {{ delivery_method.IMAGE }} | postage.png |
d) Transaction Item - Payment
The following values are available for PAYMENTS, to be placed inside a Loop, e.g.: {% for payment in TRANSACTION.PAYMENTS %} { % endfor %}:
| Data Point | Tag | Example Usage | Example Value |
|---|---|---|---|
| Payment Name | NAME | {{ payment.NAME }} | Online Payment Card |
| Payment Net | NET | {{ payment.NET }} | 100 |
| Payment Tax | TAX | {{ payment.TAX }} | 20 |
| Payment Total | TOTAL | {{ payment.TOTAL }} | 120 |
| Payment Type | TYPE | {{ payment.TYPE }} | Stripe |
| Payment Created At (Order date and time) | CREATED_AT | {{ payment.CREATED_AT }} | 17/11/2028 09:00pm |
f) Transaction Item - Product
The following values are available for PRODUCTS, to be placed inside a loop, e.g.: {% for product in TRANSACTION.PRODUCTS %} {% endfor %}:
| Data Point | Tag | Example Usage | Example |
|---|---|---|---|
| Product Title | TITLE | {{ product.TITLE }} | T-shirt |
| Product Description | DESCRIPTION | {{ product.DESCRIPTION }} | Bands official t-shirt |
| Product Tax | TAX | {{ product.TAX }} | 4.17 |
| Product Total | PRICE.VALUE | {{ product.PRICE.VALUE }} | 25 |
| Created At (Order date and time) | CREATED_AT | {{ product.CREATED_AT }} | 17/11/2028 09:00pm |
| Discount Name | PRICE.DISCOUNT.NAME | {{ product.PRICE.DISCOUNT.NAME }} | CHRISTMAS2028 |
| Discount Amount | PRICE.DISCOUNT.AMOUNT | {{ product.PRICE.DISCOUNT.AMOUNT }} | 10.00 |
g) Transaction Item - Product - Price Adjusters
Within product transaction items, you can access data related to price adjusters on that product. This can be achieved by placing another loop within your TRANSACTION.PRODUCTS loop, e.g. {% for product in TRANSACTION.PRODUCTS %} {% for PRICE_ADJUSTER in product.PRICE_ADJUSTERS %} {{ YOUR TAG HERE }} {% endfor %} {% endfor %}:
| Data Point | Loop Example |
|---|---|
| Product Price Adjusters | {% for price_adjuster in product.ADJUSTERS %} {% endfor %} |
Price Adjuster Tags - to be placed within the loops above:
| Data Point | Tag | Example Usage | Example |
|---|---|---|---|
| Price Adjuster Name | NAME | {{ adjuster.NAME }} | Inside 1 |
| Price Adjuster Description | DESCRIPTION | {{ adjuster.DESCRIPTION }} | In-depth description of adjuster |
| Price Adjuster External | EXTERNAL |
{% if adjuster.EXTERNAL %} {{ adjuster.NAME }} {% endif % } |
In the example to the left, we’re saying if there are any external adjusters, then show the name of the external adjuster. |
| Price Adjuster Rate Type | RATE_TYPE | {{ adjuster.RATE_TYPE }} | FIXED |
| Price Adjuster Rate | RATE | {{ adjuster.RATE }} | 1.50 |
Having issues with Merge Tags? Contact us here with examples of code that aren't working for you.
Comments
0 comments
Please sign in to leave a comment.