
Marketing automation helps your team respond consistently when something meaningful happens: a person signs up, submits an enquiry, books an appointment or reaches a new stage in their relationship with your organisation.
The strongest starting point is one useful journey with a clear trigger and a clear finish. For a Nigerian training provider, that could be helping new registrants find their joining instructions. For a software business, it could be helping new accounts complete their first setup task.
This guide shows how to plan that journey, build it in Yournotify, connect application events and test the workflow before opening it to a wider audience.
Table of Contents
A brand example: Duolingo’s reminders with context
Duolingo’s explanation of its practice notifications describes selecting reminders using context such as the language someone is studying and their current streak. The useful lesson is to connect a reminder with the person’s goal and progress.
For a Nigerian training provider, that could mean reminding a learner about the next useful course action. For a service business, it could mean helping an applicant complete a requested booking. Start with a clear rule and helpful content before adding more complex personalisation.
With Yournotify, identify the contact, send the relevant confirmed application event and configure the workflow to act on that event. Keep the message and stopping condition aligned with the task you want to help the person finish.
Automation use cases by industry
| Industry | Trigger | Useful sequence | Stop or change the sequence when… |
|---|---|---|---|
| Education | Registration completed | Welcome, access instructions and one relevant reminder | The learner completes the intended step |
| Ecommerce | A confirmed order event | Order information and the appropriate follow-up | The order is cancelled or the journey finishes |
| Hospitality | Booking confirmed | Preparation details and an arrival reminder | The booking changes or is cancelled |
| B2B services | A qualified enquiry is recorded | Consultation information and an agreed follow-up | An appointment is confirmed or the enquiry closes |
| Membership organisations | Registration or renewal completed | Welcome, programme information and relevant updates | The member changes preferences or the sequence ends |
Implement each row using the events and conditions your application actually supplies. If your workflow needs to stop after a cancellation, connect the cancellation event or state update before activating it.
Worked example: an admissions follow-up
A prospective learner requests information about a Lagos programme. Send the requested details first. After an appropriate delay, check whether an application has been completed. If it has, move the person to application guidance. If it has not, send one useful answer to a common question, such as the timetable or entry requirements.
Use Africa/Lagos for the relevant schedule, and test the real delay and exit behaviour before launch. Where an organisation serves learners abroad, choose timing suitable for those recipients rather than copying the same send time to every audience.
Measure applications completed and support questions resolved. The purpose of the workflow is to help people progress, so a successful exit is as valuable as a successful send.
Step 1: write the journey before building it
Describe the trigger, audience, outcome and stopping rule in plain language. If your team cannot agree on those four items, adding more workflow steps will make the uncertainty harder to manage.
| Decision | Example onboarding journey |
|---|---|
| Trigger | A person completes signup |
| Audience | New accounts eligible for the onboarding journey |
| First action | Send a welcome email with one setup task |
| Delay | Wait 24 hours |
| Decision | Check whether the setup task is complete |
| Next action | Send one useful reminder only when it is still needed |
| Finish | Exit after completion or after the planned reminder |
This is a suggested journey design. Configure the matching trigger, conditions and actions available in your workflow builder. Keep the initial version short enough to test thoroughly.
Step 2: prepare the contact data and message
Your workflow needs a stable contact identity and the data used by its conditions. If the journey depends on an activation state, decide which application event or profile update confirms that state.
Prepare the message before connecting it to the workflow. A welcome email might say:
Welcome to Example Academy. Your account is ready. Choose your first course here: https://example.com/courses. If you need help choosing, reply and our team will guide you.
The reminder should add help, not merely repeat “You have not completed this”. Explain the next step, answer a common question or offer support.
Choose an approved sender and use a channel appropriate to the message and the person’s preferences. Test personalisation with missing optional fields. Do not make the entire workflow depend on a field your form rarely collects.
Step 3: build the workflow in Yournotify
Open Automations, create the workflow and give it a clear name, such as New account — first course selection. Keep it inactive while you configure the trigger, audience rules and steps.
Add the first action, the delay and the condition that decides the next step. Check each branch and its destination. A branch that never reaches a finish can cause confusing behaviour even when the individual messages are well written.
Review enrollment and repeat-entry settings. Decide whether a person should enter once, after a particular event or again only under an explicit rule. Set frequency controls that fit the journey and check how it interacts with other active campaigns.
Use the builder’s validation and preview tools before activation. A valid workflow structure is the beginning of testing, not the end: you still need to prove the contact, event and message behave together.
Step 4: identify the contact from your application
For application-driven journeys, send identity information from your backend using POST /sdk/identify. Use a stable application ID rather than generating a new ID on every visit.
curl -X POST 'https://api.yournotify.com/sdk/identify' \
-H "Authorization: Bearer $YOURNOTIFY_API_KEY" \
-H 'Content-Type: application/json' \
--data '{
"integration_id": "academy",
"external_id": "student_123",
"name": "Zaynab Example",
"email": "zaynab@example.com",
"traits": {
"interest": "weekend_training",
"onboarding_stage": "new"
}
}'
This writes identity information in your workspace. Use test details first, and keep the same integration namespace and external ID when sending later events. Keep your workspace API key on the server.
If you need browser-side tracking, use the documented restricted public-token flow with allowed origins and events. Confirmed business events, such as paid orders or completed registrations, should come from the system that verifies them.
Step 5: send the event that starts the journey
After the signup has actually completed, submit the event through /sdk/events. Configure the automation trigger to match the event you send.
curl -X POST 'https://api.yournotify.com/sdk/events' \
-H "Authorization: Bearer $YOURNOTIFY_API_KEY" \
-H 'Content-Type: application/json' \
--data '{
"integration_id": "academy",
"event_id": "signup_student_123_v1",
"event": "signup.completed",
"external_id": "student_123",
"properties": {
"signup_source": "website"
}
}'
This is a real event-writing endpoint and may trigger matching active workflows. Test against an isolated test workflow and contact before using production events. Reuse the stable event ID for a retry of the same action instead of creating a fresh ID and making it look like a new signup.
Store the returned event receipt and inspect processing results when investigating a journey. The Yournotify event documentation includes receipt inspection and the supported payload fields.
Step 6: test both the happy path and the stopping rules
Create a short test plan before activation:
| Test | Expected result |
|---|---|
| Eligible new contact completes signup | The contact enters the intended journey |
| The same event is retried | It does not become an unrelated second signup |
| The contact completes setup before the reminder | The reminder is skipped according to the configured rule |
| Optional name data is missing | The message remains readable |
| A channel is unavailable or not appropriate | The workflow follows the intended failure or exclusion path |
| The workflow finishes | No additional step runs unexpectedly |
For a test copy, use shorter delays where the builder permits them, then restore the intended timing before activating the real workflow. Check the message on an actual test device and review the contact’s event and workflow history.
Step 7: improve the journey using its outcome
Measure eligible entrants, successful actions, failures, exits and the intended outcome. For onboarding, the outcome may be first-course selection; for an appointment journey, it may be confirmed attendance.
If 100 eligible accounts enter and 40 complete setup, the completion rate is 40%. That does not by itself prove automation caused all 40 completions. Compare suitable cohorts or a controlled test when you need to estimate improvement.
Change one important element at a time: the first message, the delay or the reminder’s help content. Keep event names and measurement rules stable so the comparison remains useful.
Frequently asked questions
How is automation different from a scheduled campaign? A scheduled campaign runs at a chosen time. A workflow coordinates actions around triggers, conditions, delays and a person’s progress.
Should every journey use several channels? No. Start with the channel that fits the task. Add another when it solves a clear communication need and respects the recipient’s preferences.
What prevents repeated messages? Use stable event references, deliberate enrollment rules, suitable frequency controls and a clear stopping condition. Test them together rather than relying on one setting alone.
Automate one useful journey first
Open Yournotify Automations, define one trigger and build a short workflow with a measurable finish. Connect your application using the API documentation, test the entire journey and expand from what the results show.