Privy supports many form field types, which combined with custom field sync can create powerful marketing automation workflows. To see supported marketing services, refer to Syncing custom fields to an ESP.
Text input for the user’s email address. This field is always present and always required unless the phone field is added to replace it.
A first and last name field. This field can be marked required or optional. Currently, its label and name cannot be configured.
Either the Phone field or the email field are required on all campaigns that contain forms. The phone field is for collecting phone numbers in the United States and Canada (+1 country code). When adding this field, an opt-in checkbox will automatically be added as well to opt in to receive sms messaging. You may remove the opt in checkbox if you are not planning to send sms messages to the collected phone number, but if you are sending sms messages the opt in will ensure you remain compliant.
The Text Opt-In field will automatically be added to campaigns where the phone field is added to adhere to marketing text messaging compliance laws. To ensure compliance when sending text messages, this field must be present. If there is no intention to send text messages to collected phone numbers, this field is not required and can be deleted. For more information about email marketing compliance, see our article on Privy Email and SMS marketing compliance.
The Email Opt-In can be added where required depending on whether or not your industry or location requires this level of opt-in to remain complaint for email marketing. For more information about email marketing compliance, see our article on Privy Email and SMS marketing compliance.
A date field for a birthday. This field asks for the day, month, and year parts, but is designed to sync correctly to external services that store birthdays in other formats, such as day/month only.
A text field for a single line of input. This field will be stored and transmitted as text, even if the user enters a numeric value. This field can be marked required or optional.
A dropdown field that asks users to select from a pre-defined set of values. The data stored and transmitted will be the value the user selected. If multiple values are allowed, and the user selects multiple values, they will be stored as a single comma-separated string. This field can be marked required or optional.
A date field asks for the day, month, and year parts. In most cases, this field will be stored and transmitted as text, unless otherwise noted. This field can be marked required or optional.
Multiple Select (Checkboxes) Field
A group of multiple choice fields that asks users to check all boxes that apply. If multiple checkboxes are defined in the group, and the user selects multiple values, they will be stored and transmitted as a single comma-separated string. This field can be marked required or optional.
Single Select (Radio) Field
A group of multiple choice radio inputs. Users must pick exactly one option.
A text field that will be submitted, but not visible to the user.
Hidden fields can be configured to send a predefined value, or a detected attribute (like the user’s current URL or the number of pages they’ve viewed). To send a predefined value, enter it in the Value input. To send a detected attribute, select one from the dropdown.
A label is what is shown to the user. Some fields cannot have their label changed. Some field types like checkboxes have options, each of which also has a label. Labels have no effect on the data that is submitted.
A name determines how the field is identified in Privy, as well as synced to partners. Some fields cannot have their name changed (for example, birthday). Each field in a form must have a unique name.
- Mapping Custom Fields to Your Email Service Provider
- How to Customize Privy Forms
- How to Use Hidden Form Fields and Detected Attributes