Blanchard Exchange allows you to add unique variables to your emails to pull in dynamic content, such as a user’s email address or the name of a project. For example, the ${accesslink} variable included in all Blanchard-provided email templates generates each participant’s unique Blanchard Exchange login link based on the project.
There are two sets of variable lists below: learner communication variables and project team/email recipient communication variables. Learner communication variables apply specifically to learners, while project team/email recipient variables are used when the automated communication feature is leveraged as a notification tool for individuals in either of these target audiences.
Important!: All variables you include must be encapsulated with "${}" to work properly. Example:
Correct: ${accesslink}
Not correct: accesslink
Learner Communication Variables
| NAME | DESCRIPTION | EXAMPLE |
|---|---|---|
| ${accesslink} | An individual's unique link to access their course/content | https://www.blanchardexchange.com/l/pnjz3iP70LUwoXdT4PnE |
| ${orgname} | The name of your organization | Blanchard |
| ${name} | The user's full name (both first and last name) | Ken Blanchard |
| ${firstName} | The user's first name entered into the "First Name" field of Blanchard Exchange. | Ken |
| ${lastName} | The user's last name entered into the "Last Name" field of Blanchard Exchange. | Blanchard |
| ${email} | The user's primary email | ken.blanchard@example.com |
| ${projectAdministrativeName} | The project title (as entered by an Administrator) shown to Learners or Team Members associated with the project. | April 21-23, 2021 - SLII Experience |
| ${projectName} | The Learner Portal course name | The SLII Experience |
| ${projectDescription} | The course description from the course template. | Welcome to The SLII Experience. You will learn a new language for leadership that will help you increase the quality and quantity of conversations you have with your team members, accelerate their development, increase their performance, and support autonomy. Becoming a situational leader will allow you to partner with those you lead, giving them what they need to succeed. |
| ${sliiAppActivationCode} | Contains the SLII App activation code if the product is enable for the project the mail was sent in | "1a2b3c" |
| ${usersite} | A url to the generic login page for Blanchard Exchange (useful for returning users, but it is recommended to primarily use ${accesslink} to generate login URLs to Blanchard Exchange) | https://www.blanchardexchange.com/ |
| ${locale} | The user's preferred locale | en |
| ${userid} | The numerical user id. Can be used for referencing a specific user. | 132819 |
| ${partid} | The participation id. Can be used for referencing a specific user's participation id. | 10921679 |
Project Team/Email Recipient Communication Variables
These variables are specifically used for the Project Team and Email Recipients audiences when sending automated communications. They make it possible to use the automated communications feature as a notification tool.
For example, if you want to send a notification to the project team and/or specific individuals whenever a learner completes an assignment, you can create an automated communication that targets the specific assignment within your rules and then select the Project Team or Email Recipients audiences.
Below is an example of a communication that targets completion of the SLII Challenge and assumes that Step 1 of the automated communication rule is configured to track completion of this assignment. Once a learner completes the assignment, the email is triggered and sent to anyone listed on the project team or anyone listed as an email recipient or external contact. The variables included in the example pull in the learner’s name, email address, project name, and the date and time stamp of completion.
This example can also be used to target other assignments. The SLII Challenge reference in the message would need to be updated to reflect the name of the assignment being tracked, and the automated communication rule should be reviewed to ensure it is monitoring completion of the same assignment.
SUBJECT
${participantName} has completed the SLII ChallengeBODY
${participantName} (${participantEmail}) has completed the SLII Challenge in project ${projectAdministrativeName}.
This completion was recorded on ${datetime.full}.
| NAME | DESCRIPTION | EXAMPLE |
|---|---|---|
| ${projectName} | The Learner Portal course name | The SLII Experience |
| ${projectDescription} | The course description from the course template. | Welcome to The SLII Experience. You will learn a new language for leadership that will help you increase the quality and quantity of conversations you have with your team members, accelerate their development, increase their performance, and support autonomy. Becoming a situational leader will allow you to partner with those you lead, giving them what they need to succeed. |
| ${projectAdministrativeName} | The project title (as entered by an Administrator) shown to Learners or Team Members associated with the project. | April 21-23, 2021 - SLII Experience |
| ${locale} | The user's preferred locale | en |
| ${usersite} | A url to the generic login page for Blanchard Exchange (useful for returning users, but it is recommended to primarily use ${accesslink} to generate login URLs to Blanchard Exchange) | https://www.blanchardexchange.com/ |
| ${orgname} | The name of your organization | The Ken Blanchard Companies |
| ${name} | The recipient's full name (both first and last name) | Scott Blanchard |
| ${firstName} | The recipient's first name entered into the "First Name" field of Blanchard Exchange. | Scott |
| ${lastName} | The recipient's last name entered into the "Last Name" field of Blanchard Exchange. | Blanchard |
| ${userid} | The numerical user id. Can be used for referencing a specific user. | 132819 |
| ${email} | The recipient's primary email | scott.blanchard@example.com |
|
${participantName} |
The participant's full name based on who triggered the communication (both first and last name) |
Ken Blanchard |
|
${participantFirstName} |
The participant's first name (given name) based on who triggered the communication |
Ken |
|
${participantLastName} |
The participant's last name (surname) based on who triggered the communication |
Blanchard |
|
${participantUserid} |
The numerical user id of the participant based on who triggered the communication. Can be used for referencing a specific user. |
132819 |
|
${participantEmail} |
The participant's primary email based on who triggered the communication |
jane.doe@example.com |
|
${date.short} ${date.medium} ${date.long} ${date.full} |
The current date in different date formats. The format is taken from the project |
1/1/19 2019-01-01 Tuesday January 1 2019 |
|
${datetime.short} ${datetime.medium} ${datetime.long} ${datetime.full} |
The current date and time in different date formats. The format is taken from the project |
1/1/19 3:00PM 2019-01-01 15:00 3 o'clock Tuesday January 1 2019 |