Translate release notes 1.6.0

Release date

• General availability: 20 March 2026

Enhancements

• All matching templates now have parity in how consumer defined settings can be specified, either through the user_settings table or as runtime parameters at request time. Runtime parameters always take precedence over user settings when both are provided.
  • For waterfall_match templates, consumer defined settings can now also be configured via the user_settings table as an alternative to passing them as runtime parameters.
  • For all other templates, consumer-defined settings can now be passed directly as runtime parameters at request time, as an alternative to configuring the user_settings table.
  • For the exact user_settings key values and runtime parameter examples for each template, refer to the Configure the Translate app and Match data with the Translate app.
• All matching templates now support pass-through fields, allowing consumers to include additional fields from their own dataset in the output alongside the matched IDs.
  • Pass-through fields are specified using the c. prefix in the dimensions parameter (e.g. c.my_field).
  • Pass-through fields must be defined as consumer-defined settings (either in the user_settings table or as runtime parameters) and be included as dimensions in the request.
  • Fields defined as settings but omitted from dimensions will not appear in the output for that request.
  • Fields specified as dimensions but not defined as settings will produce an error.
  • For configuration details and examples, refer to Configure the Translate app and Match data with the Translate app.