Lead Fields

Feature Snapshot

Summary:
Lead Fields are the individual data points that compose a lead’s profile within your flow, ensuring all submitted information is organized, validated, and, when needed, protected to maintain data quality and compliance.

Key Benefits:

• Provides a structured, database-like model for capturing lead information
• Simplifies data validation, integration mapping, and reporting
• Enables automatic PII protection for sensitive consumer data
• Allows consistency between standard and custom field configurations
• Facilitates dynamic data routing and enhanced decision-making

Typical Use Cases:

• Capturing and storing basic contact information (e.g., first name, email, phone) from web forms or APIs
• Creating custom fields for unique data requirements when standard fields do not suffice
• Validating lead submissions with required versus optional field distinctions
• Protecting consumer PII through built-in masking or encryption features
• Supporting routing, enhancement, and integration steps with consistent field definitions

How Lead Fields Work?

Lead Fields function similarly to columns in a spreadsheet or database, defining exactly what data is captured for each lead. The platform provides numerous pre‑defined (standard) fields complete with built‑in validation and formatting, and also allows for the creation of custom fields when needed. Each field is designated either as required or optional—required fields must contain data for the lead to be processed, while optional fields provide supplemental information without blocking lead acceptance. Additionally, fields that capture consumer PII are automatically safeguarded through data protection features to ensure compliance with privacy standards.

Step‑by‑Step Instructions

Adding or Editing Lead Fields

1. Open Your Flow Editor:
   Log into your ActiveProspect (LeadConduit) account and navigate to the desired flow. Click on the Fields step at the top of the flow editor.

2. Access the Field Management Interface:
   Add/Remove any fields from your Flow with the toggle next to each field name.

3. Select and Configure Fields:

   • Standard Fields: Review the pre‑defined fields (e.g., First Name, Last Name, Phone 1, Email) that come with built‑in format validation.
   • Custom Fields: If additional or specialized data is required, go to Add to Flow > Flow Field. Provide a descriptive name, choose the appropriate data type (such as Text, Number, Date, etc.), and optionally add an example to clarify its purpose.

4. Save Changes:
   Once configured, click Save to commit your changes.

Expected Result:
The flow displays an updated and structured list of Lead Fields. New leads will now include data for the defined fields with required fields enforced and any sensitive information automatically protected.

Validation & Monitoring (optional)

• Test the Setup: Submit a sample lead through your usual lead source or testing tool and verify that all defined fields populate correctly in the lead details.

• Where to Monitor?: Check the Events tab within your account to review the lead’s data and validate that required fields are present, optional fields are processed when available, and any PII protection measures are active.

Best Practices

• Utilize Standard Fields When Possible:
  Standard fields are universally recognized and come with built‑in validations, reducing configuration errors and ensuring seamless integration with enhancement and delivery steps.

• Create Custom Fields Only as Needed:
  Add custom fields when the standard options do not meet your data requirements. Always document the purpose and expected data format for these fields to maintain clarity within your team.

• Enable PII Protection:
  For fields capturing sensitive consumer data (such as email addresses and phone numbers), ensure that PII protection features are activated to mask or encrypt values, safeguarding privacy and compliance.

• Regularly Review and Optimize Field Configurations:
  As your business needs and lead sources evolve, periodically reassess your field definitions and mappings to ensure they remain aligned with consumption, validation, and reporting requirements.

Troubleshooting

Frequently Asked Questions (FAQ)

What are Lead Fields?

Lead Fields are the individual data points—comparable to columns in a spreadsheet—that make up a lead’s profile. They structure the data captured in your flow and ensure consistency in validation, mapping, and reporting.

What is the difference between a required field and an optional field?

A required field must be populated for a lead to be accepted into the flow; if the data is missing, the lead is rejected. An optional field, however, provides additional context or information and will not block processing if left empty.

How do I add new fields or edit existing ones?

Navigate to your flow’s Fields step in the Flow Editor, Add/Remove any fields from your Flow with the toggle next to each field name.

How is consumer PII protected in Lead Fields?

Fields flagged for PII protection are automatically processed using built‑in data protection features such as masking or encryption, ensuring that sensitive consumer information is safeguarded throughout lead processing and reporting.

Why are Lead Fields important?

Lead Fields are crucial for establishing a standardized data model that guarantees accurate lead validation, simplifies integration and mapping, supports data enhancement strategies, and upholds compliance by protecting sensitive information.

Glossary