0796995888 werner@pixzil.co.za Allen Grove, Gauteng, South Africa
Pixzil Pixzil
Build Notes

A newsletter that remembers who agreed to receive it

13/10/2026  ·  Pixzil

Campaigns, subscribers and a consent trail — plus the rule that a mailing list never travels between two sites.

A newsletter that remembers who agreed to receive it

Sending to your own list, without the grey area

The newsletter module, and what it refuses to do

A mailing list is the most sensitive data a small business keeps. This is how the newsletter module handles it, and why one part of it was built to go nowhere.

A campaign, an audience and a queue

You write a campaign once: a subject, a preheader line and the body, composed as a normal email with your branding around it. Then you choose the audience: the people who subscribed, everyone in the client list, or a custom selection. The system builds the send queue from that choice and works through it in throttled batches, so a few hundred recipients never have to share a single slow request.

Sign-ups are handled properly rather than casually. Somebody who subscribes gets a confirmation email, and the record keeps the wording they agreed to and the address they agreed from. Unsubscribing is a single click from any email, it is honoured immediately, and a message already queued for someone who has opted out is skipped rather than sent. The footer blurb and the button label are editable in Settings, so every site sends in its own voice.

Where the newsletter does more than send

Consent that can be proven

The subscribers list records the consent wording and the address it was given from, so an opt-in can be demonstrated, not just asserted.

A customer choice, honoured

Account holders can switch the newsletter on or off, and the switch is wired to the module so the send queue always agrees with it.

Batched, resumable sending

The queue drains in throttled batches, so a large list never depends on one long-running request.

Nothing sends by itself

A campaign is written, reviewed and sent deliberately. No background process in the system will ever mail your list on its own.

What travels, and the one thing that never does

The newsletter joined Site Sync as its own tab, and the design decision behind it is the whole feature. The campaign travels. The subscriber list does not.

That is not a limitation, it is the point. A list belongs to the site that collected it. Every record was given by somebody on that website, with that consent wording, from that address, and copying it to another domain would mean emailing people who never agreed to hear from it. So the wording a campaign is written with crosses to the live site, and the live site sends it to the people who actually signed up there.

Two more rules follow the same instinct. A pushed campaign always lands as a draft, never queued, because sending mail is irreversible. And the option to let a master trigger a send on a live site exists, but it is off until that site switches it on itself, and a campaign that has already gone out is never quietly reset to draft and sent twice.

Your list, your customers, your wording

Campaigns, subscribers and consent live in the same system as everything else, so there is one place to look when somebody asks what they agreed to.

Talk to us
← All articles