Would be great if we had Dynamic Content functionality for emails

Hi,

Yes, this is on our roadmap but may not be available in next two quarters.

Hey there GS! 

Any chance this is scheduled for a release date already :)

Can’t wait for this feature to replace my use of “template versions” and eventually having to break out over multiple programs :) 

Thanks!

Any updates on this?

Keep in mind that you can also use calculated fields to tokenize elements of your template email. Check out the details here: https://support.gainsight.com/SFDC_Edition/Journey_Orchestrator_and_Email_Templates/Programs/Programs%3A_Using_Calculated_Fields#Email_Steps

.Calculated fields or use case statements in your source query.

Hello @kelly 

This is in our roadmap, may not be available in next two quarters.

Checking back on this thread, given the functionalities afforded by the new beta editor. This relates to my recent question about an easier way to re-order the versions of a template. For certain emails, simply having a block (or section) that we could apply variant logic to only show certain blocks if a participant met the requirements would be very useful, and would allow us to send emails without having to send multiple variants.

One big use case for us is an event roundup email sent to a global audience. We would prefer to send different text depending on a user’s region so we only invite them to the webinars they would be most interested in attending, rather than those they wouldn’t be able to attend (middle of the night).

I wanted to follow up on this idea following the beta for the upcoming Email Template Editor. We would love to see conditional statements for dynamic content blocks so we could send emails where the bulk of the content is the same (including the subject line), but depending on certain variables (specific product modules, global region, billing country, webinar attendance status, etc.), a specific block of content (event paragraph, banner, etc.) would either be hidden or visible.

The only way for us to accomplish this right now is by building multiple variants, but that doesn’t allow us to create truly personalized emails with content that matches every possible scenario, so we end up sending emails that are not applicable to a broad swath of our user base. It’s not practical (or an efficient use of time) to create, edit, and map that many variants for our emails.

To @dan_ahrens post: 

Keep in mind that you can also use calculated fields to tokenize elements of your template email. Check out the details here: https://support.gainsight.com/SFDC_Edition/Journey_Orchestrator_and_Email_Templates/Programs/Programs%3A_Using_Calculated_Fields#Email_Steps

Unfortunately tokens can’t replace entire content blocks, which is what we’d be looking to do.

Following up on this thread, as we’re in the midst of a perfect use case for conditional statements with dynamic content blocks in an email template.

Is there any update you can provide on when dynamic content functionality may be available?

We’re in the creation stages of a monthly report, which includes several tokenized fields (number of specific actions taken, seat allocation, etc.) AND two embedded reports (charts). We have four variants, based on certain products the users may have licensed.

While we ARE able to use case expressions for the tokenized fields if there is a null value, we are CANNOT do the same for the embedded reports, and the current visualization if there is no data for a report… doesn’t look great.

Our only option if we want to include the participants who would have an email that didn’t show that “No Data Found” image would be to create a variant that included that logic -- but if we did that, we’d have to create three additional variants for each of the aforementioned variants, so it would look like:

• Variant 1a: organization meets criteria 1
  • 1b: first report has no data
  • 1c: second report has no data
  • 1d: neither report has any data
• Variant 2b… and so on… with 16 total variants

Unfortunately, this would be too much manual edits and mapping of tokens (with too much room for error), so our current best option is to restrict the eligible user list in our query and remove participants for whom either report had a null value.

Ideal scenario

Ideally, we would be able to send this email to the full audience that shows up in our query, and simply have conditional logic statements on a container surrounding the relevant report that excluded it if the associated data had a null value, thereby eliminating the need to either exclude the participant or create and map an additional three template variants per report.