Maqetin starts a journey when a customer acts.
It waits as long as you say, checks what they did since, and sends the next email. Other channels are planned.
Sample workspace: Harbour Money, a digital bank in London. A wait shows how many people are in it right now.
A journey is built from five kinds of step.
A condition branches the path. Waits until local time, A/B splits and goals are planned.
Nine in the morning, in four timezones.
Wait until local time will send to each person at the hour you choose, in their own timezone. Campaigns will be scheduled the same way.
- Each profile knows its timezone and where it came from: a trait you set or the device. An IP lookup is planned.
- Daylight-saving gaps and repeats will be handled by a maintained timezone library.
- A send time that has passed will go out tomorrow, or now if you prefer.
Rules every journey follows, and rules still planned.
Versions, suppressions and the marketing-email flag apply today. Frequency caps, quiet hours and goals are planned.
Frequency caps
Planned: at most N messages per person per day or week, across every journey and campaign, per channel or overall.
Quiet hours
Planned: nothing marketing between the hours you set, in each person's own time. Transactional messages will still go.
Goals and exits
Planned: the moment someone does what the journey was for, they will leave it. Nobody will get a reminder for a cart they already paid for.
Versions
Publishing a change makes a new version. People already inside finish the version they entered.
Suppressions
A hard bounce, a complaint or an unsubscribe stops sends to that address across your workspace.
Consent checks
Marketing is never sent to a profile marked no for marketing email. A code or a receipt still reaches it; an address that unsubscribed, complained or hard-bounced gets no mail at all.
Campaigns will go out for launches, fee changes and sales.
You will pick a segment, write once for each channel, and send now or at each person's local morning. Each campaign will report the revenue it brought in.
- A/B tests with a holdout will show whether the campaign changed behaviour.
- Drag-and-drop email will sit beside your own HTML.
| Campaign | Audience | Status | Revenue |
|---|---|---|---|
| Year-end saleEmail · Push · WhatsApp | Bought in the last 90 days | Scheduled | — |
| New savings rateEmail · In-app | Savings holders | Sending | £6,120 |
| Card fees are changingEmail · SMS | All card holders | Sent | — |
| Black Friday early accessPush · Email | VIP buyers | Sent | S$43,150 |
Six templates will cover fintech, ecommerce and SaaS.
Each template will use the suggested event names. Abandonment is worked out from what didn't happen, so your app never sends a "cart abandoned" event.
| Template | For | How it runs |
|---|---|---|
| KYC nudge | Fintech | kyc.started→wait 24 h→notkyc.completed→email |
| First transaction | Fintech | kyc.completed→wait 1 day→nottransfer.completed→email |
| Cart recovery | Ecommerce | cart.updated→wait 1 h→notorder.placed→email |
| Replenishment | Ecommerce | order.delivered→wait 30 days→email |
| Trial activation | SaaS | trial.started→wait 3 days→notinvoice.created→email |
| Trial expiry | SaaS | trial.started→wait 11 days→notplan.upgraded→email |
Connect your events and start a journey on one of them.
People start entering the journey with the first matching event.