I am currently using 1 form on a few pages in our website for report downloads. One issue I face is capturing source of form submission for certain web pages. One of the suggestions i found was to use a hidden field in the forms. Im slightly confused on how this can work. For example, since this is 1 form, how do i ensure a hidden field value is dynamic based on the web page? And for reporting, im concerned if it can show source of submission based on this. Appreciate any assistance here.
What would be the use case for this? Are you looking to track form fills that are coming from external sources i.e. (google ads, facebook, etc)? Or are you just looking to see which pages your form fills are occurring on? If it’s the latter, the hidden field method would probably not help.
If you’re looking to set up a tracking link and have that data populate to the contact that converts on the form, I’ll explain how it works here:
Add the field you wish to populate data to, and make it hidden.
Once you have your hidden field set in your form. Take whichever link to your site you are sending traffic to and set some parameters at the end of your link. To do this, at the end of your link add ?{{field_name}}={{field_value}}.
In the example i’m using utm_source which is a common use case for doing this, but you can do this with any text field. For the value you set it after the “=”.
If you want to track multiple fields just add an “&” after this. For example:
/?utm_source=test-source&utm_medium=test-medium
Then when contacts fill out the form the value should be populated based on what you set:
If you are just looking to see what pages your form fills are occuring on, go to forms, pick the form you wish to see the data on and in the performance tab there should be a conversion pages report, and source report that will give you that info. You can also see the “First Conversion” and “Recent Conversion” properties on your contacts and build reports based on that.
If you want to create a form that captures the page its embedded on in a property, you can find two approaches here. Both require tinkering with Javascript:
