The next step in the process is to map the fields from your vendor to your InsideSales.com fields. This process is the same whether the integration is an XML or HTTP post.

You can have multiple mappings for each web vendor in case you have different types of leads coming in from the same vendor. This will be where you will get the posting URL to give to the lead vendor as well.

To add a new mapping you will want to click the Add Mapping button under the lead vendor's integration.

This will take you to the following page.

• Mapping Name: This is the name that you want this mapping to have. If you plan on having multiple mappings under one integration it is best to have as descriptive names as possible.
• Mapping Default Owner: This is the default owner that a lead will be assigned to when it comes in. You can have leads go through a routing rule to automatically assign it to a new owner.

After you have entered the information click save and then it will create the ability to map the fields from your vendor to InsideSales.

• Integration Field: is the field from your lead vendor.
  Note-- STATIC FIELD -- is to setup fields that will never change for this integration such as campaign, lead source, and lead status. We will go over static fields later in this tutorial.
  
• InsideSales Field: The InsideSales fields are all of the lead fields that are in InsideSales.com under your account. This includes all custom and standard fields.

To map the fields simply select the Integration Field and then select the corresponding InsideSales field. If you do not have a corresponding InsideSales field to the Integration field then you will need to create a new field from the Manage Fields/Labels page.

Note:You do not need to map all of the fields that your source is sending over. Any field you do not map will be unretrievable and not put into InsideSales.

The posting URL is displayed in the Field Mapping Information under Post URL:

Static Fields:As mentioned briefly before static fields are fields that will most likely never change in your system such as setting the lead source, which campaign the lead goes into, the lead status when it first enters your system.
Below is a list of all the common static variables that are typically set in the mapping and the ones we suggest you set to static. The "**" next to the InsideSales field are some of the recommended fields to place static data into. If you leave a static field blank our system will by default turn it off.

InsideSales Field	Static Data	Purpose
**ACD Id	Id of the ACD you wish to push the lead to	Queue the lead in an ACD to be called IF there is an available agent.
**Call Now	0 or 1	Setting to 1 will ensure that the lead will be the next lead loaded into the dialer.
**Dialer Initiative Id	Id of your dialer initiative that you wish to have the lead appear in.	Sets the dialer initiative that you would like to have the new lead appear in. If you do not set a dialer initiative id the call will be queued up in all the initiatives and go to the next rep who hits Next Call or Save and Next in the dialer.
**Do Not Notify	0 or 1	If set to 1 the default owner will not receive a notification of the lead being created.
**Duplicate Campaign Id	Id of your duplicate campaign Id	Sends duplicate leads to a certain campaign to help you keep track of your duplicate leads. If you are not worried about capturing duplicate leads this can be left out of the mapping.
**Duplicate Check Basis	email, company, phone, or name	Will perform a duplicate check basis on the fields entered in the static data. The four fields listed are the only fields that you can do a duplicate check on. If you want to check on multiple fields you will need to have them comma separated values such as: phone,email. Setting it as such means that both the phone and email need to match up to a lead in our system for it to be marked as a duplicate.
**Email Template Id	Id of an email template	Will automatically send the specified email template to a lead.
**IVR Id	Id of an IVR	Initiates IVR with lead and given IVR unless inbound_initiative_id is provided AND there is an available agent.
**No HTML for Id Return	0, 1 or 2	Setting to 0 will just return the lead Id in a table format. Setting to 1 will just return the lead Id as plain text. Setting as 2 will send back the ID in XML format.
**Phone Survey Id	Id of the IVR that records a message to your lead.	Will have an IVR call the lead and record their message on the fail over.
**Queue	Number of minutes	Set the number of minutes before a lead appears in an ACD. Must have an ACD Id in the mapping for this to work.
**Redirect Link	URL ex. http://www.insidesales.com	Set the URL where someone will be redirected after they submit their information to your site.
**Relate to Duplicate	0 or 1	Relates the lead to the original if it is marked as a duplicate. Will put - duplicate account: id=12345 days idle=0 in the company name field. This will be the Id of the original lead so you can search on it. You can set it so that if a lead is idle for X amount of days to use the new one and not mark it as a duplicate.
**Reroute if Idle Days	Number of days	Reroute lead if not modified for specifed 'reroute_if_idle_days' days using the routing rule Id.
**Return Lead Id	0 or 1	Returns the lead Id back to the provider as confirmation that the lead has been received. If you have a redirect link it will overwrite the return lead Id.
**Routing Rule Id	Id of the routing rule that you wish to send the lead through	Sends the lead through a routing rule.
The following fields are recommended but do not have the ** next to their name.
Campaign	Campaign Id	Sets the default campaign to put the lead into when it is first created. A common practice is to put the lead into a campaign named after the lead source.
Lead Source	Id of the lead source	Sets the lead source of the lead when it comes into the system.
Lead Status	Id of the lead status	Sets the lead status of the lead when it comes into the system

Previous Step: XML Integration