Custom lead data refers to any additional data fields you wish to include within your lead lists. This data can be used for tracking and reporting purposes, and it can also be used to provide agents with additional information about their leads.
If you wish to upload a lead list with additional columns that contain extra information about your leads, you’ll be able to identify and map
those additional columns during the lead list upload process. As discussed in Mapping auxiliary lead list data
, one option is to use the auxiliary fields provided by the system.
Another option is to use custom lead data fields to organize and map that lead data. Custom lead data fields allow you to create configurable groups that contain custom fields of your choosing. The custom fields you create here will show up as mapping destinations during the lead list file upload process
. You’ll be able to map
those custom destinations to any additional lead data column in your lead list.
Another option for identifying and mapping additional lead data is to use the Extra Data Mappings setting available during lead list file upload. This option allows you to create new destinations on the fly during list upload.
Essentially, the two methods for creating custom lead data function similarly. They can both be used for additional data mapping, and they can both be tracked, referenced via agent scripts and APIs, and reported on via the system’s analytics options. The biggest difference between using extra data mappings and custom lead data field groups is that extra data mappings are created outside of the group format — they cannot be managed via custom lead data field group settings, and they cannot be used in other campaigns located under the same dial group like custom lead data fields.