Cloning a use case
Reuse an existing use case's setup, data, or segments as the starting point for a new one.
Cloning copies an existing use case into a new one so you can iterate without touching the original. The definition always carries over; you choose whether the input data and the segment results come with it. Cloning is handled by Neuralift’s data science team as part of the engagement (see Roles & permissions), and it’s how most repeat work happens: agree on what should change, and Neuralift clones and reruns.
When to clone
Two situations come up constantly:
- Rerun on fresh data. Your quarterly refresh has landed in the warehouse and you want the same segmentation on the new snapshot. Clone the use case, point the clone at the newly synced source table, and rerun. The original keeps its published results while the new run is in flight.
- Try a different definition. You want to see the same customers at a different granularity (say Large instead of Small) or with a reworked goal or KPI priority. Clone with the input data carried over, adjust the definition on the clone, and rerun on identical data so the comparison is clean.
In both cases the payoff is the same: the original stays intact as a reference point, and the clone gives you a safe place to change exactly one thing.
What carries over
Every clone starts from the original’s full definition. The two data toggles are off by default:
| What | Carries over? |
|---|---|
| Name | Prefilled as “<original name> (Copy)”; rename it in the clone dialog. |
| Goal, business context, and KPIs | Always copied. |
| Desired Segments size | Always copied. |
| Run configuration | Always copied. |
| Input data | Only if Copy input data is switched on. |
| Segment results | Only if Copy segmented data is switched on. |
Switch on Copy input data when you want to rerun against the exact same prepared dataset, for example to compare definitions or segment sizes. Leave it off when the point of the clone is fresh data. Switch on Copy segmented data when you want the clone to start with the original’s segments already in place rather than waiting for a new run.
What happens next
While the copy is in progress the new use case shows a cloning badge on the dashboard. Once it settles, it behaves like any other use case: edit the definition, prepare or reuse data, and Neuralift starts a run when you’re ready.
Tip. Clone before changing a use case whose results your team relies on. Published results stay exactly as they are while you experiment on the copy, and you can archive whichever version loses.