{"id":1896614,"date":"2019-10-18T13:19:38","date_gmt":"2019-10-18T17:19:38","guid":{"rendered":"https:\/\/theeventscalendar.com\/knowledgebase\/disable-the-ticket-email-2\/"},"modified":"2026-04-09T15:25:33","modified_gmt":"2026-04-09T19:25:33","slug":"customizing-ticket-emails","status":"publish","type":"post","link":"https:\/\/theeventscalendar.com\/knowledgebase\/customizing-ticket-emails\/","title":{"rendered":"Customizing Ticket Emails"},"content":{"rendered":"\n

Conditionally Disable Ticket Emails<\/h2>\n\n\n\n

When using the Event Tickets plugin, tickets are automatically emailed to your customers as soon as purchase is complete. The confirmation email includes the ticket details and is essential to the attendee experience. However, there may be scenarios where you want to turn off confirmation emails, especially if you’re handling ticket distribution differently. These solutions enable you to customize email behavior, such as disabling emails for specific providers or restricting them to certain events, giving you complete control over the timing and recipients of the emails.<\/p>\n\n\n\n

WooCommerce<\/h4>\n\n\n\n

The following PHP code snippet disables the sending of ticket confirmation emails for tickets using WooCommerce as the payment platform,<\/p>\n\n\n

\n\/* Disable tickets emails for Woo *\/\nadd_filter( 'tribe_tickets_plus_email_enabled', '__return_false' );\n<\/pre><\/div>\n\n\n
It will not, however, affect the order emails WooCommerce sends.<\/p>\n\n\n\n
Disable Ticket Emails for Certain Events<\/h4>\n\n\n\n
The following code snippet customizes how email notifications are handled in Event Tickets by preventing emails from being sent for specific events. It works by checking if the email is related to an event and whether the event ID matches any in a list of excluded event IDs (like 123, 124, or 125). If the event is on the list, the code stops the email from being sent by returning null<\/code>.<\/p>\n\n\n\n
This can be useful when you want to block email notifications for certain events, such as private gatherings or internal testing events.<\/p>\n\n\n
\n&lt;?php \/\/Do not copy this line\n\nadd_filter( 'tec_tickets_emails_dispatcher_to', function ( $to, $dispatcher ) {\n\n\t\/\/ Event IDs for which the email should not be sent.\n\t$excluded_event_ids = [ 123, 124, 125 ];\n\n\tif ( ! function_exists( 'tribe_is_event' ) ) {\n\t\treturn $to;\n\t}\n\n\t$email    = $dispatcher->get_email();\n\t$event_id = $email->get( 'post_id' );\n\n\t\/\/ Check if it's an event and is in the excluded event list.\n\tif ( tribe_is_event( $event_id ) &amp;&amp; in_array( $event_id, $excluded_event_ids, true ) ) {\n\t\treturn null;\n\t}\n\n\treturn $to;\n}, 10, 2 );\n<\/pre><\/div>\n\n\n
Add the code snippet to the functions.php<\/em> file of your theme, or use your preferred method for integrating snippets into your WordPress site, such as the free Code Snippets<\/a> plugin.<\/p>\n\n\n\n
Extending Event Tickets Emails Placeholders<\/h2>\n\n\n\n
When using Tickets Commerce<\/a><\/span> as the payment method, order emails and purchase receipts are handled by Tickets Commerce itself. Although email templates include placeholders, not all are available for every type of email. You can find more information about the different types of emails and the available placeholders for each one here.<\/p>\n\n\n\n
Event Tickets Emails Knowledgebase<\/a><\/p>\n\n\n\n
By default, the Completed Order email from Tickets Commerce includes a limited set of placeholders and does not provide built-in support for adding custom placeholders such as the purchaser’s name or event title. However, one can extend this functionality with custom coding. This article provides a snippet that enables the use of {purchaser_name}<\/code> and {event_title}<\/code> placeholders in the Completed Order email.<\/p>\n\n\n\n
Adding Custom Placeholders to Completed Order Email<\/h2>\n\n\n\n
Add the following PHP code to the site to be able to use {event_title}<\/code> and {purchaser_name}<\/code> placeholders in the Completed Order email.<\/p>\n\n\n
\n&lt;?php \/\/Do not copy this line\n\nadd_filter( 'tec_tickets_emails_completed-order_placeholders', function ( $placeholders, $id, $email ) {\n\t\/\/ Ensure the email object contains attendees\n\t$attendees = $email->get( 'attendees' );\n\n\tif ( empty( $attendees ) || ! is_array( $attendees ) ) {\n\t\treturn $placeholders;\n\t}\n\n\t\/\/ Extract the first attendee's purchaser name and event ID\n\t$first_attendee = reset( $attendees );\n\t$purchaser_name = $first_attendee['purchaser_name'] ?? '';\n\t$event_id       = $first_attendee['event_id'] ?? 0;\n\t$event_title    = '';\n\n\t\/\/ Retrieve event title if a valid event ID is available\n\tif ( $event_id &amp;&amp; ( $event = tribe_get_event( $event_id ) ) ) {\n\t\t$event_title = $event->post_title ?? '';\n\t}\n\n\t\/\/ Add placeholders if values exist\n\tif ( $purchaser_name ) {\n\t\t$placeholders['{purchaser_name}'] = sanitize_text_field( $purchaser_name );\n\t}\n\n\tif ( $event_title ) {\n\t\t$placeholders['{event_title}'] = sanitize_text_field( $event_title );\n\t}\n\n\treturn $placeholders;\n}, 10, 3 );\n<\/pre><\/div>\n\n\n
Add the code snippet to the functions.php<\/em> file of your theme, or use your preferred method for integrating snippets into your WordPress site, such as the free Code Snippets<\/a> plugin.<\/p>\n\n\n\n
The snippet retrieves attendee information from the email object. It obtains the name of the individual who made the purchase, along with the associated event ID. Using this event ID, the title of the event is then retrieved. These details are then added to the available placeholders in the email.<\/p>\n\n\n\n
Add Ticket Description to Ticket Confirmation Emails<\/h2>\n\n\n\n
When creating tickets with the Event Tickets<\/a> plugin, the Description<\/strong> field offers a space to incorporate extra details that pertain specifically to that ticket. This is ideal for providing context or information that may enhance the ticket\u2019s relevance and clarity for the users.<\/p>\n\n\n
\n
\"Ticket<\/figure><\/div>\n\n\n
For example, you might use it to share:<\/p>\n\n\n\n