Skip to main content
Email is the workhorse channel. Senderz signs every message with your own DKIM key, routes it through more than one provider, and adds tracking, the unsubscribe link and the compliance headers at send time, so your templates stay clean.

What makes an email send-able

Two things have to be true before Senderz will send from an address. Both are checked on the server, so neither can be skipped by editing the campaign.

A verified sending domain

The domain after the @ must be verified. See Domains and authentication.

A verified sender address

The full mailbox, for example hello@yourstore.com, must be confirmed from a link emailed to it.
A verified domain on its own is not enough. Every sender address is created as Awaiting verification and cannot send until someone opens the confirmation email. If a From address that used to work suddenly stops, this is the first thing to check.

Verifying a sender address

Open Settings → Domains & senders (also reachable at /domains) and use the Sender addresses card.
1

Add the address

Pick one of your verified domains, type the part before the @, and add the address. Only verified domains are offered.
2

Open the confirmation email

Senderz emails that mailbox a confirmation link. Opening it flips the address to Verified.
3

Resend if needed

The link is valid for 48 hours. Resend issues a fresh one, and is rate limited to once a minute per address.
The card shows one of three states:
This proves the mailbox is real and monitored, so replies and bounces land somewhere a person reads. No operator approval is involved. The mailbox itself is the approver.

Sender names

Sender names is a separate, reusable list of From names in the same place. Pick one per campaign or per automation step, or type a one-off name. Senderz checks the name as you type:
  • Blocked and cannot be saved: line breaks and control characters, and the characters < > @ " [ ] and a backslash. These break the From header outright.
  • Warned but allowed: punctuation like . , : ; ( ), repeated punctuation such as !!! or ***, emoji, names that look like a link or a domain, and names over 60 characters. These render inconsistently or attract spam filters.
The field accepts up to 100 characters.

Limits

Default sender

Default sender on the same screen sets the From name and address that new campaigns and new automation email steps start with. The email you pick must itself be a verified sender address. Apply to all messages stamps that address onto every existing email campaign that is a draft, scheduled or paused, and onto every email step of every draft, active or paused automation. Before you confirm, Senderz shows how many campaigns and automations will change.
Campaigns that have already sent are never rewritten.

Reply-to

Each campaign can reply to the sender address or to a different address. The pre-send checklist blocks the send if you choose a different address and leave it empty or invalid.

What Senderz adds to a marketing email

These are added at send time, per recipient, to marketing mail only. Transactional and test messages are covered further down.

DKIM signature

Signed with the private key held for your domain in a hardware-backed key store. The key is never downloaded and never appears in the message.

Open and click tracking

A tracking pixel plus rewritten links.

Unsubscribe

One-click headers plus a link in the body. Every marketing email is guaranteed to carry one.

Copy-to BCC

Optional hidden copy of every marketing campaign to an inbox you choose.

Open and click tracking

Tracking is added to marketing email only. Transactional messages and test sends are never tracked.
  • Opens are counted by a 1x1 pixel added at the end of the message.
  • Clicks are counted by rewriting each link so it passes through a Senderz redirect first, then lands on your original URL.
Only real http and https links are rewritten. Anchor links, mailto: and tel: links, and any URL that still contains an unresolved merge tag are left exactly as written. If the campaign has UTM tracking turned on, the UTM values are added to the destination URL at the same moment.
The Tracking record on the Domains screen is optional. It serves the open pixel and click redirects from a subdomain of your own domain instead of a shared one. Your domain still verifies without it.

Unsubscribe

Every marketing email gets both halves of the unsubscribe: the headers mailbox providers read, and a link a person can click.

The one-click headers

Senderz adds List-Unsubscribe and List-Unsubscribe-Post with the one-click value. This is what makes Gmail and Yahoo show their own native unsubscribe button next to your From name, and it is a requirement for bulk senders on both. Senderz also adds a List-ID header derived from your sending domain, which is what lets Gmail group your mail. All three headers are covered by the DKIM signature, so a receiver can tell they were not added in transit.
A click on the mailbox provider’s own button unsubscribes the email channel for that contact. It does not touch their SMS, WhatsApp or push consent.
You control where the in-body link goes. Senderz uses a placeholder token, %%UNSUBSCRIBE_URL%%, and swaps it for that recipient’s own preference-center link when the message is built. In the email builder you can insert it four ways:
Unsubscribe → Unsubscribe URL only drops the token on its own, for when you want to write the surrounding sentence yourself.
Every URL field in the block inspector has an Insert unsubscribe URL action, so a button, a linked image or a plain hyperlink can point at it.
Place the link where you actually want it. If you never place one, Senderz adds a fallback footer for you, and you have no control over how it looks.
If a marketing email is about to go out with no Senderz unsubscribe token anywhere in it, Senderz appends a small footer at the very bottom. It is right-to-left, centred, grey, and carries two lines:
  1. Your From name, or the From address if no name is set.
  2. The bilingual link הסרה מרשימת התפוצה · Unsubscribe.
The footer is deliberately plain. It exists so no marketing email can go out without a working opt-out, not to look good.
A hand-typed unsubscribe URL that you copied from somewhere else does not count. Senderz only recognises its own token, so a foreign link will get the fallback footer appended underneath it.

Order of operations

Link rewriting for click tracking runs before the unsubscribe token is resolved, and the token is not a URL, so unsubscribe links are never turned into tracked links. A recipient clicking unsubscribe is never counted as a click.

Copy-to BCC

