Call Flow Tagging: Bracketed Tag Keys Now Normalize Correctly
Released: July 23, 2026
Category: Bug
Location: Call Flows → Tagging node; Targets/RTBs → Response tag mapping
What was happening
Tag keys and tag-value placeholders use different syntax, which could lead to malformed configurations.
For example, a user could enter [zip_code] as the tag key when the correct key is zip_code.
Bracket syntax is still valid when a tag is referenced as a value or placeholder.
What’s fixed
Brackets are automatically removed when entered around a tag key—for example, [zip_code] becomes zip_code.
Selecting a tag for the key field inserts the plain tag name.
Selecting a tag for the value field continues to insert the bracketed placeholder.
The same tag-key normalization applies when mapping RTB response values to tags.
Updated helper text makes the difference between key and value syntax clearer.
Impact
Call Flow and RTB tag mappings are less likely to be saved with malformed tag keys.
Existing placeholder behavior for tag values remains intact.