Objects and fields Gong needs access to

Prev Next

Tech admin and Salesforce admin

When you connect Gong to Salesforce, Gong can access any Salesforce data that the connecting user can access. To control this access, connect using a dedicated integration user.

Configure the integration user

Integration users should only have the permissions needed to import and export data between Gong and Salesforce. This protects your data, but if permissions are too limited, activities may be missing until the setup is adjusted.

Manage data access and actions in Salesforce

Salesforce separates what a user can do from what a user can see.

  • What a user can do depends on their object and field permissions, such as the ability to create or update accounts.

  • What a user can see depends on organization hierarchy, their role, and sharing rules. For example, a user may have permission to update accounts but will only see the accounts their role and sharing settings allow.

Salesforce permission sets and profiles

The ability to perform actions in Salesforce is set in profiles and permission sets. Permissions include CRUD (create, read, update, delete) operations per object, access to apps or connected app assignments, and which Apex classes and Visualforce pages can be accessed.

  • Profiles: Every Salesforce user must have one profile, which defines a baseline set of permissions.

  • Permission sets: Add permissions to specific users beyond their profile, without changing the profile itself.

Salesforce roles

Salesforce roles define which objects the user has access to. If the integration user has a role that only has access to specific records in Salesforce, Gong will only see those records.

However, if you assign View All Records to an object in the integration user’s permission set, that overrides the limit set by the role and the integration user will have access to all records for that object.

Salesforce Integration license

Salesforce offers a dedicated license for integration users, which Gong supports. You may want to set up a dedicated integration user for each integration. The integration user needs permissions sets with both the Salesforce API Integration license and the Salesforce Integration license.

  • Select the Salesforce API Integration license to assign system permissions (required for creating tasks and events).

  • Select the Salesforce Integration license for your to assign field-level permissions (required for importing Salesforce data to Gong).

Setup for the integration user is the same as for a regular Salesforce user.

Permissions and visibility required for Salesforce objects

In Salesforce, you must assign the integration user permissions at both the object and field level. The integration user should have the following permissions in Salesforce:

Note:

To edit Salesforce fields in Gong (such as the Deal board), the team member needs edit permissions to the relevant fields. The integration user’s permissions don’t determine this.

  • Read or View All Records: If the integration user has read permissions, they will only be able to access records according to their Role. To give access to all records, assign View All Records.

    • Lead, Contact, Account, and Opportunity objects: Separate check boxes located under Standard Object Permissions

    • Task and Event objects: If you export Gong activities to tasks or events

    • For Deals and Forecast: Opportunity team, Opportunity Splits, and Opportunity Product objects

  • Write access (create, update, and delete):

    • Task and Event objects: Set in the System Settings of the profile or permission set. Assign Access Activities, Edit Tasks, Edit Events, and View All Users.
      System permissions table showing various user access options and descriptions.

  • Record types: If you set up task record types, make sure you give access permissions to the integration user

  • API enabled

  • View All users

If you have an Engage license

Make sure the integration user has the following permissions:

  • Contact: Edit and modify all

  • Lead: Edit and modify all

  • Account: Edit and modify all

  • Opportunity: Edit and modify all

  • Campaign: View all

  • Campaign members: View all

Permissions required for fields in each object

Refer to the following tables to understand what fields are required for the integration, and what's recommended to get the most out of Gong.

  • Required fields cannot be deselected and must be included in the integration. Your Salesforce integration won't work if we can't access these fields.

  • Recommended fields can be deselected and don't have to be included in the integration. However these fields enhance functionality or customization options for your deal boards, call filters, and so on and we recommend importing them to Gong.

Other fields can be added as necessary. Scroll down to Supported field types for a list of the supported field types.

Account

API field name

Salesforce field label

Required

Recommended

AccountSource

Account Source

Id

ID

Industry

Industry

IsDeleted

Is deleted?

LastActivityDate

Last activity (user)

LastModifiedDate

Last modified (user)

Name

Account name

OwnerId

Owner ID

ParentId

Parent ID

SystemModstamp

System Modified Timestamp

Type

Type

Website

Account URL. This is not displayed in Gong, for example on the Deals page. If you want to see the website in Gong, create a formula text field in the Account object which contains the account's website, import it to Gong and display it in the relevant page.

Contact

API field name

Salesforce field label

Required

Recommended

AccountId

Account ID

Email

Email address

FirstName

First name

Id

ID

IsDeleted

Is deleted?

LastActivityDate

Last activity (user)

LastActivityDate

Last activity (user)

LastName

Last name

LastModifiedDate

Last modified (user)

LeadSource

Lead source

MobilePhone

Mobile phone number

Phone

Phone

SystemModstamp

Last modified (automated and user)

Title

Title

Event

When exporting meetings or calls you can choose to export them as tasks or events. Activities exported as events have a start and end date and time, but don’t include a status or the call outcome. In addition, you must define custom fields to see all the data available.

API field name

Salesforce field label

Required

Recommended

ActivityDate

Date

Description

Description

DurationInMinutes

Duration

EndDateTime

End

EventSubtype

Event Subtype

Id

Id

OwnerId

Assigned To

StartDateTime

Start

Subject

Subject

Type

Type

WhatId

Related To

WhoId

Name

Lead

API field name

Salesforce field label

Required

Recommended

Company

Company

Phone

Phone

Email

Email

FirstName

First Name

Id

Id

