Tag Casing Standardization
Location: Targets/RTBs, Webhooks, Call Flows, Call Logs, Custom Tags
Release Date: July 2 2026
We standardized tag references across the platform so tag examples, picker inserts, and tag displays now follow a consistent lowercase format.
What changed
Tag references now use a consistent lowercase format across customer-facing UI examples and picker inserts, such as
[caller_id],[state], and[zip_code].Tag picker and preview behavior was normalized so inserted tag references match what users see in the UI.
Call log tag displays now follow the same lowercase convention for tag keys.
Helper text was added where casing could cause confusion, clarifying that tag matching is case-insensitive.
How to use it
Continue using tag placeholders anywhere tags are supported.
Lowercase examples are now the standard display format, but existing uppercase or mixed-case placeholders still resolve normally.
For example,
[state],[STATE], and[State]are treated the same.
Impact
This reduces confusion around whether tag casing matters and gives teams one consistent convention to follow across tag-related workflows.