Sync

Nektar’s Salesforce sync system reads and writes data objects such as Accounts and Contacts, and reads settings objects such as Users and Salesforce metadata. Each read or write operation runs independently every 10–15 minutes, except Salesforce metadata which is read every 24 hours.

The sync table displays:

• the time the most recent record was synced to or from Salesforce
• a sync health icon that can be clicked for more information
• toggles to enable or disable Salesforce reads or writes

Sync health icons may indicate the following states:

Objects synced

Nektar reads, updates, creates and deletes records under the following Salesforce objects.

By default, all fields and records accessible to the integration user are read. If required, we can configure it to read only a subset.

Only records that were previously created by Nektar and never updated manually are deleted.

Standard fields updated

In the default configuration, Nektar updates the following fields if they are (a) empty, or (b) contain a value previously written by Nektar.

¹ “What” refers to the Opportunity or Account an activity is related to, and is labelled “Related”
² “Who” refers to the primary Contact or Lead an activity is related to, and is labelled “Name”

Custom data transform rules may also update these or other fields of the Account and Opportunity objects.

Owner

The “Owner” field of Nektar-created Contacts, Events and Tasks will contain the most appropriate seller(s) responsible for that record, which is:

• for Contacts: the owner of the Account with which the Contact was associated
• for Tasks (emails): the sender of the email, if they are a seller; otherwise, the primary among sellers in “To”; if there are none, the primary seller in “Cc”.
• for Events: the organizer of the calendar event, if they are a seller; otherwise, the primary seller from the invitee list.

The primary seller in a list is the owner of the Opportunity or Account with which the activity was associated, if present in the list; otherwise the first one in the list.

If no appropriate sellers were found, or if the most appropriate seller is not a Salesforce user, the Nektar Salesforce integration user is assigned as the owner.

Name (“Who”)

This “Name” field of Events and Tasks contains the buyer(s) that participated in that activity. If your Salesforce organization has enabled Shared Activities, all buyers will be included in this field; if not, it will contain only the primary buyer, which is:

• for Tasks (emails): the first buyer found in the email’s From, To or Cc headers (in that order)
• for Events: the organizer of the calendar event, if they are a buyer, or the first buyer in the invitee list

Attendees

The “Attendees” field on Events will contain all the sellers and buyers invited to the event, whether or not your Salesforce organization has enabled Shared Activities.

Nektar custom fields

Nektar creates several custom fields in your Salesforce organization. Nektar does not automatically add them to any views, layouts, reports etc. but you may do so.

This table shows the data type and possible values the field may have in each Salesforce object:

Notes

1. Required field
2. Requires Zoom or MS Teams integration
3. Requires Buyer Movement feature

Output screening

Nektar only creates records that can be linked to existing Salesforce records.

• Contacts must link to an existing account or contact via a shared, non-public domain name. Consequently, Nektar will never create contacts with public domains (such as @gmail.com).
• Activities must link to valid contacts or leads. Contacts created from participants found in the same email or event qualify.
• Opportunity-Contact Roles are created for all contacts that have participated in activities linked to the opportunity.

Additionally, write rules can be configured to further restrict which Activities, Contacts and Opportunity Contact Roles are created.