Is your feature request related to a problem? Please describe.
In many pages, there are more than 1 form, especially with search form in the header. Checking which form the user interacted with is difficult in those situations. Adding an id (or classname) of the form can help in identifying the form which user have interacted with.
Also the button type of the button element is not present in the selector, especially inside forms. That will help in identifying if a submit button was clicked or not, in cases where users have prevented the default form submit action (leading to non tracking of form submits)
Describe the solution you'd like
Adding id/classnames in the sourceSelector for form tag
Adding buttonType in the button selector for form tag
Describe alternatives you've considered
It is difficult to identify which form the user interacted/submitted with just by looking at the source selector as (form .button).
looking at the source of the page to identify which button was clicked, and that works only if there is 1 button in the form.
kptdobe
commented
2 days ago
Is your feature request related to a problem? Please describe. In many pages, there are more than 1 form, especially with search form in the header. Checking which form the user interacted with is difficult in those situations. Adding an id (or classname) of the form can help in identifying the form which user have interacted with.
Also the button type of the button element is not present in the selector, especially inside forms. That will help in identifying if a submit button was clicked or not, in cases where users have prevented the default form submit action (leading to non tracking of form submits)
Describe the solution you'd like
Describe alternatives you've considered