In a country where word of mouth travels fast and customers often deal with the same business for years, a newsletter that clearly knows who it is talking to earns attention. One that invites a Dunedin reader to an Auckland pop-up, or promotes summer gear to a customer in Europe in December, quickly teaches people to stop opening. Personalisation is how you avoid that, and in Mailpro it does not require a data team.
Personalisation that makes sense in Aotearoa
- Region and island. New Zealand has 16 regions, and weather, events and store networks differ between them. Send the Canterbury A&P Show offer to Canterbury, and the Northland event to Northland.
- Season and hemisphere. Exporters and tourism operators often mail customers in Europe, North America and Asia as well as at home. A “winter warmers” issue in July suits Kiwi readers but not someone in Hamburg; a field recording the reader’s country lets one campaign serve both.
- Interests and purchase history. A garden centre can separate vegetable growers from rose lovers; an outdoor retailer can split trampers, cyclists and anglers.
- Greeting and tone. Addressing the reader by name, with a greeting such as “Kia ora” when it genuinely suits your brand, feels natural to many New Zealand readers. Spell te reo Māori correctly, with macrons, and do not use it as decoration.
- Lifecycle. New subscribers, loyal regulars and lapsed customers each need a different message. Birthday and anniversary emails can run on their own through automated emails.
The Mailpro tools behind it
Personalisation starts with the data you hold. Custom contact fields let you store region, preferred store, interests or customer type. Dynamic fields then insert those values into the subject line and body, so each reader sees their own name, nearest branch or loyalty balance. For larger differences, segmentation sends different versions to different groups, and you can personalise the newsletter layout itself, not just the text. Always set a fallback value for each field so that a missing first name never leaves a gap.
A worked example: a Canterbury garden centre
Spring runs from September to November, but planting dates in Southland and Northland are weeks apart. The garden centre collects each subscriber’s postcode region on its subscription form, plus a tick-box for “edibles”, “ornamentals” or both. One September newsletter then carries three regional planting calendars, shows each reader only their own, swaps the hero image for edibles or flowers, and names the reader’s nearest store with its opening hours. One campaign, many versions, no manual work.
Personal data, Privacy Act 2020 style
Every extra field is personal information, so collect with care. The Privacy Act 2020, overseen by the Privacy Commissioner, sets out Information Privacy Principles that map neatly onto newsletter data:
- Collect only what you need for a clear purpose (IPP 1). If you will never send a birthday offer, do not ask for a date of birth.
- Tell people why you are collecting it at the point of sign-up (IPP 3). Since 1 May 2026, IPP 3A also requires reasonable steps to let people know when you obtain their details from someone else.
- Keep it secure (IPP 5) and let people see and correct what you hold (IPPs 6 and 7).
Consent to receive the newsletter is a separate question, governed by the Unsolicited Electronic Messages Act 2007, and every issue still needs a working unsubscribe link. Mailpro hosts your data in Switzerland on private infrastructure, outside US jurisdiction, and never sells or rents it; read why Swiss hosting matters.
Ready to build one? Start from the newsletter creator and add your first dynamic field in minutes.