This article explains how to use the Cloning Notifications feature in Momenta. Cloning allows Admins to quickly duplicate one or more notifications across cohorts and teams within the same journey—saving time, reducing manual effort, and ensuring consistency across programs.
Overview: Why Clone Notifications?
The cloning feature allows you to:
- Reuse notifications across cohorts or teams without rebuilding
- Maintain consistent logic and message formatting
- Quickly localize or version communications
- Reduce error from manual re-entry
- Scale post-pilot programs with proven messaging
How Cloning Works – Key Principles
- Cloning happens within the same journey only (cross-journey cloning not supported)
- All cloned notifications are saved as Drafts, regardless of the original status
- Cloned versions are fully editable: title, content, audience, and conditions
- Clones are tagged with a “COPY” label and metadata for traceability
- You can clone via:
- Action menu (three dots) for single notification
- Bulk selection checkboxes for multiple notifications
Understanding Audience Targets
Cloning works within the same journey and supports the following source/target flows:
Source | Target | Use Case |
---|---|---|
Journey | Cohort | Adapt a general message for specific group |
Cohort | Team | Send subgroup-specific messages |
Cohort | Different Cohort | Roll out to new waves |
Team | Same Cohort | Promote team messages to cohort |
Team | Different Team | Reuse message for peer teams |
Note: All primary and secondary conditions are preserved, but you should always confirm they apply in the new context.
Cloning a Single Notification
- Navigate to the Notifications table
- Click the 3-dot menu next to the notification
- Select Copy Notification
- Choose your target audience (Journey, Cohort, or Team)
- A modal opens with all content and conditions copied
- Edit as needed:
- Update the title
- Change audience
- Edit content or timing
- Save the copy (default status is Draft)
- Enable when ready
Cloning Multiple Notifications (Bulk Copy)
- Open the Notifications table at Journey/Cohort/Team level
- Select checkboxes for 2+ notifications
- Click the “Copy Selected” button
- In the modal:
- Choose target audience (Journey, Cohort, or Team)
- Confirm destination and notification list
- Click Confirm and Clone
Each copy is saved as a Draft with the “COPY” suffix. You can edit them individually afterward.
Best Practices
- Use clear, specific titles for notifications — helps organize COPY versions
- Review conditions in the new cohort or team context
- Apply filters (e.g., “Status: Draft” or “Title contains COPY”) to audit new drafts
- Only clone finalized or approved notifications to maintain quality
- For localization, clone then update language content in the body
Visual Aids
- Journey to Journey
- Journey to Cohort
- Journey to Team
- Cohort to Journey
- Cohort to Same Cohort
- Cohort to Different Cohort
- Cohort to Team
- Team to Journey
- Team to Same Cohort
- Team to Different Cohort
- Team to Same Team
- Team to Different Team
- Copying a Draft Notification
- Copying an Enabled Notification
- Copying a Disabled Notification
- Single Copy Modal
- Clone Multiple Notifications
- Bulk Copy Modal for Multi-Notification Cloning
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article