Currently, there is no mechanism to allow for populating a form field if the form is embedded on a website page via the embed code method. A field can only be populated by passing a parameter as part of a URL and that parameter is not seen by the form.

This limits the utility of having one form being able to be used on several pages with an automation being able to discern which page the form was submitted from.

For example, suppose I have 20 eBooks as lead magnets, and I want to use one form, include an identifier as to which page or eBook as a hidden field populated when the form is embedded or rendered, and then use that in an automation to deliver the eBook. With parameterization, I could have one form and one automation that branches based on the field value. Without parameterization, I need 20 forms and 20 automations.