Merge Key Translation Control

Hire now lets admins mark Merge Key rows as translatable. Once flagged, the Translation engine includes those fields in the applicant experience — closing the multilingual gap where merge-field content was previously skipped.

Previously, merge-field content was excluded from Hire's translation engine. Multilingual accounts had gaps where localized flows fell back to the source language for merge fields.

What's new

• New UI control — recruiters/admins can mark Merge Key table rows as translatable directly in the Hire frontend

• Backend translation coverage — flagged Merge Key rows are now processed by the Translation engine, where previously merge-field content was skipped entirely

Why it matters

Merge fields carry a lot of the dynamic content applicants see. Without translatable Merge Keys, multilingual accounts had gaps where localized flows fell back to the source language. This closes that gap for customers using Polyglot or live-translation.

Availability

Available to all Fountain customers.

Customers on select plans may have this feature enabled on a phased basis. Contact your Customer Success team for details.