Cloning campaigns and campaign templates to other workspaces

Before cloning messages between workspaces, we recommend reading Introduction to cloning.

This article presents how to clone the following objects to another workspace:

• email
• in-app
• web push
• mobile push
• SMS
• dynamic content
• campaign templates (cloned in the same way as campaigns)

You can clone the whole campaign or just the template.

• When you clone a campaign, the campaign is cloned together with the content and settings (template used in the campaign isn’t cloned).
• The “Schedule” section of the campaign isn’t cloned.
• Each campaign is cloned in the “Draft” status.
• When you clone the template of the campaign separately, the cloned template is saved in Communication > Templates > Default.

Cloned campaign elements

Together with the campaign or template, you can clone the objects it contains:

• AI Recommendation campaigns included in the content (together with the objects it contains, such as expressions, aggregates, metrics, and so on)
• Audience of the message (segmentation/s, aggregates, expressions)
• Analyses included in the template content (aggregates, expressions, metrics, segmentations)

There are some message elements which are cloned but they are transparent during the cloning process:

• Email attachments - The attachment is cloned and available in a target workspace in the Data Management > Files.
• Triggers (for example, occurrence of specific events for in-app messages) and display settings such as priority, frequency are cloned.
• UTM & URL parameters are cloned.
• Additional parameters are cloned.
• The type of the builder in which the content/template was created - If you will edit the content/template in the target workspace, you will do it in the same type of editor that the original template was created in.

Not cloned elements

In the process of cloning your object, you map the elements contained in it which are not copied, but have an equivalent in the target workspace. Some of them must be created before cloning, others can be created as part of the cloning process.

Prerequisites

To clone objects between workspaces:

• You must be assigned a user role (Settings > Roles) that has all possible permissions in the source and target workspaces.
• In the target workspace, if you want to clone an email or SMS, you must configure an email/SMS account. Other campaign types don’t require sender accounts.
• If the campaign/template you clone contains AI recommendations:
  • In the target workspace, enable models for the types of recommendations you want to clone to the workspace and configure the recommendation attributes while configuring the AI engine.
  • Make sure the item attribute names (feed catalog columns) and value types in the item feeds in the source and target workspaces are the same.
• If you refer in a message to:
  • a catalog - make sure you have a catalog with corresponding data and structure (column names and types of values) in the target workspace.
    • If the catalog on the source and target workspaces have the same structure (column names and value types), you don’t have to do anything after cloning is complete.
    • If the catalog on the source and target workspaces have different structure (column names and value types), after the cloning is complete, the cloned message/template includes references to the columns and values from the catalog from the source workspace. You must replace them with the target workspace’s catalog.
  • a voucher pool - make sure you have a voucher pool in the target workspace
  • promotions - make sure you have a corresponding promotion in the target workspace.
  • customer attributes - make sure you have equivalent customer attributes in the target workspace.
• If your campaign includes AI search: After the cloning is complete, the cloned message/template includes references to the search index from the source workspace. You must replace them with the target workspace’s search index.

Select a campaign/template to clone

1. Go to Communication and select the message type.
   • If you want to clone a campaign:
     1. On the list of campaigns, find the campaign you want to clone.
     2. To the right side of the campaign author information, click .
   • If you want to clone a template:
     1. On the left pane, click Templates.
     2. Select the folder where the template is saved.
     3. On the template you want to clone, click .
2. From the context menu, select Clone to workspace.
   Result: The Choose destination pop-up appears.
3. On the pop-up, select up to 5 workspaces to which you want to clone your message.

   

4. Confirm your choice by clicking Next.
   Result: The mapping wizard opens.

Cloning

The procedure of cloning a campaign/template takes place in the mapping wizard and involves:

Cloning campaigns with AI Search references

While cloning a campaign that contains reference to AI Search, it will not be detected. This means, you won’t be able to map the AI search from source workspace with AI search from target workspace.

In such case, after cloning is complete, open the content of the cloned campaign and modify the reference with the AI search parameters from the target workspace.

Resolving cloning issues

An issue occurs when:

• An object of the same type with the same name already exists in the target workspace
• The system could not find the equivalent events, attributes, tags, item feed, item attributes, sender account, catalog, promotion, or voucher pool

To resolve a problem, go to the details of each section whose button says Solve issues.

Section name	Solution
Objects to clone	You can select one of the following conflict solutions: - Update - overwrite the object in the target workspaces with the object version from the source workspace - Don’t update - don’t overwrite (skip cloning) - Create a copy - create a copy of the object version from the source workspace in the target workspaces, the copied object inherits the objects name from the source workspace.
Mapping events	From the dropdown list, select an equivalent event. If there is no equivalent event, you can create one by clicking Create [event name] on the top of the dropdown list.
Mapping parameters	From the dropdown list, select an equivalent customer attribute. There is no possibility of adding a new customer while cloning.
Mapping tags	From the dropdown list, select an equivalent tag. If there is no equivalent tag, you can create one by clicking Create [tag name] on the top of the dropdown list.
Mapping product feed	From the dropdown list, select an equivalent item feed. If there is no equivalent item feed, you must go to the target workspace and create one.
Mapping settings/objects	In this section, you can resolve conflicts connected with sender account, voucher pool, promotion, and/or a catalog by selecting their equivalents from a dropdown list. If equivalents don’t exist, go to the target workspace and create them. - Creating email account - Creating SMS account - Creating voucher pool - Creating a promotion - Creating a catalog

Objects created during cloning

The elements created during cloning are available in their respective modules on target workspace, for example events are added in Data Management > Events.

Jinjava-related issues

The mapping of objects such as catalogs, voucher pools, promotions is available only when the campaign template contains Jinjava code referencing these objects. When it comes to Jinjava references to AI recommendations, aggregates, and other analysis types, mapping isn’t necessary, because these objects are cloned automatically to the target workspace.

Possible issues in detecting dependencies:

• If the Jinjava is incorrect (for example, missing endif), the dependency may not be detected.
• If you clone a campaign that doesn’t support a particular Jinjava tag (for example, the socialproof tag in email template) and the campaign contains the reference to such a tag, the dependency will not be detected. See inserts documentation for detailed info.
• If the Jinjava code is inserted in the comment snippet {# commentary #}, the dependency to such Jinjava will not be detected.
• If you used a variable in the content replacing an element of Jinjava code with a dependency, the dependency will not be detected. For example, if you used a Synerise insert select, after cloning, you must open the content of the cloned campaign in the target workspace and select the insert manually in the content.
• If you used a Jinjava variable instead of directly using the ID of the object being the subject of dependency, the dependency will not be detected. You must open the cloned campaign content or template in the target workspace and replace the object ID manually. See the example below:

      {% set dynamic_object = {'Reco id': 'xyz'} %}
  
      {% macro withParam(param)%}
          {{ dynamic_object.get(param) }}
      {% endmacro %}
  
      {% recommendations3 campaignId={{ withParam('Reco id') }} %}
          // logic of displaying the recommendation
      {% endrecommendations3 %}