Field Handling for Cloning Campaigns with Related Records
The Clone with Related operation saves campaign field values and relationships to
available asset records. Some fields are altered during the clone process, such as the new
campaign and asset IDs. Some fields can’t be duplicated, and appear blank on the new campaign or
asset records.
Required Editions
Available in: Salesforce Classic and
Lightning Experience
Available in: Salesforce Professional, Enterprise, Performance,
Unlimited, and Developer Editions
Usually, fields on a cloned asset record are copied to the new campaign 1:1. However, some
records handle certain fields differently in the cloned asset records, which are noted in this
table.
Field
What Appears in the Cloned Record
Affected Records
Name
Formatted as “Old Record Name + Date_Time”
All
Campaign
Cloned campaign ID
All
Created At
Time when clone operation created the campaign
All
Updated At
Time when clone operation created the campaign
All
Created By
User who initiated clone operation
All
Updated By
User who initiated clone operation
All
Archive Date
This field is blank
All
Bitly URL
This field is blank
Landing pages, custom redirects, files
Vanity URL
This field is blank
Landing pages, custom redirects, files
Other content fields
URL strings are replaced with the URL of the cloned records, using the primary domain
used with Account Engagement
Landing pages, forms, form handlers, custom redirects, files
Form
Cloned form ID
Landing pages only
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.