Maqetin sends marketing email from what your customers do.
A journey starts when a customer acts, waits as long as you say, checks what they did since, and sends the next email. Campaigns for launches and sales are planned.
A journey starts on an event.
Your app sends the event. The journey waits as long as you say, from 5 seconds to 1 year, then a condition checks what the person did since.
- A condition branches the path. It checks whether the person did the event since entering, or whether a trait matches.
- Versions. Publishing a change makes a new version. People already inside finish the version they entered.
Sample workspace: Harbour Money, a digital bank in London.
Consent is checked before every send.
The marketing-email flag
Your app sets it when it identifies the person, and marketing is never sent to a profile marked no.
One-click unsubscribe
On every marketing email, honoured across your workspace.
Suppressions
A hard bounce, a complaint or an unsubscribe stops sends to that address across your workspace.
Marketing and transactional are separate
A code or a receipt still reaches a profile marked no for offers.
What is planned.
| What | Status | What it will do |
|---|---|---|
| Campaigns | Planned | Pick a segment, write once, and send now or at each person's local morning. |
| Waits until local time | Planned | Send to each person at the hour you choose, in their own timezone. |
| Goals | Planned | People leave a journey the moment they do what it was for. |
| Frequency caps | Planned | At most a set number of messages per person per day or week, across every journey. |
| Quiet hours | Planned | No marketing goes out between the hours you set, in each person's own time. |
| A/B tests with a holdout | Planned | They will show whether the campaign changed behaviour. |
| A drag-and-drop editor | Planned | It will sit beside your own HTML. |