Marketing Automations currently run with Fake or replay providers. They can store workflow definitions, import Ellich events, evaluate conditions, preserve delays, enforce consent checks, and record test evidence, but they do not send real Email, SMS, Instagram, webhook, or paid-AI traffic.
Initialize the starter workflows
Open Admin > Marketing > Automations and select Initialize starter workflows. Ellich creates or restores five versioned test journeys:
- Product Promotion begins when a product is activated and prepares a consent-safe email step.
- Review Request waits one day after a paid order before its test email step.
- 30/60/90 Day Win-back accepts supported inactivity windows, issues an idempotent customer coupon action, and prepares a test email.
- Birthday records a birthday reward action and prepares a consent-safe test message.
- First-to-Second Visit recognizes the first paid visit, waits seven days, and prepares a return invitation.
Initialization does not import events, start a run, or contact a customer.
Import and process test journeys
Select Import current Ellich events to copy eligible tenant events into the marketing event ledger. The result separates new, duplicate, and rejected events. Duplicate protection prevents the same event key from creating the same work twice.
Select Process ready customer journeys to advance eligible runs using the displayed test clock. A delayed node remains waiting until its next action time. Every Email or SMS node rechecks current consent and contact status before the Fake provider step. A run can succeed, wait, fail, meet its goal, exit, or be cancelled without implying external delivery.
Activate and pause correctly
Activate makes a workflow eligible to process matching test events. Pause prevents new progress through that workflow. Neither control grants permission to use a live provider.
The run table shows the workflow, source event, state, current node, and next action. Use those records as test evidence only. A succeeded Fake-provider run is not a delivered customer message and must not be reported as campaign delivery.
Understand the two automation areas
The page also retains CRM automation rules for scheduled, segment-event, and RFM-compatible campaign drafting. Those rules can save a message template, channel, optional segment, schedule interval, execution contract, campaign name, and audience-sync choice. Review the selected execution contract before running a CRM campaign; automation-rule activation and campaign dispatch are separate operations.
Real outbound canary or production sending requires a separately authorized provider workflow. While the page reports Provider mode: Fake by default, do not enter live credentials or interpret test counts as provider billing or delivery evidence.