Introduction to cloning

Cloning objects allows you to copy a Synerise object (such as an expression, segmentation) to other workspaces you are using. The cloning extends to all elements the object contains such as other analysis nested in the object (for example, when a segmentation includes an expression). This is meant to save your time so you don’t have to create these objects from scratch or clone them separately in every workspace you work on.

Objects you can clone:

• Analytics
  • funnels,
  • segmentations,
  • metrics,
  • histograms,
  • reports,
  • trends,
  • Sankey diagrams,
  • aggregates,
  • expressions
• AI recommendations
• Communication-related objects:
  • emails,
  • SMS,
  • web push notifications
  • mobile push notifications
  • dynamic content
  • in-app messages
  • message templates

The process of cloning involves:

1. Selecting an object for cloning.
2. Resolving potential conflicts - a conflict occurs when the system detects the object of the same type and with the same name on the workspace where you want to clone the object. For example, if you clone the “Unnamed segmentation” to the target workspace and there already is a segmentation with identical name, a conflict occurs.
   During this step, you will be redirected to a wizard and you must define what will happen with the object in the target workspace or workspaces:
   • overwrite the object in the target workspaces with the object version from the source workspace,
   • don’t overwrite (skip cloning)
   • create a copy of the object version from the source workspace in the target workspaces.
3. Mapping events/event parameters/attributes/item attributes between the source workspace and target workspace. In this step, you indicate the equivalents of these elements in the target workspaces.
   For example, if the object you clone contains the shoeSize attribute, but this attribute exists in the target space under a different name - size_of_shoe, you can map these two parameters together.