The following article describes the mapping behaviour and details for fields on Salesforce records to the corresponding fields on records in Arlo.
- Log in to Salesforce.
- Open the Settings tab.
- Click Arlo to open the plugin settings.
- From the Information section, click Settings.
- Click the Field Mappings heading. Your fields will take a moment to load.
- In the Salesforce field mapping settings, each entity will be displayed with a collapsible section. Click the relevant section (e.g. Contact) to show all active fields for that entity.
- Fixed Arlo fields being mapped to Salesforce for the entity will be displayed.
The Arlo contact fields map with the Salesforce contact fields.
When mapping contacts in Salesforce:
- You have a choice of how fields are mapped to Salesforce.
- Main or core contact fields have default mapping applied, but custom fields do not.
- You must create the custom fields Arlo and in Salesforce and choose the mapping for custom field data to show in Salesforce.
- You must choose the mapping for Arlo to be able to synchronise the data. Any field that is not mapped will not be synchronised.
- You must map Arlo yes/no fields to Salesforce checkbox fields.
- Regions settings (for multi-region platforms) are sent to Salesforce.
Field mapping for contacts
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
Arlo field name / Salesforce field name |
Arlo API field type / Salesforce field type |
Values (if picklist) |
Length / max characters (Arlo API / Salesforce) |
Mapping |
Description |
FirstName / Name |
String / Text |
|
64 / 40 |
Fixed |
Standard Salesforce field |
LastName / Name |
String / Text |
|
64 / 80 |
Fixed |
Standard Salesforce field |
Email / Email |
String / Email |
|
128 |
Fixed |
Standard Salesforce field. |
Organisation / Account |
Lookup (Account) |
|
|
Fixed |
Standard Salesforce field. |
PostalAddress / MailingAddress |
Address / Address |
|
|
Fixed |
Standard Salesforce field. |
PhoneWork / Phone 2 |
String / Phone |
|
128 |
Manually setup |
Recommend mapping to standard Salesforce field. |
PhoneHome / HomePhone 2 |
String / Text |
|
128 |
Manually setup |
Recommend mapping to standard Salesforce field. |
PhoneMobile / MobilePhone 2 |
String / Text |
|
128 |
Manually setup |
Recommend mapping to standard Salesforce field. |
Position / Title 2 |
String / Text |
|
128 |
Manually setup |
Recommend mapping to standard Salesforce field. |
Status |
|
|
|
Manually setup |
Do not recommend mapping. |
CodePrimary |
String |
|
50 |
Manually setup |
A reference code for a contact, e.g. customer number, membership number. |
Department / Department 2 |
String / Text |
|
64 / 80 |
Manually setup |
Recommend mapping to standard Salesforce field. |
Branch |
String |
|
64 |
Manually setup |
Either a) map the field to an existing Salesforce field, or b) create new Salesforce field and map the new field to this field. |
Regions / Region 1 |
Collection / Text |
|
255 |
Fixed |
List of regions a contact is associated with separated by commons, e.g. "AU,NZ,UK". Note: Updates to this field in Salesforce will not be copied back to Arlo. |
Custom fields |
Custom field |
|
|
Manually setup |
Custom fields are supported with the Salesforce integration. |
ContactID / Arlo contact ID |
Integer 3 / - |
|
|
Fixed |
Arlo's unique ID for the contact, e.g. 45 |
UniqueIdentifier / Arlo UniqueIdentifier |
Guid 3 / - |
|
|
Fixed |
Arlo's unique ID for the contact across multiple Arlo platforms. |
Management page / Arlo management URL 1 |
URL |
|
|
Fixed |
Link that opens record in Arlo’s management platform. |
The Arlo newsletter subscriptions fields map with the Salesforce newsletter subscription fields on contacts.
Field mapping for newsletter subscriptions
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
| Arlo field name / Salesforce field name | Arlo API field type / Salesforce field type | Values (if picklist) | Length / max characters (Arlo API / Salesforce) | Mapping | Description |
| NewsletterSubscriber 5 / Newsletter_Subscriber 1 | Boolean / Checkbox | Fixed | Newsletter subscriber flag. Note: Updates to this field in Salesforce will not be copied back to Arlo. |
||
| NewsletterSubscribedTopics 5 / Newsletter_Topics 1 | List / Text | 200 | Fixed | List of newsletter topics contact is interested in separated by common, e.g. "Marketing, Sales". Note: Updates to this field in Salesforce will not be copied back to Arlo. |
The Arlo organisation fields map with the Salesforce account fields.
When mapping organisations in Salesforce:
- You have a choice of how fields are mapped to Salesforce.
- Main or core organisation fields have default mapping applied, but custom fields do not.
- You must create the custom fields Arlo and in Salesforce and choose the mapping for custom field data to show in Salesforce.
- You must choose the mapping for the Arlo to be able to synchronise the data. Any field that is not mapped will not be synchronised.
- You must map Arlo yes/no fields to Salesforce checkbox fields.
- Regions settings (for multi-region platforms) are sent to Salesforce.
Field mapping for organisations
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
| Arlo field name / Salesforce field name | Arlo API field type / Salesforce field type | Values (if picklist) | Length / max characters (Arlo API / Salesforce) | Mapping | Description |
| Name / Name | String / Name | 128 | Fixed | Standard Salesforce field | |
| ParentOrganisation / ParentOrganisation | Lookup (Account) | Fixed | Standard Salesforce field | ||
| ChildOrganisations / ChildOrganisations | Lookup (Account) | Fixed | Standard Salesforce field | ||
| PostalAddress / BillingAddress | Address / Address | Fixed | Standard Salesforce field | ||
| PhysicalAddress / ShippingAddress | Address / Address | Fixed | Standard Salesforce field | ||
| CodePrimary / | String | 50 | Manually setup | Reference codes for an organisation, e.g. customer number, membership number. Either a) map the field to an existing Salesforce field, or b) create new Salesforce field and map the new field to this field. |
|
| CodeSecondary / | String | 50 | Manually setup | ||
| PhonePrimary / Phone 2 | String / Phone | 64 | Manually setup | Recommend mapping to standard Salesforce field | |
| PhoneSecondary / | String | 64 | Manually setup | No recommended mapping. Create a new Salesforce field and map the new field to this field. | |
| WebsiteUrl / Website 2 | String | 256 | Manually setup | Recommend mapping to standard Salesforce field | |
| Status / | Manually setup | Do not recommended mapping. | |||
| Regions / Region 1 | Collection / Text | 255 | Fixed | List of regions an account is associated with separated by commas, e.g. "AU,NZ,UK". Note: Updates to this field in Salesforce will not be copied back to Arlo. |
|
| Custom fields / | Custom fields | Manually setup | Custom fields are supported with the Salesforce integration. | ||
| OrganisationID / Arlo organisation ID | Integer | Fixed | Arlo's unique ID for the organisation, e.g. 45. | ||
| UniqueIdentifier / Arlo UniqueIdentifier | Guid | Fixed | Arlo's unique ID for the organisation across multiple Arlo platforms. | ||
| Management page / Arlo management URL 1 | URL | Fixed | Link that opens the record in Arlo’s management platform. |
The Arlo lead fields map with the Salesforce opportunity fields.
When mapping leads in Salesforce:
- You have a choice of how fields are mapped to Salesforce.
- Main or core lead fields have default mapping applied, but custom fields do not.
- You must create the custom fields Arlo and in Salesforce and choose the mapping for custom field data to show in Salesforce.
- You must choose the mapping for the Arlo to be able to synchronise the data. Any field that is not mapped will not be synchronised.
- You must map Arlo yes/no fields to Salesforce checkbox fields.
Field mapping for leads
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
| Arlo field name / Salesforce field name | Arlo API field type / Salesforce field type | Values (if picklist) | Length / max characters (Arlo API / Salesforce) | Mapping | Description |
| Organisation / Account | Lookup (Account) | Fixed | Standard Salesforce field | ||
| PrimaryContact (Key contact) / Key contact 1 |
Lookup (Contact) | Fixed | Your key contact for the opportunity | ||
| AssignedContact (Assigned to) / Owner |
Lookup (User) | Fixed | Salesperson who is managing the opportunity. Salesforce 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 set up in Salesforce first. | ||
| EstimatedCloseDate Time (one word) / CloseDate |
DateTime / Date | Fixed | 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. At this stage, the actual closed date in Arlo is ignored even if it is available. | ||
| Topic / Name 2 | String / Text | 256 / 120 | Auto setup | Standard Salesforce field | |
| Type / Type 2 | Enums / Picklist Dropdown in Arlo management platform. |
List options need to maintained in Arlo and Salesforce. | Auto setup | Describes the type of opportunity, e.g. New public event, custom enquiry. Note: Arlo types will not be added to items in the Salesforce field picklist. |
|
| Stage / StageName 2 | String / Picklist Dropdown in Arlo management platform. |
List options need to maintained in Arlo and Salesforce. | 32 | Auto setup | Sales stage of the opportunity, e.g. "Identified","Validated". Note: Values not already in the Salesforce field picklist will be added as Inactive Picklist Values for the field. |
| Source / LeadSource 2 | String / Picklist Dropdown in Arlo management platform. |
List options need to maintained in Arlo and Salesforce. | 256 | 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 |
32,000 | 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. | |
| Regions / Region 1 | Collection / Text (255) | 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 will not be copied back to Arlo. |
|
| LeadID / Arlo opportunity ID | Manually setup | ||||
| UniqueIdentifier / Arlo UniqueIdentifier | Manually setup | ||||
| Management page / Arlo management URL 1 | URL | Fixed | Link that opens the record in Arlo’s management platform. | ||
| Custom fields | Custom field | Manually setup | Custom fields are supported with the Salesforce integration. |
The Arlo course fields map with the Arlo event fields (New object) in Salesforce. Custom mapping is not supported or necessary for courses. Regions settings (for multi-region platforms) are sent to Salesforce.
Field mapping for courses
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
| [Template] Name / Name | Text | Fixed | Name of course | ||
| [Template] Provider / Provider | Text | 255 | Fixed | Organisation delivering the course when it is not your course. | |
| [Template] Code / Template_Code | Text | 128 | Fixed | Learn more about template and course codes. |
|
| Code / Event_Code | Text | 128 | Fixed | ||
| Status / Event_Status | Formula | Fixed | e.g. Draft, Active, Completed, Cancelled. | ||
| Event confirmed? / Confirmation Status | Picklist Dropdown in Arlo management platform. |
Confirmed (not confirmed is blank) | Fixed | Only shows if Arlo platform has course confirmation workflow activated. | |
| Date Event confirmed / Confirmation Date | Date/Time | Fixed | Only shows if Arlo platform has course confirmation workflow activated. | ||
| Last Modified Date / Arlo Last Modified Date | Date/Time | Fixed | The date that the course was last modified (by an admin) in Arlo. | ||
| / Arlo Event ID | Number | 18 | Fixed | Generated by Salesforce and does not exist in Arlo. | |
| Created Date / Arlo Created Date | Date/Time | Fixed | The date that the course was created (by an admin) in Arlo. | ||
| Status (Raw Data) / Status (Raw Data) | Picklist Dropdown in Arlo management platform. |
Draft Active (in progress) Completed Cancelled Unknown |
Fixed | The status value received from Arlo. The field labelled "Status" should be used on page layouts instead, which infers values for "In progress" etc. | |
| Private event/course information / | Fixed | Learn more about private courses. | |||
| / Private | Checkbox | Fixed | If ticked, course is Private/In-House. | ||
| Organisation / Client Account | Lookup | Fixed | Name of the organisation that the private course is provided to (if applicable). | ||
| [Private Event] Organisation Key / Account UID | Text | 128 | Fixed | Unique Identifier Key of the organisation that the private course is being delivered to (if applicable). | |
| Key contact / Key Contact | Lookup | Fixed | Key contact on the private course (if applicable). | ||
| [Private Event - Key contact] Contact Key / Contact UID | Text | 128 | Fixed | Unique Identifier Key of the Key contact for the private course (if applicable) | |
| Website / | Fixed | ||||
| Summary / Summary | Text | 8 lines / 500 chars | Fixed | The summary from the Arlo course's website page, if applicable. | |
| Schedule / | Fixed | ||||
| Start date / Start date | Date/Time | Fixed | The start date of the course (the date of the first session if a multi-session course). | ||
| End date / End date | Date/Time | Fixed | The end date of the course (the date of the last session if a multi-session course). | ||
| Time zone / Timezone | Text | 128 | Fixed | ||
| Start date event (with event timezone) / Start_Date_Event_Timezone |
Text | 100 | Fixed | E.G. 13/09/2019 08:00 AM (UTC+12:00) | |
| End date event (with event timezone) / End_Date_Event_Timezone |
Text | 100 | Fixed | E.G. 13/09/2019 08:00 AM (UTC+12:00) | |
| Delivery Method / Delivery | Picklist Dropdown in Arlo management platform. |
Webinar At a venue |
Fixed | Only Live online and At a Venue (courses) are supported, not Online Activities. | |
| Presenter(s) / Presenter(s) | Text | 255 | Fixed | All presenters on a course, if presenting any/all sessions (not only advertised presenters). Learn more about course presenters. | |
| Venue details / | Fixed | ||||
| Venue / Venue Name | Text | 255 | Fixed |
The Address of the venue associated to the course.
Note: The venue address fields will not show for multi session courses as there could be multiple venues.
|
|
| Venue Location / Location Name | Text | 255 | Fixed | ||
| [Venue] Street / PO Box / StreetLine1 | Text | 255 | Fixed | ||
| / StreetLine2 | Text | 255 | Fixed | ||
| [Venue] Suburb / Suburb | Text | 255 | Fixed | ||
| [Venue] City / City | Text | 128 | Fixed | ||
| [Venue] Post Code / Postcode | Text | 16 | Fixed | ||
| [Venue] State / Province / State | Text | 128 | Fixed | ||
| [Venue] Country / Country | Text | 128 | Fixed | ||
| Maximum registrations / Maximum registrations | Number | 18 | Fixed | The maximum registration limit on the course (if applicable) | |
| Registrations / Registrations/Max registrations | Number | Fixed | The number of registrations for the course, over max registrations (if applicable), including Completed, Approved, and Awaiting Approval statuses. | ||
| Completed registrations / Completed registrations | Number | Fixed | The number of completed registrations on a course. This is equal to all registrations on the completed course, regardless of attendance. | ||
| [Template] Website page link / View on website | Hyperlink | Fixed | Direct link to the course template page on your website. Potentially public on the website or available to people who have the link. | ||
| Website page URL / | URL | Fixed | URL to the course template page on your website. Potentially public on the website or available to people who have the link. | ||
| Website Registration URL / | URL | Fixed | URL to register for or add the course to the checkout. Use this to send customers to your checkout through marketing campaigns if you want people to go straight to the registration form (not hyperlink). | ||
| Arlo Management URL / | URL | Fixed | URL of the course in your Arlo Management platform (Arlo admins only) | ||
| Arlo Management Link / | Hyperlink | Fixed | Direct link to the course in your Arlo Management platform (Arlo admins only) | ||
| Website Registration Link / Website Registration Link | Hyperlink | Fixed | Direct link to the course's registration page on your website. If using order process, the course will be added to the checkout. | ||
| / Awaiting Approval or Approved Count | Number | Fixed | Sum of all registrations that are either Approved or Awaiting approval. | ||
| Links & URLs / | Links & URLs | Fixed | |||
| Confirmation Status / | Fixed | ||||
| Regions / Regions 1 | Collection / Text | 255 | Fixed | List of regions a course is associated with separated by commas, e.g. "AU,NZ,UK". Note: Updates to this field in Salesforce will not be copied back to Arlo. Learn more about the multi-regions feature. |
|
| Custom fields | Custom field | Fixed | Custom fields are supported with the Arlo - Salesforce integration. Course custom fields are not mappable, they are fixed when created in Salesforce. |
||
| Arlo field name / Salesforce field name | Arlo API field type / Salesforce field type | Values (if picklist) | Length / max characters (Arlo API / Salesforce) | Mapping | Description |
The Arlo registration fields map with the Arlo registration fields (New object) in Salesforce. Custom mapping is not supported or necessary for registrations.
Field mapping for registrations
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
| Arlo field name / Salesforce field name | Arlo API field type / Salesforce field type | Values (if picklist) | Length / max characters (Arlo API / Salesforce) | Mapping | Description |
| Registration GUID / Unique_Identifier | Text | 255 | Fixed | The unique identifier of the registration in Arlo. | |
| Registration Result / Result | Picklist Dropdown in Arlo management platform. |
Pass Fail Unknown |
Fixed | Learn more about registration results. | |
| Registration Status / Status | Picklist Dropdown in Arlo management platform. |
PendingApproval Approved Cancelled Completed Unknown |
Fixed | ||
| Registration Grade / Grade | Text | 64 | Fixed | Learn more about registration grades. | |
| Contact GUID / Contact_UID | Text | 128 | Fixed | The unique identifier of the contact in Arlo. | |
| Contact Email Address / Contact_Email | - | Fixed | |||
| Event Start Date / Event_Date | - | Fixed | |||
| Contact/Registrant Name / Contact | Lookup | Fixed | |||
| Registration Attendance / Attendance | Picklist Dropdown in Arlo management platform. |
Attended DidNotAttend Unknown |
Fixed | Learn more about registration attendance. | |
| Registration Last Modified Date / Arlo_LastModifiedDate | Date/Time | Fixed | The date and time that the registration was last modified in Arlo. May be same as created date. Record modified by marking attendance, for example. | ||
| Registration Comments / Comments | Long Text Area | 5 lines, 2,048 characters. | Fixed | ||
| Event Code / Code | - | Fixed | |||
| Registered Date / Arlo_CreatedDate | Date/Time | Fixed | The date and time that the registration was created. | ||
| Registration ID / Arlo_ID (Registration ID) | Number | 18 | Fixed | The number of the registration in Arlo. | |
| Organisation Name / Account_Name | - | Fixed | The registrant's organisation name. | ||
| Event Name / Event | Master-Detail | Fixed | The name of the course (template) in Arlo. | ||
| Regions / Region | Collection / Text | Automatic | 255 | Fixed | List of regions a contact is associated with separated by commas, e.g. "AU,NZ,UK". Note: Updates to this field in Salesforce will not be copied back to Arlo. |
| Custom Fields | Custom field | Fixed | Custom fields are supported with the Arlo Salesforce integration. Registration custom fields are not mappable, they are fixed when created in Salesforce. |
The Arlo address fields map with the Salesforce address fields. Custom mapping is not supported or necessary for addresses.
Field mapping for addresses
- Fixed = Mapping setup as part of the Arlo Salesforce app. Mapping cannot be edited.
- Auto Setup = Mapping setup as part of the Arlo Salesforce app. Mapping can be edited.
- Manually Setup = You are required to manually set up the field mapping in Salesforce.
| Arlo field name / Salesforce field name | Arlo API field type / Salesforce field type | Values (if picklist) | Length / max characters (Arlo API / Salesforce) | Mapping | Description |
| StreetLine1 / Concatenated into Salesforce StreetAddress field | String / Address | 256 | Fixed | Standard Salesforce field | |
| StreetLine2 | String / Address | 256 | Fixed | Standard Salesforce field | |
| SuburbOrRegion | String / Address | 256 | Fixed | Standard Salesforce field | |
| StreetLine3 | Not currently supported in the plugin. | ||||
| StreetLine4 | |||||
| City / City | String / Address | 128 | Fixed | Standard Salesforce field | |
| StateOrProvince / State | String / Address | 128 | Fixed | Standard Salesforce field | |
| PostCode / PostalCode | String / Address | 16 | Fixed | Standard Salesforce field | |
| Country / Country | String / Address | 128 | Fixed | Standard Salesforce field | |
The following object as not supported by the integration and these entities will need to be viewed within Arlo.
- Orders
- Sessions
- Optional extras
Before attempting to map a new field you should ensure that:
- In Arlo, you have activated the field you would like to map to Salesforce. Learn how to configure system and custom fields in Arlo.
- In Salesforce, you have the field available that you would like to map to.
Yes/No with text and Dropdown with text fields are not available to mapping to Salesforce.
Once the fields are available in both systems, follow the instruction below.
- In Salesforce, from the field mapping settings, click Add Row.
- In the Arlo Field column, click on the drop-down.
- Select the Arlo field you would like to map.
- In the Salesforce field column, click on the drop-down.
- Select the Salesforce field you would like to Arlo data to be mapped to.
If you receive an error, the field may already be mapped to an existing field or the field type may not be compatible e.g. you cannot map a drop-down field to a text box field.
- Repeat these steps for any additional fields you would like to map.
- Press Save at the bottom of the page.
- You will receive a success confirmation message.
Before you can see any of the data in Salesforce you will need to trigger a synchronisation.
If you no longer wish for information to be mapped between Arlo and Salesforce, you will need to remove the field mapping setting.
You cannot remove mapping for any fixed fields.
You can remove the field mapping in Arlo by disabling the field. This will not remove any existing field values in Salesforce but will stop any new records using the mapping. The field will show as disabled in the Salesforce field mapping settings.
You can also remove the mapping in Salesforce. This will not disabled the field in Arlo, but will stop any new records created in Salesforce using the mapping. Once you have removed the field, press Save.
If you can't find the field that Arlo is mapping to you may need to change the field availability permissions in Salesforce.
Learn more about modifying field access settings.
If your Salesforce connection has already completed a synchronisation of historic Arlo information before you configure your custom field mapping settings, the custom field data for contacts, organisations, and leads will not be displayed in Salesforce.
This is because each record only synchronises to Salesforce once (when it is created).
For this reason, when setting up the Salesforce integration we recommend leaving the initial import date as From now. This is so you can configure your custom field mapping once the connection has been established.
You can then change the date to synchronise older records after your field mapping is complete (so that all historic custom field information can be passed through to Salesforce when the record is created).