This article walks through the process of creating and configuring a cohort in Momenta. Cohorts are essential for managing groups of participants, whether for testing, live delivery, or integrating coaching features. This setup must be completed after a journey has been created and published.

Overview

To create or configure a cohort, you must first have a published journey available. Cohorts are managed under the Experiences & Cohorts section or directly from the journey card in the client collection.

For configuring cohort blueprints, see: Manage the Cohort Blueprint
For uploading participants, see: Bulk Upload Participants
For cohort notifications, see: Set Up Notifications
For team setup, see: Set Up Teams

How to Create a Cohort

Go to Experiences & Cohorts in the Admin App
Search for your client and journey
Click the 3-dot menu > Cohorts or select Manage Cohort from the journey card
Click Create Cohort
Enter the Cohort Title and Start Date
Click Save; the Cohort Code is generated automatically
Optionally, you can create cohorts using the bulk upload tool

Cohort Configuration Options

Once created, cohorts can be configured based on delivery type:

1. Test Cohort

Toggle Test Cohort ON
Automatically toggles off unneeded settings
Recommended for internal testing and journey preview
Enable:
- Cohort Enabled
- Platform Notifications
- Create Coach Users (if testing Coach)
- User Creation Using SSO (if testing self-registration)

2. Live Cohort (No Coach)

Default live settings are automatically toggled ON
Recommended to toggle OFF: User Creation Using SSO unless SSO is required

3. Live Cohort (With Coach)

Toggle ON: Create Coach Users
Select a Coach OS Cohort and a default coach
Bulk upload can then sync users into both Momenta and Coach OS
Note: The Coach OS cohort must be created in Coach before linking

Changing Cohort Settings

Cohort Enabled: Toggle OFF to prevent participants from accessing this cohort (e.g., if sunsetting)
Platform Notifications: Toggle OFF to temporarily disable automated notifications
Include on Dashboard: Toggle OFF to exclude this cohort from standard dashboards

Watchouts

Never name a cohort “unassigned” – this is a system-reserved term
Avoid duplicate cohort titles within the same client collection
Using the same name causes login errors and upload mismatches
Avoid generic titles like “June” or “EMEA”—use format: [JourneyName - CohortNumber - Month]
User Creation Using SSO is ON by default—turn OFF unless you're testing or enabling self-registration