Can I personalise emails? What are merge fields?
Merge fields are system tags which pull information automatically from within the user profile and/or applications. Merge fields are a great way to populate notifications and more with personalised information like first and last names, application and category name, etc.
Merge fields are available in the following places in Good Grants:
Some merge fields are essential to the successful management of your program. For example, the merge field used in the account confirmation notification - which is sent to new users when they register - contains an important link which allows those users to verify their email address. This step is required to complete registration.
This notification can be seen in the Manage workspace at Settings > Communications > Notifications. The body message for the account confirmation notification looks like this:
The curly brackets {} are merge fields. When the message is sent the merge fields are replaced with data. For example, the {confirmation_url} field will be replaced by a unique confirmation link for new users to click to confirm their account.
When merge fields are available, they will appear as clickable links.
To use the merge field all you need to do is click on the merge tag:
Custom merge fields
You can create custom merge fields from fields you’ve created by using the {application_field:abcd1234} and {user_field:abcd1234} merge fields.
For this option to work you’ll need to replace the abcd1234 with the slug for the field. The slug is the unique ID for each field which can be found at the very end of the URL of that field. To find it, open the Manage workspace, go to Settings > Applications > Fields, and click on any field to open it for editing in your browser. Check the URL in the browser address bar and you’ll see something like this:
https://yourprogram.grantplatform.com/field/YlegNDAo
The eight-character code at the end is the slug. The slug is the unique ID that references that specific field. If it’s an application field, the merge field in this example will look like this: {application_field:YlegNDAo}
If the field is a user field, then it will look like this: {user_field:YlegNDAo}
Default merge fields
Depending on what trigger you've selected, the available merge fields will change. Below you'll find a handful of common merge fields and the information that they pull.
Merge field | Definition |
{account_name} | The name of your Good Grants account. |
{first_name} | The first name of your recipient. This is pulled from their user profile. |
{last_name} | The last name of your recipient. This is pulled from their user profile. |
{application_name} | The name assigned to the recipient's submission. |
{application_slug} | The slug associated with the recipient's submission. Learn more about slugs here: What is a slug? |
{application_local_id} | The ID number of the submission within your program. |
{category} | The category associated with the recipient's submission. |
{account_url} | The URL / web address of your Good Grants account. |
{password_set_url} | Generates a unique link for the recipient to reset their Good Grants password. |