Loading Leads into Campaigns

This article is going to be covering loading leads into a campaign in ChaseData’s Cloud Software Administrator Portal.

The first thing you have to do is login to the Administrator Portal and click on Data Import then Lead Import over on the left menu.

From here you are going to be brought to the file upload screen which is where you are going to pick from you PC the file that you wish to upload. ( .csv file or text delimited )

You have some options on this screen like showing the amount of rows you would like to preview but by default it is set to 100.

You can tell the uploader that the first row does or does not contain your header information.

If you have any text qualifiers like “ or other. Generally, you would not have to change this setting if you are importing a comma delimited CSV file.

Finally what is the delimiter of your file if not commas by default.

You would click on Select File and choose from your desktop which file we are going to upload and then hit open.

The uploader will come back with a preview of the data you are going to upload and you can hit next to proceed to our next screen which is field mapping.

On the field mapping screen you are going to be presented with all of the options you would need to map your lead information to your campaign.

Note that if our campaign is not using a custom table you will only be able to map just the default fields in the system. (reference custom table article.)

First step is to choose the campaign we are going to load into by clicking on the drop down for Import Destination.

We also have the ability to make this campaign active in all agent skills immediately once we finish the upload but that is an optional choice.

Next would be selecting the subcampaign if any for this batch of records.

Subcampaigns are smaller buckets within a campaign that can be targeted to get called and report on as more specific versions of the campaigns in which they reside. This also helps you manage your leads better in what can be thought of as “lists.”

You have the option of choosing an existing subcampaign or creating a new one or again none at all if you so wish.

Then we have our import options which include:

Using the advanced table or not for this specific campaign you have chosen. If you do have a custom table built to work with your campaign then we do recommend using it (enabled by default).

Next would be checking this lead load against your internal DNC lists if you have any uploaded. If you do not have a DNC list uploaded then typically what this would do is filter any of the leads within your system that your agents have dispositioned as Do Not Call so as you can stay compliant with your customers.

After the DNC check option you will see the Check Against No Call States option. This will prevent any numbers in the states specified in the no call states module from loading.

Note that even if you load these leads in and you have certain states configured the system will not call those leads until that setting has been removed from the Do Not Call States module.

The next setting is going to be to check against duplicates. ChaseData recommends not loading duplicates into the same campaign unless it is necessary. By default the system will check against duplicates across the entire system in all campaigns. However you have the option to select which campaigns the system will check for duplicate phones.

For allow updates please reference our article covering updating leads in campaigns.

In the table below you will see all of the campaign fields to the left and your lead fields to the right.

The system will automatically map your data if they have similar names. You can always click on the field to the immediate right of the campaign field you want to map and choose any one of your lead fields manually. If you leave the field as “select” nothing will be loaded into that field in our system.

One quick tip is to rename your lead fields to match the syntax of your campaign fields for faster importing.

When you have finished with your mapping you can click next and will be brought to the Data Verification screen which is going to show you all of your filtered leads.

You also have the option of exporting those filtered leads out into a .csv file for your local desktop.
 

​
Finally you can hit import and you will be brought to the Imported Data screen which is going to show you how many records were successfully loaded into your campaign.
From there we are finished and you can check your Campaign in the Campaign Create and Manage module or you can use the Search tool to verify your data was loaded into the Campaign and or Subcampaign you intended.

 

• Related Articles

• Updating Leads in Campaigns

  This article is going explain how to use the ChaseData Cloud Based Software Administrator Portal to update leads you have in your campaigns.   Doing this is going to be very similar to importing leads so we will head over to the left menu and choose ...

• Creating and Loading Leads into a Campaign

• Using The Search Module

  The search module is one of the most powerful tools available in your arsenal. Here are some of the things it will allow you to do: Search for records inside all of your campaigns Move records to different campaigns/subcampaigns (as well as creating ...

• Disposition Termination

  Beginning with version 1.40.76 of our admin application users will now have the ability to automatically move a record to a different campaign based on disposition selected by an agent (selected from either the left menu, disposition drop-down or ...

• Feature Update - Skill Priority

  Feature Update Skill Priority We are expanding Skill Priority to include both outbound and inbound calls. This article revisits the Dial priority feature as a whole, including enhancements. Let us first start with the end result of defining a Skill ...