Dynamic Text

---

When setting up a third-party integration, in any fields that support Dynamic Text you can enter feedback field names in double curly braces, and they will be replaced with the corresponding value from the feedback.

Eg: If you set a field that supports dynamic text to “{{Category}} feedback from {{Name}}”, and feedback is submitted with the category “Question”, and name “Matt Bearman”, the dynamic text field would be submitted to the third-party service as “Question feedback from Matt Bearman”

All field names are case-insensitive, so the example above would work equally well with “{{caTegOry}} feedback from {{NAME}}”

Missing fields

If a field isn’t submitted as part of the feedback, that placeholder will be removed.

Eg: using the “{{Category}} feedback from {{Name}}” example from before, but the feedback was submitted with the Name of “Matt Bearman”, but a category wasn’t chosen, the dynamic text field would be submitted to the third-party service as “feedback from Matt Bearman”

Escaping

If you need to include double curly braces in a dynamic text, but don’t want them to be replaced with feedback data, you can escape them with an underscore between the opening curly brackets.

Eg: If you set a field that supports dynamic text to “{_{Category}} feedback from {{Name}}”, and feedback is submitted with the category “Question”, and name “Matt Bearman”, the dynamic text field would be submitted to the third-party service as ”{{Category}} feedback from Matt Bearman”

You can also use multiple escapes in the unlikely event you want to include {_{ in a dynamic field. In this situtaion, you would just need to add two underscores between the opening brackets.

You can also add three underscores if you would like to include two in the final data, and so on.