Marketing Automation

Reading Workflow Performance

Per-Activity Statistics

Each activity in the campaign view shows Processed, Rejected, Sent, Opened, Clicked, Replied, and Bounced counts, letting you see exactly where a workflow is losing engagement — e.g. a strong open rate on Activity 1 but a weak click rate suggests the email's content/offer, not its subject line, needs work.

Comparing Branches

Since branches are just activities with different triggers, compare how many participants ended up on the "engaged" branch (opened/clicked) vs the "re-engagement" branch (didn't open) to judge overall campaign health, not just a single email's stats.

Best Practices

• Keep the entry filter narrow and specific — a campaign targeting "everyone" behaves like a blunt mass mailing, defeating the point of branching logic.
• Always test-run before starting live.
• Review Participants regularly for the first week after launch to catch a misconfigured trigger before it affects many contacts.
• Keep unsubscribe/compliance requirements from the Email Marketing course in mind — every mailing activity is still subject to the same deliverability and legal rules.

Before You Go Live

Test Mode

Run a campaign against a specific test record before activating it broadly — this lets you walk an activity chain forward manually and confirm the emails/actions look right without waiting for real trigger timing or affecting real contacts.

Starting the Campaign

1. Click Start once satisfied with the workflow — the campaign moves to Running.
2. A scheduled action periodically checks for new records matching the filter and enrolls them as participants, then processes any activities whose trigger/delay has come due.

Note: once a campaign is running, changing an activity's timing (Send After) is restricted, since participants may already be mid-flow relying on the original schedule — stop the campaign first if a structural change is needed.

Participants View

Open the campaign's Participants to see every record that has entered, which activity they're currently on, and their full trace history — useful for answering "why hasn't this specific contact received the follow-up yet."

Pausing & Stopping

Pause a campaign to stop new participants entering and new activities firing without losing the configuration, or stop it entirely once it's no longer needed (e.g. a seasonal promotion campaign after the season ends).

From Target Audience to Chained Activities

Go to Marketing Automation → Create.

Campaign Setup

1. Target Model – which type of record this campaign runs against (e.g. Contacts, Leads).
2. Filter – a domain deciding which records are eligible to enter (e.g. only contacts tagged "Newsletter" who haven't purchased yet).
3. Unicity – optionally restrict so the same contact can't enter the same campaign twice.

Adding Activities

Each activity is either a Mailing (send an email template) or a Server Action (any automated backend action — e.g. add a tag, create an activity for a salesperson). Every activity after the first has:

• Trigger – what causes this step to fire: beginning of workflow, a fixed time after another activity, or a response to a previous mailing (opened / not opened / clicked / not clicked / replied / not replied / bounced).
• Send After – the delay (hours/days/weeks/months) after the trigger condition is met.

This is what creates branching: two activities can both be children of the same mailing, one triggered on "Mail: opened" and the other on "Mail: not opened" — each participant only proceeds down the branch matching what they actually did.

Example Workflow

1. Activity 1 (trigger: beginning of workflow) – Welcome email, sent immediately.
2. Activity 2 (trigger: Mail opened on Activity 1, after 2 days) – Product highlight email.
3. Activity 3 (trigger: Mail not opened on Activity 1, after 3 days) – A re-send with a different subject line.
4. Activity 4 (trigger: Mail clicked on Activity 2, after 1 day) – Notify the salesperson via server action — this lead is engaged.

Validity Duration

Set how long an activity's trigger condition stays "open" for evaluation (e.g. "not opened after 3 days" needs a window to actually wait those 3 days before deciding not-opened is true) — this is handled automatically per activity, but is worth understanding when a workflow seems to be waiting longer than expected.