This guide describes a small welcome campaign: an internal test contact enters a segment, receives one welcome email, and reaches the end of the workflow. Keep that scope until you can explain every transition. It is a documentation-based walkthrough, not a report of a campaign we executed.
1. Prepare a working installation
Start with a maintained Mautic instance, an administrator account, a configured email transport, and an internal mailbox you control. Installation and sender setup are prerequisites; drawing a campaign does not establish message delivery. Confirm the release-specific instructions for your installation before changing its configuration. [1][5]
Write down the intended outcome: one test contact should receive one specific message. Use a distinct campaign name and a test-only audience so the exercise cannot accidentally include a production mailing list.
2. Define the audience
Create a new segment from the Segments area. Give it a clear name such as Welcome campaign test. Use a filter that identifies your internal test contact, and check that the intended person actually appears in the segment after processing. Mautic updates filter-based membership through its segment job. [3]
Avoid mixing manually added contacts and filter rules while learning the workflow. The documentation notes that manually added contacts remain in a segment independently of its filters. If someone appears unexpectedly, check how they entered before changing the campaign.
3. Prepare the message
Create the email intended for the campaign, choosing the message type appropriate to automation rather than an unrelated segment broadcast. Write a short subject, a recognizable sender name, and a single useful next step. Preview the message and send an internal test before connecting it to the campaign. [5]
Inspect the result on a phone as well as a desktop mail client. Check the destination of every link and replace any sample copy. Successful rendering and successful delivery are different checks, so record both.
4. Connect the campaign
Create a campaign, open its builder, and choose the test segment as the contact source. Add the action that sends your prepared email, then save the workflow. Check publication settings and timing before enabling it. Mautic requires a source and at least one event for a useful campaign. [2]
Keep contact restart disabled for this introductory one-time sequence unless you deliberately want repeat entry. A recurring workflow needs a separate decision about what should happen when the same person qualifies again.
5. Verify scheduled processing
Ask the installation owner to confirm the required segment, campaign-update, and campaign-trigger jobs. Mautic recommends staggering jobs rather than scheduling all of them at the same instant. Additional sending or queue commands depend on how the installation handles email. [4]
Do not add duplicate jobs to an existing deployment. Check current schedules, recent successful runs, and logs first. If a contact qualifies but no email arrives, follow the stages in order: segment membership, campaign membership, action execution, and delivery.
6. Review the result before expanding
Use the internal contact record, campaign information, delivery logs, and received message to verify the full path. Check that the same person does not receive an unintended second welcome message. Test any exclusion conditions you introduced.
Only then replace the test audience with the intended audience and document the operational owner. Add later messages or branches one at a time. The objective is a journey that is understandable and repeatable, with evidence at each step when something fails.
Continue reading
Sources and verification
Official sources checked on September 19, 2026. Product plans and interfaces may change.