Add and configure form fields

Add contact, choice, rating, upload, payment, consent, and layout fields to a Revup form or promotion.

Add and arrange fields

Form fields determine what participants see and what Revup stores.

Open your promotion in the builder and select Form.
In Form Fields, select Search for a field type.
Search for or select the field you want to add.
Open the new field card and configure the available Basic, Validation, and Advanced settings.
Use the drag handle to place the field in the intended order.
Review the field in the form preview.

Changes save automatically as you edit. The settings available in each field card depend on the field type.

Common settings include:

Basic: Label, placeholder, help text, choices, and whether a response is required.
Validation: The error message and field-specific rules such as verification, minimum age, character limits, or accepted values.
Advanced: Field width, field ID, and whether the field is hidden when those options are supported.

Hidden fields

Turn on Hidden Field when a supported field should remain in the form without appearing to participants. This is useful when your site supplies a value instead of asking the participant to enter it. A hidden field is not a security control: someone using browser development tools may still be able to inspect or change its value. Do not use it by itself to prove eligibility, grant access, record consent, store a secret, or determine a prize outcome.

Field-based bonus entries

Turn on Bonus Entries to award the configured Entries to Award when a participant submits a non-empty value for that field. An optional field left blank does not award entries. Show Bonus Entries Badge controls whether the participant sees the amount beside the field; hiding the badge does not disable the award. Test both a completed and skipped response before publishing.

Fields that support multiple copies also show a duplicate control. Use the remove control to delete an optional field. A promotion must always keep at least one primary identifier: Email, Phone, or Unique Identifier.

Primary and additional contact fields

Primary contact fields are marked with a star in the builder. Revup uses them to create and update the participant's contact profile. Email, Phone, and Unique Identifier can each identify a participant. You can remove Email after adding a Phone or Unique Identifier field, but Revup will prevent you from removing the last remaining primary identifier.

Additional contact fields are stored with the form submission but do not create a separate contact profile. Use an Additional field when you need information about someone other than the participant, such as a guest, nominee, parent, shipping recipient, or emergency contact.

Primary contact fields

Field	Best used for	Important settings and behavior
Email	Identifying the participant, sending follow-up messages, and syncing a person to integrations	Supports email verification and allowed or blocked domain lists. It can be removed after Phone or Unique Identifier has been added as another primary identifier.
Name	Collecting the participant's name	A grouped selector that can add Name Title, First Name, Middle Name, Last Name, and Name Suffix fields. Add only the parts you need.
Address	Mailing prizes, confirming a service area, or collecting a participant's address	A grouped selector that can add Address, Address Line 2, City, State, Postal Code, and Country. Address autocomplete can be enabled for the primary street-address field.
Phone	Contacting a participant by phone or supporting SMS workflows	Collects a phone number and supports phone verification when enabled. Use a separate SMS Consent field before sending marketing text messages.
Birthday	Birthday campaigns, age-aware experiences, or collecting a full birthdate	Supports custom date labels, month labels, year limits, and a minimum-age validation rule.
Gender	Collecting a gender response when it is relevant to the experience	Uses a selectable option list that can be customized. Include an appropriate set of choices and ask only when the information will be used.
Unique Identifier	Membership numbers, employee IDs, customer IDs, student IDs, or another organization-specific identifier	Supports a validation pattern and character limit. Explain the expected format in the label or help text.

Consent, access, and security fields

Field	Best used for	Important settings and behavior
CAPTCHA	Reducing automated spam and bot submissions	Presents a verification challenge rather than collecting a response for reporting. The visual theme and error message can be customized.
Official Rules	Requiring a participant to acknowledge the promotion's official rules	Available for promotion types that support official rules. Keep the checkbox unchecked by default so the participant makes an affirmative choice.
Email Consent	Collecting permission for marketing email	When this field is present, Revup sends mapped email data to connected integrations only when the participant checks it. If the field is absent, mapped email data is allowed to sync. Supports custom consent language plus Terms and Privacy links.
SMS Consent	Collecting permission for marketing text messages	When this field is present, Revup sends mapped phone data to connected integrations only when the participant checks it. If the field is absent, mapped phone data is allowed to sync. Supports custom consent language plus Terms and Privacy links.
Age Gate	Preventing people below a configured minimum age from continuing	Appears before the main form fields. Configure the minimum age, date format, labels, continue button, and under-age error message.
Passcodes	Requiring an approved code before accepting an entry or response	Paste up to 1,000 codes at a time or upload larger CSV batches. Codes are single-use by default and can optionally be reusable. Use this for invitation codes, event codes, in-package codes, or other controlled-access campaigns.
Instant Win Code	Determining an Instant Win result from an imported winning or losing code	Available only for Instant Win promotions. It works with the Winning Codes allocation method and is different from the general Passcodes field.

Payment and approval fields

Field	Best used for	Important settings and behavior
Payment	Registration fees, donations, deposits, paid applications, or other form payments	Requires a connected Stripe account. It appears after the other form fields and is not available for Instant Win promotions. Test the complete payment flow before publishing.
Signature	Agreements, acknowledgements, releases, or applications that require a signature	Provides a signature pad where the participant draws a signature. Add clear surrounding language explaining what the signature applies to.

