The use case is the following:
I have 3 urls which are used in many email content. They are always the same. At the moment they are stored in every data extension that feeds each journey builder that use them. Every time we port from one environment to another one, we have to port the email content and change the dynamic content of the email that use that because the data source name is different.
I would like to use a more efficient way (in terms of time to deploy because the are many emails), what do u suggest to use?
- store them in an ENT data extension
- store them in a shared data extension
- add if else ampscript inside the email content
or what else?
Thank you