Feb 17
Configurable Technical IDs and Metadata for Tally Form Fields
We’re really enjoying using Tally, but we’ve run into a limitation when it comes to automation.Right now, it doesn’t seem possible to define stable, unique identifiers (IDs or metadata) for form elements such as buttons and input fields. As a result, we have to use some fragile workarounds to distinguish elements, for example:
- Duplicating buttons and relying on their copy or position
- Identifying input fields by label text or DOM structure instead of a canonical ID
These approaches tend to break easily when labels, layout, or copy change, which impacts:
- E2E/UI tests (Playwright, Cypress, Selenium, etc.)
- Mapping Tally responses reliably into our internal systems
It would be incredibly helpful if the Tally form builder allowed us to define technical metadata per field, such as a custom ID (e.g. customer_id_input, submit_primary_button) or custom data attributes like:
- data-field-id="customer_id"
- data-role="primary-submit"
- data-automation-id="checkout_email_input"
This could live as an “advanced” option per field and be injected into the rendered HTML.
Thank you in advance!
Pending
HI Ivica, Thanks a lot for the detailed explanation — this is very helpful. To better understand your specific setup, could you please reach out to us via our support form with more technical details about your implementation and constraints? Our team will be happy to take a closer look and explore possible workarounds with you. You can contact us here: https://tally.so/support Looking forward to learning more about your setup.