Lists
A list is a group of people who agreed to hear from you: a newsletter, a waitlist, product updates. A workspace can run several, and each issue you send to a list goes to its subscribers. A broadcast is different: a one-off email to a segment or every contact, not part of any list.
Create a list
Lists → New list asks what you're starting from, a name and where replies should go. Newsletter, Waitlist and Blank only set the wording of the emails made for the list. After that they behave the same, so you can run a waitlist like a newsletter or the other way round.
Creating a list also creates a confirmation workflow, the email that asks new signups to confirm their address. Tick the welcome email to add a second workflow that greets each person once they've confirmed. Both are normal workflows, so you can edit their emails and steps in Workflows.
Under a list's Settings you can set its description, from name and from address. With a verified sending domain, issues go out from that domain under the list's name. Without one, they go out from a shared address under the list's name, and replies still reach you.
Confirmation
Everyone who signs up on a form, or through subscribe() with a public key, gets the confirmation email. What happens until they click its link depends on Require confirmation under Settings:
- Off (the default). They join at once and receive issues. The Subscribers tab marks them Not confirmed until they click.
- On. They're waiting to confirm and receive nothing until they click. Then they join.
The link opens a page with a button, so a mail scanner that opens every link can't confirm anyone. Anyone you add yourself, by import, from a segment, by hand, through the API with a secret key or with a workflow step, counts as confirmed already and gets no confirmation email.
Because the email is a workflow, you control it. Require confirmation can only be turned on while the confirmation workflow is running, and the list's settings warn you if it's paused or deleted. A Confirm a subscription workflow step does the same as the link, for example to confirm someone when your app verifies their address. Someone who unsubscribed stays unsubscribed.
When you send an issue you can limit it to confirmed members only. Signups that never confirm can be cleared out from the Waiting to confirm and Not confirmed views of the Subscribers tab. That removes them from the list, and deletes the contact too when the signup is all there is to it.
Add subscribers
Being a contact doesn't make someone a subscriber, so a new list starts empty. You can add people:
- one at a time, from the list's Subscribers tab or a contact's page
- all at once from a segment
- from a file, by choosing the list under Contacts → Import
- with a Subscribe to a list step in a workflow
People can also sign up themselves, see Share and get signups.
Anyone who opted out is passed over, along with addresses that bounced or complained. Only that person can come back. Removing a subscriber yourself isn't an opt-out, so you can add them again.
Share and get signups
A list's Share tab has three ways in. All of them use your email branding, and only ask for an email address and an optional name.
- Public page. Off until you turn it on. It shows the list's name and description, a signup form and past issues, at a link you can share anywhere. An issue marked Subscribers only, in the editor or on its report, stays off the page.
- Embed. Paste the snippet into any page to show the signup form there. It works whether or not the public page is on.
- Your own form. Call
subscribe()from the browser SDK with a public key and the list's id from the Share tab. Say on your form what people are signing up for, because the call records their consent. A public key can't claim that someone confirmed, so these signups follow the same confirmation rule as a form.
JourneyKit.subscribe("ada@example.com", { list: "the-weekly", name: "Ada" });Anyone can type any address into a form, so a signup only fills in empty contact fields, never brings back an address that bounced or complained, and always shows the same thanks message. Someone who unsubscribed earlier gets an email with a link to confirm instead of being subscribed again. Each subscription keeps where it came from, when, the IP address and the wording the person agreed to. Forms are protected by an invisible bot check and rate limits. The SDK has no form to put a check on, so it is limited by rate only.
Archiving a list closes its page, embed and signups.
Send an issue
Open the list and choose New issue. The editor is the same as for broadcasts. To narrows the issue to a segment of your subscribers if you want, and you can send now or schedule it. For a waitlist this is how you announce launch.
Your workspace needs a postal address before anything can go out.
Opting out
An issue's footer has two links:
- Unsubscribe removes the reader from that list only, after one confirming click. The unsubscribe button in their mail client does the same right away. Your workflow emails keep reaching them.
- Manage preferences lists all your lists with a switch for each, plus Unsubscribe from all, which puts the address on your suppression list and stops all marketing email.
If a workflow shouldn't outlive a subscription, such as a welcome series with several emails, stop it on the unsubscribe event.
Events
Signing up records list_subscribed and a click on the confirmation link records list_confirmed. Leaving records list_unsubscribed. Each has listId and listName, and list_subscribed also has status (active or pending) and needsConfirmation. Use them in segments and workflow triggers. Imports and segment adds record list_subscribed but start no workflows, so moving a list over doesn't email everyone on it.
Retire a list
Lists are archived, not deleted. Archiving stops new subscribers and sends, returns scheduled issues to drafts and stops any issue that's sending. Past issues and subscription records stay, and your contacts aren't touched. It can't be undone.