Advanced Field Mapping Options

Field mappings in PropFuel connect data from your AMS or integration to contact fields in PropFuel. For most use cases, standard field mapping is all you need — just select the source field from your integration and the destination field in PropFuel, and you're set.

However, there are situations where you need more control over how incoming data is handled. That's where Advanced Mapping Options come in.

Previously, when a field value came back from an integration as a "zero" or "false" value (for example, a checkbox being unchecked or a numeric field set to 0), PropFuel treated that the same as an empty field — meaning it would skip the update entirely. This caused issues in cases like email or SMS opt-in fields: a contact could be opted in (set to 1), but when they opted back out (set to 0), PropFuel wouldn't record the change because it interpreted 0 as "no data."

This has been fixed. Now there is a button in the mapping process for Advanced Mapping Options. Existing field mappings work like they always have (0 values will not overwrite anything), but new field mappings will work as you would expect (0 values will be recorded). If you would like to change an existing mapping, just flip the "When False" setting in the advanced mapping options for that field — but make sure you understand the implications of that change on existing workflows in that account.

1. Navigate to Advanced Settings → Connectors.

2. Open the connector whose field mappings you want to adjust.

3. You'll see your standard field mapping table (AMS field → PropFuel field).

4. Click the Show Advanced Mapping button below the mapping table:

   

This expands the table to reveal four additional columns for each mapped field.

This option lets you change the data type of the incoming value before it's saved to the PropFuel field. The most useful setting here is Boolean, which converts any value into a simple true or false.

When set to Boolean, the logic works like this: if the field has any value at all, it is saved as true. If the field is empty, it is saved as false.

When to use it: This is useful when you want to use a non-consent field to drive opt-in behavior. For example, if you want to opt in every contact who has a phone number on file, you can map the phone number field to an opt-in field and cast it to Boolean. Contacts with a phone number get opted in (true); contacts without one do not (false).

This controls what happens when the integration returns an empty value for a mapped field. There are two options:

• Ignore (default): PropFuel does nothing and leaves the existing field data as-is. This is the default because many organizations use multiple integrations. For example, your AMS may populate all fields while your marketing automation platform only provides name and email. You wouldn't want the empty fields from your marketing platform to overwrite the data already stored from your AMS.

• Delete data: PropFuel clears the existing value from the field when the integration returns it as empty. Use this when you want PropFuel to always reflect exactly what's in the source system — if a value disappears from the AMS record, you want it removed from PropFuel too.

This is the setting that addresses the original issue with 0 and false values. There are two options:

• Do nothing: PropFuel skips the field update when the value is 0 or false. This is the legacy behavior and is the default for any field that was mapped before this update.

• Overwrite data: PropFuel records the value even when it's 0 or false. This is the default for any field mapped after this update.

If you want to update an existing mapping to use the new behavior, simply flip this setting from "Do nothing" to "Overwrite data." Before making this change, review any workflows or campaign logic tied to that field to make sure the updated values won't trigger unexpected actions (like suppressing or unsuppressing contacts).

This option only appears when you have multiple AMS fields mapped to a single PropFuel field. There are two options:

• Concatenate (default): Combines all the mapped field values into one string, separated by a space. This is the standard behavior and works well for fields like full names (first name + last name).

• Coalesce: Returns the first non-empty value from the list of mapped fields and ignores the rest. This is ideal for fields like phone numbers or email addresses where you have multiple options in your AMS but only want the best available one stored in PropFuel.

Example: You map Home Phone, Mobile Phone, Work Phone, and Office Phone to a single Phone field in PropFuel. With Concatenate, you'd get a long string of all four numbers. With Coalesce, PropFuel checks them in order and stores the first one that has a value — giving you one clean phone number.

• For day-to-day use, you don't need to touch the advanced options. Standard field mapping works the same as it always has, and new mappings are already configured with the corrected behavior.

• Existing mappings are not affected. No field behavior has changed for mappings that were already in place. This ensures that campaigns and workflows continue to operate as expected.

• Changing "When False" on an existing mapping may have downstream effects. If a field suddenly starts recording 0 or false values where it previously ignored them, that data change could flow through to workflows, suppression lists, or other campaign logic. Review your account's workflows before flipping this setting.

If you have questions about advanced field mapping or need help adjusting your connector settings, reach out to us at support@propfuel.com!