Skip to main content

Through the API it is possible to update a Template with HTML - which is great because one can have an external tool managing and creating templates.

But if you update a template, there is no way to push that template into the campaigns where it was used. If there was such a thing at strict linking between template and campaign then an update to a template would be immediately pushed to the campaign.

Such a feature would allow endless opportunities for users to work with an outside email builder or template library management system.



Hi David,

Thanks for your input here! There are two sides to this. One is the scenario/use case you've outlined, and the other is where the same base template is used in multiple campaigns as a starting point, and edits/customizations are made to that base on a campaign by campaign basis, and an update to all the campaigns using that base template could be disastrous.. Additionally, when a campaign is created using a template, the version of the template associated with that campaign gets a brand new template id, so that would be a pretty significant overhaul to our campaign creation process.

I could definitely see a use case where on either a project or template basis, a toggle was created where changes to a base template should update all campaigns using it, but that would be a feature request. Just wanted to offer a perspective on why the functionality exists in it's current form as well.

Let me know if you have additional questions!

-Heather

Reply


Terms & ConditionsCookie settings