Christopher Rehn

This feels like a basic standard feature that would benefit us a lot.

My workaround today is adding a tag when the trigger fires, and having that tag as a requirement for "does not exist" upon firing. However, this does not help for Triggers that may need to fire more than once, but not always.

We desperately want this feature, it should be handled similarly to how we are able to build Views.

We often have very similar copy prepared which is sent out to our requester in Triggers. To avoid having to edit multiple Triggers when changing a URL or similar, we utilise DC and call on that DC within multiple triggers.

It has come to my attention Dynamic Content does not support HTML.

How does this limit us?

We are unable to format our email triggers properly when relying on Dynamic Content. For example, any URL included will have to be written out in raw text instead of using Click here!.

Today, the workaround is simply accepting the lack of formatting and design, leaving our Trigger emails looking less professional yet maintaining functionality.

The other option, writing the same string within the Trigger itself and writing the HTML there, would be counterproductive in the grand scheme of things since we operate with a lot of various Triggers and Automations and are also in the process of rebuilding our Customer Experience.

How is this still not a solved issue? We need this.

This is certainly a valid function. As it stands, we've come to the conclusion that any customer data older than X years is unnecessary for us. We would like that data to automatically be deleted after a defined time period.