Transactional Emails

Transactional Emails allow you to send automated, one-to-one emails through Transpond when a particular action or event takes place.

For example, you might use Transactional Emails for:

• Order confirmations and receipts
• Password resets and account verification
• Payment or invoice confirmations
• Shipping and delivery updates
• Booking confirmations
• Account or application notifications

Unlike a regular Campaign, Transactional Emails aren't sent to a Group of Contacts. Instead, they're triggered individually by another application or system and sent directly to a specific recipient.

Why use Transactional Emails?

Transactional Emails are useful when you need emails to be sent automatically as part of another process.

For example, if a customer places an order through your website, your system could trigger a Transactional Email through Transpond containing their order confirmation.

Using Transpond to send these emails also allows you to keep track of your transactional sending alongside your other email activity.

What can I send?

Your Transactional Emails can include information such as:

• Sender and recipient details
• A subject line
• HTML email content
• Attachments
• Custom Field values
• Open and link tracking

You can also use an existing Transpond Template instead of providing the HTML content each time.

Transactional Emails can be sent immediately or scheduled for a specific date and time.

Setting up Transactional Emails

To find the information they'll need:

1. Click your profile picture in the top menu bar.
2. Go to Transactions.
3. Select Settings.

From here, your developer can choose how they'd like to send Transactional Emails.

Sending via the API

The Settings page provides your API endpoint and Access Token, along with details of the available parameters.

There's also a Sample Code section where your developer can choose their preferred programming language and use the example as a starting point for the integration.

Sending via SMTP

Transactional Emails can also be sent using SMTP.

You'll find the SMTP host, port, username and authentication information under Transactions > Settings, along with the additional options available when sending.

Keeping your Access Token secure

If you're using the API, your Access Token is used to authenticate requests from your application to Transpond.

Your Access Token should be treated like a password and shouldn't be shared publicly or included in publicly accessible code.

Tracking Transactional Emails

Once Transactional Emails are being sent, you can view them from the Transactions area in Transpond.

Here you can review your transactional sending activity and check information such as whether an email was successfully sent, opened or clicked.

If someone tells you they haven't received an expected Transactional Email, you can also use this area to check the status of the email and identify any sending errors.