Skip to content
AzimeaDocs
Dashboard

Welcome and onboarding

Greet everyone who subscribes or signs up, at the moment they are most interested, and guide new users until they reach their first result.

A welcome journey introduces your business, explains what someone can expect and helps them take their next step. Use it for newsletter subscribers, new accounts or people starting a service. Choose the trigger that matches your source of contacts and check their consent before sending marketing.

For an application, CRM or membership service, start with onboarding from your own events. For a newsletter list you have already imported, choose its segment in a scheduled or manually started flow. Store newsletter sign-ups can use the connected-store setup below.

Choose the workflow for this journey in Flows, then inspect its trigger, waits and emails. The demo workflows shown are drafts and do not send messages.
Choose the workflow for this journey in Flows, then inspect its trigger, waits and emails. The demo workflows shown are drafts and do not send messages.

For any audience, verify your sending domain, prepare an email template and select a trigger in Flows. Test the flow with a contact before publishing. Importing a list alone is not a sign-up event for a store welcome flow.

  1. Settings › Consent: choose how your shop collects consent and declare it. Until you do, no marketing email goes out, the welcome included.
  2. Optional, in the same place: turn on double opt-in.
  3. Flows › Welcome: check the email and press Publish. The flow was created as a draft when you set up your first emails; until it is published, nobody is welcomed.
  4. Optional: use the Welcome series template for more than one email.

For the connected-store welcome described above:

  1. Someone subscribes: a newsletter form, a popup, the newsletter box at checkout, or the shop’s own newsletter. Their consent and its proof are kept.
  2. If you use double opt-in, they first receive a confirmation email and stay PendingConfirmation. The welcome waits: it starts only when they click the confirmation link. Someone who never confirms is never welcomed.
  3. They become Subscribed, and Azimea records contact.subscribed on their timeline.
  4. The welcome flow starts. A flow whose trigger is Store events › New subscriber begins for them; the ready-made Welcome flow sends its email right away.
  5. A person who ticked “subscribe” while creating an account in your shop starts the flows whose trigger is Customer created or updated instead, so you can greet new account holders differently. An account created without the tick starts nothing: it gives no right to marketing.

The ready-made flow sends one email. The Welcome series template in Flows › New workflow sends three: on the day, two days later and three days after that.

Only these consent statuses lead to a welcome; the full list is in consent statuses:

Status or reasonWhat it meansWhat you do
SubscribedThey ticked a box or signed up to hear from you; the proof is kept in their consent history.Everything reaches them, once you have declared how you collect consent (Settings › Consent).
PendingConfirmationThey asked to subscribe and have not clicked the confirmation link yet (double opt-in).Nothing to do: the confirmation email is on its way. Cart reminders still reach them; marketing waits for the click.

A welcome is a marketing email, so the sending gate applies. It can be stopped for:

Status or reasonWhat it meansWhat you do
sending.gate_bouncedThe person's address does not work any more.Nothing: the address is no longer used.
sending.gate_complainedThe person marked one of your emails as spam.Nothing: they are never written to again.
sending.gate_not_declaredYou 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_topic_opted_outThe person turned off the topic this email belongs to; they still receive your other topics.Nothing: respect their choice.
sending.gate_unsubscribedThe person unsubscribed from your marketing emails.Nothing: they said no. Service emails still reach them.
EventWhat it meansWhen it happensWho sends it
contact.subscribedA contact became a subscriber: a newsletter or form sign-up starts welcome flows; someone who ticked marketing while creating a shop account starts the flows on new customer accounts.When a contact's consent becomes Subscribed.Azimea

The shop sends the sign-up itself as subscriber.created (or customer.upserted for an account); both are explained in the events catalog.

Your system tells Azimea when someone signs up or completes a step, and flows take it from there. How your system sends events is in Connect your systems.

Ready-made flows. With An app or digital service selected in Settings › Company, Flows › New workflow offers flows built on the suggested product events:

Flow Starts on Stops on What it sends
Welcome new users user.signed_up — An email at once, another two days later, a third three days after that
Activation nudge user.signed_up user.activated A tip a day after sign-up, another two days later, only to those who have not activated
Trial ending trial.ending subscription.started One email before the trial ends, never to someone who already subscribed
Re-engage quiet users A schedule — An email to the people you choose, then a tag on who was reached

Your system can use other names. A flow can start on any event, and Stop the workflow when… takes up to 10 events.

An onboarding in several steps. When an account is ready only after a few steps (a form, documents, a confirmation), send one event per step and let a flow write to whoever stopped:

  1. A flow starts on the first step, for example application.started.
  2. It waits a day, then sends what is still needed; two days later, a last reminder.
  3. Under Stop the workflow when…, the next step (documents.submitted) ends it for whoever completed it.
  4. A second flow on the last step (account.activated) welcomes them into the account.
  5. Mark account.activated as a conversion in Settings › Events, and reports count the accounts activated after each email.

The developer’s side, with the calls, is in Connect your own system.

Consent. A sign-up is not a newsletter subscription. A flow that only helps a person finish or use the account they opened, with no offer in it, can be marked Service message under What it is for: it then reaches them without marketing consent (see marketing or service). Anything with an offer stays marketing and needs their consent, sent with the contact as in Contacts and consent.

Symptom Likely cause Fix
Subscribers appear but get no welcome The Welcome flow is not published, or consent is not declared. Publish the flow; declare consent in Settings › Consent.
Some subscribers get it, others not Double opt-in is on and they have not confirmed. Nothing: they are welcomed when they click the confirmation link.
The flow history says “Email not sent” The sending gate stopped it; the reason is shown next to it. See why an email was not sent.
A new shop account got no welcome The account was created without the newsletter tick. Expected: an account alone gives no right to marketing.