Hi all. We have created an email 2.0 template made up of a series of modules in a newsletter format. We have included every possible module that we would want in an email campaign, with the intention of removing ones we don't need in specific campaigns.
When we clone an email, however, we lose the functionality of being able to drag modules back in.
Is there a way around this? We ideally don't want to have to use the large template in place of cloning, but occasionally need to add modules to cloned emails. Curretly this means we start from scratch.
Hi Sarah Samuels,
This is not the expected behaviour. You should have the ability to drag and drop modules or delete modules just as if it was a brand new email. Who created your template? Do you know if it contains any errors or warnings when you go to approve it in the design studio template library. My guess is that there is some type of minor error that is causing it to behave in that way.
Hi Gerard. Thanks for the reply, i thought that may be the case.
Our digital agency created the templates a while ago, but they are by no means marketo experts.
We don't get any error messages.
Do you know of any marketo template designers/ specialists who could take a look maybe? Or could this be something for Marketo support?
I don't think this is something that Marketo Support typically helps with. A few agencies I know of for template help:
There are a couple of others on launchpoint.marketo.com, but these are the ones that immediately come to mind.
If you're comfortable posting the HTML for the template you're working with, I'd be happy to take a look and see if I can help you thru this.
Here's what I think might be normal to expect of your email 2.0 template:
Could you walk us thru the process you're stepping thru to clone the email, etc. It sounds like you've got a working template if you're able to create a new email and drag new modules in there. From there, are you approving the email, then just cloning that email asset as a new email and the modules tab is no longer active (but it still works in the email you're cloning from)?
Happy to help take a peek at the code or help get you moving in the right direction here, maybe this is something that the community could benefit from as well.
Hi Dave, thanks so much for the detailed response!
I have actually found the problem now. It's because I changed the code in the template prior to cloning it, hence breaking it away from its template. This email was then used as a template for a number of clones!
So I started from scratch, didn't alter the code and cloning now works as normal