LastActivityDate

Last Activity

LastModifiedDate

Last Modified Date

LastName

Last Name

LeadSource

Lead Source

MobilePhone

Mobile Phone

Phone

Phone

SystemModStamp

System Modstamp

Title

Title

OwnerId

Owner ID

Opportunity

API field name

Salesforce field label

Required

Recommended

AccountId

Account ID

Amount

Amount

CloseDate

Close date

CreatedDate

Created date

Id

ID

IsClosed

Is closed?

IsDeleted

Is deleted?

IsWon

Is Won?

LastActivityDate

Last activity (user)

LastModifiedDate

Last modified (user)

LeadSource

Lead source

Name

Name

OwnerId

Owner ID

Probability

Probability

StageName

Stage

SystemModstamp

Last modified (automated and user)

Type

Type

Opportunity Contact Role

API field name

Salesforce field label

Required

Recommended

OpportunityId

Opportunity ID

ContactId

Contact ID

CreatedDate

Created date

Id

ID

IsPrimary

Is Primary?

Role

Role

SystemModstamp

Last modified (automated or user)

Opportunity History

API field name

Salesforce field label

Required

Recommended

Amount

Amount

CloseDate

Close date

CreatedDate

Created date

ForecastCategory

Forecast category

Id

ID

OpportunityId

Opportunity ID

Probability

Probability

StageName

Stage name

Opportunity Split

Make sure you're importing the following fields when working with opportunity splits:

API field name

Salesforce field label

Required

Recommended

SplitAmount

Amount

IsDeleted

Deleted

SplitOwnerId

User ID

SplitPercentage

Percent (%)

OpportunityId

Opportunity ID

SplitTypeId

Opportunity Split Type ID

CreatedDate

Created Date

Id

ID

SystemModstamp

System Modstamp

Opportunity Split Type

Make sure you're importing the following fields when working with opportunity splits:

API field name

Salesforce field label

Required

Recommended

IsDeleted

Deleted

IsActive

Active

CreatedDate

Created Date

IsTotalValidated

100% Validated

SplitEntity

Custom Object Definition ID

SplitField

Field

Id

ID

MasterLabel

Label

DeveloperName

Developer Name

SystemModstamp

System Modstamp

Opportunity Stage

API field name

Salesforce field label

Required

Recommended

Id

ID

Description

Description

IsActive

Is active?

IsClosed

Is closed?

IsWon

Is won?

MasterLabel

Master label

SortOrder

Sort order

SystemModstamp

Last modified (automated or user)

Opportunity Team Member

Make sure you're importing the following fields when working with opportunity teams:

API field name

Salesforce field label

Required

Recommended

IsDeleted

Deleted

OpportunityId

Opportunity ID

OpportunityAccessLevel

Opportunity Access

UserId

User ID

CreatedDate

Created Date

Title

Title

TeamMemberRole

Team Role

Id

ID

SystemModstamp

System Modstamp

Name

Name

Record Type

API field name

Salesforce field label

Required

Recommended

Id

Id

IsActive

Active

Name

Record Type

SobjectType

Sobject Type Name

SystemModstamp

Last modified (automated or user)

Task

The integration user should have write access to the task object so that Gong activities can be created in Salesforce. You can choose to export calls and meetings as either tasks or events. Set up custom fields to see all task data. Tasks include the status and call outcome fields, but don’t have a start and end date and time.

API field name

Salesforce field label

Required

Recommended

AccountId

Account ID

ActivityDate

Activity date

CallDisposition

Disposition

CallDurationInSeconds

Call duration in seconds

CreatedDate

Created date

Description

Description

Id

ID

OwnerId

Owner ID

Subject

Subject

Status

Status

TaskSubtype

Task subtype

Type

Type

WhatId

What ID

WhoId

Who ID

SystemModstamp

Last modified (automated or user)

User

API field name

Salesforce field label

Required

Recommended

Department

Department

Email

Email address

FirstName

First name

Id

ID

lastName

Last name

LanguageLocaleKey

Language / Locale

LastModifiedDate

Last modified (user)

Phone

Phone number

SmallPhotoUrl

URL for photo

SystemModStamp

Last modified (automated or user)

TimeZoneSidKey

Timezone

Title

Job title

UserRoleId

User role ID

Supported field types

We support the following field types:

Note:

Formula is not a field type. When you define a formula field in Salesforce, in addition to the formula you assign a field type. Therefore, we support formula fields when they are assigned to a supported field type.

  • BOOLEAN

  • COMBOBOX

  • CURRENCY

  • DATE

  • DATETIME

  • DOUBLE

  • EMAIL

  • ID

  • INT

  • LONG TEXT AREA: Data in this field is trimmed to hold 10k of characters.

  • LOOKUP: displays the value of the field it is linked to

    Note:

    Only fields that reference users are supported. Fields that reference Campaign objects are not supported.

  • NUMBER

  • PERCENT

  • PHONE

  • PICKLIST

  • REFERENCE: Data in this field isn't supported in search.

    Note:

    In deal boards, we support only reference to Owner and Record Type. In forecast boards, we support only reference to Record Type (we don't support reference to owner, i.e. alternative owner)

  • RICHTEXT

  • STRING

  • TEXTAREA

  • TIME

  • URL

Note that we don't support the following field types:

  • ADDRESS

  • ENCRYPTED STRING

  • LOCATION

  • MULTIPICKLIST