In Ubeeo ATS, e-mails and merge files can be made more personal and customized by using so-called merge tags.
❗️Please note, always test your adjustments to see if they work as expected before you put an email live.
Mergetags in Ubeeo are dynamic placeholders that are automatically replaced with specific information, such as names, job titles, or contact details. They help simplify personalized communication in emails and other templates without requiring manual data entry. This makes it easier to create a personalized user experience and saves time.
Quickly jump to:
Step-by-step
1. Open an email template or merge file.
2. Replace the text to be retrieved from the database with merge tags.
3. Test the email or file
Which merge tags are available ?
The availability of merge tags depends on the track types to which the e-mail or merge file is called. At Ubeeo ATS, all customer-specific data and the candidate data are available as standard. Vacancy, event, reference or test data are available if they are linked to the track type.
The overview below is not a definitive list of tags, but an overview of the most used tags. Are you missing a tag or are you curious about the possibilities, let us know via the Livechat or send a message to [email protected]
Practical Tips for Using Merge Tags
Test your template with sample data before sending emails or forms to ensure the tags are populated correctly.
Use only the tags essential for your communication to maintain clarity and simplicity.
Refer to Ubeeo's documentation when looking for a complete list of available merge tags and their applications.
Common Problems and Solutions
Problem: The merge tag is not replaced with the expected value. Solution: Ensure that the merge tag is spelled correctly and is compatible with your version of Ubeeo.
Problem: The generated content contains incorrect data. Solution: Check the source data (e.g., the user’s or candidate’s profile) for accuracy and make corrections if needed.
[initials] - initials of the candidate
[first_name] - first name of the candidate
[last_name] - surname of the candidate
[full_name] - full name of the candidate
[mobile_phone] - mobile phone number of the candidate
[work_phone] - fixed telephone number of the candidate
[email_address] - e-mail address of the candidate
[cand_url] - link to the candidate profile (in combination with a button, for example, this becomes [button:green:Go to candidate:var_cand_url] )
Go to Configuration -> Back office -> Processes -> Workflow settings -> Workflow roles.
Add the "Id" column to your overview. This is the ID that you use to retrieve the specific role of the vacancy and what you fill in on the dots below.
[role_..._full_name] - Full name of the relevant user role for the vacancy
[role_..._email_address] - Email address of the relevant user role for the vacancy
[role_..._job_title] - Job title of the relevant user role in the vacancy
[role_..._mobile_phone] - Telephone number of the relevant user role for the vacancy
[job_owner_full_name] - Volledige naam van de vacaturehouder
[job_owner_first_name] - Voornaam van de vacaturehouder
[job_owner_last_name] - Achternaam van de vacaturehouder
[job_owner_email_address] - E-mail adres van de vacaturehouder
[job_owner_job_title] - Functietitel van de vacaturehouder
[job_owner_mobile_phone] - Mobiel nummer van de vacaturehouder
[job_owner_work_phone] - Werk nummer van de vacaturehouder
The user is the person that is taking the action
[users_full_name] - Full name of the user
[users_first_name] - First name of the user
[users_last_name] - Last name of the user
[users_email_address] - E-mail address of the user
[users_job_title] - Job title of the user
[users_mobile_phone] - Mobile phone number of the user
[users_work_phone] - Work phone number of the user
[job_title] - Vacancy title
[refno] - Reference number of the vacancy
[job_id] - Vacancy ID
[org_name] - Name of the organisation
[date_on] - Date online
[date_off] - Date offline
[date_on_intranet] - Date online on intranet
[date_off_intranet] - Date offline intranet
[job_url] - Link to the vacancy
[class:ATTRIBUTEID] . This allows you to return a value from the vacancy.
How to look up: Go to Configuration -> Back office -> Jobs -> Features. Add the Attribute ID column and use that ID instead of the text above. So you get for example [class:23940].
[intvw_date:en:day_full_date] - Full date of the interview
[intvw_time] - Time of the interview
[intvw_location_city] - City where the interview is held
[intvw_location_address1] - Address where the interview will be held
[link:var_intvw_location_google_maps_dir:here] - The Google Map to the address where the interview is held.
[interviewers:0:comma:{users_full_name} ({job_title}):en] – The interviewers involved in the interview. If no positions have been filled in for the users, then ({job_title}) can be removed.
[track_date] - Date of the process step
[track_date:en:full_date] = Date of the process step written in Dutch
[track_reason] = reason for rejection
Italic text: [ft:i:TEXT]
Bold text: [ft:b:TEXT]
[link:https://ubeeo.nl]
[button:{color}:{title}:{url}:{action}]
For example, a green button with the text My candidate portal, linking to the candidate portal:
[button:green:My candidate portal:var_candidate_portal]
Tag |
| Remark |
[job_title] | Vacancy title |
|
[class.IDkenmerk] | Classification | For example: |
[users_full_name] | Vacancy holder full name |
|
[users_job_title] | Job title of vacancy holder |
|
[users_branch] |
|
|
[users_email_address] | Email of vacancy holder |
|
[users_work_phone] | Work phone vacancy holder |
|
[users_mobile_phone] | Cell phone vacancy holder |
|
[org_name] | Organisation name |
|
[org_location_telephone] | Organisation location phone number |
|
[org_location_address1] | Organisation location address |
|
[org_location_address2] | Organisation location address |
|
[org_location_city] | Organisation location city |
|


