Salesforce Docs Portal

Capture Visitor Information with the Lead Form Component

After you finish setting up your Guest User profile and configuring the correct object access, navigate to Experience Builder to configure the Lead Form component.

Required Editions

Available in: Enterprise, Performance, Unlimited, and Developer Editions.
User Permissions Needed
To customize or publish an Experience Cloud site:
  • Create and Set Up Experiences AND View Setup and Configuration AND be a member of the site

    OR

  • View Setup and Configuration AND be a member of the site AND have appropriate role-based site access
  1. From your Experience Builder canvas, select the Lead Form component.
  2. Decide which fields you want displayed on your form.
    Note
    Note

    There are several required fields on the Lead object, including Last Name and Company. If you don’t want to display these fields on your form, uncheck Show field and enter a default value.

  3. Choose to display standard fields, like Last Name, and add other Lead fields using the Custom Field sections.
  4. To gather information from the form without displaying the field, use a custom field and under Select an Input Type, choose Hidden.
    Note
    Note We strongly recommend that you avoid collecting and storing sensitive information in a hidden field. It’s possible for users to intercept and potentially change field information during data transfer.

Limitations and Behavior

  • Keep in mind the possible scale of your use case. Microsites have an upper limit of 12,000 concurrent lead form submissions per minute. If you’re worried about exceeding this limit, reach out to your account executive.
  • The Show Field option determines whether a field displays on, and collects information from, the form. In contrast, hidden fields allow you to hide a field but still capture data. If you select Hidden, the form ignores Show field and hides the field.
  • Hidden fields capture the default value, unless you map to a standard field that exists on the form, such as Email. If you map to an existing field with a hidden field and another standard field, the visitor entered data is collected and the default value is ignored.
  • If multiple custom fields map to the same field on the Lead object, the last field collected is the field that is stored in the record. To avoid confusion, we recommend mapping each custom field to a unique field on the Lead object.
  • Certain default values require specific formatting. If you plan to map a custom field to a date, dateTime, multiple picklists, or reference field, use these formatting instructions.
    • Date: 2020-09-07
    • DateTime: 2020-09-07T00:00:00Z
    • MultiplePicklist: A;B;C
    • Reference: Valid ID