Skip to content
Docs menu

Guides

Features

API

Integrations

What recipients see

The people on your list never sign in to Wakio. They meet it only through a few public pages and the emails you send: the page where they sign up, the page that confirms their address, the page where they unsubscribe, your public archive, and the footer at the bottom of every email. This page shows each one, so you know what your readers see.

None of these pages carries Wakio's menus or links back into the dashboard. Each is a single plain card on a light background, and it looks the same whether the reader's device is set to light or dark. The signup, confirmation and unsubscribe pages ask search engines not to list them.

The subscribe page

The subscribe page for Northwind Coffee's Website newsletter form: the headline Coffee notes, once a week, the intro line, an Email address field, the consent wording that starts By subscribing you agree to receive email from Northwind Coffee, and a Subscribe button
  1. Where the visitor types their address.
  2. Your consent wording, as you last published it.
  3. The Subscribe button.

Each published form has its own page. It shows the form's headline and intro, an email field, your consent wording, and a Subscribe button. With no headline, the page is titled "Subscribe". Between the wording and the button, the page runs a check that the visitor is a person, which this picture leaves out.

The page does not print your account's name. Visitors know who they are signing up with from your headline, your intro and your consent wording, so name yourself in at least one of them. The example above does it in the consent wording.

The form also holds a field that people cannot see. A bot that fills in every field it finds fills that one too, and Wakio turns the signup away.

"Check your email"

A card titled Check your email, saying: If we can add you, you will get a message with a link to confirm. The link is how we know it was you.

After Subscribe, the visitor sees Check your email, with a line saying a confirmation link is on its way if Wakio can add them. They see this same page whether or not a confirmation email went out. It is shown when the signup is accepted, and also when Wakio quietly turns it away: a bot, an account past its daily signup limit, an address that is suppressed, or an address that looks undeliverable.

That is deliberate. If the page said "this address is blocked", anyone could type in someone else's address and learn whether that person is on your list. One answer for everyone gives nothing away, and a real person still has their inbox to tell them what happened.

A visitor is told about a problem only when they can do something about it: an address that is not valid, a failed check that they are a person, too many attempts in a short time, a browser that did not send back the page's cookie, or JavaScript turned off. Subscribe forms lists the exact messages.

Confirming the address

A card titled Subscription confirmed, saying: Thank you, you are on the list.

The confirmation email holds one link. Opening it shows a page that confirms the subscription by itself after a moment, so the person does not have to press anything, and then says Subscription confirmed. In a browser with JavaScript turned off, the page shows a Confirm subscription button instead.

Opening the link alone confirms nobody. Some email systems open every link in a message to check it is safe, and Wakio does not count that as the person agreeing. The confirmation happens when the page itself submits, which most link checkers do not do.

The link works for 30 days. After that, or if the link was damaged on its way, the page says This confirmation link is not valid and asks them to use the link in a recent email. In practice, that means signing up again.

Unsubscribing

The Unsubscribe page, asking: Stop receiving marketing email from Northwind Coffee at ada.bakerstreet@example.test? Below it, a Yes, unsubscribe me button and a note that messages the reader asks for directly, such as password resets and one-time codes, still arrive
  1. One press unsubscribes them.

Every campaign and flow email ends with an Unsubscribe link. It opens a page naming your account and the person's address, with one button, Yes, unsubscribe me. After they press it, the page says You have been unsubscribed. Opening the page alone changes nothing, for the same reason as the confirmation link.

Many inboxes also show their own unsubscribe button next to the sender's name. Wakio supports it on campaign and flow email, so a press there unsubscribes the person straight away, without opening any page.

Unsubscribing covers your whole account, not one list. The person stops getting your campaigns, and any flow they are in stops at its next email. Their address joins your Suppressed list, and their contact shows as unsubscribed. Email your app sends them directly, such as a receipt or a password reset, still arrives, and the unsubscribe page tells them so.

Nothing in your dashboard undoes an unsubscribe, and an import cannot either. The only way back is for the person to sign up again through one of your forms and confirm.

Your public archive

The archive page for Northwind Coffee's October roast is here campaign: the title October roast is here, the date, a small View this in your browser link, a one-line body about this week's roast, then a dividing line and the name Northwind Coffee
  1. The issue's title, which is the email's subject.

Each campaign you put in your public archive gets its own page once it starts sending. It shows the subject as the title, the date it went out, and then the email as it was sent, down to the footer with your account's name. Your account's name also sits above the card. Campaigns covers which campaigns appear and how to turn the archive on or off.

The page leaves out the parts that only make sense in someone's inbox. The footer's unsubscribe link is gone, an unsubscribe link you put in the body shows as plain words, and there is no open tracking. Merge tags that fill in from the reader, such as their first name, show blank, because the page has no reader to fill them from. "Hi {{first_name}}," reads "Hi ,", so write issues you plan to archive to read well without a name.

The small View this in your browser link from the top of the email stays on the page, just under the date, and leads back to the page it is on.

Wakio adds a footer to every email it sends for you: a dividing line, then your account's name. Campaign and flow emails also carry your postal address under the name, once you add one in Settings, and the Unsubscribe link under that. Email your app sends, and the confirmation email, carry your name but no unsubscribe link, because the person asked for that one message. The plain-text version of each email ends the same way.

A campaign that is in your public archive also starts with a small View this in your browser link. Flow emails never carry one.

Add your postal address. US law expects marketing email to show the sender's postal address. Add yours under Settings, and every campaign and flow email carries it from then on. Email your app sends does not carry it. What else you need to include depends on where you and your readers are. This page describes what Wakio adds for you, not everything your email may need.