mail, keyboard, key, button, technology, text, type, word, internet, communication, message, lyrics, character, plastic, buttons, digital
Photo by padrinan on Pixabay

List Building

Email preference and unsubscribe experiences

Design clear email choices and unsubscribe routes, then make sure requests reach every relevant marketing system.

Give subscribers clear ways to change the marketing they receive or stop it. A preference centre helps only when its choices affect future emails; it must not make leaving harder.

The Spam Act requires every Australian commercial electronic message to include an unsubscribe statement or similar effect, except where the designated-message exception applies. The statement must say that the recipient may use an electronic address in the message to send an unsubscribe message to the individual or organisation that authorised it.

Lawful commercial electronic messages must also include information about the sender’s identity and contact details. The Australian Communications and Media Authority (ACMA) publishes guidance on avoiding spam and common e-marketing mistakes.

Show what each action does

Name the routes plainly. “Change email topics” should change future topic selections. “Unsubscribe from marketing” should stop the marketing described by that action. If someone can stop one newsletter or all the business’s marketing, explain the difference before they choose.

The confirmation must match the stored result. Saying “You are unsubscribed” is misleading if another covered campaign still selects the address. Likewise, a saved frequency choice is of little use if an automation ignores it.

Keep permission separate from preferences

A topic selection is a preference within an eligible email programme. It does not establish consent by itself or reverse an earlier opt-out. Apply consent and exclusion rules before using preferences to choose content or frequency.

Assess whether a message is commercial before treating it as a service message. A platform’s “transactional” label does not settle that question.

Do not infer consent from an address alone

The Spam Act applies to commercial electronic messages sent by email, SMS, multimedia message service or instant messaging, and requires recipient consent. Consent may be express or inferred, but merely publishing an electronic address does not by itself establish inferred consent.

For certain conspicuously published work addresses, such as those of employees, directors or officers of organisations, consent may be inferred only where the publication does not indicate that unsolicited commercial messages are unwanted. Consent can also be withdrawn when the account holder or a user of the account indicates they do not wish to receive further commercial electronic messages.

Key Compliance Stats Under Australian Spam Act

Spam Act coverage
Applies to email, SMS, MMS and instant messaging
Consent types
Express or inferred (but not from address alone)

Account for the designated-message exception

The Spam Act’s unsubscribe-message requirement does not apply to designated commercial electronic messages. The Act does not prohibit sending designated commercial electronic messages.

These include messages consisting only of factual information. They also include messages authorised by a government body, registered political party, religious organisation or charity or charitable institution, where the message relates to goods or services and the body is their supplier or prospective supplier.

An educational institution’s message is included only if the account holder is or has been enrolled there, or is or has been a member or former member of the household of the relevant account holder who is or has been enrolled. The message must relate to goods or services supplied, or prospectively supplied, by that educational institution.

Define the scope of each choice

Reader actionResult to implement
Removes a topicExclude marketing for that topic while applying any other valid choices.
Chooses a lower frequencyApply the stated frequency to the campaigns and automations it covers.
Stops a named newsletterStop that newsletter and describe the scope accurately.
Asks to stop all marketing from the businessExclude the address from every marketing route covered by the request.

Read a reply or support request in its context. Do not narrow “stop emailing me marketing” to the list that happened to receive it.

Set each route’s reach in programme terms: one named newsletter, selected marketing or all marketing covered by the choice. Make that scope consistent when interpreting a preference, reply or support request.

Carry the result across sending systems

Identify newsletters, automations, event tools, sales systems and providers that can send marketing. Record where each request enters, which marketing it covers and how the exclusion reaches those routes. If a business uses several audiences, check how an unsubscribe is recorded across them.

Treat a request as a change to sending eligibility, not just a page response. Update the relevant status and make the exclusion available to every system that selects recipients.

Keep enough of the request and resulting status to resolve a discrepancy. Prevent later imports or customer updates from silently restoring marketing eligibility after an opt-out.

Translate each request into the corresponding programme-level status and pass it to relevant audience selectors and automations. A page confirmation alone does not show that a sending system has received the change.

Check the received experience

Before a campaign goes out, use an authorised controlled contact to follow each relevant unsubscribe and preference route from a received message. Inspect the saved status, next audience selection and queued marketing, as well as the confirmation page. Repeat affected checks after changes to templates or integrations.

Compare the confirmation with the stored status and the messages the address remains eligible to receive. Keep enough evidence of the request and resulting status to investigate any mismatch.

In this guide

  1. Designing a preference centre that is not a barrier to leavingOffer useful email choices while keeping a clear unsubscribe route available throughout the preference-centre journey.
  2. Offering topic choices without confusing subscribersChoose clear email topic labels, explain what selections change and handle overlapping or blank choices.
  3. Handling unsubscribe requests across several listsRecord the scope of an unsubscribe and apply it across every relevant marketing list, automation and provider.
  4. Checking a broken unsubscribe link before the next sendTrace a broken unsubscribe from the received email to stored status, address earlier sends and recheck before release.

More from List Building