| Table of Contents |
|---|
...
The number of Salesforce.com daily API calls used depends on the level of updates to records in your Salesforce.com instance. On average, around 1,500 daily API calls are required. Make sure your Salesforce.com license supports these API requests. Based on a large sample set of 50 clients, daily API calls to Salesforce.com range from 1,000 to 1,700 calls per day.
Syncing
Sync Time
All fields and events synchronized between Salesforce.com and Lead Liaison are updated approximately every 5 minutes.
Initial Sync
Lead Liaison uses the SFDC email to match with Lead Liaison records on initial import. When there is a match, we use the SFDC record ID and link it with the Lead Liaison Prospect ID. If there are duplicate SFDC records (based on email address) then Lead Liaison uses the duplicate management settings in your account.
...
When synced, the Profile ID and Last Sync to Lead Liaison Web App will get updated on the next sync interval (~ 5 minutes after initial sync).
Visualforce Data Syncing
When syncing data in the activity, nurture, score, etc. tabs (as shown in the screenshot below), Lead Liaison will match the SFDC record to a Lead Liaison Prospect based on the SFDC record ID, which indicates the record is linked to a Lead Liaison Prospect, and display the information in a Visualforce component inside Salesforce.com.
If no match is found, then Lead Liaison will look for a match based on the email address of the SFDC record and show data in the Visualforce section. This does not imply the two records are synced together. This Visualforce data, as shown below, will show up on all records in Salesforce.com, including duplicates, that have the same email address as the Lead Liaison Prospect.
Field Updates on Sync
If a field has a value in SFDC and a value in Lead Liaison at sync time then SFDC will be considered the master. Consider the following scenario:
- Lead Source in SFDC is "Trade show A"
- Lead Source in Lead Liaison is "Search Terms"
- The prospect name in Lead Liaison is Anonymous
- The lead name in SFDC is some known name, say "John Smith"
- A phone call occurs with the prospect and the sales person on the call knows this is John Smith and sees John Smith online from the same company
- The sales person syncs the prospect from the Anonymous Lead Liaison lead to the lead in SFDC called John Smith
- The Lead Source value will remain "Trade show A" since that value was in SFDC. SFDC is the master and Lead Liaison is the slave in this case.
| Info | ||
|---|---|---|
| ||
In the above scenario, if field values were empty in SFDC (such as State) but the same field value is not empty in Lead Liaison then Lead Liaison will populate the value in SFDC when the prospect's record is synced to SFDC |
Dates & Times
All dates and times in SFDC are on Greenwich Mean Time (GMT). Lead Liaison uses GMT since each user who is accessing Lead Liaison may be in different time zones. The Activity History section (as shown below) is built as a Visual Force page in SFDC and data is read from Lead Liaison's servers.
...
- Most fields have the orange bi-directional sync enabled. This means when one value is updated in Lead Liaison, it gets pushed into Salesforce.com and vice versa. When a value gets updated in Salesforce.com, the update gets pushed into Lead Liaison. The Country Salesforce.com is the master, and will not get overriden, when a bi-directional field sync is set or when the direction is one-way, from Salesforce.com to Lead Liaison.
- The Country field has a one-way sync enabled, from Lead Liaison to Salesforce.com. This means that updates to this field in Salesforce.com will not get pushed into Lead Liaison while updates to this field in Lead Liaison will get pushed into Salesforce.com. With this one-way mapping data Data will flow from Lead Liaison to Salesforce.com when:
- A record in Salesforce.com is created at the same time a Lead Liaison Prospect is created. If the Country values are different, then Lead Liaison will be the master, and overwrite the value in Salesforce.com. Salesforce.com is the master, and will not get overriden, only when a bi-directional field sync is set.
- A record exists in Salesforce.com and Lead Liaison with the same value in the Country field, and the Country field is changed in Lead Liaison. When this happens, the new Country field in Lead Liaison will get pushed to the Country field in Salesforce.com and override the value.
- Notice the "Do Not Call" field and the check under the Create column. If we wanted to map this field from Salesforce.com to Lead Liaison we could single-click this check box to automatically create the field in Lead Liaison and set the sync direction.
...