Subster.aiSubster.aiSubster.ai
EN

Traffic and analytics

Emails to customers

You will build an email sequence that goes out on its own to a person who left an email in the funnel, and brings them back to payment.

The “Email sequences” section is currently hidden in the cabinet. The project menu does not show it. Sequences already turned on keep sending emails, but you cannot open or turn them off from the cabinet.

Before you start

An “Email” block in the funnel. Emails go only to an address the visitor entered themselves. The block goes on a quiz screen or on the paywall — how a funnel is built is in Build a funnel. The block itself is described on Fields and data collection. No block — no address, and the sequence has no one to write to.

Step 1. Create the sequence

Open “Email sequences” and click “Create a sequence”. The window has four fields. Only you see the name; leave the “Active” switch off — you will turn the sequence on in step 3, once the emails are written.

Trigger — the event the countdown starts from. For our task, take “Lead registration”: it happens the second the visitor enters an email, that is, before payment. The other five triggers — about purchase, subscription, trial and app install — are for other tasks.

If the project has “On your own” selected, the list has two triggers: “Lead registration” and “App installed”. The four money ones are not offered — payments go past us, and we will not have the event.

Email class — leave “Marketing email”: such an email does not go to those who unsubscribed. “Transactional email” bypasses the unsubscribe list; the cabinet warns but does not forbid. This class is only for emails about what the person paid for: access, a receipt, a download link.

Step 2. Write the emails

One sequence step is one email. “Add a step” opens three fields: “Subject”, “Delay” and “Email body (HTML)”. The body is typed as markup; the “Preview” button next to the field shows the finished email.

There are no placeholders in the body. Something like {{email}} reaches the recipient exactly as written — the email is the same for everyone. Emails are not translated: even if the funnel is translated, everyone gets them in the language you wrote them in — Translate a funnel.

The “Delay (hours after the event)” field counts each email’s hours from the event that started the sequence, not from the previous email. Use growing numbers: 0 — at once, 24 — a day later, 72 — three days later. Three equal numbers give three emails in the same minute.

Step 3. Check and turn on

The “Send a test” button sends the first email of the sequence to any address — exactly what the recipient will get.

The switch in the sequence header turns it on. The countdown runs only for those who hit the event after it is on: the sequence sends nothing to addresses already collected.

When the sequence stops

Before each email we check that the sequence is on and that the recipient has not bought anything in the project since it started.

  • You turned the sequence off — scheduled emails will not go out.
  • The recipient bought — the remaining marketing emails will not go out. If the sequence is for buyers too, turn on its “Keep sending after a purchase” switch. A purchase does not stop sequences started by a purchase, or transactional emails.
  • Editing the text changes emails not yet sent too, and deleting a step cancels its email altogether.

What you see after launch

The “Send history” tab shows each email: “Sent”, “Failed” or “Skipped”.

Why an email did not go is in the “Failure reason” column: for a skipped one it is an unsubscribed address, the person refusing emails, “Not sent: the sequence was turned off” or “Not sent: the recipient has already bought”.

Most often the history is empty because no events happened since it was turned on: a row appears when the email goes out, not when scheduled.

If events surely happened but rows are missing, there are three causes: the sequence is off, the funnel has no “Email” block, or a visitor from Europe pressed “Decline” on the consent banner — Ad networks and pixels, section “Tracking consent”.

One email address triggers “Lead registration” in a project once a day, days counted in UTC. Entering the same address again on the same day gives no new emails — test the sequence on a new address.

“Won't we end up in spam?”

Emails go from our service address; you cannot connect your own sender domain in the cabinet.

To every marketing email we add an “unsubscribe” link and a service header, by which mail services show an unsubscribe button next to the subject. Whoever presses it gets no more emails from this project — from any sequence.

Next

  • Subscriptions — who pays you, how to cancel a subscription and refund money.
  • Funnel analytics — at which step visitors leave and which ads pay off.
  • A/B tests — compare two funnel variants on one ad address.