Email Placeholders
Eventixa email placeholders let you insert dynamic booking, event, attendee, ticket, payment, and customer information into reusable email templates.
Instead of manually writing details for every booking, you can build one template and let Eventixa replace placeholders with information from the actual registration.
Available in: Eventixa Core + Eventixa Pro
Location: Eventixa → Settings → Emails → Email Template → Manage
Related features: Email Templates, Customer Emails, Administrator Emails, Reminder Emails
What Is an Email Placeholder?
A placeholder is a dynamic value inside an email template.
For example, instead of manually writing: Hello John
you can use the supported placeholder for the recipient name.
When Eventixa generates the email, it replaces that placeholder with the correct value.
Why Use Placeholders?
Placeholders make email templates reusable.
Without placeholders, you would need separate email content for every:
- Customer
- Event
- Booking
- Ticket
- Attendee
- Payment
With placeholders, one template can work across many registrations.
Where to Use Placeholders
Go to: Eventixa → Settings → Emails → Email Template
Find the email template you want to edit.
Click: Manage
Depending on the template, placeholders can be used in supported fields such as:
- Email subject
- Email heading
- Message body
Use only the placeholders supported by that template.
Placeholder Example
A template could conceptually contain:
Hello {customer_name},
Your booking for {event_name} has been confirmed.
Booking: {booking_id}
When generated, the email could become:
Hello John Paul,
Your booking for Community Science Festival has been confirmed.
Booking: EC26001572
The exact placeholder names available in your Eventixa screen should always be used as shown by Eventixa.
Do Not Guess Placeholder Syntax
Different email systems use different formats.
For example, placeholders may use:
- Braces
- Double braces
- Percentage signs
- Another internal token format
Always copy the supported placeholder exactly as Eventixa displays it.
A misspelled placeholder may appear as raw text in the final email.
Event Placeholders
Event-related placeholders can be useful for inserting information such as:
- Event title
- Event date
- Event time
- Venue
- Organizer
- Event URL
These are useful across booking, reminder, ticket, and waitlist emails.
Event Title
A dynamic event-title placeholder lets the same email template work across multiple events.
Instead of:
Your Community Science Festival booking is confirmed
use the supported event-title placeholder.
Eventixa then inserts the correct event name.
Event Date
Event date is especially important for event notifications.
A confirmation or reminder should make it clear when the event takes place.
Recurring Event Date
For recurring events, use occurrence-aware event information where supported.
The email should identify the actual registered occurrence rather than only the recurring parent event.
For example:
August 16, 2028
rather than simply:
Community Science Festival
Event Time
Where supported, use the event-time placeholder to communicate:
- Start time
- End time
- All-day event state
This is especially helpful for reminder emails.
Venue
Venue placeholders can be useful for in-person and hybrid events.
They can help include:
- Venue name
- Location information
Do not hard-code a venue into a reusable template used across different events.
Organizer
Organizer information can help recipients know who is responsible for the event.
Use a supported organizer placeholder when the template needs that context.
Booking Placeholders
Booking placeholders can provide information such as:
- Booking reference
- Booking status
- Booking date
- Booking total
- Payment method
These are especially useful in customer and administrator booking emails.
Booking Reference
The booking reference is one of the most useful placeholders for support.
For example:
Booking: EC26001572
Customers can provide this reference when contacting the organizer.
Booking Status
Where supported, a booking-status placeholder can insert the current registration state.
Examples include:
- Pending
- Completed
- Cancelled
- Failed
- Expired
- Refunded
Be careful when using booking status in customer-facing messages because the wording should remain understandable.
Booking Total
A booking-total placeholder can display the payable or recorded amount.
This is useful for:
- Booking confirmations
- Payment confirmation
- Administrator notifications
Payment Placeholders
Payment-related placeholders can provide financial context.
Depending on the template, available values may include:
- Payment method
- Payment status
- Amount
- Transaction reference
Use payment placeholders only where financially appropriate.
Payment Method
This can identify whether the booking used:
- PayPal
- Stripe
- Local
- WooCommerce
- Free
Payment Status
Where supported, payment status can indicate:
- Pending
- Paid
- Failed
- Refunded
Do not confuse this with Booking Status.
Payment Amount
A payment amount should reflect the final applicable total after discounts.
For example:
Subtotal: $100
Coupon: -$20
Paid: $80
The email should not imply $100 was paid if the actual transaction was $80.
Transaction Reference
Transaction IDs can be useful in administrator emails.
Avoid exposing unnecessary financial references in customer-facing emails unless there is a clear reason.
Customer Placeholders
Customer placeholders can personalize booking-level emails.
They may provide values such as:
- Customer name
- Customer email
- First name
- Last name
The exact values depend on the applicable Eventixa template.
Customer vs Attendee
The customer/purchaser and attendee may be different people.
For example:
Purchaser: Eventixa Team
Attendee: John Paul
Do not automatically use purchaser placeholders when the email is intended for an attendee.
Attendee Placeholders
Attendee-level placeholders can be useful for:
- Attendee name
- Attendee email
- Ticket
- Registration type
- Custom attendee information
These are especially useful in ticket emails.
Multiple Attendees
If a booking contains several attendees, an attendee-level email should use the data belonging to the correct attendee.
For example:
- John receives John’s ticket
- Jane receives Jane’s ticket
Do not assume every attendee shares the purchaser’s information.
Ticket Placeholders
Ticket-related placeholders can insert information such as:
- Ticket name
- Ticket type
- Ticket price
- Quantity
- Ticket-related registration details
Ticket data is especially important for confirmation and attendee ticket emails.
Ticket Name
For example: Standard Event Pass
A ticket placeholder avoids hard-coding a particular ticket name into a template.
Ticket Price
Where supported, ticket price should respect the configured Eventixa currency.
For example: $19.00
Quantity
Booking-level templates may use quantity information to show how many registrations were purchased.
RSVP Placeholders
RSVP email templates may provide values related to:
- RSVP status
- Going / Not Going response
- Event
- Attendee
Use the placeholders appropriate to the RSVP template.
RSVP Response
A dynamic RSVP response can make an email clearer.
For example: Your RSVP has been updated to Not Going.
This avoids maintaining separate hard-coded wording for every possible response.
Reminder Email Placeholders
Reminder templates are especially dependent on placeholders because the same reminder content can be used across many events.
Useful dynamic information may include:
- Event name
- Event date
- Event time
- Venue
- Attendee
- Booking reference
Waitlist Placeholders
Requires Eventixa Pro
Waitlist templates can use dynamic information relating to:
- Event
- Ticket
- Waitlist visitor
- Reservation
- Expiration
These are important for time-sensitive waitlist emails.
Waitlist Seat Available
A Seat Available template should clearly identify:
- Event
- Ticket
- Required action
- Reservation expiration where supported
Use placeholders for time-sensitive values instead of hard-coding them.
Waitlist Offer Expiration
If the reservation expiration changes from one offer to another, a dynamic expiration placeholder is more reliable than static wording.
Virtual Event Placeholders
Virtual and Hybrid event emails may need to include access-related information where Eventixa supports it.
Do not manually paste managed Zoom or Google Meet credentials into reusable templates.
Use Eventixa-controlled values and access rules.
Access Timing
Even when virtual access information is available as a placeholder, it should respect Eventixa’s access workflow.
Do not use a generic template to expose meeting information earlier than intended.
Coupon and Discount Values
Where supported, placeholders can help display discount information.
For example:
- Coupon code
- Discount
- Final total
This is useful when a customer needs to understand why the amount paid differs from the original subtotal.
Currency Formatting
Monetary placeholders should use the applicable Eventixa currency formatting.
For example: $1,250.00 or another format based on your currency settings.
Do not manually add currency symbols around a monetary placeholder unless the placeholder is documented as returning only the raw number.
Otherwise, you may accidentally generate: $$19.00
Placeholder in Subject Lines
Where supported, placeholders can make subjects more specific.
For example: Your booking for {event_name} is confirmed
This can become: Your booking for Community Science Festival is confirmed
Keep Subjects Short
Even with dynamic placeholders, keep email subjects concise.
Very long event titles can make already-long subjects difficult to read.
Placeholder in Headings
Dynamic placeholders can also be useful in email headings.
For example: Your {event_name} Registration
Use them only when they improve clarity.
Placeholder in Message Body
The message body is usually the most flexible place for dynamic content.
A useful body might combine:
- Customer name
- Event
- Date
- Ticket
- Booking reference
Example Confirmation Template
Conceptually:
Hello {customer_name},
Your booking for {event_name} is confirmed.
Booking: {booking_id}
Date: {event_date}
Ticket: {ticket_name}
Total: {booking_total}
This creates a reusable confirmation template.
Again, use the exact placeholder syntax displayed by Eventixa rather than copying conceptual names from documentation examples.
Missing Placeholder Data
A supported placeholder may sometimes have no value.
For example:
- Venue is not assigned
- Organizer is empty
- Transaction ID does not exist
- Ticket is free
Consider how the email reads when optional information is missing.
Avoid Awkward Empty Values
Instead of creating content such as: Venue:
with nothing afterward, only include optional data when it makes sense for your template and workflow.
Raw Placeholder Appears in Email
If the customer receives something like: {event_name}
instead of the actual event name, possible causes include:
- Placeholder was misspelled
- Placeholder is not supported by that template
- Syntax is wrong
- Template parsing did not occur
Use the placeholder exactly as Eventixa provides it.
Placeholder Works in One Template but Not Another
Not every placeholder is necessarily available in every email context.
For example, an attendee-specific placeholder may not have meaningful data in a general administrator template.
Use the placeholder list appropriate to the template you are editing.
Do Not Invent Placeholders
If Eventixa does not list a particular placeholder, do not assume one exists.
Use only documented or interface-provided placeholders.
Test After Adding Placeholders
Always trigger a real test email after editing a template.
Verify that:
- Placeholder is replaced
- Correct value appears
- Formatting is correct
- No raw placeholder remains
Test Recurring Events
For recurring events, verify:
- Correct occurrence date
- Correct event title
- Correct ticket
This is particularly important for reminder and booking emails.
Test Multiple Attendees
Create a booking containing multiple attendees.
Verify attendee-level emails use the correct individual data.
Test Coupons
For a discounted booking, check that monetary placeholders show the correct final amount.
Test Free Tickets
Make sure payment-related template content still makes sense when the booking total is zero.
Test RSVP
Verify RSVP placeholders accurately show:
- Going
- Not Going
- Updated response
Test Waitlist
Requires Eventixa Pro
Test:
- Join waitlist
- Seat available
- Offer expiration
Make sure waitlist placeholders are resolved correctly in every message.
Security and Privacy
Email placeholders can expose personal or operational information.
Only include data the recipient actually needs.
Avoid inserting:
- Internal notes
- API credentials
- Secret keys
- Passwords
- Full card data
- Private virtual-provider credentials
Customer-Facing vs Administrator Placeholders
An administrator may need information that a customer does not.
For example: Transaction ID may be useful internally but unnecessary in a customer ticket email.
Design templates based on the recipient.
Common Problems
Placeholder Is Displayed as Raw Text
Check spelling and supported syntax.
Wrong Event Information Appears
Verify the booking and recurring occurrence.
Wrong Attendee Name Appears
Make sure the template is using attendee-level rather than purchaser-level data.
Amount Is Incorrect
Check:
- Ticket quantity
- Coupon
- Final total
- Currency
Placeholder Is Blank
The related value may not exist for that booking.
Transaction Placeholder Is Empty
This can be expected for:
- Free tickets
- RSVP
- Offline payment before verification
Waitlist Expiration Is Missing
Verify that the waitlist workflow and applicable reservation data exist.
Virtual Meeting Details Are Missing
Check the attendee’s access eligibility and the configured virtual-event access rules.
Recommended Placeholder Workflow
- Go to Eventixa → Settings → Emails → Email Template.
- Click Manage on the desired template.
- Review the available placeholder list.
- Copy the placeholder exactly.
- Insert it into the subject, heading, or message where supported.
- Save Changes.
- Trigger the applicable workflow.
- Open the received email.
- Verify every placeholder was replaced.
- Test relevant edge cases.
Recommended Template Design
A good email usually needs only a small number of dynamic values.
For example:
- Recipient name
- Event
- Date
- Booking reference
- Ticket
Avoid filling the template with every available placeholder simply because it exists.
Important Notes
- Email placeholders insert dynamic Eventixa data into reusable templates.
- Use the exact placeholder syntax shown by Eventixa.
- Do not guess or invent placeholder names.
- Placeholder availability can vary by email template.
- Customer, attendee, booking, payment, RSVP, reminder, and waitlist templates may expose different values.
- Purchaser and attendee are not always the same person.
- Recurring-event placeholders should represent the correct occurrence.
- Monetary values should respect Eventixa currency formatting.
- Always test templates after adding or changing placeholders.
- Never expose sensitive credentials or internal-only information through email placeholders.
