Good practices with Custom Fields

What is a Field ID?

Each form field has a unique identifier (displayed in blue on the right side of the field title). This identifier is used to name the data you collect.

Concrete example:

• Field title: "What is your company's annual revenue range?"
• Field ID: annual_revenue_range
• In your submissions: You'll see a column called annual_revenue_range with all the responses

Why does it matter?

📊 Data organization

Your Field IDs become the column names in your Submissions page. Clear IDs help you quickly find the information you're looking for.

Example:

• email is easier to identify than field_3
• phone is clearer than short_answer_5
• budget_range is more explicit than dropdown_2

🔗 Integrations and automations

If you connect your form to other tools (via webhook, Zapier, Make, etc.), Field IDs are used to transfer your data.

Webhook example:

{
  "email": "client@example.com",
  "company_name": "Acme Corp",
  "contact_method": "Email",
  "budget_range": "$10,000 - $25,000",
  "message": "Hello, I would like to discuss..."
}

The tools receiving your data will use exactly these names (email, company_name, contact_method) to process the information.

How does it work?

Automatic generation

When you add a field and give it a title, the Field ID is automatically created:

• "What is your preferred method of contact?" becomes → contact_method
• "Tell us about your project requirements" becomes → project_requirements
• "Numéro de téléphone (France)" becomes → telephone

The system automatically removes spaces, accents, and special characters to create a simple identifier.

Automatic duplicate handling

If two fields have the same title, the system automatically adds a number:

• First field "Additional Comments" → additional_comments
• Second field "Additional Comments" → additional_comments_2

This ensures each piece of data has its own unique location.

Best practices

• ✅ Keep them simple
• ✅ Be consistent
• ✅ Think about integrations: If you're connecting a tool that expects phone_number, name your field phone_number
• ✅ Use underscores: company_name not companyName or company-name for better compatibility