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

This includes:

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

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 is located within the Leads section of the dashboard and replaces the previous standalone Tags page.

Field Manager includes four tabs:

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:

ELC teams can access:

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

These values can also be exported to CSV.

DBC teams can access:

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

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

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

When possible, Popl automatically parses and fills:

All three fields remain available throughout the platform.

Popl automatically classifies phone numbers into categories such as:

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

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

Custom Fields are team-created fields used throughout Popl.

These fields can appear in:

Each custom field displays:

ELC teams can create:

DBC teams can create all field types except Multi Select.

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

Admins can:

Admins can edit:

Field types cannot be changed after creation.

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

Archived fields are removed from:

The underlying lead data is preserved in the database.

If the field is later unarchived:

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

When fields are merged:

Only compatible field types can be merged.

Examples of compatible merges include:

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

Admins can:

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

Deleting a tag removes it from:

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

The Archived Fields tab displays all archived fields.

This gives admins visibility into:

Archived fields can be restored at any time.

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

Duplicate fields create several issues:

Field Manager automatically identifies likely duplicates through field name matching.

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

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

If one of the duplicates is a Default Field:

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

Merge is recommended for compatible field types.

During a merge:

Inline tooltips explain this behavior during the merge process.

Renaming updates the field everywhere it exists, including:

Fields can be renamed again later if needed.

Archiving removes the field from:

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

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.