Solutions · SaaS
Lifecycle email that reacts to what users actually do.
Send product events to Sendalto, and journeys start when something happens in your product — and stop when the user reaches the goal. Every journey passes your approval first.
Use cases
Four journeys most SaaS teams need first.
Examples of how a journey is put together. Event names are yours; these are illustrations.
Trial to paid
Help trial users reach the moment the product clicks, before the trial ends.
- Starts on
trial_started- Emails
- Day 1 · Finish the one setup step that matters
- Day 4 · Invite your team
- Day 11 · What happens when the trial ends
- Stops when
subscription_started
Onboarding
Guide new accounts through setup, skipping what they have already done.
- Starts on
account_created- Emails
- Day 0 · Connect your first data source
- Day 2 · Build your first dashboard
- Day 6 · Share it with a colleague
- Stops when
activation_completed
Win-back
Give quiet or cancelled customers one relevant reason to return — and respect every opt-out.
- Starts on
subscription_cancelled- Emails
- Day 14 · What changed since you left
- Day 30 · Your data is still here
- Stops when
subscription_started
Product updates
Tell only the users a change matters to, instead of the whole list.
- Starts on
feature_used · reports- Emails
- Day 0 · Scheduled reports are here
- Stops when
feature_used · scheduled_reports
Product events
Your product events, one request each.
Your backend sends an event when something happens. The event can start journeys, end them at the goal, and feed segments.
- Scoped server API key; browsers cannot call the endpoint directly
- Your own event ID makes retries safe — a repeat is recognised as a duplicate
- Events are matched to contacts by email
Up to 600 events per minute per workspace.
curl -X POST https://sendalto.com/api/events \
-H "Authorization: Bearer $SENDALTO_EVENTS_KEY" \
-H "Content-Type: application/json" \
-d '{
"externalId": "evt_8f2c41",
"name": "trial_started",
"email": "[email protected]",
"properties": { "plan": "team" },
"occurredAt": "2026-10-06T09:14:00Z"
}'CSV import
Bring existing contacts and consent records in a file.
HubSpot
Sync contacts with your own HubSpot credentials.
Webhooks
Forward incoming events to your own systems.
Consent
Opt-outs that hold everywhere.
Lifecycle email goes through Amazon SES from your verified domain, and the rules are checked again for every recipient right before sending.
Consent re-checked at send time
Consent, unsubscribes, the do-not-contact list and bounces are checked when the email goes, not only when the journey was planned.
One-click unsubscribe
Marketing emails carry one-click unsubscribe headers. An unsubscribe applies across the whole workspace.
Export or erase a person
Answer privacy requests from the workspace. Erasing a person keeps their opt-out, so they are never mailed again.
Measurement
Measure the goal, not the open rate.
A journey is judged by the product event it aims for.
What Insights shows
Delivery states as reported by the provider, replies and goal events. Opens and clicks are labelled raw and unfiltered. Experiments hold back a control group and say “inconclusive” when there are too few people.
- Control group per experiment
- “Delivered” is never presented as “in the inbox”
- No invented benchmarks
Start with your trial-to-paid journey.
Setup and test sends are free. Nothing is billed today, and you see the price before any charge.