> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transactional emails

> Create and send event-specific emails to participants of a particular event.

Transactional emails are event-scoped messages about a specific event — race-day logistics, kit collection details, pre-event briefings, and anything else that only makes sense in the context of a participant's registration.

There are two types of transactional email:

* **Automatic emails** — sent by Let's Do This on your behalf when a booking event occurs. You do not need to create or schedule these.
* **Campaigns** — emails you compose and send yourself, either on a schedule you set or triggered automatically when a participant action occurs.

## Emails Let's Do This sends automatically

Let's Do This sends the following emails automatically on your behalf. These use LDT-managed templates and do not require any action from you.

| Email | When it sends |
| - | - |
| Booking confirmation | Immediately after a participant completes their registration |
| Booking receipt | After payment is processed |
| Abandoned cart | Up to three reminders, 1 hour, 1 day, and 3 days after a participant starts checkout without completing it |
| Entry withdrawn | When a booking is cancelled |
| Upcoming payment reminder | Before a payment plan instalment is due |

These emails use a Let's Do This address and their content can't be edited.
Contact Let's Do This support with questions about the content or delivery.

The abandoned cart reminders are the one exception: you can turn them off for an event and send your own instead. See [Replacing the Let's Do This abandoned cart emails](#replacing-the-lets-do-this-abandoned-cart-emails).

## Finding your campaigns

Find your campaigns under **Email campaigns** in the dashboard. Select the
**Transactional** tab to see campaigns for all events, or open an event and go
to its email section to see that event's campaigns.

Each campaign card shows its current status:

| Status | What it means |
| - | - |
| Draft | Saved but not yet sent or scheduled |
| Scheduled | Set to send at a future date and time |
| Sending | Currently delivering to recipients |
| Sent | Delivered successfully |
| Error | Something went wrong — check the card for details |

## Creating a transactional email campaign

**1. Start a new campaign**

On the transactional emails list, click **Create**. If prompted, confirm you want to create a campaign for a specific event, then click **Apply**.

The wizard opens at the **Overview** step.

**2. Fill in the email details**

On the Overview step, complete the send configuration:

* **Campaign name** — an internal label, not visible to participants.
* **Subject** — the subject line participants see in their inbox.
* **Preheader** — the short preview text that appears after the subject in most email clients. Use it to complement the subject line.
* **From name** — the display name in the sender field. Defaults to your organizer name if left blank.
* **From email** — enable **Use a custom from email** if your account has a verified sending domain; otherwise the email comes from Let's Do This by default. See [Custom Domains](https://partner-help.letsdothis.com/docs/email-communications/custom-domains.md) to set one up.
* **Reply-to name** and **Reply-to email** — where replies are directed, so participants can reach you directly. Like the from address, the reply-to address must be on a verified sending domain; see [Custom Domains](https://partner-help.letsdothis.com/docs/email-communications/custom-domains.md).
* **Brand theme** — select a theme to apply your branding to the email layout. See [Branding & Custom Domains](https://partner-help.letsdothis.com/docs/email-communications/branding.md) for how to set up themes.

Click **Save Draft** to preserve your settings, or **Save and continue** to move to the next step.

**3. Build the email content**

The Builder step is where you compose the email body. When you first open it, choose your editing experience:

**Basic Builder** — add content blocks in sequence. Available block types:

| Block | Use for |
| - | - |
| Heading | A large title at the top of a section |
| Text | Body copy and paragraphs |
| Button | A call-to-action with a label and URL |
| Image | A photo, banner, or illustration |
| HTML | Custom HTML for layouts the block builder cannot produce |

Drag blocks to reorder them.

**Advanced Builder** — a full drag-and-drop visual editor. Build multi-column layouts, customize spacing, and design more complex email templates with greater visual control.

Both builders support personalization variables so each recipient sees their own data — for example, their first name or the event they registered for. See [Email personalization](https://partner-help.letsdothis.com/docs/email-communications/email-personalisation.md).

Click **Preview** to see how the email will look before continuing.

**4. Select the audience**

On the Audience step, choose which participants receive this email. You can target the entire event participant list or narrow it down with the Audience Builder. See [Audiences](https://partner-help.letsdothis.com/docs/email-communications/audiences.md) for detail on each option.

**5. Schedule or set up a trigger**

Choose how the campaign is sent:

* **Send now** — delivers immediately after you confirm on the Launch step.
* **Schedule** — pick a specific date and time.
* **Triggered** — the email sends automatically when a participant action occurs. See [Triggered sends](#triggered-sends) below.

If you are editing a campaign that is already scheduled, you'll see a warning. To change the delivery type you must cancel the campaign first, which returns it to drafts.

**6. Review and send**

The Launch step shows a summary of your send configuration and the estimated recipient count. You can still edit any field before sending.

Click **Send Test** to send a preview to yourself. When you are happy, click **Send** (or **Schedule**) and confirm.

## Triggered sends

A triggered campaign sends automatically when a participant action occurs — without you needing to schedule or manually press send each time. Use triggered sends for follow-up messages, welcome emails, or reminders that should go out relative to a specific moment for each individual participant.

On the Schedule step, select **Triggered** to configure the trigger:

**Trigger type** — the participant action that starts the send:

| Trigger | What activates it |
| - | - |
| Participant Registered | A participant completes registration for the event |
| Participant Checked-In | A participant is checked in at the event |
| Membership Created | A participant's membership is created |
| Abandoned Cart | A participant starts checkout for the event but does not complete it |

**Timing** — choose whether to send immediately when the trigger fires, or after a delay. Delays can be set in hours, days, weeks, or months — for example, send a follow-up 2 days after a participant registers.

> [!NOTE]
>
> A triggered campaign begins sending once it is set to Scheduled status. It
> sends to participants who meet the trigger condition from that point forward —
> it does not backfill participants who met the condition before the campaign
> was activated.

## Replacing the Let's Do This abandoned cart emails

An abandoned cart email reminds someone to finish registering after they start
checkout. Let's Do This sends up to three reminders for each event by default.
To use your own copy and branding, turn off these reminders and create a
campaign with the **Abandoned Cart** trigger.

Build your own campaign first and turn the Let's Do This reminders off only once it is live. An event with the automatic reminders off and no campaign of your own sends nothing at all when someone abandons checkout, so doing it in this order avoids a gap.

> [!NOTE]
>
> Whether you build the campaign as transactional or marketing decides who is
> able to receive it. A transactional campaign sends regardless of a
> participant's marketing preferences. A marketing campaign only reaches people
> who have given marketing consent, and someone who abandoned checkout usually
> never got far enough to give it — so the same campaign built as marketing
> typically reaches very few of them, and often none.

> [!WARNING]
>
> Sending an abandoned cart email as a transactional message is not permitted
> everywhere. Some countries and some US states treat it as marketing, which
> means you would need the recipient's consent before sending it. You are
> responsible for making sure your abandoned cart emails comply with the laws
> and regulations that apply to you and to your participants — take your own
> legal advice if you are unsure.

**1. Create your own abandoned cart campaign**

Create a transactional campaign for the event as described above. On the Schedule step, select **Triggered**, then choose **Abandoned Cart** as the action and pick the event.

The trigger fires about an hour after the checkout is abandoned. Selecting **Immediately** sends your email at that point; adding a delay counts from there, so a 2-day delay arrives roughly 2 days and 1 hour after the checkout was abandoned.

The trigger fires once per abandoned checkout. To send a series like the Let's Do This one, create a separate campaign for each message with a different delay. Each email is checked again just before it sends, so someone who registers between messages doesn't get the later ones.

**2. Turn off the Let's Do This abandoned cart emails**

Open the event, go to **Automated emails** in the event settings, and turn off **Enable Let's Do This abandoned cart emails**. Click **Save changes** — you'll see `Abandoned cart email setting saved.` once it applies.

The setting is per event and is on by default, so you need to turn it off for each event you want it off for. It stops all three Let's Do This reminders for that event and nothing else — your own campaigns still send.

## Skipped abandoned cart emails

An abandoned cart reminder is skipped when the checkout was for a ballot,
application, or volunteer registration; when the participant was editing an
existing booking; or when they completed another booking with you afterward.
If someone expected a reminder, check whether they booked after abandoning
checkout. They can also return to your event page and register directly.

Your own abandoned cart campaigns are checked again just before each email
sends. The email is skipped if the person already has a booking for the event,
including a cancelled one. It's also skipped if they booked with you after
abandoning checkout, or went back and finished that checkout. Bookings are
matched on the lead booker's email, or the first participant's if no booker
email was given.

Your own abandoned cart email isn't sent if, when the trigger fires about an
hour after checkout, the event has started or can't be booked, or a ticket in
the basket for this event is sold out, deleted, switched off, not on sale yet,
no longer on sale, or full. A ticket sold only through a hidden link,
or an unlisted event, doesn't stop the email. If the basket can't be checked,
the email still sends.

## Fields for abandoned cart emails

There's no booking behind an abandoned cart email yet, so its field menu offers
the person's own details plus:

* **Event name**: `{{ eventTitle }}`
* **Checkout link**: `{{ checkoutUrl }}`
* **Ticket in basket**: `{{ cart.ticketName }}`
* **Race in basket**: `{{ cart.raceName }}`
* **Distance in basket**: `{{ cart.distance }}`

Booking fields, such as bib number or booking ID, aren't offered. An email that
already uses them still passes its checks and sends as it does today.

### Basket fields

The basket fields name what the person had in their basket for this event. Use
them to remind someone of the exact ticket or distance they were choosing, for
example "Your 10 km place is waiting".

* **Ticket in basket** shows the ticket name the person saw at checkout. If a
  [price change](https://partner-help.letsdothis.com/docs/event-setup/ticket-price-changes.md) with its own title was
  active, such as `Early Bird Entry`, the email uses that title.
* **Race in basket** shows the race the ticket belongs to.
* **Distance in basket** shows the race distance as checkout shows it, for
  example `10 km`. It's blank for a volunteer race, or a race with **Display distance** turned off.

Names appear in the language the person was using at checkout, where you've
added a translation. When a basket holds more than one ticket, race, or
distance, each name appears once. Names are separated by commas, for example
`10 km, 21.1 km`. Tickets for another event in the same basket aren't included.

The names are taken when the trigger fires, about an hour after checkout
started. Renaming a ticket after that doesn't change an email that's already
scheduled.

A basket field is blank when it has nothing to show. Add a fallback so the
sentence still reads well, for example
`{{ cart.ticketName | default: "your ticket" }}`. See
[Email personalization](https://partner-help.letsdothis.com/docs/email-communications/email-personalisation.md) for
how fallbacks work.

### Testing basket fields

Previews show sample values for the abandoned cart fields. Test emails leave
them blank, including the event name and checkout link. That's because a test
email isn't linked to a real checkout.

To see real values, set the campaign's trigger to an event that hasn't started.
Start checkout for that event with your own email address and leave without
booking. The email arrives about an hour later, plus any delay you set. It
isn't sent if your address already has a booking for the event. See
[Skipped abandoned cart emails](#skipped-abandoned-cart-emails) for the other
reasons it can be skipped.

## Abandoned cart campaign recipients

The Audience step doesn't determine recipients for a triggered campaign. The
trigger sends the email to the address entered during checkout: the lead
booker's address, or the first participant's if no booker address was
provided. If someone says the reminder went to the wrong inbox, check that
address.

## Unsubscribes and opt-outs

Transactional emails are sent to participants regardless of their marketing email preferences, because the content is event-specific and not promotional. Transactional emails do not include an unsubscribe link — participants cannot opt out of them through the email itself.

If a participant asks not to receive further emails for an event, you can exclude them manually by removing them from the audience before sending.

## Editing and duplicating campaigns

You can edit a **Draft** or **Scheduled** campaign at any point before it sends. Open the campaign card's menu and select **Edit**.

To reuse a campaign for another event or send a similar message again, select **Duplicate** from the campaign card menu. The duplicate starts as a draft and is not tied to any schedule from the original.

## Send errors

If a campaign ends in an error state, the card shows the error type. Common causes include missing required fields (subject line or email body) and configuration issues with a custom from address. Correct the issue and resend. If the error persists, contact Let's Do This support with the campaign name and the error message you see.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.