The following information describes the mapping between Arlo lead fields and Salesforce opportunity fields. Note: Leads are mapped to Salesforce opportunities.
- Supports one way (Arlo to Salesforce), creation only (i.e. no updates), synchronization between Arlo leads and Salesforce opportunities.
- You can choose whether or not all Arlo leads are imported into Salesforce (as opportunities)
|Arlo field name||Salesforce field name||Field Arlo API / Salesforce||Mapping||Description|
|Core fields, i.e. always enabled in Arlo|
|Organisation||Account||Lookup (Account)||Fixed||Standard Salesforce field|
|Key contact 1||Lookup (Contact)||Fixed||Your key contact for the opportunity|
|Owner||Lookup (User)||Fixed||Salesperson who is managing the opportunity. Note: SF separates Users (admin) from Contacts. Where a user with matching email doesn’t exist, a new user is not created, i.e. Users need to be setup in Salesforce first.|
Time (one word)
|CloseDate||DateTime / Date||Fixed||Note 1: If an estimate close date is not recorded in Arlo, today's date will be used and a note will be added in the opportunity explaining this. Note 2: At this stage the actual closed date in Arlo is ignored even if it is available.|
|Topic||Name 2||String (256) / Text (120)||Auto setup||Standard Salesforce field|
|Type||Type 2||Enums / Picklist||Auto setup||Describes the type of opportunity, e.g. New public event, custom enquiry. See Arlo API for list of types. Note: Arlo types will not be added to items in the Salesforce field picklist.|
|Stage||StageName 2||String (32) / Picklist||Auto setup||Sales stage of the opportunity, e.g. "Identified","Validated". Note: Values not already in the SF field picklist will be added as Inactive Picklist Values on the field.|
|Source||LeadSource 2||String (256) / Picklist||Auto setup||Describes where the opportunity was generated, e.g. "Website","Existing client". Note: Arlo options will not be added to items in the Salesforce field picklist.|
|Information||Description 2||Unlimited size /
Long Text Area(32000)
|Auto setup||Background information on the opportunity.|
|Value||Amount 2||Decimal / Currency(16,2)||Auto setup||Estimated value of the opportunity. Note: Currency conversions are not applied.|
|ValueCurrencyCode||Manually setup||Currency of the value|
|ValueIsTaxExclusive||True or False / -||Manually setup||When true, the value includes tax|
|Status||Enum / -||Manually setup||Either "Open", "Closed", or "Archived"|
|Rating||String (32) / -||Manually setup||Describes the likelihood of closer, e.g. "Hot", "Warm", "Cold".|
|Category||String (32) / -||Manually setup||Opportunity classification, e.g. Existing course, New topic idea, Private course, ..|
|Location||String (256) / -||Manually setup||Location of the opportunity, usually the city.|
|Optional fields, i.e. can be enabled/disabled in Arlo|
|Regions||Region 1||Collection / Text (255)||Fixed||List of regions an opportunity is associated with separated by commons, e.g. "AU,NZ,UK". Note: Updates to this field in Salesforce Arlo will not be copied back to Arlo|
|<Custom fields>||Custom fields / -||Custom fields are not currently supported with the Arlo Salesforce integration. Hint: Request new feature|
|Connector fields 4|
|LeadID||Arlo opportunity ID|
|Management page||Arlo management URL 1||
|Fixed||Link that opens record in Arlo’s management platform.|
1 New Salesforce field automatically created with the integration
2 Recommended Salesforce field
3 Required specification for new Salesforce field
4 Details for each Arlo Connector, i.e. Arlo platform connected to Salesforce. Integration supports connecting multiple Arlo platforms to a single Salesforce platform.
5 Arlo field label maybe incorrect
Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
Auto setup = Custom mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
Manually setup = You are required to manually setup the field mapping in Salesforce.
Other articles that may be helpful