In Good Grants, the communications sent to your programs users can be personalised through the use of merge fields.
What are merge fields?
Merge fields are system tags which pull information automatically from within a user's profile and/or applications. Merge fields are used to populate messages with personalised information like a user's name, the name of their application, their category selection, and more.
Where can I personalise content?
Merge fields are available in broadcasts, notifications, certificates, and more. They're represented with curly brackets ({}) like those shown below. When the message is sent the merge field is replaced with data. For example, the {account_name} field will be replaced by a the name of your Good Grants program.
What merge fields are available?
There are two different types of merge fields: those that are built into the platform and those that you can customise yourself based on your program's application form or user fields.
Depending on what trigger you've selected in a notification or where you've opted to broadcast from, the available merge fields will change. When you're composing your message they'll appear as clickable links.
To add a merge field, all you need to do is place your cursor where you want the merge field and then click the merge tag you want, it will automatically be placed where your cursor is in the email subject line, email body, or SMS body.
Default merge fields
| Merge field | Definition |
| {account_name} | The name of your Good Grants account. |
| {applicant_first_name} | The first name of an application's submitter. This is pulled from their user profile. |
| {applicant_last_name} | The last name of an application's submitter. This is pulled from their user profile. |
| {recipient_first_name} | The first name of your recipient, whether that be the applicant, a collaborator, reviewer, etc. This is pulled from their user profile. |
| {recipient_last_name} | The last name of your recipient, whether that be the applicant, a collaborator, reviewer, etc. 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. |
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, however, these are subject to the notification trigger type.
Example: Trigger: Application submitted
For this to work you’ll need to replace the 'abcd1234' sample slug with the actual 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. This is the unique ID that references that specific field. If it’s an entry field the merge field in this example will look like this:
{entry_field:YlegNDAo}
If the field is a user field then it will look like this:
{user_field:YlegNDAo}