Additional contact fields

Field	Best used for	Important settings and behavior
Additional Email	A guest, nominee, parent, recipient, or secondary contact email	Validates an email address but does not replace the participant's primary Email field or create another contact profile.
Additional Name	A guest, nominee, parent, recipient, or other person's name	A grouped selector for additional name components. Label the fields so participants know whose name to provide.
Additional Address	A shipping recipient, event location, business address, or other non-primary address	A grouped selector for additional address components. It does not replace the participant's primary Address.
Additional Phone	A guest, nominee, emergency contact, or secondary phone number	Validates a phone number but does not replace the participant's primary Phone field.
Additional Birthday	A child, guest, nominee, or other person's birthdate	Supports date labels, year limits, and minimum-age validation. Clearly identify whose birthday is requested.
Additional Gender	A response about a guest, nominee, or another person	Uses a customizable option list and does not replace the participant's primary Gender field.

Questions and response fields

Field	Best used for	Important settings and behavior
Text Input	A short answer such as a company, job title, city, order number, or brief response	Supports a placeholder, help text, character limit, and validation pattern. Use Text Area for longer responses.
Text Area	Comments, explanations, stories, feedback, or other multi-line responses	Supports a placeholder, help text, character limit, and validation pattern. State the expected length or topic in the prompt.
Checkbox	One yes-or-no acknowledgement or optional selection	Can be required or optional and can be checked by default. Use a Consent field instead when collecting email or SMS marketing permission.
Dropdown	Selecting one option from a compact list	Supports a placeholder and custom options. It is useful when displaying every option at once would make the form unnecessarily long.
Multiple Choice	Selecting exactly one answer from visible options	Displays all choices so they can be compared before selection. Use clear, mutually exclusive options whenever possible.
Picture Choice	Choosing one or more products, designs, destinations, styles, or other visual options	Supports images, image aspect settings, randomized order, and optional multiple selection. Use meaningful labels or imagery that remains understandable on mobile.
Multiselect	Selecting more than one answer from a list	Supports a placeholder and custom options. Make it clear that multiple selections are allowed.
Website URL	Collecting a portfolio, social profile, company site, product page, or another web address	Validates the response as a website address. Specify which kind of link you expect.
File Upload	Collecting documents, images, videos, or other files	Configure accepted file types and file-count limits. Contest uploads can also support photo, video, external-video URL, and caption options; contests allow one active upload field.
Date Picker	Appointments, event dates, travel dates, deadlines, or date ranges	Supports a single date or range, date format, placeholder, and help text. State the timezone elsewhere when the meaning of a date depends on it.
Star Rating	Satisfaction, quality, likelihood, or another quick rating	Configure the maximum rating and rating icon. Explain what the lowest and highest ratings mean.
Opinion Scale	A numbered sentiment, effort, likelihood, or agreement score	Configure the minimum and maximum values. Define the meaning of both ends of the scale in the question or help text.
Ranking	Asking people to place products, ideas, features, or preferences in order	Participants drag the options into their preferred order. Configure the options and the labels shown at both ends of the ranking area.

Layout and instructional fields

These fields organize or explain the form. They do not collect a participant response.

Field	Best used for	Important settings and behavior
Heading	Introducing a section or grouping related questions	Configure the heading text, size, and alignment. Use a clear hierarchy rather than making every section equally prominent.
Paragraph	Adding instructions, context, disclosures, or supporting information between fields	Configure the text, size, and alignment. Keep long instructions scannable.
Divider	Visually separating groups of fields	Configure the line style. A divider adds structure but should not replace a descriptive Heading when a new section needs a label.
Media	Adding an image or video within the form	Configure the media, maximum height, label, and width. Make sure the form remains understandable if the media does not load.
Banner	Highlighting an important notice, warning, success message, or informational callout	Configure the banner title, message, and visual type. Reserve banners for information that genuinely needs emphasis.
New Page	Splitting a long form into multiple steps	Creates a page break and supports custom Next and Previous button labels. Group related questions together and avoid creating pages with only one simple field.

Submit button

The Submit Button is always shown after the form fields and is configured separately. You can change its text, width, alignment, and submission-confetti setting. Its colors come from Design → Colors.

Good field design

Ask only for information you will use.
Use one clear question per field.
Use the field's label for the question and help text for extra context or format requirements.
Choose the response type that requires the least effort while still collecting useful data.
Make consent specific and separate from unrelated terms.
Use required fields sparingly.
Keep option lists complete, mutually understandable, and free of overlapping answers.
Preview narrow mobile layouts after changing field width.

Before publishing

Complete the form once on desktop and once on mobile.
Trigger every required-field and validation error you configured.
Confirm conditional or product-specific fields behave as expected.
Check that response labels are understandable in Participants and exports.
Verify any integration field mappings after adding, deleting, or changing fields.

Changing a form does not rewrite earlier submissions. Existing submissions keep the data that was collected when they were submitted.