E-mail

E-mail

Tickera sends automatic transactional emails throughout the ticket purchase process. Depending on your workflow, emails can go to buyers, attendees, and even your event staff (admins). You control the content, the sender information, and whether tickets are delivered directly via attachment or through download links.

When you open Tickera -> Settings -> E-mail, you’ll see multiple collapsible sections. Each section represents a specific email scenario:

• Attendee order completed email 
• Client order placed email
• Client order completed email
• Client order refunded email
• Admin order placed email
• Admin order completed email
• Admin order refunded email

All email types share the same set of options, so once you configure one, the rest follow the same logic.

Configuring an email

Each email block contains:

Enable
Turn the email on or off.

Subject
The subject your customer/admin sees in their inbox. Example: Your tickets are ready!

From name
Displayed name in the recipient’s inbox (often the event or organizer name).

From e-mail address
Displayed sender address. For best deliverability, use an email on your own domain (e.g., info@yourdomain.com).

E-mail content
This is the body of the email. You can:

• Use the Visual editor, or
• Switch to the Text editor for full HTML editing (yes, you can paste custom HTML layouts and styling here).

Below the editor, Tickera shows available placeholders — dynamic values automatically replaced when the email is sent. Depending on the nature of the email, the list of available Tickera placeholders is different and is listed below the text area of the content of the email. The complete list of available placeholders is as follows:

Available placeholders depend on the type of email. For example, buyer/attendee emails support ticket download links, while admin emails include direct order-management links.

Sending tickets as attachments

Tickera gives you the option to send the ticket itself as a PDF attachment, but this option exists only for attendee emails (Attendee Order Completed). It is intentionally not available for emails sent to the buyer.

Why is that?

When a buyer purchases multiple tickets in a single order, sending all of those PDFs as attachments in a single email can:

• dramatically increase the email size (tickets may include background images, logos, QR codes, etc.),
• exceed attachment limits imposed by email service providers,
• trigger spam filters or hard delivery failures.

Tickera avoids these issues by attaching only the attendee’s own ticket to attendee notification emails.
Buyers still receive the download link, so they can retrieve all their tickets—just without risking an overloaded email server.

In short:

• Attendees can receive their ticket attached to the email
• Buyers do not receive attached tickets (they get download links instead)

This design maximizes deliverability and removes the risk of emails bouncing because they are too large.

Customizing the table of purchased tickets (optional)

Every email that includes a table listing the tickets purchased in the order shows basic ticket information, but Tickera gives you full control over what appears in that list.

Using the solution described here you can decide whether to show or hide elements such as:

• event title
• event date and time
• event location
• ticket type
• attendee first/last name
• ticket download link

...but here is the game-changer: You can include the QR code of each ticket directly inside the email.

This means that buyers can simply open the email on their phone at the venue and have their tickets scanned straight from the email body—no downloading, printing, or searching for PDFs required.

This is incredibly useful when:

• attendees don’t want to print anything,
• ticket PDFs are intentionally disabled,
• organizers want the fastest check-in experience possible.

Combined with the “Send attachments to attendees” option, this gives you complete control over both deliverability and convenience.

Email sending method

At the bottom of the screen, you’ll find the Miscellaneous section:

E-mail send type

• WP Mail (default) – uses WordPress' default mail function
• PHP Mail – alternative method if the first one doesn’t work

If your emails fail to send, switching this setting can sometimes resolve the issue. If both fail, consider using an SMTP plugin such as WP Mail SMTP or Post SMTP to improve deliverability. Please note that these plugins will only work if WP Mail is selected in Tickera's Email Send Type.

Spam filtering notice

Some email providers (especially Gmail and Outlook) may flag automated emails as spam. If a customer does not receive the message, ask them to check the spam folder first. To reduce spam risk, use a professional sender address (e.g. tickets@yourdomain.com rather than @gmail.com). However, even perfectly configured systems can run into email deliverability problems, especially when relying on default hosting mail functions.

• For help diagnosing issues, refer to:
  Why emails are not delivered or end up in spam (Tickera FAQ)
• For a deeper guide to email reliability, including SPF/DKIM/DMARC setup and SMTP usage:
  Tackling email deliverability in WordPress like a pro (Tickera blog post)

If you’re using the Check-in Notifications add-on

That add-on adds its own email configuration area right here in the same E-mail section, so all message-related settings for ticketing live in one place.

You can find complete documentation about this add-on here.

If you're using Bridge for WooCommerce

When Tickera is used alongside WooCommerce via the Bridge for WooCommerce add-on:

• The Email settings screen will look different.
• Emails are handled by WooCommerce’s system.
• Available placeholders are different.

Full WooCommerce-specific email documentation is here.