it upserts as saleswings__SW_Tag__c all tags from SalesWings

it upserts as saleswings__Score__c all scores from SalesWings

it upserts as saleswings__Prospect__c all prospects marked as changed by SalesWings since the last synchronization. Each prospect record with life cycle set to Active will have their sync status set to Not Processsed - otherwise Processed - and the Processed Attempts value set to 0.

it aligns (creates new, updates existing, deletes orphans) all the tags associated with the prospect being synced to the respective saleswings__SW_Prospect_Tag__c records

it aligns (creates new, updates existing, deletes orphans) all the scores associated with the prospect being synced to the respective saleswings__Prospect_Score__c records

it aligns (creates new, updates existing, deletes orphans) all the pages associated with the prospect being synced in the previous step with the respective saleswings__Page_Prospect__c records

it processes all the prospects set to Not Processed in the GetProspects step. The matching is based on the email address. If there are any leads whose email address corresponds to the prospect’s, the lead gets selected for matching.

For each matching lead, the step proceeds to create/align/delete a copy of each prospect’s score, tag, and page (if Disable Page Visit Sync is disabled). See The Data Models subheading for further information.

If Match Leads via Platform Events is disabled the matching lead gets immediately updated1 with the information coming from the prospect and its scores, according to the SW Studio Field Mapping records configured. If Match Leads via Platform Events is enabled the update1 is deferred and performed through the publishing and catching of a platform event (this system provides compatibility for org-code cannot run in a Batchable context).

it disconnects - by removing any prospect data - the lead1 from any prospect that was marked as Merged or Deleted, or any prospect record that was physically deleted.

if Account Aggregation is enabled, it aggregates all contact tags at their respective Account level via the saleswings__SW_Account_Tag_Segment_Trigger__c object.

if Account Aggregation is enabled, it aggregates all contact scores at their respective Account level via the saleswings__Account_Score__c object.

it assigns the median Temperature value at the Account level for its associated contacts.

if Account Aggregation and Opportunity Tags are enabled, it copies aggregated account tags to any existing account opportunity (saleswings__Opportunity_Tag__c).

if Account Aggregation and Opportunity Scores are enabled, it copies aggregated account scores to any existing account opportunity (saleswings__Opportunity_Score__c).

it deletes any orphaned prospect scores1 (saleswings__Prospect_Score__c, this might be necessary in case a prospect is physically deleted, as the relationship between prospect and scores is of Lookup type).

it deletes any orphaned prospect pages (saleswings__Page_Prospect__c, this might be necessary in case a prospect is physically deleted, as the relationship between prospect and pages is of Lookup type).

it deletes any orphaned contact/lead pages1 (saleswings__Website_Visit__c).

it counts he number of records in each of the SalesWings custom-objects and send the total back to SalesWings for monitoring.

it matches by email address either contact or lead with the respective prospect.

it removes from the contact or the lead any prospect information if the prospect was marked as Merged or Deleted. This will be skipped if the setting Match Leads via Events or Match Contacts via Events.

it deletes orphaned contact/lead pages

it deletes orphaned saleswings__Page__c records (which connect prospect pages to contact/lead pages).