Available starting December 10, 2025
When scanning prospective leads onsite at conventions, you can if needed enrich the lead profile based on input provided into the lead qualification form. This might be useful in cases where key information is not initially available when scanning a lead. The entire/complete profile can later be synchronized to the integrated CRM.
One example could be to capture the country of the prospect, save it into the relevant prospect “country” metadata, and then synchronize the complete profile of the prospect with an integrated CRM.
To do so, we will edit the “Choose your country” form component in the lead qualification form, in the Advanced options, so that the “Value key” now contains the following fp_leadprofilefield_country:
By doing this, we are telling the form component to populate the “country” prospect metadata with the captured information, when saving the form. By populating the prospect’s country via the form, this data will in-turn be synchronized to any configured integration.
Important: The form component and the linked prospect metadata must use the same field type to ensure that the prospect metadata can be populated successfully.
Please see below the supported matching field types for the form components and the prospect metadata:
| Form component | = | Prospect meta data type |
| textinput | Text | |
| textinput (email validation) | Text OR email | |
| Country selector | Text (or default country metadata field) | |
| Choice - Multiple answers (check boxes) - 1 option. (use-case: consent capture) | Bool | |
| Choice - Single answer (radio buttons), with 3 options. | Choice | |
| Choice - Multiple answers | List | |
| Choice - Dropdown | Choice list OR text |
Note: Please make sure that the user profiles do not have any mandatory fields that are empty, as this will prevent the metadata from being updated based on the form input.
Technical notes:
- Updating a lead qualification form data after a CRM synchronization will update the prospect metadata data. A new synchronization will be needed to import the updated data in the integrated CRM.
- When using OCR scanning the profile data will be updated once you convert a draft lead to a profile by mapping the captured text.
- If you scan and complete a lead qualification form for a prospect created by another representative, the prospect metadata will not be updated.
- If you rescan a prospect that you had already captured, the prospect metadata will be updated.
Consent and communications use case
Another use case for this can be for congresses, where communications to HCPs often include promotional or scientific information.
Regulations require that companies contact only HCPs who have agreed to receive this type of communication, especially when it may involve promotional material or follow up.
For this reason, during the lead scanning process the device is given to the HCP asking them to agree (give consent) to receive communications. When they do, this would then be stored against the lead profile which will then be used to synchronize (or not if no consent was given) to their CRM.
Comments
0 comments
Please sign in to leave a comment.