What are merge tags?
A merge tag is a placeholder you drop into a landing page or landing page template — the same way you already do with message templates. Once the page is published, it automatically fills in with the matching value from the project, job requisition, or job profile it's tied to: built-in fields like Project Display Name, Location, or Description, or any custom field you've created on requisitions, job profiles, or projects.
This is especially useful if you're managing a high volume of landing pages across multiple teams, brands, or locations, and want your careers content to stay accurate without manual upkeep.
Templates are the recommended route, since the setup is reused across every page built from them. Adding tags to a single landing page works too, but only once that page already has a project attached.
Setting up merge tags
1. Add or confirm your custom fields
If you're already using custom fields, great, you can merge them into your landing pages. If not, you can create new ones under Organization Settings → Custom fields.
Make sure the fields you want to merge into your landing page (e.g. job title, department, location, hiring manager) are already filled in directly on the job requisition, the job profile, or the project.
2. Insert a merge tag into your landing page template or directly into a landing page
In the Landing Page builder, open (or create) a template and use the merge tag option to insert a placeholder wherever you want dynamic content to appear.
For example, in the Hero Block you could add the Projects Display Name merge tag, or in your about the role section, you could insert the Project description merge tag (as seen in the screenshot above), Every landing page (job ad) built from that template will pick up the same merge tags automatically and from the specific project that it's linked to.
You can also add merge tags straight to an individual landing page instead of a template, but only once that page is already linked to a project, otherwise there's no field value for the tag to pull from. This works fine for a one-off page, but since it has to be set up per page, we recommend building merge tags into a landing template wherever possible.
Working with an inserted merge tag
Once a merge tag is in place, you have three handy actions available directly from it:
Preview the text or data that will be inserted - just hover your mouse over the merge tag
Convert to text - turns the merge tag into its plain text value, so it becomes regular editable text instead of a live placeholder. Just click the diagonal down arrow in the bottom right of the merge tag as seen here:
Open related entity - jumps straight to the linked requisition or project, so you can check or update the source field without leaving the page. Just click the merge tag once and on the formatting toolbar select the diagonal up arrow as seen here:
3. Publish the ad
When you publish a landing page, Teamdash pulls in the values from the connected requisition, job profile and project fields and replaces each merge tag automatically.
By default, this uses the value from when the merge tag was first inserted into the landing page, it doesn't automatically pick up a later change to the source field on its own. To confirm you are happy with the data that will be merged in you can use the existing Preview toggle here:
After clicking the Blue Publish button (top right) you still have chance to review before the page goes live. In the Review panel you can choose to:
Automatically use latest field value for merge tags (toggle) - turn this on to have Teamdash check for the latest field value every time you publish, so the merge tag always reflects current data. Leave it off to keep using the original value from when the tag was first inserted.
Sync once - pulls in the current field values a single time, without turning on automatic syncing going forward.
If something needs your attention like a merge tag with no value to pull from, or a landing page that isn't linked to a project yet, the Review step will flag it (e.g. "1 merge tag needs attention" or "Missing related project").
Either way, changes only go live once you hit the green Publish button at the bottom of the Review tab. The public landing page keeps showing its last published content until then.
💡 If you're relying on merge tags to stay current, turn on Automatically use latest field value for merge tags. If you'd rather lock in a value on purpose (e.g. you edited the merged text manually and don't want it overwritten), leave it off.
FAQ
What happens if a custom field is empty?
The Review step flags it and you'll see a notice like "1 merge tag needs attention" — and you won't be able to publish until it's resolved.
Can I still edit the merged text manually after it's inserted?
Yes, use Convert to text diagonal down arrow (or press Tab while the merge tag is selected) to turn it into regular editable text. Once converted, it's static content and won't update again if the source field changes. Until you convert it, it stays a live merge tag.
Does the landing page update automatically if I change a linked field later?
Not by default. A merge tag keeps the value it had when it was first inserted, until you either turn on Automatically use latest field value for merge tags (so it re-checks on every publish) or use Sync once to pull the current value a single time. Either way, the change only appears on the public page once you publish again.