This article explains the relationship between base templates and campaign templates, and how to identify and edit specific templates to update corresponding campaigns or workflows.
In Iterable, when you import a template or initially create a template from the Templates menu, a "Base Template" is created.
Whenever you choose a template to use in a Blast Campaign, Triggered Campaign or in a Workflow node, a copy of the base template is created into an entirely different template with its own unique template ID. Keeping copies separate is useful to separate metrics for templates that may be used in multiple places in Iterable.
When these copies are created, base templates remain in the base templates folder. The new template associated with a new campaign will be in the corresponding blast, triggered, or workflow folders.
Base Templates are essentially a library where unused templates sit. If there are changes to any tempates that are actually in use by campaigns, you need to go into the Blast/Triggered/Workflows tabs to make those edits:
Each template has a different template id. These ids can be seen in the Templates menu and in the url on the template page:
Note: When you edit a base template, the edits will not carry over to other copies of blast, triggered, and workflow templates.
Templates from Blast/Triggered Campaigns
To edit a template that relates to a specific campaign, go to the campaign page and click on the link of the title of the template:
Templates in Workflows
If the campaign is in a workflow, you can also access the campaign by double-clicking on the campaign email node so that you can edit the template that was created for the workflow: