Event Tour

Forms

Forms capture information from registrants at the point of registration. Every event has at least one registration form. You can add custom questions — dietary preferences, T-shirt size, session pre-selection, emergency contact — and optionally map any of them directly to a Salesforce field on the Attendee or Contact record.

The Forms tab showing a registration form with standard and custom form elements, and their Salesforce field mappings.
The Forms tab showing a registration form with standard and custom form elements, and their Salesforce field mappings.

Form Types

Form TypeWhen used
Registration FormShown during checkout. Captures attendee information at registration time. Every event requires one.
Session Sign-up FormShown when an attendee selects a session. Can capture session-specific preferences.
Survey FormPost-event survey. Sent via email or displayed after check-in.
Waitlist FormShown when an attendee joins the waitlist. Can capture preferences for when they are promoted.

Form Elements

A form is composed of form elements — individual questions or fields. Each element has a type, a label, and optionally maps to a Salesforce field.

Element TypeDescription
TextSingle-line free text (name, company, etc.)
Long TextMulti-line text (e.g., dietary restrictions, bio)
DropdownSingle selection from a list of options
Multi-selectMultiple selections from a list
CheckboxBoolean yes/no
DateDate picker
File UploadRegistrant uploads a file (e.g., headshot)
Section HeaderNon-interactive label to visually organize the form
Waiver / TermsCheckbox with linked terms text — must be accepted to continue

Mapping to Salesforce Fields

By default, a submitted answer is stored on a Form Submission record linked to the registrant. You can additionally map an individual form element directly to a specific Salesforce field, so the answer is also written straight to that field on submission.

  1. Click a form element to open its settings.
  2. Under 'Salesforce Mapping', select the target object (Attendee, Contact, or Lead) and the target field to enable direct field mapping for that question.
  3. Only fields your SF admin has enabled in Admin > Field Mapping are available.
  4. Save. The mapping is live immediately for new submissions.

PII from form submissions stays in Salesforce

Forge never persists form answers in its own Postgres database. Answers are stored on Salesforce Form Submission records by default, and any question you've explicitly mapped is also written straight to the target field on Contact/Attendee. The conference360__Form__c record stores only the form definition.

Conditional Logic

Form elements can be shown or hidden based on previous answers. For example: 'If dietary preference = Vegan, show the Allergen Detail field'. Set conditions in the element's 'Show when' settings.

Reusing Forms Across Events

Forms can be cloned and reused. Go to the global Forms zone in the sidebar to see all forms and clone one for a new event. Cloning copies the form structure and field mappings but not the submitted responses.

Salesforce Field Mapping
ForgeSF ObjectSF Field
Form nameconference360__Form__cName
Form typeconference360__Form__cconference360__Type__c
Form element labelconference360__Form_Element__cName
Maps to objectconference360__Form_Element__cconference360__Maps_To_Object__c
Maps to fieldconference360__Form_Element__cconference360__Maps_To_Field__c