You can use the Form Action tag to gather information about visitor interaction with elements in HTML forms. Data collected includes form name or ID, field name or ID, submits, unloads, and resets. Actual visitor-provided data values are not collected.
The Form Action tag is generated automatically for HTML form objects in pages that include the Digital Analytics libraries and tags. There is no manual equivalent of the Form Action tag.
- Key Reports Populated:
- Content (Forms)
Metrics for each tracked form and form element appear in reporting according to the NAME= attribute value of each tracked form. If no NAME= attribute is defined, Digital Analytics uses an available ID= attribute if defined. If neither attribute is defined, the form or form element is reported as Form Name "UNDEFINED". It is possible to see 'undefined' forms reported in combination with defined related form elements, and vice-versa.
It is possible to automatically prefix reported form names (sourced from name= or id= attribute) with the 'Page ID' value set on the hosting page by the Digital Analytics 'PageView' tag. This can assist in identifying which pages forms are submitted from in cases where the same form exists across multiple 'pages'.
- Enabling Form Action 'Page ID' prefixing on a page (cmSetupOther):
<head> <script type="text/javascript" src="//libs.coremetrics.com/eluminate.js"> </script> <script type="text/javascript"> cmSetClientID("69999999",false,"testdata.coremetrics.com","thesite.com"); cmSetupOther({"cm_FormPageID":true}); </script> </head>
- Example: A form previously reported as "paymentinfo" would be reported as two separate forms after enabling Page ID prefixing in two distinct pages: "CHECKOUT:GUEST:BILLING" and "CHECKOUT:REGISTERED:BILLING".
1."CHECKOUT:GUEST:BILLING_paymentinfo" 2."CHECKOUT:REGISTERED:BILLING_paymentinfo"
Comments
0 comments
Article is closed for comments.