Overview

Required Subscription: Event Lead Capture Plan

A Priority Field sends one CRM field the value from the first Popl field that has data. You pick two or more Popl fields, put them in the order Popl should check, and map the result to a single CRM field.

Priority Fields live on the Integration Fields tab in Field Manager, next to Combined Fields. Where a Combined Field merges several fields into one value, a Priority Field picks one.

Before you start

You need to be a Full Team Admin.
Priority Fields are set up on the web dashboard. There is nothing to configure on mobile.
The fields you want to use need to already exist in Field Manager.
Know which CRM field the result is going to. A Priority Field can only be used in a field mapping.

How Priority Fields Work

Behavior	What It Means
The first filled field wins	Popl checks your fields in order, top to bottom, and sends the value from the first one that has data.
Empty means empty	No value, an empty string, and no selection all count as empty. Zero and false are values and will be sent.
All empty sends nothing	If no field in the list has a value, Popl sends nothing for that mapping. Your CRM field keeps whatever is already in it.
One field type per Priority Field	Every field has to be the same type. Your first pick sets the type, and fields of other types become unavailable.
Two fields minimum	A Priority Field cannot be saved with fewer than two fields selected.
Field mappings only	A Priority Field is selectable wherever you pick a Popl field in a field mapping. It does not appear on the lead record, in CSV exports, or in the mobile app.
Tags are separated with a semicolon	When the fields are tags, multiple tags arrive in your CRM separated by a semicolon, the same as mapping tags directly.

Creating a Priority Field

Go to Leads, then Field Manager, and open the Integration Fields tab.
Click + New Integration Field and choose Priority Field.
Enter a name in Field Name. Popl fills in a default name such as Priority Field 1, which you can replace.
Set your first choice. Click row 1, use Search fields... or the Default and Custom tabs, and pick a field.
1. This pick sets the field type for the whole list.
Set your fallback. Click row 2 and pick a field.
1. Only fields matching the type in row 1 are selectable. The rest are greyed out with a tooltip explaining why.
Add a third field if you want one. Click + Add Field.
1. A trash icon appears on that row so you can remove it.
Reorder by dragging a row. The numbers update as soon as you drop it.
Click Create Priority Field. The button stays unavailable until at least two fields are selected.

Changing the Field Type Later

Editing row 1 lets you pick any field type again, so a wrong first pick can be corrected.

Click row 1 and choose a different field type.
A confirmation appears: "Change field type?" This warns that changing the type clears your other priority fields.
Select Change field to keep your new first field and clear the rows below it, or select Cancel to leave everything as it was.

Mapping a Priority Field to Your CRM

Open the field mapping page for your integration.
Add or edit a mapping and select your Priority Field as the Popl field. It appears in the same list as your other Popl fields.
Choose the CRM field it should fill.
Save your mappings.

Value mappings are set on each field inside the Priority Field, not on the resolved result. If two of your source fields need different value mappings, set them separately.

What to Expect

On the Integration Fields tab, a saved Priority Field shows a Priority label with its fields listed in order.
After a lead syncs, open its Sync Log to see which value was sent to the CRM field.
A lead where every field in the list is empty shows no value for that CRM field, and the CRM record keeps what was there before. That is expected behavior, not a failed sync.
Run a test lead for your integration before your event to confirm the value arrives where you expect.

Troubleshooting

Issue	What to Do
The CRM field is still empty after a sync	Check the lead and confirm at least one field in the list had a value. Popl only sends something when one of them is filled.
A field I want is not selectable	Every field has to match the type of the field in row 1. Change row 1 to that type, or build a second Priority Field for the other type.
Picking a new first field cleared my other rows	Changing the type in row 1 clears the rows below it by design, and a confirmation appears before it happens. Reselect your fallbacks after the change.
I cannot save the Priority Field	Two fields minimum. Fill both rows before clicking Create Priority Field.
The wrong value is reaching my CRM	The order decides which value is sent. Drag the field you want checked first into row 1.

FAQ

Question	Answer
What is the difference between a Priority Field and a Combined Field?	A Combined Field merges several Popl fields into one value. A Priority Field sends one value only, from the first field in your list that has data.
How many fields can one Priority Field hold?	[VERIFY: whether the number of rows is capped]
Can I use a Priority Field in a CSV export?	No. Priority Fields are available in field mappings only.
Can the same Popl field be used in more than one Priority Field?	[VERIFY]
Does anything change for my reps in the mobile app?	No. Setup is on the web dashboard and the resolved value syncs with the lead.
Do members need access?	No. Priority Fields are admin configuration.

💡 Tip

Need more help? Get support from our team
Chat with us or email us at [email protected]