Currently, our emails are using content blocks where shared areas like header and footer are called in an email file.

The reason we use content blocks is because if anything changes in these content blocks, we do not have to refresh the emails using these blocks. The change can be published across all emails without needing to refresh.

We want to move to templates but hesitant to go that route since template will have dependent emails and if anything needs to be updated in email template, all dependent emails will need to be refreshed.

1) Is there any way to create dynamic templates where changes can be published to all emails without manual refresh?

2) Which approach is better - keeping content blocks that still needs to be coded each time and called in email files VERSUS template that can be coded once and emails will become WYSIWYG and save coding time?

  • 3
    I see many of your previous questions have good answers, which you haven’t marked as accepted. Accepting answers is a good indicator for others in search of similar solutions, and gives credits to members of this community who volunteer to share their knowledge. Please go through your previous questions, and mark answers as accepted where they provide good replies to your enquiries. Sep 5 at 20:08
  • 1
    Hi @LukasLunow I probably missed, thanks for the call out (I just did).
    – kl2
    Sep 5 at 20:49
  • Thank you, @kuml2 Sep 6 at 14:41

1 Answer 1


I hope I understand you correctly. All emails in SFMC are using templates (unless you build it using pure HTML copy/paste).

You can use templates referencing content blocks (wither in Ampscript using e.g. ContentBlockByKey function) or by dragging ReferenceContent block into the email. Both of these cases will allow you to perform "central" updates which will reflect in all emails referencing that particular block.

But you will not be able to adapt that block in the specific email, as it will be read only. Content referenced by either using ReferenceContent block or ContentBlockByKey is fetched into the email at preview/sendtime, and the changes applied to that block are automatically reflected in all the emails using this block.

Your other option is dragging a content block directly into the email. This will create a copy of this content, allowing you to edit and adapt it in the context of the email. However by doing this, you will obviously miss out on the ability to have central edits of it reflecting in the emails using this content. As by dragging it, you "broke" that relationship.

So it is basically up to you to choose which approach for using content blocks is best for you. Based on experience, it will probably be a mix of both.

  • Thank you Lukas for sharing your feedback. Yes, this is exactly where my head is. I just need some clarification on your last statement "But you will not be able to adapt that block in the specific email, as it will be read only." could you please elaborate on this as I am not sure if I am following? To my knowledge, if we create ContentBlocks and call it by key, I think we can use it / call it by IDs in an email file or a template. I am assuming you are referring to ReferenceContent only- if used it will be local to template only and cannot be called in email files like contentblockbyid?
    – kl2
    Sep 7 at 1:36
  • Hi Lukas, I just wanted to follow up if you got a chance to review my comment / question above? if you have any recommendations?
    – kl2
    Sep 12 at 14:45
  • @kuml2 I provided additional explanation in my answer Sep 13 at 7:13
  • @kuml2 - remember to mark my answer as accepted, if it has been helpful. Otherwise, you are more than welcome to ask clarifying questions. Sep 25 at 9:42
  • Hi Lukas - Yes, done; thank you for the additional explanation, it is helpful!
    – kl2
    Sep 25 at 18:53

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .