Skip to main content
Skip table of contents

Portable Campaigns

image-20240703-060034.png

Broadcast campaigns of any channel type can be shared as a deep copy across any set of accounts that the user has access to and with the Edit Campaign permission.

Trigger campaigns can be shared across accounts by sharing the Experience they are part of.

Sharing a Broadcast Campaign

1. Within the Campaigns list, click on the action menu on the right of the desired experience and select Share from the dropdown. The Share Campaign panel pops open on the right.

Screen Shot 2024-06-20 at 12.10.38 AM.png

2. Name your copy and select the account(s) the campaign has to be shared across.

You need to have an ‘Edit Campaign’ permission in the account that you wish to share an experience with. Reach out to your system administrator to get suitable access to the account, if you do not see the expected account in the list.

Optional: You can add a tag and include people to notify

Screen Shot 2024-06-20 at 12.14.48 AM.png

3. Click on Share Campaign. Within the popup that appears, click on Share to Account to confirm the action.

Screen Shot 2024-06-20 at 12.17.49 AM.png

For sharing to be successful, both the source and target accounts must have the same set of relevant Campaign features enabled, which means they need to be feature-compatible.

4. Once a copy is created, a link to the created copy can be accessed through the Share Campaign panel.

A campaign can be shared multiple times with one or more accounts.

Screen Shot 2024-06-20 at 12.19.43 AM.png

Components of the Shared Campaign

Components

Behavior

Audiences

  • Segment-based campaigns:

    • Include, Control Groups, Seed Recipients - If an audience of the same name exists on the destination account, then that would be used. Otherwise, a copy of the audience would be created on the destination account to be used by the campaign copy.

    • Exclude - If an audience of the same name exists on the destination account, then that would be used. Otherwise, a copy of the audience would be created on the destination account to be used for the copy of the campaign. For exclusions based on campaigns, no campaigns would be created

  • File-based campaigns:

    • For one time, the original file is automatically added to the ftp folder of the destination account.

    • For file-drop, no file will be copied over but the FTP folder for the campaign will be created.

  • API-based campaigns: A new API request URL will be generated.

Content

  • HTML content will be copied as is.

  • Liquid codes will be copied as is and will only reference existing objects within the destination account. This means that the content might be rendered differently than in the original account.

  • Email templates used on the original campaign would not be created on the destination account.

  • Snippets being referenced to the original campaign would not be created on the destination account. Thus, if no snippet of the same name exists on the destination account, the content will not render correctly.

  • Image links are public links and would continue working on the campaign copy but would not be re-uploaded on the destination account.

From and Reply-to

If the same email addresses exist on the destination account, they will applied, otherwise, they will be left as blank on the copy of the campaign.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.