Skip to content

Setting up your newsletter

Learn it in the academy: Set up a newsletter (video)

The newsletter is an add-on for organisations on the Org plan: it sends a designed email to the people on your contact lists who agreed to receive it. It is in beta. A member’s own contacts cannot be sent to — move them to an organisation first.

This page is everything before the first send. Writing and sending one is on Designing and sending a newsletter.

The add-on lives under Settings → Integrations → Add-ons → Newsletter, and only an organisation’s admins can switch it on. It is a monthly add-on, separate from the plan. While it is in beta, the page may offer Ask to join the beta rather than a way to buy it; an add-on the platform has included for you says so beside its status.

The newsletter add-on page: what it does and how to get itOpen /a/settings/integrations/add-ons/newsletter in the app
The newsletter add-on page: what it does and how to get itThe newsletter add-on page: what it does and how to get it

Once it is active, Newsletters appears under Contacts in the sidebar. Admins and editors can write and send; members and viewers cannot.

A month includes a set number of emails. The add-on page shows how many are used under This month. Every email counts — each recipient of a newsletter, each test copy and each confirmation email — and the count starts again on the first of each month (UTC). A send that would go over is not started at all, rather than reaching part of a list.

If the add-on ends, or a payment is open, sending pauses. Newsletters already queued wait, and earlier ones stay listed.

Under Settings on the add-on page, Sender asks for three things, and nothing can be sent until they are set:

Sender name The name readers see in their inbox
Replies go to Where a reader’s reply arrives
Postal address (shown in the footer) Required. Every newsletter carries one

The email is sent from an address on the platform’s own sending domain, shown under the form once saved (Sent from …). Sending from your organisation’s own domain is not available.

A newsletter goes only to people who agreed to receive it — per list, not per person. Being in your contacts, being on a list, being imported or carrying a tag are never consent. With the add-on active, each list shows a Newsletter column for its members:

State Meaning Receives newsletters
Not asked No consent recorded — where everyone starts No
Asked A confirmation email went out; no answer yet No
Agreed Confirmed by email, or recorded by you Yes
Unsubscribed Opted out No

Hovering an Agreed shows how it was given: Confirmed by email or Recorded by you.

Ask by email — the double opt-in. Ask to confirm by email (one person) or Ask all to confirm (the list) sends the confirmation email. Only the person’s own click on its button makes them Agreed. Up to 200 people are asked per click, and nobody is asked again within a week; people with no email address, who unsubscribed, or who were asked in the last week are skipped, and the result says so. Each email counts towards the month.

Record consent you already hold. Record consent… (or Record consent for all) marks people as Agreed without emailing them, recorded with today’s date and your name, and asks how they agreed. Use it only for consent you genuinely have — a signup sheet, a form on your website, an event. If you are not sure, ask by email instead.

A reader’s unsubscribe, a complaint or a permanent bounce wins over everything. The address is blocked for your organisation, on every list, and stays blocked even if the contact is deleted and added again. Recording consent cannot bring it back:

  • An unsubscribe is cleared only by the person themselves, by confirming again — through a confirmation email or a signup form.
  • A spam complaint or a bounce is never cleared.

One unsubscribe covers all your lists. A reader who unsubscribes is unsubscribed from every list of your organisation, not only the one the newsletter went to.

Mark as unsubscribed is how you take someone off a list yourself — when they ask you by phone, say. It applies to that one list, and unlike the reader’s own unsubscribe it does not block the address. It works even without the add-on.

Changing a contact’s email address resets their consent. Their Agreed places go back to Not asked, because the new address never agreed to anything.

Moving contacts into the organisation does not move consent — see Moving your contacts to an organisation.

Every newsletter carries an Unsubscribe link in its footer, and the one-click unsubscribe that mail apps show beside the sender. The link opens a page with an Unsubscribe button: opening the link alone changes nothing, because mail scanners open every link in an email.

The email that asks someone to confirm is the same whether you asked them or they signed up through a form. Edit it under Confirmation email on the add-on page — Subject, Heading, Message and Button. Use the default text restores the platform’s version.

Three placeholders are filled in for each reader: {organization}, {list}, and {{firstName|there}}, which greets them by first name or, without one, by the word after the bar. The confirm button and your footer are always added, whatever the text says. Links typed into the message stay plain text.

The confirmation link is valid for 14 days. Someone who does nothing is not subscribed.

A list can have one signup form: a public page where people add themselves. Open the list under Contacts → Lists and choose Signup form.

Field
Title, Introduction What the page says
What people agree to The sentence beside the box they must tick
Button, Message after signing up The button, and what they see once they have pressed it
Ask for first and last name Optional name fields
Open: people can sign up Switch off to close the form without deleting it

Share it gives the form’s link, and embed code to put it on a page of your own website. The form is unavailable to visitors until a sender and postal address are set.

Signing up is a double opt-in. The person gets the confirmation email, and only their click subscribes them. A new address is not even added to your contacts until then; an unconfirmed request is deleted after 14 days. An address already in your contacts is put on the list as Asked. The page never says whether an address was already known to you.

Forms are protected against automated signups, and each address gets at most one confirmation email per form per week. There is also a daily cap on confirmation emails per form and per organisation; signups beyond it on that day are not sent a confirmation.

Something wrong on this page? Report it