What is it and why is it important?
As an email creator that has access to multiple libraries you sometimes need to repurpose one email from one library to another without the extra work of re-writting all the content, uploading the same images and configuring the same modules multiple times.
In order to do that we have enabled a new functionality that allows users to duplicate one email from one library to another.
What is supported in Stensul?
The process is simple, when having access to multiple libraries you will find inside the email actions a new action that is called “Duplicate to Library” this allows users to repurpose the same email in a different library than where it was created.
This includes also the ability to search in case users have a lot of libraries allowing them to quickly find where they want to duplicate their email to. This applies to Draft emails, templates and finished emails.
To better explain the behavior across this documentation we will use the following therms:
Origin library: The library where the email comes from, original library where the email was created
Origin Email: The email that was duplicated to another library, email where the duplicate to library option was used.
Destination library: Library where the email was cloned to. The one selected in the dropdown of the feature.
Destination email: Email created after duplicating it.
Module Update Notifications
Once the email is duplicated it works the same as when the email was duplicated within the same library. If the duplicated email is related to a template it will still receive the Module Updates only when the template accepts them first. For finished and draft emails the module updates will notify the user when a module was edited as usual.
If when duplicating the email from one library to another there are modules that are not present in the destination library the modules will remain in the email with no notification to the users. It is important to consider this since both libraries can have different modules, the duplicated email will preserve its original content and styles.
Dynamic content
In the event of both libraries having different dynamic content configuration the behavior will be the following:
Destination library and Origin library have the same Dynamic content provider and integration (Same ESP type and instance).
The content of the segments are preserved as well as the logic of the segments
The users still need to push the dynamic content modules to the ESP.
Destination library and Origin library have the same Dynamic content provider but a different BU or instance (In the case of multiple BUs with different API integrations)
The content of the segments are preserved.
The logic of the segments is removed (We can no longer link the data extensions and variables since the id will be different in a different ESP instance).
Destination library and Origin Library have different dynamic content provider.
Content of the segments as well as the logic is removed since each ESP handles logic and order of the segments in a different way.
Variations
In the event of both libraries having different Variations selected.
Variation on the email will remain selected as long as it is present in the destination library.
If the destination library doesn’t have within its options the Original Email library the variation selected will be reverted to the default of the destination library.
URL Tracking
Tracking will match with the destination library, if they share the same configuration across library the tracking set will be preserved, if they have different configuration the tracking will be removed.
Other feature interactions
Language: The Destination Library has different Language settings but the email already created different language versions
When duplicating the email for the first version we will not duplicate the different language options created in the Original Email.
Language: The email has translations.
The translations do not get cloned.
ESP/MAP: The Destination Library has a different ESP/MAP integration configured.
No impact in the duplication since the output is generated afterwards.
Workflows: The Destination library has different workflow tools enabled.
The duplicated email will always be “unlinked” from any workflow started for the Origin Email when duplicating it
Messaging tool: The Destination library has a different messaging tool enabled.
No impact in the duplication
PDF Download, OFT Download, EMLTPL Download
No impact in the duplication.
Preheader, Title or Subject line: The destination library has a the Preheader, Title or Subject line disabled but the Origin library had the title enabled and it has a value in the Original Email.
When cloning the email the value of the title is lost.
Customization requests: Allow customization requests has a different configuration in the destination library:
No impact in the duplication.
Default View: Destination library has a different Default View than the original
Duplicated email will show the default view of the destination library when opened.
Desktop width (px): The width of the destination library is different than the origin library.
The duplicated email will open in the builder with the destination library width
Template BG: The background color of the Destination Library is different from the Origin Library
The duplicated email will open in the builder with the destination library template background
Enable Mobile Settings: The Mobile Settings of the Destination Library are different from the Origin Library
The duplicated email will open in the builder with the destination library Mobile Settings.
External CSS Link: The destination library has a different external CSS link than the origin library
The duplicated email will open in the builder with the External CSS of the destination library.
Color palettes: The destination library doesn’t have color palettes that are used in the modules of the original email
The modules of the duplicated email will only show color palettes that are added to the destination library.
Proprietary styles, Custom Head HTML code: Destination library has different proprietary styles or Custom code than the original library.
Duplicated email will have the Destination library proprietary styles.
Enable prepend/append body: Disabled in the destination library but with content in the Original Email
Remove the option to add content in the prepend/append body in the duplicated email.
Remove any content present in prepend and append body code in the duplicated email.
Personalization tags: A module in the Original Email has personalization tags added that are not present in the destination library
If the personalization tag is already added into the module it will not be removed and it will work as it was set in the Origin Library
The personalization will not show up to be added in the Duplicated Email
Header and Footer Modules: Destination library has a different header or footer module than the Original Email.
The Duplicated email should show the Header and Footer that the destination library has configured. ' " '
How is it enabled?
Users need to have the permission duplicate_email_between_libraries assigned through an existing role.
No feature flag required.
Users need to have access to more than one library to see the feature. Users can only duplicate to libraries they have access to.
Want more help?
Have no fear, your Stensul team is here! Please email us at [email protected].