Eventixa includes a powerful Placeholder System that automatically inserts booking, customer, event, attendee, and payment information into email templates. Instead of manually editing each email, placeholders are replaced with real data when the email is generated.
This allows a single email template to be reused for every booking while delivering personalized information to each recipient.
Available in: Eventixa Core
Additional placeholders available in: Eventixa Pro
How Placeholders Work
Placeholders are special tags enclosed in curly braces ({}).
For example:
Hello {customer_name},When the email is sent, Eventixa replaces the placeholder with the actual value.
Example output:
Hello Emily Johnson,All replacements happen automatically before the email is delivered.
Using Placeholders
Placeholders can be used in:
- Email Subject
- Email Heading
- Email Body
They can also be combined with Eventixa’s HTML information blocks to create rich, professional email layouts.
Example:
Hello {customer_name},
Thank you for registering for {event_name}.
Your booking number is {booking_number}.
{booking_summary}
{booking_button}Site Placeholders
These placeholders insert general website information.
| Placeholder | Description |
|---|---|
{site_title} | Website title. |
{site_url} | Website URL. |
Booking Placeholders
Booking placeholders provide information about the customer’s reservation.
| Placeholder | Description |
|---|---|
{booking_id} | Internal booking ID. |
{booking_number} | Customer-facing booking number. |
{booking_date} | Date the booking was created. |
{booking_status} | Current booking status. |
{booking_total} | Total booking amount. |
{booking_url} | URL to the booking details page. |
{booking_link} | Clickable link to the booking details page. |
Customer Placeholders
These placeholders insert customer information collected during checkout.
| Placeholder | Description |
|---|---|
{customer_name} | Customer’s full name. |
{customer_first_name} | Customer’s first name. |
{customer_last_name} | Customer’s last name. |
{customer_email} | Customer’s email address. |
{customer_phone} | Customer’s phone number. |
Event Placeholders
These placeholders display event information.
| Placeholder | Description |
|---|---|
{event_name} | Event name. |
{event_title} | Event title. |
{event_url} | Event page URL. |
{event_start_date} | Event start date. |
{event_start_time} | Event start time. |
{event_end_date} | Event end date. |
{event_end_time} | Event end time. |
{event_date_time} | Combined event date and time. |
{event_start} | Formatted event start date and time. |
Venue Placeholders
Venue placeholders display event location information.
| Placeholder | Description |
|---|---|
{venue_name} | Venue name. |
{venue_address} | Venue address. |
{venue_url} | Venue page URL. |
Organizer Placeholders
Organizer placeholders provide organizer details.
| Placeholder | Description |
|---|---|
{organizer_name} | Organizer name. |
{organizer_email} | Organizer email address. |
{organizer_phone} | Organizer phone number. |
{organizer_url} | Organizer page URL. |
Payment Placeholders
Payment placeholders display payment-related information.
| Placeholder | Description |
|---|---|
{payment_status} | Current payment status. |
{payment_method} | Payment gateway or method used. |
{transaction_id} | Payment transaction ID, when available. |
Attendee Placeholders
Attendee placeholders are useful for attendee-related emails.
| Placeholder | Description |
|---|---|
{attendee_name} | Attendee’s full name. |
{attendee_email} | Attendee’s email address. |
{attendee_phone} | Attendee’s phone number. |
{attendee_status} | Registration status. |
{ticket_name} | Ticket name. |
{ticket_number} | Ticket number. |
Note: For bookings containing multiple attendees, attendee-specific placeholders use the attendee context available to the email being generated.
HTML Information Blocks
Eventixa provides pre-built HTML blocks that automatically generate complete sections of an email.
These blocks should be used whenever you want to display formatted booking information without manually creating tables or layouts.
| Placeholder | Description |
|---|---|
{booking_details} | Complete booking information section. |
{booking_summary} | Booking summary table. |
{customer_information} | Customer information section. |
{event_information} | Event information section. |
{ticket_summary} | Ticket summary section. |
{payment_summary} | Payment summary section. |
{order_summary} | Order summary section. |
{feature_information} | Additional feature-specific information. |
{booking_button} | Call-to-action button linking to the booking details page. |
These placeholders generate HTML automatically and should be placed on their own line within the email template.
Example Email
Example template:
Subject:
Booking Confirmation – {event_name}
Heading:
Your Booking is Confirmed
Content:
Hello {customer_name},
Thank you for registering for {event_name}.
Booking Number:
{booking_number}
{booking_summary}
{event_information}
{payment_summary}
{booking_button}When sent, Eventixa automatically replaces every placeholder with the appropriate booking information.
Placeholder Availability
Not every placeholder is applicable to every email.
For example:
- Booking Confirmation uses booking, customer, event, and payment placeholders.
- Payment Confirmation includes payment-related placeholders.
- Booking Refunded uses booking and payment placeholders.
- Administrator Notifications can use booking, customer, event, and payment placeholders.
If a placeholder does not have a value for the current email, it may be left empty or omitted, depending on the template and context.
Best Practices
- Use placeholders instead of manually entering booking or customer information.
- Use HTML information blocks for booking, payment, and event summaries to maintain a consistent email layout.
- Keep subjects concise while including important placeholders such as
{event_name}or{booking_number}. - Test email templates after making changes to verify that placeholders are replaced correctly.
- Avoid modifying the placeholder names, as they must exactly match the supported syntax.
Tips
- Placeholders make every email personalized without requiring multiple templates.
- Eventixa automatically replaces placeholder values at the time the email is generated, ensuring recipients receive the latest booking information.
- HTML information blocks provide a professional, consistent layout and are recommended over manually creating tables or repeating individual placeholders.
- Eventixa Pro uses the same placeholder system for additional email types, including ticket delivery, QR code emails, invoices, reminders, and waitlist notifications, making customization consistent across all notifications.
