This article explains how to use the enhanced Conditions System for scheduled notifications in Momenta. Admins now have increased control over when messages are sent and to whom, using both primary and secondary conditions with dynamic and static triggers.

1. Overview of Conditions

Primary Condition: Required. Determines when the message is sent (based on date/time or user action).
Secondary Conditions: Optional. Up to 3 can be added to further filter the audience.
AND/OR Logic: Combine conditions using “Additionally” (AND) or “Alternatively” (OR).
Real-Time Summary: Plain-language logic preview helps avoid errors.
Conflict Detection: Warnings help catch conflicting or overly restrictive setups.

Click “New Notification” from Journey, Cohort, or Team view
Fill in required fields:
- Title
- Audience
- Channel (Email/In-App)
- Message Body
- Primary Condition
Optionally add up to 3 Secondary Conditions
Use the Summary section to confirm logic reads clearly
Click Save as Draft or Save & Enable

The new modal UI is cleaner, uses dropdowns and toggles, and validates entries in real time.

3. Defining a Primary Condition

Static Primary Condition:

Choose a specific date and time
Used for announcements or fixed-date reminders
Sent at midnight UTC if time is not set

Dynamic Primary Condition:

Triggered by a user action (e.g., completion, login, booking)
Components:
- Time value (e.g., 3)
- Unit (minutes, hours, days, weeks)
- Moment (before, after, immediately)
- Trigger (e.g., "user added to cohort", "module completed")
0 = Immediately after the action occurs
Time is stored in UTC for consistency

4. Using Secondary Conditions

Secondary Conditions help filter the audience for more precision. You can define up to 3 per notification using AND or OR logic.

Available Filters Include:

Learner Score Range: e.g., “greater than 100”
User Added to Cohort: by date (before/after/equal)
Last Login Date: inactivity nudges or engagement filtering
Completion Status: based on activity/module/stage completion
Coaching Session Status: unbooked, missed, completed, etc.

Logic Type:

AND: All conditions must be true (“Additionally” in summary)
OR: At least one must be true (“Alternatively” in summary)

Warnings: The system will flag combinations that result in no recipients due to conflict or misalignment.

5. Reviewing the Condition Summary

As you define logic, a real-time summary appears at the bottom of the modal. This provides a plain-language description of the full logic setup.

Examples:

Primary Only: “Send this notification 1 day after module completion.”
Primary + Secondary (AND): “...only if score > 100 and login was before Jan 10.”
Primary + Secondary (OR): “...if score < 50 or they joined before March 1.”

This helps prevent delivery mistakes and provides a clear record for QA or reviews.

6. Tracking Conditions in the Notification Table

All configured conditions are shown in their own columns
Primary Condition: displayed as static or short-form dynamic description
Secondary Conditions: shown as simplified filter logic
Use the Notification Table filters to:
- Search by condition type (static vs dynamic)
- Find notifications using specific filters (e.g., “last login”)
- QA logic for upcoming launches
To review filters, see: Scheduled Notifications