Skip to main content

Field Manager

Manage all lead fields, custom fields, and tags for your team from one centralized workspace.

Overview

Required subscriptions: Available for Event Lead Capture (ELC) teams and Digital Business Card (DBC) teams. Some field access and functionality differ between plans.

Field Manager is a centralized admin experience that allows teams to manage all lead fields used throughout Popl in one place.

This includes:

  • Default fields

  • Custom fields

  • Tags

  • Archived fields

Before Field Manager, teams had no single view of all lead fields across their workspace. This often resulted in:

  • Duplicate custom fields

  • Confusion around enriched data

  • Inconsistent CRM mappings

  • Messy CSV exports

  • Difficulties managing integrations and workflows

Field Manager solves these challenges by creating a structured and standardized system for managing lead data. It also serves as the foundation for future workflow automation and dynamic lead actions that rely on structured field data.

Field Manager Tabs

Field Manager is located within the Leads section of the dashboard and replaces the previous standalone Tags page.

Field Manager includes five tabs:

  1. Default Fields

  2. Custom Fields

  3. Integration Fields

  4. Tags

  5. Archived Fields

Default Fields

Default Fields are Popl system fields used across all teams.

Most Default Fields are populated through enrichment and cannot be edited or deleted by admins.

Admins can:

  • Search fields by name

  • View field details

  • Use fields throughout the platform

  • Alias fields within Event Flows and Lead Capture Forms

ELC Team Access

ELC teams can access:

  • Lead Info fields

  • Company Info fields

  • Metadata fields

Some fields also include a View Field Values option, which displays available values for fields such as:

  • Company Industry

  • Company Type

These values can also be exported to CSV.

DBC Team Access

DBC teams can access:

  • Lead Info fields

  • Metadata fields

DBC teams do not have access to enriched company data fields.

Instead, enriched company fields display an upgrade prompt for Event Lead Capture plans.

Special Default Field Behavior

Full Name

The Full Name field always stores the most complete available name.

When possible, Popl automatically parses and fills:

  • First Name

  • Last Name

All three fields remain available throughout the platform.

Phone Number Fields

Popl automatically classifies phone numbers into categories such as:

  • Mobile

  • Work

  • Office

  • Fax

  • Other

The generic Phone Number field always prioritizes the best available number in the following order:

  1. Mobile

  2. Work

  3. Office

  4. Fax

  5. Other

Teams can also use the specific phone type fields independently if needed.

Custom Fields

Custom Fields are team-created fields used throughout Popl.

These fields can appear in:

  • Qualifiers

  • Lead Capture Forms

  • Event Flows

  • CSV imports

  • CRM integrations

Each custom field displays:

  • Field name

  • Field type

  • Available values for choice-based fields

Available Custom Field Types

ELC teams can create:

  • Free Text

  • Number

  • Single Choice

  • Multi Select

  • Opt-In

  • Upload File

DBC teams can create all field types except Multi Select.

Multi-select fields are limited to Event Lead Capture workflows.

Managing Custom Fields

Admins can:

  • Create custom fields

  • Rename fields

  • Edit field values

  • Archive fields

  • Merge duplicate fields

Editing Fields

Admins can edit:

  • Field names

  • Choice values

Field types cannot be changed after creation.

Before saving updates, Popl displays a confirmation explaining that changes apply across the entire workspace.

Archiving Fields

Archived fields are removed from:

  • Templates

  • Integrations

  • Event Flows

  • Active lead views

The underlying lead data is preserved in the database.

If the field is later unarchived:

  • Historical lead data becomes visible again

Merging Fields

Admins can merge compatible duplicate fields directly from the field options menu.

When fields are merged:

  • Source field data populates the target field only when the target field is empty

  • Existing target field values are never overwritten

  • The source field is archived after the merge completes

Only compatible field types can be merged.

Examples of compatible merges include:

  • Same-type fields

  • Number fields into text fields

Integration Fields

The Integration Fields tab lets admins create combined fields, which merge two or more Popl fields into a single value sent to one field in a connected CRM.

This is useful when a CRM field needs data pulled from multiple Popl fields at once, for example, combining a qualifier notes field with the default Notes field before syncing to the CRM.

