The following scenarios help understand why email placeholders fail while applied to an email and how they can be solved.
When are email placeholders most likely to fail?
Email placeholders are most likely to fail in the following scenarios:
Scenario 1
Scenario for failure | Example | What needs to be done? |
When the associated field value is empty, i.e, when the field associated with a particular placeholder does not carry a value. | If a few of your contacts have an empty ‘Mobile’ field, sending a bulk email with the ‘Mobile’ placeholder will result in these contacts receiving an email where there will be null value in place of the placeholder. | Ensure that the fields associated with a placeholder are filled. |
Scenario for failure:
For the territory placeholder to work, the associated field must be filled with values.
Here is how the error appears:
As the associated field does not have a value, the outgoing mail was sent with a blank, replacing the placeholder.
Scenario 2
Scenario for failure | Example | What needs to be done? |
When a special character is used in custom field placeholder, i.e, you have used a special character in your placeholder content.
Note: This limitation is only for the ‘name’ of the custom field and not the value under the custom field. | A placeholder used for the custom field ‘Type of $ payment’ will be void or empty when sent to the recipient. | Remove the special character from the field title before using it as a placeholder in the email. |
Scenario for failure:
The use of a special character in the placeholder will lead to the placeholder being omitted in the sent email.
Here is how the error appears:
The placeholder for owner email has been removed from the outgoing email due to the presence of a special character.
