Conditions feature relies heavily on the use of Custom fields. If you’re not familiar with the concept, it’s a good idea to start by getting acquainted with them here.

Using Conditions

Conditions is a feature that allows you to differentiate the content of your messages based on the prospects you send them to. An example would be a cadence that would look differently for male and female prospects.
example-cadence

Conditions vs custom fields

Of course, you can achieve this with custom fields. Following the gender example, you can easily create a custom field that will contain “Mrs.” for female prospects and “Mr.” for male prospects and use it in your communication.

However, as you use more words that require inflection by gender (e.g. “she” and “he” or “her” and “him”, etc.) it starts to become quite cumbersome, as you’ll need to create a separate custom field for each of these words.

The easiest way out of this would be to rephrase your messages, by avoiding the gender specific vocabulary. However, in some languages this might be impossible to do.

Conditions

The solution to the issue of gender specific vocabulary in your messages is to use the Conditions feature. It lets you provide alternative blocks of text directly within the cadence, using if/then/else statements. Conditions are made using a simple true/false logic that allows you to control all the alternating words with just one custom field.

A condition statement is made of condition tags surrounding the alternative blocks of text:
{% if is_female %}Mrs.{% else %}Mr.{% endif %}

The whole thing reads as:
If the custom field has a value (is true), then use the text provided ("Mrs."). Otherwise, use the alternative text ("Mr.").

The first tag contains a name of the custom field the Condition refers to. If the custom field has any value for a given prospect, the statement is evaluated as true and the provided text is included. Alternately, if it is empty, the statement is evaluated as false, and the alternative text is used instead.

In this case, we want to provide a value for female prospects. It can be anything, such as “1”, “abc”, or “f”. Alternately, we’re going to leave the custom field empty for male prospects.
custom-field-values

How to use Conditions

  1. In order to use Conditions, you first need to create a custom field that you’ll use to control it. It’s best to name this custom field as “is_something”. It will make it easier to understand when the statement will be evaluated true and when it will be false. Following our example, let’s call it “is_female”.If you’re not sure how to create a new custom field, please refer to the instructions in this article.
  2. Don’t forget to either fill out the new custom field or leave it empty, depending on the prospect’s gender.
    add-custom-field
  3. Next, you’ll need to build the Condition into your cadence. You can insert a template Condition from the dropdown list by clicking Conditions and choosing the if / else option.
  4. Make sure to remove the unnecessary line breaks.
  5. You’ll also need a custom field to base the if statement upon. Replace the “your_field_name” placeholder with the name of the custom field.
  6. Make sure to remove the braces ( “{{“ and “}}” ) surrounding the custom field’s name.
  7. Finally, place the alternative pieces of text between the Condition tags.
    using-conditions

And that’s it! Make sure to test the Conditions you built into your cadence before sending it out to your prospects.

Testing Conditions

The show preview feature will give you a general indication as to whether the Conditions you built into your cadence are working the way you expect them to.
preview-conditions

However, to ensure that they are working properly, test the cadence by sending it as a campaign. Send each and every combination to yourself and your colleagues as prospects to be certain they all work. You’ll find a detailed guide to doing that in this article.

Following our example, we can test the Condition we’ve built in the prior section by importing two prospects into Growbots and sending a campaign to them. We’ll want to make one of the prospects male and one female, by assigning the is_female values accordingly.

Experimenting with Conditions

The example provided in this article showcases the basic use of Conditions, allowing you to easily alternate between two options.

You can make it even simpler, though, by using just the if/then part and omitting the else tag and the alternative block of text. This will create a Condition that will either include or exclude a block of text in your messages, depending on whether the custom field has a value or not. This way, you can refer to a custom field you’re not 100% sure will be available for each and every prospect.
{% if custom_field %}Text referencing to a {{ custom_field }}.{% endif %}

If you have any doubts, feel free to reach out to the Growbots Customer Success team!

Related