Using another property as a default value

[DJohnson4]

Hi,

Does anyone know if setting a personalisation token default value as another property is possible?

For example, if I am starting an email with Dear [[Title]] [[Last Name]], I don't always have a value for [[Title]]. So, what I would like to do is force Hubspot to use their first name instead, if the title is missing. I realise the easiest way to do this is probably to use smart rules, but i already have smart rules for something else on this module.

Any advice would be greatly appreciated.

Thanks,

David

[karstenkoehler · Accepted solution]

Hi @DJohnson4,

Here are the options I see:

• Custom code a solution directly in your email template, with the help of a developer.
• Copy the First name into the Title when the Title is unknown. This has the huge disadvantage that you do not know anymore which contact has a valid title or not.
• Create a custom single-line text property Full salutation and hard code the entire full salutation into that; the entire phrase 'Dear Salutation Last Name'. In a contact-based workflow, enroll all contacts, then branch on the different options of title being known / unknown, first and last name being known / unknown. In each branch, you can then use the Set property value action to fill the new Full salutation property with the correct personalization tokens. Again, this would be the entire line of text, hardcoded into one property. You wouldn't have to think about smart rules anymore. If you choose this option, make sure to enable re-enrollment for your workflow so that the Full salutation is updated when a Title becomes known, for example.

Let me know if you have any follow-up questions!

[Jerdaine_digita · Accepted solution]

Yes, it is possible to set a default value for a personalization token using another property. One way to do this is by using the “Fallback” feature in the personalization token settings. This allows you to specify a default value that will be used if the primary token is empty.

Another way to accomplish this is by using a “smart content” module in your email template. Smart content allows you to create different versions of your email based on certain conditions. You can create a condition that checks if the “Title” property is empty and if so, use the “First Name” property as the default value.

In addition to these methods, you can also use the “if-else” statement in the email template code. This allows you to check if the “Title” property has a value, and if not, use the “First Name” property as the default value.

Please note that these are all ways to achieve this, but it's important to test and make sure the solution you choose works as expected in your specific use case.

[karstenkoehler · Accepted solution]

Hi @DJohnson4,

Here are the options I see:

• Custom code a solution directly in your email template, with the help of a developer.
• Copy the First name into the Title when the Title is unknown. This has the huge disadvantage that you do not know anymore which contact has a valid title or not.
• Create a custom single-line text property Full salutation and hard code the entire full salutation into that; the entire phrase 'Dear Salutation Last Name'. In a contact-based workflow, enroll all contacts, then branch on the different options of title being known / unknown, first and last name being known / unknown. In each branch, you can then use the Set property value action to fill the new Full salutation property with the correct personalization tokens. Again, this would be the entire line of text, hardcoded into one property. You wouldn't have to think about smart rules anymore. If you choose this option, make sure to enable re-enrollment for your workflow so that the Full salutation is updated when a Title becomes known, for example.

Let me know if you have any follow-up questions!