eLead Field Mappings

The following tags are officially recognized by the system and are mapped to their own fields on the eLead object. Unrecognized elements are appended to the 'Comments' section of the eLead. Values that are too long are automatically truncated.

Element Notes
FirstName Any text up to 255 characters.
LastName Any text up to 255 characters.
StreetAddress Any text up to 255 characters.
City Any text up to 255 characters.
State Preferably, the two letter state or province abbreviation. The full name can also used, and the system will attempt to convert it to the two letter abbreviation for you.
Zip Any text up to 255 characters.
Email Any text up to 255 characters. Recommend you validate this field before submitting.
Email2 Any text up to 255 characters. Recommend you validate this field before submitting.
Phone1 The system will automatically format this to (xxx) xxx-xxxx.
Phone2 The system will automatically format this to (xxx) xxx-xxxx.
Phone3 The system will automatically format this to (xxx) xxx-xxxx.
Phone1Type Any text up to 255 characters. Usual values are 'Home', 'Mobile', and 'Work', but anything will be accepted.
Phone2Type Any text up to 255 characters. Usual values are 'Home', 'Mobile', and 'Work', but anything will be accepted.
Phone3Type Any text up to 255 characters. Usual values are 'Home', 'Mobile', and 'Work', but anything will be accepted.
Comments Any text up to 32,000 characters.
YearHomeBuilt Any text up to 4 characters.
YearHomePurchased Any text up to 255 characters.
HouseholdIncome Any text up to 255 characters.
HomeValue Any text up to 255 characters.
BestTimeToCall Any text up to 255 characters.
Taker The full name of the person who took the lead that will get populated on the new Lead Source. This has to match exactly with an existing Staff name. I.E. 'John Doe'. If no match is found it will be ignored.
Product Can be a single value or multiple separated values e.g. "Doors;Gutters;Windows." For best results, these values should match up with the 'Components' in your system.
RequestAppontmentDate (yes, RequestAppontment is misspelled - missing the letter "i". If you try to spell it correctly, the value will be placed in comments.) If populated, an Appointment is automatically created in the system with this date. The Appointment will have a special status of ‘Requested’ so they can filtered on easily. Must be in either YYYY-MM-DD or MM/DD/YYYY format.
RequestAppontmentTime (yes, RequestAppontment is misspelled - missing the letter "i". If you try to spell it correctly, the value will be placed in comments.) If ‘RequestAppointmentDate’ is populated, this will further populate the time on that Appointment. Format must be h:mm tt (i.e., '7:30 PM').
Date The date this lead was taken on in either YYYY-MM-DD or MM/DD/YYYY format. Defaults to current date.
Latitude The latitude of the address in decimal format.
Longitude The longitude of the address in decimal format.
Source Defaults to "eLead". This is used with the 'SourceType' to build the Lead Source in the system. If a source is not found in the system based on these two values, it is built automatically.
SourceType Defaults to "Lead Provider". This is used along with the 'Source' field to build the LeadSource in the system. If a source is not found in the system based on these two values, it is built automatically.
CampaignID Used to identify a campaign in an external system
VendorLeadID Used to identify the lead id in an external system
MarketSegment Any text up to 255 characters. If you are using this, you should validate that this matches up to a Market Segment in your system.
Custom_Field__c (See details below!) If you pass in your own custom fields, the system will do it's best to try to convert the value to fit in your field. If the value cannot be converted, it will get added to the comments. For example, if the field is a 'Checkbox' (boolean) passing in the word 'true' would work. But passing the word 'Maybe' would not, so the field name and the value passed in would get added to comments.

Custom fields

If you need to capture some non-standard piece of information for your company, and maintain them in their own field in the database, you can add your own custom fields to the eLeads, Prospects, and Lead Sources. To do this, you will need to add the field to the eLead, and then also to the Prospect and/or Lead Source object. Then you put data in that field through eLeads by using it's API name. For example, instead of using the 'FirstName' value from above, you could also use 'i360__First_Name__c' and get the same result. Note that the field has to have the exact same API name and type on the eLead, Prospect, and/or Lead Source to get copied automatically.

To find the API name of a field:

  1. Log in as the system administrator.
  2. Go to Setup | Create | Objects and click on eLead (It is near the bottom of the page, NOT in alphabetical order.)
  3. Under Custom Fields & Relationships you can see the listing of all the fields along with their API names.

For example, let's say you want to add 'Favorite Color' to your Web-to-Lead form and have it get populated on your eLeads and Prospects . You would:

  1. Add the Favorite Color field to the eLead object with the API name Favorite_Color__c.
  2. Add the Favorite Color field to the Prospect object, again with the API name Favorite_Color__c.
  3. If you are using Web-to-Lead, you would add the following field to your form: <input name="Favorite_Color__c">.
  4. if you are using Email-to-eLead, you would add the following XML field to the email body: <Favorite_Color__c>Blue</Favorite_Color__c>.

Here's a step by step example to add a new field called 'Favorite Color' to your system.

  1. Log in as the system administrator.
  2. Go to Setup | Create | Objects and click on Prospect.
  3. Scroll down to Custom Fields & Relationships and click New.
  4. Under data type select Text and click Next.
  5. In Field Label type 'Favorite Color'. In Length type 255. Click Next.
  6. On the permissions page check all the boxes under Visible and click Next.
  7. Click Save.
  8. Now under Custom Fields & Relationships find the Favorite Color field and copy the API name down somewhere. This is the name that the system looks for when trying to map values sent in to eLeads. It should be Favorite_Color__c if you left it at it's default value in step 5.