Campaign Enrollment
Choose how recipients enter a campaign, define recipient scope, and control re-entry
Enrollment creates a recipient's individual journey. Open a campaign and select the Enrollment tab to configure the entry rule and review recent recipients.
Automatic enrollment runs only while both of these conditions are true:
- The campaign status is Active.
- Enable automatic enrollment is selected.
Entry methods
Manual or Campaign API
Use manual or API enrollment when another workflow decides exactly who should enter. This is also useful for controlled backfills of existing recipients.
When a module record is created
Use this for customer-managed CRM data such as new leads or contacts.
- Select When a module record is created.
- Choose a source module with an email field.
- Select the re-entry policy.
- Enable automatic enrollment.
Records created through the Coherence UI, API, or an integration use the same trigger. Existing records are not treated as newly created merely because the rule was enabled.
When an external event is received
Use this when an external application pushes a lifecycle event into Coherence.
- Select When an external event is received.
- Enter a stable event name, such as
trial_started. - Select a re-entry policy.
- Enable automatic enrollment.
Send an account-authenticated request to:
POST /api/v1/module-config/marketing-campaigns/eventsExample body:
{
"eventName": "trial_started",
"idempotencyKey": "trial:trial_123",
"recipientEmail": "[email protected]",
"recipientName": "Taylor Example",
"sourceId": "trial_123",
"properties": {
"plan": "pro"
}
}Use a stable, unique idempotency key for every real event. Retrying the same request with the same key will not intentionally create a duplicate enrollment.
When a new Coherence workspace signs up
This vendor-only entry method is available only in the configured Coherence workspace. It reads directly from product Account, User, and Role tables rather than creating CRM People records.
Recipient scopes are:
| Scope | Enrolls |
|---|---|
| First signup user | The first user created for the workspace |
| Workspace owner | The current owner |
| Workspace admins | Active users with the admin role |
| Owners and admins | Active owners and admins |
| All active users | Every active user in the workspace |
| Selected roles | Active users in the selected owner, admin, manager, or user roles |
Enable Include users who join later when new matching users should begin the journey from their own workspace join date.
Only accounts and users created after the signup rule is enabled are included automatically. Use manual or API enrollment when you intentionally need to backfill earlier users.
Re-entry policies
| Policy | Behavior | Typical use |
|---|---|---|
| Once ever | A recipient can enter the campaign only once | Onboarding, learning, or welcome campaigns |
| Again after exit | A recipient may re-enter after the previous enrollment is no longer active | Eligibility-based programs where an exited person may qualify again |
| Again after completion | A recipient may re-enter only after completing the journey | Repeatable training or renewal education |
| Once per unique event | Each unique event may enroll the recipient again when no enrollment is active | Purchases, trials, projects, or other repeatable lifecycle events |
For new-user onboarding or a learning series, Once ever is usually correct. Include users who join later handles future users; it does not require a more permissive re-entry policy.
Recent enrollments
The bottom of the Enrollment tab shows recipients who entered the campaign, their enrollment source, status, and timing. Use this list to confirm that the rule is firing before diagnosing sending or provider behavior.
Next: Connect a provider and review Sending and Compliance.