The data synchronization is achieved by constantly running a variable number - depending on the options enabled - of steps. These steps perform different duties and they all concur to keep the data between Salesforce and SalesWings consistent.
Table of content:
Overview of Data Flow
SalesWings -> Salesforce
During the synchronization step
GetTags
a request to SalesWings is performed. All the existing tag definitions are returned and corresponding records in Salesforce are created/updated/deletedDuring the synchronization step
GetScores
a request to SalesWings is performed where all the existing score definitions are returned and corresponding records in Salesforce are created/updated/deleted.During the synchronization step
GetProspects
a request to SalesWings is performed. All the modified prospects since the last synchronization are returned (or all the existing prospects if a full synchronization was requested) and corresponding records in Salesforce are created/updated.
Salesforce -> SalesWings
When a contact or lead matched with a prospect is updated and the value for any of the following field changes -
Email
,SW Favorite
,First Name
,Last Name
,Owner Id
,Prospect Id
- an update containing the following information -Id
,Email
,SW Favorite
,Name
,First Name
,Last Name
,Owner Email
,Prospect Id
- is sent to SalesWings. This is done to keep the information presented in the SalesWings cockpit aligned with Salesforce’s.
This document will now describe the workflow steps responsible for keeping data consistent between Salesforce and SalesWings. Follows a description of the duties performed by each step.
Active Steps
Name | Scope | Since |
GetTags |
| 2.62 |
GetScores |
| 2.62 |
| 2.62 | |
GetProspectPages |
Note: Since the data volume for pages is significantly higher a dedicated step in the sync is required. Note: This step is optional and included in the synchronization only if explicitly enabled (see Disable Page Visit Sync in the SalesWings Studio: Custom Settings). | 2.119 |
MatchProspectsToLeads |
1 If the lead gets successfully updated the prospect sync status gets set to | 2.103 |
MatchProspectsToContacts | See MatchProspectsToLeads. Instead of leads the step works on contacts. | 2.103 |
CleanLeads |
1 Only unconverted leads are considered by the process. | 2.90 |
CleanContacts | See CleanLeads. Instead of leads the step works on contacts. | 2.90 |
AggregateTags |
| 2.62 |
AggregateScores |
| 2.62 |
AggregateTemperature |
| 2.80 |
CreateOpportunityTags |
| 2.71 |
CreateOpportunityScores |
| 2.71 |
DeleteProspectScores |
1 Any contact/lead score is also automatically deleted (Master-Detail cascading effect). | 2.62 |
DeleteProspectPages |
| 2.62 |
DeleteRecordPages |
1 Any contact/lead score is also automatically deleted (Master-Detail cascading effect). | 2.119 |
Deprecated Steps
Name | Scope | Since |
CountRecords |
| 2.118 |
MatchProspects |
| 2.103 |
DeleteProspects |
| 2.119 |
DeleteContactPages |
| 2.119 |
DeletePages |
| 2.119 |