# Dynamic Content Block data should be saved to mautic instance, not specific email

**URL:** <https://forum.mautic.org/t/dynamic-content-block-data-should-be-saved-to-mautic-instance-not-specific-email/27900>\
**Category:** Ideas and Feature Requests\
**Tags:** email-backend, contacts-and-fields, user-interface\
**Created:** [May 4, 2023, 7:10am UTC](https://forum.mautic.org/t/dynamic-content-block-data-should-be-saved-to-mautic-instance-not-specific-email/27900 "2023-05-04T07:10:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dirk\_s](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/dirk_s/32/748_2.png) [@dirk\_s](https://forum.mautic.org/u/dirk_s)\
**Post date:** [May 4, 2023, 7:10am UTC](https://forum.mautic.org/t/dynamic-content-block-data-should-be-saved-to-mautic-instance-not-specific-email/27900/1 "2023-05-04T07:10:55Z")

</div>

My idea is:

Currently dynamic content setup is saved individually in every email. This means, that it can’t be reused - even if its always the same configuration. It would be better to save it to the general dynamic content table and reuse it from different emails.

I think these groups of people would benefit from this idea:

People who make use of a lot of dynamic content in emails.

Why I think they would benefit from this idea:

Reducing effort, better managability of dynamic content blocks. Reuse existing logic.

Any code or resources to support this idea:

Dynamic content for other use is already using this approach.

Are you willing to work on this idea?:

No Coding, but support to form and shape this idea.

What skills and resources do you need to explore this further?

Dev knowledge - is it feasible to centralize dynamic content this way?

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [May 4, 2023, 7:59am UTC](https://forum.mautic.org/t/dynamic-content-block-data-should-be-saved-to-mautic-instance-not-specific-email/27900/2 "2023-05-04T07:59:29Z")

</div>

Well, this is what Twig Templates do:  
[https://mtcextendee.com/2021/12/06/examples-of-the-best-selling-twig-templates-plugin/](https://mtcextendee.com/2021/12/06/examples-of-the-best-selling-twig-templates-plugin/)

Here is a video (from 2 years ago)

[![](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/5/51db1ba26f5d336615fd6d4bba9e46476e2e1bf9.jpeg "The One With The Dynamic Content For Emails") ](https://www.youtube.com/watch?v=0sY5AfIu2gE)

---

<div class="post-metadata">

**Author:** ![dirk\_s](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/dirk_s/32/748_2.png) [@dirk\_s](https://forum.mautic.org/u/dirk_s)\
**Post date:** [May 4, 2023, 8:54am UTC](https://forum.mautic.org/t/dynamic-content-block-data-should-be-saved-to-mautic-instance-not-specific-email/27900/3 "2023-05-04T08:54:47Z")

</div>

Thanks @joeyk … will check. Regarding the reuse of configured dynamic content setup, would you agree that a centrally managed function (there is dynamic web content already) for dynamic email content would be efficient and user friendly as well?

---

<div class="post-metadata">

**Author:** ![joeyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/joeyk/32/11164_2.png) [@joeyk](https://forum.mautic.org/u/joeyk)\
**Post date:** [May 4, 2023, 11:35am UTC](https://forum.mautic.org/t/dynamic-content-block-data-should-be-saved-to-mautic-instance-not-specific-email/27900/4 "2023-05-04T11:35:33Z")

</div>

I agree, and I think it should be super user friendly.  
At the same time, the sculptors of Mautic are trying to keep the codebase super lean.  
If a plugin and well documented and anone can easily add it, then why not.  
Joey