Copying Resources

This feature:

Copies resources if they do not exist on the target instance.
Updates only the parent resource if the parent and dependent resources exist on the target instance. Original and copied resource items have the same name and creation date.
For example, if a Segment having a Visited a Specific Landing Page filter for a landing page is copied from one instance to another, the Segment and the landing page used in the segment filter is copied to the destination instance. If the Segment already exists in the destination instance, it is updated with any changes from the source instance. If that landing page already exists in the destination instance, it will not be updated with changes from the source instance.

Note

If a copied item exists in the destination instance (identified by the item’s UUID or alias), the system overwrites the existing item with the copied item. To ensure accuracy of the copies, you must create dependent resources in the source instance and copy the resources through the resource copy feature. If you create a resource with the same alias of a different resource of the same type, the destination resource might be overwritten by any copy that references it.

Important

Acquia recommends you to not use the same alias for different resources belonging to the same resource type.

To copy a resource from one instance to another:

Log in to Campaign Factory.
Click Instances.
Click the instance from which you want to copy the resource.
The system displays the Instance Overview page
Locate the Instance Resources section on the right of the page.
Click the Copy icon for the type of resource that you want to copy.
The following Campaign Studio resources are supported:
- Assets
- Builder Presets
- Campaigns
- Categories
- Custom Fields
- Dynamic Web Content
- Emails
- Forms
- Messages
- Notifications
- Landing Pages
- Point Actions
- Point Triggers
- Reports
- Roles
- Segments
- Stages
- Test Messages
In the Copy Resource pop-up window, select one or more resources that you want to copy.
To send the copied resource, select one or more from the following options:
- Accounts: The Campaign Factory account to which the current logged-in user has access.
  Resources are copied to all the instances associated with the selected accounts.
- Tags: The tags associated with the instances to which the current logged-in user has access.
  Resources are copied to all the instances associated with the selected tag.
- Destination instance: The destination instance to which you want to send the copied resource.
  Resources are copied to all the instances that are explicitly selected.

Resource copy scenarios

If you have a segment email that embeds a landing page, a global token, and an asset, and you want to copy the email over to other Campaign Studio instances, you can resource copy the email.

For the first time copy, all dependencies are copied.
For a subsequent copy, only the top-level entity and tightly-coupled entities are copied.

In this example scenario:

Dependencies refer to the landing page, global token, and asset.
Top-level or main entity refers to the email.
Tightly-coupled entities refer to segment, segment filters, campaigns, and campaign events.

Scenario	Expected
Create a dependent resource in the source and destination with the same alias. Copy the parent resource.	Only the parent resource should be copied once the parent entity exists in the destination.
Create a dependent resource in the source and destination with the same alias. Copy the parent resource. Edit the parent resource in the source. Copy the parent resource again.	Updates in the parent resource should be copied.
Create a dependent resource in the source. Copy the resource to the destination. Copy the parent resource that uses this resource.	The parent resource should be copied successfully.
Create a dependent resource in the source. Copy the resource to the destination. Copy the parent resource that uses this resource. Edit the parent resource. Copy the parent resource again.	Updates in the parent resource should be copied.
Create a dependent resource in the source and destination with the same alias. Copy the parent resource. Edit the dependent resource in the source. Copy the parent resource again.	The parent resource should be copied and the dependent resource should show no change.

This feature:

Copies resources if they do not exist on the target instance.
Updates only the parent resource if the parent and dependent resources exist on the target instance. Original and copied resource items have the same name and creation date.
For example, if a Segment having a Visited a Specific Landing Page filter for a landing page is copied from one instance to another, the Segment and the landing page used in the segment filter is copied to the destination instance. If the Segment already exists in the destination instance, it is updated with any changes from the source instance. If that landing page already exists in the destination instance, it will not be updated with changes from the source instance.

Note

Important

Acquia recommends you to not use the same alias for different resources belonging to the same resource type.

To copy a resource from one instance to another:

Log in to Campaign Factory.
Click Instances.
Click the instance from which you want to copy the resource.
The system displays the Instance Overview page
Locate the Instance Resources section on the right of the page.
Click the Copy icon for the type of resource that you want to copy.
The following Campaign Studio resources are supported:
- Assets
- Builder Presets
- Campaigns
- Categories
- Custom Fields
- Dynamic Web Content
- Emails
- Forms
- Messages
- Notifications
- Landing Pages
- Point Actions
- Point Triggers
- Reports
- Roles
- Segments
- Stages
- Test Messages
In the Copy Resource pop-up window, select one or more resources that you want to copy.
To send the copied resource, select one or more from the following options:
- Accounts: The Campaign Factory account to which the current logged-in user has access.
  Resources are copied to all the instances associated with the selected accounts.
- Tags: The tags associated with the instances to which the current logged-in user has access.
  Resources are copied to all the instances associated with the selected tag.
- Destination instance: The destination instance to which you want to send the copied resource.
  Resources are copied to all the instances that are explicitly selected.

Resource copy scenarios

If you have a segment email that embeds a landing page, a global token, and an asset, and you want to copy the email over to other Campaign Studio instances, you can resource copy the email.

For the first time copy, all dependencies are copied.
For a subsequent copy, only the top-level entity and tightly-coupled entities are copied.

In this example scenario:

Dependencies refer to the landing page, global token, and asset.
Top-level or main entity refers to the email.
Tightly-coupled entities refer to segment, segment filters, campaigns, and campaign events.

Scenario	Expected
Create a dependent resource in the source and destination with the same alias. Copy the parent resource.	Only the parent resource should be copied once the parent entity exists in the destination.
Create a dependent resource in the source and destination with the same alias. Copy the parent resource. Edit the parent resource in the source. Copy the parent resource again.	Updates in the parent resource should be copied.
Create a dependent resource in the source. Copy the resource to the destination. Copy the parent resource that uses this resource.	The parent resource should be copied successfully.
Create a dependent resource in the source. Copy the resource to the destination. Copy the parent resource that uses this resource. Edit the parent resource. Copy the parent resource again.	Updates in the parent resource should be copied.
Create a dependent resource in the source and destination with the same alias. Copy the parent resource. Edit the dependent resource in the source. Copy the parent resource again.	The parent resource should be copied and the dependent resource should show no change.

This feature:

Copies resources if they do not exist on the target instance.
Updates only the parent resource if the parent and dependent resources exist on the target instance. Original and copied resource items have the same name and creation date.
For example, if a Segment having a Visited a Specific Landing Page filter for a landing page is copied from one instance to another, the Segment and the landing page used in the segment filter is copied to the destination instance. If the Segment already exists in the destination instance, it is updated with any changes from the source instance. If that landing page already exists in the destination instance, it will not be updated with changes from the source instance.

Note

Important

Acquia recommends you to not use the same alias for different resources belonging to the same resource type.

To copy a resource from one instance to another:

Log in to Campaign Factory.
Click Instances.
Click the instance from which you want to copy the resource.
The system displays the Instance Overview page
Locate the Instance Resources section on the right of the page.
Click the Copy icon for the type of resource that you want to copy.
The following Campaign Studio resources are supported:
- Assets
- Builder Presets
- Campaigns
- Categories
- Custom Fields
- Dynamic Web Content
- Emails
- Forms
- Messages
- Notifications
- Landing Pages
- Point Actions
- Point Triggers
- Reports
- Roles
- Segments
- Stages
- Test Messages
In the Copy Resource pop-up window, select one or more resources that you want to copy.
To send the copied resource, select one or more from the following options:
- Accounts: The Campaign Factory account to which the current logged-in user has access.
  Resources are copied to all the instances associated with the selected accounts.
- Tags: The tags associated with the instances to which the current logged-in user has access.
  Resources are copied to all the instances associated with the selected tag.
- Destination instance: The destination instance to which you want to send the copied resource.
  Resources are copied to all the instances that are explicitly selected.

Resource copy scenarios

If you have a segment email that embeds a landing page, a global token, and an asset, and you want to copy the email over to other Campaign Studio instances, you can resource copy the email.

For the first time copy, all dependencies are copied.
For a subsequent copy, only the top-level entity and tightly-coupled entities are copied.

In this example scenario:

Dependencies refer to the landing page, global token, and asset.
Top-level or main entity refers to the email.
Tightly-coupled entities refer to segment, segment filters, campaigns, and campaign events.

Scenario	Expected
Create a dependent resource in the source and destination with the same alias. Copy the parent resource.	Only the parent resource should be copied once the parent entity exists in the destination.
Create a dependent resource in the source and destination with the same alias. Copy the parent resource. Edit the parent resource in the source. Copy the parent resource again.	Updates in the parent resource should be copied.
Create a dependent resource in the source. Copy the resource to the destination. Copy the parent resource that uses this resource.	The parent resource should be copied successfully.
Create a dependent resource in the source. Copy the resource to the destination. Copy the parent resource that uses this resource. Edit the parent resource. Copy the parent resource again.	Updates in the parent resource should be copied.
Create a dependent resource in the source and destination with the same alias. Copy the parent resource. Edit the dependent resource in the source. Copy the parent resource again.	The parent resource should be copied and the dependent resource should show no change.

You can select multiple items to be copied. After you make your initial selection, you can either begin typing or select an option from the drop-down list. To remove a selected item, click the x icon.
A resource is copied to the desired Instance only once during a saved session, regardless of whether the instance is associated multiple times through Accounts and Tags.
To meet processing demands and ensure a correct order of operations, Acquia limits resource copy to a single process per instance. If you initiate the resource copy process during peak hours or initiate multiple copies within a short timeframe, expect it to be completed within 1-2 hours.

Click Save.

The system initiates the copy process and displays a status messages in the user interface. The status messages include the processing status and confirmation of items successfully copied or failed.

If any copy operation fails, you can click the Bell icon in the top-right corner to open the Notifications page to view the details of the copy resource process.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

You can select multiple items to be copied. After you make your initial selection, you can either begin typing or select an option from the drop-down list. To remove a selected item, click the x icon.
A resource is copied to the desired Instance only once during a saved session, regardless of whether the instance is associated multiple times through Accounts and Tags.
To meet processing demands and ensure a correct order of operations, Acquia limits resource copy to a single process per instance. If you initiate the resource copy process during peak hours or initiate multiple copies within a short timeframe, expect it to be completed within 1-2 hours.

Click Save.

The system initiates the copy process and displays a status messages in the user interface. The status messages include the processing status and confirmation of items successfully copied or failed.

If any copy operation fails, you can click the Bell icon in the top-right corner to open the Notifications page to view the details of the copy resource process.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.