Why an email was not sent
email not sent · suppressed · blocked email · sending gate · gate_no_basis · gate_not_declared · gate_unsubscribed · no consent · not delivered
Before an email is queued, Azimea checks whether the person’s consent status allows this
kind of message. When it does not, the email is stopped: its status becomes Suppressed, the reason is written on it,
and a flow’s history shows “Email not sent” with the same reason.
| Status or reason | What it means | What you do |
|---|---|---|
sending.gate_bounced | The person's address does not work any more. | Nothing: the address is no longer used. |
sending.gate_complained | The person marked one of your emails as spam. | Nothing: they are never written to again. |
sending.gate_no_basis | The person has not subscribed and is not an existing customer, so marketing may not reach them. | Expected for people who only typed their address at checkout. To reach them, ask for consent; or make a message about their own order a service email. |
sending.gate_not_declared | You have not yet declared how your shop collects consent, so no marketing goes out, even to subscribers. | Settings › Consent: choose your method and declare it. |
sending.gate_soft_opt_in_off | The person is an existing customer, but your shop uses a consent checkbox, not a notice at checkout, so buying alone does not allow marketing. | Expected with a checkbox: only those who ticked it receive marketing. Switch to notice at checkout only if your checkout really shows that notice. |
sending.gate_topic_opted_out | The person turned off the topic this email belongs to; they still receive your other topics. | Nothing: respect their choice. |
sending.gate_unsubscribed | The person unsubscribed from your marketing emails. | Nothing: they said no. Service emails still reach them. |
Service emails (about the person’s own order or account, with no offer) only need a working address, so only
gate_bounced and gate_complained can stop them.