Adding Custom Fields

Adding and Configuring Custom Fields in LeadsWithDemos

Adding a new custom field in LeadsWithDemos is a straightforward process that allows you to collect specific information from your leads. Here’s a guide on how to add and customize different types of fields.

By clicking the “Add Custom Field” button, a popup window will appear, allowing you to select the field type. Please note that each field type will have different configurations.

Text (One Line)

This field type is ideal for brief and straightforward responses. When you click on “Add custom field” and select the ‘Text (One Line)’ type, you’ll be directed to configure it as follows:

Field Name

This is the internal identifier for your field. It’s used within LeadsWithDemos for backend management. For instance, if you’re collecting company names, you might name this field “company_name”.

Field Label

Although this label isn’t displayed to leads, it helps in managing and understanding the data you’re collecting. A clear and descriptive label, such as “Company Name,” simplifies data interpretation.

Field placeholder (Help Text)

This section is for additional instructions or clarifications for those handling the data. For example, “Input the official name of the company for internal records.”

Text Box (Multiple Lines)

This field type is suitable for gathering more detailed responses or comments that require extra space. When setting up this field:

Field Name

Choose a name that serves as an internal reference, like “internal_feedback”. This helps in identifying the field in your backend system and is useful for data mapping.

Field Label

Although leads won’t see this label, it’s important for your internal understanding. A label such as “Detailed Feedback” can clearly indicate the kind of information you expect to collect.

Field placeholder (Help Text)

Use this space to guide yourself or your team about the nature of data expected in this field. For instance, “Enter any additional comments or detailed feedback from the lead.”

Email Address

This field type is specifically designed for collecting email addresses. It ensures the data entered is in a valid email format.

Field Name

This should be an internal identifier that clearly denotes the purpose of the field within your system, such as “lead_email_internal.” This name is used for backend organization and data mapping.

Field Label

Although not displayed to leads, this label helps you understand the data being collected. A label like “Lead Email” is clear and concise.

Field placeholder (Help Text)

Use this area to provide any necessary instructions or clarifications for those managing the data. For example, “Enter the lead’s primary email address used for internal tracking.”

Number

Use this field type for collecting numerical data, such as age.

Field Name

Choose an internal name that clearly identifies the purpose of the field within your system, such as “lead_age” This name aids in data organization and backend mapping.

Field Label

This label, though not visible to leads, helps you and your team quickly identify the data type. A label like “Lead Age” is straightforward and descriptive.

Field placeholder (Help Text)

Provide instructions or notes for you in this section, ensuring clarity in data collection. For instance, “Enter the age of the lead. Use whole numbers only.”

Date

This custom field type is specifically for capturing dates, such as a lead’s birthdate.

Field Name

This is your internal identifier for organizing and mapping data. For instance, you might use “date_of_birth” as the field name. This name is key for backend data management and won’t be visible to leads.

Field Label

This label serves as your internal reference. A label like “Lead’s Date of Birth” is clear and effectively communicates the purpose of the field.

Field placeholder (Help Text)

Here, you can add instructions or clarifications for you or your team members who manage the data. An example of helpful instruction might be: “Enter the lead’s date of birth in MM/DD/YYYY format. This information is used for demographic analysis and personalized marketing.”

Dropdown

This field type is ideal for offering a predefined set of options to choose from. It’s useful for gathering standardized responses to specific questions.

Field Name

Consider this as your internal tag for the field, crucial for organizing and mapping data in your backend. For instance, “company_size” could be an appropriate field name. Remember, this name is for your internal use and won’t be visible to leads.

Field Label

This label is what you internally refer to understand the nature of the data. A label like “Company Size” succinctly indicates the purpose of the field.

Options

In this section, you enter the available choices for the dropdown. Each option should be input on a new line for clear separation. For a ‘Company Size’ example, your options could include:

Small (1-10 employees)
Medium (11-50 employees)
Large (51-200 employees)
Enterprise (200+ employees)

Checkbox

This field type allows you to offer multiple selectable options within a single field. It’s particularly useful when you want to gather information on various interests or preferences from your leads.

Field Name

This is an internal identifier for the field. For example, you might use “wordpress_demo_reason_internal” to signify the purpose of the field in your database. The field name is crucial for data mapping and backend organization.

Field Label

This label helps you identify the nature of the data being collected. A label like “Reason for WordPress Product Demo” is clear and helpful, even though it’s not displayed to leads.

Options

This is where you list the selectable choices for the checkbox. Each option should be entered on a new line. For instance, if you’re asking why someone wants a copy of the WordPress Product demo, your options might include:

“To test out features”
“To see if it fits my business needs”
“To experiment with customization options”
“Other”

Hidden

The Hidden field type is used for data that needs to be included with the lead’s information but isn’t directly input by the lead. This field type is valuable for tracking internal data or embedding information that aids in segmenting and managing leads.

Field Name

This is an identifier used internally, like “source_tracker” It’s used for your backend processes and isn’t visible to the leads.

Field Label

While not displayed to leads, this label helps you and your team understand the purpose of the data being collected. For example, “Lead Source.”

Internal Field Text (Help Text)

Here, you can provide guidelines or notes for you or your team regarding the purpose or use of this hidden field. For instance, “This field tracks the original source of the lead, for internal analytics.” This text ensures clarity and consistency in how this hidden field is utilized within your system.

Password

The Password field type is utilized to securely store password information for lead accounts or access to specific sections of your LeadsWithDemos site. It’s essential for maintaining privacy and security.

Field Name

Choose an identifier for backend use, like “lead_password” This name is for your internal database and assists in organizing and managing your data.

Field Label

Though not visible to leads, this label aids in your understanding of the data type. A label such as “Lead Account Password” is clear and helps in identifying the field’s purpose.

Field Placeholder (Help Text)

This section is for providing instructions or important notes to your team managing the data. For example, “Enter the default password for lead accounts, to be changed upon first login.” This helps ensure that the team handling this data understands its confidentiality and proper usage.

Phone Number

This field type is designed to collect phone numbers from leads, ensuring a direct line of communication for follow-ups or personalized engagement.

Field Name

Assign a name for internal use, like “lead_phone_number”, This name is intended for backend organization and helps in data management within your system.

Field Label

While this label is not shown to leads, it aids you in recognizing the kind of data being collected. A label such as “Lead Contact Number” is straightforward and indicates the purpose of the field.

Field Placeholder (Help Text)

Use this space to provide guidance or essential notes to you or your team who handle the data. For example, “Input the lead’s primary contact number for direct outreach.” This instruction ensures that your team understands the importance and intended use of the phone number data collected.

Website

This field type is specifically tailored for collecting web addresses from leads, which can be pivotal in understanding their online presence or business URL.

Field Name

Choose a name that serves as an internal identifier, like “lead_website” This name is used within your system for organization and data management purposes.

Field Label

Although not visible to leads, this label helps clarify the data type being gathered. A straightforward label such as “Lead’s Website” efficiently denotes the purpose of the field.

Field Placeholder (Help Text)

Utilize this section to provide guidelines or important notes for you or your team managing the data. For instance, “Enter the URL of the lead’s business or personal website for reference.” This helps ensure the team comprehends the context and use of the website information being collected from leads.