Settings → Sending Settings → Copy an inbox on every campaign sends a hidden copy of each marketing campaign to an address you choose.
  • It is a real envelope BCC, not a header. The primary recipient cannot see it.
  • It applies to campaign marketing sends only. Automations, transactional mail and test sends are not copied.
  • It never fires when the copy address is the same as the recipient, so a contact on your own list does not get two copies.
  • The optional name is for your own reference. A BCC envelope carries no display name, so only the address is used.

Transactional email

Order confirmations, receipts, shipping notices, password resets and one-time codes are transactional. There are two ways to send them.
  • Through the Public API, with POST /public/messages/email.
  • From an automation whose trigger step is switched to This is a transactional automation. Every message step in it inherits the setting. Only a workspace owner or admin can turn it on. See Automation triggers.
Transactional email skips:
  • marketing consent, so it reaches contacts who never opted in to marketing,
  • frequency caps,
  • your own quiet hours and any campaign block window,
  • the marketing deliverability hold, the active-contact limit and workspace suspension.
It also never carries tracking, an unsubscribe link or unsubscribe headers, and it is never copied to your BCC inbox. The sender rules are not relaxed. Transactional mail you send through the Public API, or from an automation marked as transactional, still has to come from a verified domain and a verified sender address, and that domain still has to be clear of the Spamhaus blocklist.
Suppression still applies. An address that hard-bounced, filed a spam complaint or is on the platform block list will not receive a transactional message either. Suppression is checked before the transactional exemption, by design: those addresses are undeliverable or legally off-limits, whatever the message is.
Senderz can route transactional mail through relays that are not permitted to carry marketing. Which relay a message uses is managed for you.

Plain text

Campaign and automation email is sent as HTML. Senderz does not currently build a plain-text alternative for you, and there is no plain-text editor in the builder. The Code pane and the Edit plain text action in the automation email step both open the HTML source, not a text version. If you send through the Public API you can supply your own text alongside html, and Senderz will send a proper multipart message with both.

Testing an email

Open a template and use Send test in the preview pane.
1

Pick a From address

The dialog asks for Send from and only offers verified sender addresses. Templates do not store a From address of their own, so this cannot be filled in for you. If your workspace has a default sender, or exactly one verified address, it is preselected.
2

Enter a recipient

One email address. It does not need to be a contact.
3

Send

The subject arrives prefixed with [TEST].
Two things behave differently in a test:
  • The unsubscribe link is inert. Any unsubscribe token in the message is replaced with #, so clicking it does nothing. This is deliberate: a test must never unsubscribe anybody.
  • Nothing is tracked. Test opens and clicks are not recorded, so a test cannot move your campaign numbers.
Test sends are de-duplicated for two minutes on the same recipient and content, so a double click on Send test delivers one email, not two.

Send timing

On the campaign schedule step, Send mode offers three options for email.
Everyone receives the message at the same moment.
All three only change when a send runs. Every check below still runs at the moment the message actually goes out.

Quiet hours

The Israeli legal quiet-hours and Shabbat block does not apply to marketing email. Email does honour two windows you set yourself:
  • Settings → Sending Settings → Custom quiet hours, which applies to the whole workspace.
  • Block sending window on the campaign schedule step, which applies to that campaign only.
Inside either window an email is held and retried when the window opens, not dropped. See Quiet hours and Shabbat.

Frequency caps

Marketing email is capped per contact at 5 messages a day and 15 a week. A contact over either cap is skipped for that send. Transactional mail is not counted and is not capped. A recipient who chooses reduce frequency on your preference center is capped tighter than that from then on.

Smart sending

Smart sending skips a contact in an automation when they were emailed too recently. It is switched on per automation message step, under Skip recently emailed profiles. Settings → Sending Settings → Smart sending window sets the two windows it measures against:
  • Email campaign window counts how recently a campaign reached that contact. Default 16 hours.
  • Email flow window counts how recently an automation reached them. Default 24 hours.
Each accepts 1 to 168 hours. A contact inside either window is skipped and moves straight on to the next step.

Deliverability and failover

Senderz sends through an ordered list of email providers. If one starts failing, it is skipped and the next one is tried, and it stops being tried at all for a while so a bad provider does not slow every send behind it.
Provider choice, sending IP pools and warmup are managed for you. You own the domain and the content.
One failure is treated differently. If the connection drops after the provider may already have accepted the message, Senderz stops. It does not retry and does not fail over, because either choice risks sending the same email twice. The recipient shows as Failed with Delivery status unknown, and you decide whether to resend.

The Spamhaus blocklist gate

Senderz checks your sending domains against the Spamhaus domain blocklist. If a domain is listed, sends from it are refused with:
This sending domain is listed on the Spamhaus domain blocklist. Request delisting before sending from it.
The campaign wizard flags it on the pre-send checklist before you get that far. A domain flagged as a legitimate site that has been abused is a warning rather than a block, but delivery will suffer until it is resolved.

The pre-send checklist

The review step of the campaign wizard runs a checklist before it lets you send. For email it blocks on a missing template, a missing audience, a missing subject, a missing From name, a From address that is missing or malformed, an unverified domain, an unverified sender address, a blocklisted domain, an invalid reply-to, and an unaccepted compliance declaration. An empty audience and a timing conflict are warnings you can send past. Two findings link straight to the fix: Verify sender address and Open domain settings both open the Domains and senders screen.

Why an email was skipped or failed

Open a campaign and use Recipients to see the per-recipient outcome. Each row is one of Queued, Sent, Delivered, Bounced, Complaint, Failed, Suppressed or Skipped, with a reason.
A skipped recipient is not a failure. Suppression, consent and frequency skips are the system doing its job. A campaign only reports as failed when nobody could receive it. See Consent and compliance for how a contact ends up suppressed.

Templates

Email content is built from reusable blocks, from raw HTML, or from a gallery starter. See Templates and content.