Creating a Combined Field

When creating a combined field, admins can:

  • Select two or more source fields (default fields, custom fields, phone number types, or Tags)

  • Set the order the fields appear in

  • Choose whether to include field labels in the output

Steps:

  1. Go to Field Manager > Integration Fields

  2. Click Create Combined Field

  3. Enter a Field Name for the combined field

  4. Under Select fields, click + Add Field to add two or more source fields

  5. Review the Output Preview to confirm the format

  6. Under Advanced Settings, choose whether to include both the field name and field value in the output

  7. Click Create Combined Field

Example: Combining Notes Fields

A team wants every rep's notes on a lead to sync to a single field in their CRM, but they collect notes in two separate fields: Note and Any Other Notes?

To create the combined field:

  1. Go to Field Manager > Integration Fields

  2. Click Create Combined Field

  3. Name the field, e.g., Combined Field 1: Notes

  4. Under Select fields, click + Add Field and add:

    • Note

    • Any Other Notes?

  5. Toggle on Include both the field name and field value in the combined field output so reps can tell the fields apart in the CRM

  6. Check the Output Preview to confirm the format

  7. Click Create Combined Field

Output Preview:

Note: Value; 
Any Other Notes?: Value

If a field is left blank, it's skipped, and only the completed field appears in the output.

Output Format

With field labels included: Field Label: Value; Field Label 2: Value 2
With field labels excluded: Value; Value 2

Scope

Combined fields are used for CRM mapping only. They do not appear in other field pickers across Popl, such as Event Flows, Lead Capture Forms, or CSV imports.

If a source field inside a combined field is archived or merged into another field, the combined field updates automatically to reflect the change.

Tags

The Tags tab contains the same tag functionality previously available on the standalone Tags page.

Admins can:

  • Create tags

  • Rename tags

  • Delete tags

If a tag belongs to a subteam, the subteam name appears next to the tag.

Deleting Tags

Deleting a tag removes it from:

  • Leads

  • Templates

  • Integrations

Tag deletion functions as a soft delete similar to archived fields.

Archived Fields

The Archived Fields tab displays all archived fields.

This gives admins visibility into:

  • Previously removed fields

  • Historical field structure

  • Archived lead data that still exists in the database

Archived fields can be restored at any time.

Resolving Duplicate Fields

Many teams accumulate duplicate fields over time because there was previously no centralized field management system.

Duplicate fields create several issues:

  • Duplicate CSV columns

  • Confusing CRM mappings

  • Difficulty selecting the correct field

  • Sync failures caused by mismatched field types

Field Manager automatically identifies likely duplicates through field name matching.

Duplicate Resolution Flow

Admins can launch a dedicated duplicate resolution workflow inside Field Manager.

Step 1: Select the Primary Field

Admins first choose which field should remain as the primary field.

If one of the duplicates is a Default Field:

  • The Default Field is automatically selected

  • Default Fields cannot be edited or removed

Duplicate Resolution Options

Each duplicate field can then be handled using one of three actions.

Action

Description

Merge

Moves data into the primary field without overwriting existing values, then archives the source field

Rename

Renames the duplicate field and removes the duplicate conflict

Archive

Removes the field from active use while preserving historical lead data

Merge Behavior

Merge is recommended for compatible field types.

During a merge:

  • Empty primary field values are populated from the source field

  • Existing primary field values remain unchanged

  • The source field is archived automatically after completion

Inline tooltips explain this behavior during the merge process.

Rename Behavior

Renaming updates the field everywhere it exists, including:

  • Templates

  • Integrations

  • Event Flows

  • Lead records

Fields can be renamed again later if needed.

Archive Behavior

Archiving removes the field from:

  • Templates

  • Integrations

  • Event Flows

  • Active lead views

Historical data remains stored and can be restored later by unarchiving the field.

Future Duplicate Prevention

Field Manager currently identifies duplicates after fields are created.

Future updates will introduce duplicate detection during field creation to help prevent duplicate fields before they are added to the workspace.

💡 Tip

Need more help? Get support from our team

Chat with us or email us at [email protected]

Related Articles
Did this answer your question?