Cloning broadcast campaigns between accounts

Users with the right permissions to clone broadcast campaigns can do so directly from the Broadcast campaigns screen.

Click the options dropdown and select Clone to another account:

Choose the account(s) you want to clone your campaign to, then click Next:

In the next screen, choose whether or not to clone the email templates used in this campaign.

If you have a multi-language template in this campaign you'll also have the option to convert it to a single language in the receiving account.

Click Next.

In the last screen, choose either:

• Ignore assets - Ometria won't copy the images and/or GIFs in this template to the receiving account
• Clone template assets - Ometria will copy all images and/or GIFs to the cloned template 

Then Confirm your selection:

That's it! You'll get an email once your campaign and any associated templates and assets have been cloned to the receiving account:

Receiving cloned campaigns

Users in the receiving account also get an email:

Follow the link to see the cloned campaign in the receiving account.

If templates were included, they are unpublished until you've reviewed themz.

Assets are also cloned to the receiving account's asset manager in a folder named after the template. 

You should review your campaign and templates and check for any custom fields or product recommendations that might not be present in your account.

We also recommend checking all of the URLs in your template.

Reviewing your cloned campaign

Any Ometria default filters and data fields in your campaign will transfer across to the receiving account.

If you have custom filters, specific segments, custom fields, etc. in your cloned campaign that aren't available in the receiving account, Ometria flags the node with an exclamation mark (!):

We recommend checking the following in your cloned template:

• Custom fields
• Segment conditions
• Merge tags
• Product recommendations
• Product selections
• Images

Re-cloning a campaign

If you clone the same campaign to the same account a second time, it will overwrite all of the data in the first clone.

Assets are not overwritten, and remain in your Asset folder. 

See also: Cloning assets between accounts

Cloning multi-language templates

There are some things to be aware of when cloning multi-language templates.

Cloning a multi-language template to another multi-language template

Ometria will only clone the languages that are available in the receiving account.

So, if one account has English, French and German, but the receiving account only has English and French available in their translation language settings, the German template isn't cloned.

If a template is cloned to an account with no matching languages available, then Ometria adds the source language to the receiving account and the template will only be cloned in that language.

Cloning a multi-language template as a single language template

You can also choose to clone your multi-language template as a single language template.

If the language selected doesn't exist in the receiving account then Ometria:

1. Looks for the source language and uses that if available, or;
2. Uses the template default (this is embedded in the template), or;
3. Sends a blank template. 

Cloning URLs

By default Ometria clones the URLs in campaigns and templates to the receiving account exactly as they are in the original account.

Please reach out to the Creative Team if you needs to localise the URLs in their headers and footers (or any other 'static' links that aren't likely to change often).

There is a charge for this work. 

Enabling cloning between your accounts

Set up

If you're onboarding, your Technical Project Manager (TPM) will work with you to set up your organisational structure for cloning.

If you're already onboarded, reach out to your Customer Success Representative.

See also: Cloning permissions and hierarchy

Permissions

Once your account hierarchy has been set up, users with the Administrator role in your top level account can assign cloning permissions.

Note: The administrator should also be given administrator permissions in the relevant child accounts.

See also: Cloning permissions and hierarchy