4
DIsplay Conditions in Emails
Planned
T
The IO Foundation

At times, you need to tweak some of the elements of a template to suite different audiences, for instance a the level of language to address them (Mr. / Your Excellency / Doctor...).

It is very ineffective to create separate Templates for this when the change can be minimal (maintenance can become a nightmare) and it would allow to keep segments down in a more rational manner.

Note: Text is the obvious option although images also make sense.

Comments
S
Slav Ivanov
Aug 30, 2021
Set the status to
Planned
0
S
Slav Ivanov
Aug 30, 2021

We plan to add an UI for this, but until then you can use liquid tags to achieve this: https://shopify.github.io/liquid/tags/control-flow/
For example:
{% if person.industry == "Tech" %}
We would like to invite you to our exclusive community for Tech leaders!
{% elsif person.industry == "Marketing" %}
In the latest news from the marketing world, ...
{% else %}
Hi X!
Got any plans for Friday night?
{% endif %}

2
J
Jean F. Queralt
Aug 30, 2021

Thx, that was really useful. Didn't know about that feature.

0
T
The IO Foundation
Aug 27, 2021

No, that isn't the problem. You are considering one single word when I am talking full paragraphs and language style.

For a regular person:
Dear Mr X,
We are launching our new product coming Friday...

For a person you are familiar with:
Hi X!
Got any plans for Friday night?

For a tech community (generic email address read by someone you can't tell)
Hello.
We would like to invite your community for our coming release on Friday.

For an official representative
To your excellency Mr. X Consul of Neverland
It is our pleasure to extend an invitation on the occasion of our next release on Friday...

As you can see body copies are different, it's not about the Title (or Salutation). You can indeed do this with several templates, the thing is avoiding having to have 4 types (at least) of templates when all the rest remains the same. Updating one common details implies updating all the templates.

2 options I can imagine:

  • Conditional text/properties per object (in the same fashion as you have separate renders per device type)

  • Allow the creation of "subtemplates" collections where you could configure all the common stuff and then include it on your email templates. That way you can customize body copies and have only one place to update common info.

Does that explain better?

0
S
Slav Ivanov
Aug 27, 2021

I'd recommend to keep that information in a custom field for the user. For example, we have a predefined "Title" field for this purpose.

0