- Print
- DarkLight
- PDF
The Gong Snowflake database includes various tables that store detailed information about conversations, calls, users, and activities. The CONVERSATIONS table records each conversation type, while the CALLS table tracks all calls, including scheduled ones. The CALL RECORDINGS and CALL TRANSCRIPTS tables provide details on recorded calls and their transcripts, respectively. The USERS table contains user data and licensing details, maintaining historical changes. The USER CONVERSATION GONG ACTIVITIES table logs user activities on calls, and the INTERACTION STATS table offers metrics on call management. Additionally, the WORKSPACES and TRACKERS tables help organize and analyze conversations based on specific keywords. The CONVERSATION CONTEXTS table links conversations to CRM objects, while the EMAILS, MEETINGS, and CONVERSATION PARTICIPANTS tables track email and meeting details. Finally, the FORECAST SUBMISSIONS and SCORECARD tables manage team forecasts and performance evaluations.
This section details the tables and columns available in the Gong-Snowflake database. See What's new in Gong Data Cloud for details of what's been added to the data cloud.
Conversations
The CONVERSATIONS
table contains a row for each conversation. A conversation can be an email, call, or meeting. The CONVERSATIONS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
CONVERSATION_ID | varchar | Unchanged | The Gong conversation id. This ID does not have to be unique. An email conversation can have the same CONVERSATION_ID as a call conversation. However, two conversations of the same type cannot have the same CONVERSATION_ID. |
CONVERSATION_DATETIME | timestamp_tz | NULL | The date and time the conversation occurred |
CONVERSATION_KEY | varchar | Unchanged | The primary key for the conversation in Snowflake. As there are different types of conversations, such as calls or emails, this value is unique for all conversation types. |
CONVERSATION_TYPE | varchar | NULL | The type of the conversation. Options are:
|
WORKSPACE_IDS | array (string) | NULL | The IDs of the workspaces the conversation is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Calls
The CALLS
table contains a row for each call in the system, including the call spotlight and scheduled calls that have not yet taken place. The CALLS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
BROWSER_DURATION_SEC | float | NULL | The amount of time in seconds the browser was shared during the call |
CALL_CONNECTED | boolean | When true, indicates that the call was answered by the prospect the rep wanted to reach. When false, indicates that either the call wasn't answered, or that the person who answered wasn't the correct contact. | |
CALL_SPOTLIGHT | variant | NULL | A JSON which contains all the spotlight data for the call. See below for an example of the JSON. |
CALL_SPOTLIGHT_BRIEF | varchar | NULL | A summary of the call |
CALL_SPOTLIGHT_KEY_POINTS | varchar | NULL | The key points of the call |
CALL_SPOTLIGHT_NEXT_STEPS | variant | NULL | The steps that should be done when the call is completed |
CALL_SPOTLIGHT_AUTOMATIC_DISPOSITION | varchar | NULL | The code of the outcome of the call as determined by Gong’s AI. Only populated for SDR calls One of the following:
|
CALL_SPOTLIGHT_OUTCOME | varchar | NULL | The description of the outcome of the call as determined by Gong’s AI. Only populated for SDR calls |
CALL_SPOTLIGHT_TYPE | varchar | NULL | The type of call the spotlight is for. Options are:
|
CALL_URL | varchar | Unchanged | The URL for the call |
QUESTION_COMPANY_COUNT | number | NULL | The number of questions asked by people on the call from the company |
CONVERSATION_ID | varchar | Unchanged | The Gong conversation id. This ID does not have to be unique. An email conversation can have the same CONVERSATION_ID as a call conversation. However, two conversations of the same type cannot have the same CONVERSATION_ID. |
CONVERSATION_KEY | varchar | Unchanged | The key for the conversation the call is associated with. (Unique) |
QUESTION_NON_COMPANY_COUNT | number | NULL | The number of questions asked by customers on the call |
WEBCAM_NON_COMPANY_DURATION_SEC | float | NULL | The amount of time in seconds the customer had their webcam on |
DIRECTION | varchar | Unchanged | Indicates who made the call. Options are:
|
DISPOSITION | varchar | NULL | The outcome of the call |
EFFECTIVE_START_DATETIME | timestamp_tz | Unchanged | The actual start date of the call |
IS_PRIVATE | boolean | NULL | True if the call is a private call |
OWNER_ID | varchar | Unchanged | The owner of the call. (Foreign key, |
PHONE_NUMBER | varchar | NULL | The phone number of the prospect |
PLANNED_END_DATETIME | timestamp_tz | NULL | The date and time the call was planned to end. |
PLANNED_START_DATETIME | timestamp_tz | NULL | The date and time the call was planned to start. |
PRESENTATION_DURATION_SEC | float | NULL | The amount of time a presentation was shared during the call |
SCOPE | varchar | Unchanged | Indicates whether the call is an internal call only. Options are:
|
SYSTEM (deprecated) | varchar | The telephony system the call was made on
| |
SOURCE_SYSTEM | varchar | Unchanged | The telephony system the call was made on |
TITLE | varchar | NULL | The title of the call |
STATUS | varchar | Unchanged | The status of the call recording, automatically assigned by Gong. You can filter reports based on the call status. Possible values:
|
WEBCAM_OWNER_DURATION_SEC | float | NULL | The amount of time in seconds the host had their webcam on |
WORKSPACE_ID | varchar | Unchanged | The workspace the call is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the call transcript was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Call_Recordings
The CALL_RECORDINGS
table contains a row for each recorded and processed call. The table includes details about the recording such as the start and end time. The CALL_RECORDINGS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
CONVERSATION_KEY | varchar | NULL | The key for the conversation the call is associated with. (Unique) |
DURATION | number | NULL | The duration of the call (in seconds) |
END_DATETIME | timestamp_tz | NULL | The actual date and time the call ended. |
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
LANGUAGE | varchar | NULL | The code for the language the call was made in |
MEDIA_TYPE | varchar | NULL | Sets the media for the call. Options are:
|
IS_DELETED | boolean | Unchanged | Indicates whether the call recording was deleted in Gong. Values are:
|
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
START_DATETIME | timestamp_tz | NULL | The actual start date and time of the call. |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Call_Transcripts
The CALL_TRANSCRIPTS
table contains a row for each call. The transcript is a JSON with details about who said what and at what point in the conversation. You can see an example of the JSON received below the table.
The CALL_RECORDINGS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
CONVERSATION_KEY | varchar | Unchanged | The key for the conversation the call is associated with. (Unique) |
TRANSCRIPT | varchar | NULL | A JSON of the transcript of the entire call. The transcript includes speaker segments, so you can see who said what and when in the call. |
WORKSPACE_ID | varchar | Unchanged | The workspace the call is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the call transcript was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
The structure for the JSON is as follows:
[
{
"speakerId": "4968385411579794447",
"sentences": [
{
"startMs": 420,
"endMs": 10930,
"text": "Michael. Good to meet you!"
},
{
"startMs": 11780,
"endMs": 14900,
"text": "Did you just arrive here?"
}
]
},
{
"speakerId": "4968385411579794447",
"sentences": [
{
"startMs": 172350,
"endMs": 172570,
"text": "Yeah, We arrived last week."
}
]
}
]
Users
The USERS
table contains personal data about each user in the system user as well as licensing details. The table also includes the manager_id so that you can build the organizational hierarchy. We also maintain history in this table using SCD type 2.0, so you can see for example, previous job titles or permissions. When one of the values is changed, the VALID_TO_DATETIME
is set to the current date and a new row is added with both the new and unchanged values. The VALID_FROM_DATETIME
in the new row is set to the current date and the VALID_TO_DATETIME
is set to NULL
.
The USERS
table includes the following:
Column | Type | Value on delete | Description |
---|---|---|---|
ACTIVE | boolean | NULL | Sets whether the user is active. Users are not deleted from the system, they become inactive |
EMAIL_ADDRESS | varchar | NULL | The user's email address |
LOCALE | varchar | NULL | The user's locale |
FIRST_NAME | varchar | NULL | The user's first name |
LAST_NAME | varchar | NULL | The user's last name |
LICENSED | boolean | NULL | Indicates whether the user has a paid license |
MANAGER_ID | varchar | NULL | The id of the employee's manager |
TIME_ZONE | varchar | NULL | The timezone the user is in (TZ format, such as America/New_York) |
USER_ID | varchar | Unchanged | The ID of the user in Gong (unique). |
SHOULD_IMPORT_TELEPHONY_CALLS | boolean | NULL | Indicates whether the user's calls recorded by an external telephony system should be automatically recorded and imported into Gong |
SHOULD_RECORD_WEB_CONFERENCE_CALLS | boolean | NULL | Indicates whether the user's web conference calls should be automatically recorded |
SHOULD_SYNC_EMAILS | boolean | NULL | Indicates whether the user's emails should be automatically imported to Gong |
TITLE | varchar | NULL | The employee's job title |
VALID_FROM_DATE_TIME | timestamp_ntz | Unchanged | (SCD type 2.0) The date this record was created |
VALID_TO_DATE_TIME | timestamp_ntz | Unchanged | (SCD type 2.0) The date this record was changed. A null value indicates this is the current record for the user. |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was changed |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Users_crm_ids
In some cases, one email address can be associated with multiple CRM IDs. In order to ensure that each Gong user is associated with the correct CRM ID, we store all CRM IDs associated with the user, so that one Gong user can be associated with multiple CRM user IDs.
The USERS_CRM_IDS
table includes the following:
Column | Type | Value on delete | Description |
---|---|---|---|
CRM_ID | varchar | Unchanged | The Gong user's ID in the CRM |
USER_ID | varchar | Unchanged | The ID of the user in Gong (unique). |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the CRM data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
User_conversation_gong_activities
The USER_CONVERSATION_GONG_ACTIVITIES
table stores details of which user performed which activity on a call. For each activity a user performs in the application, a new row is added with the user and call ids, the date of the activity and the type of the activity.
The USER_CONVERSATION_GONG_ACTIVITIES
table includes the following:
Column | Type | Value to delete | Description |
---|---|---|---|
CONVERSATION_KEY | varchar | Unchanged | The ID of the conversation the user made the activity on (from the conversations table) |
GONG_ACTIVITY_DATETIME | timestamp_tz | Unchanged | The date and time of the activity |
GONG_ACTIVITY_TYPE | varchar | Unchanged | The activity type. Options are:
|
USER_ID | number | Unchanged | The ID of the user who had the activity (from the users table) |
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Interaction_stats
The INTERACTION_STATS
table contains statistics about how a rep manages their calls. Each row includes statistics for a single call, such as the rep's talk ratio, and interactivity. For a full explanation of how these metrics are calculated, see Analyze team performance.
The INTERACTION_STATS
table includes the following:
Column | Type | Value on delete | Description |
---|---|---|---|
CONVERSATION_KEY | varchar | Unchanged | The ID of the call in the conversations table |
CALL_ID | varchar | NULL | The call ID |
CALL_OWNER | varchar | NULL | The Gong user ID of the person who owns the call |
INTERACTIVITY | double | NULL | Indicates the number of times the conversation switched between the rep and the customer. The value is based on a calculation which normalizes the number of times the conversations switched size to a 60 minute conversation. |
LONGEST_CUSTOMER STORY | double | NULL | The longest amount of time at any one time the customer spoke in the call |
LONGEST_MONOLOGUE | double | NULL | The longest amount of time the user spoke at one time in the call in seconds |
PATIENCE | double | NULL | The average amount of time the rep waited before speaking after the customer finished speaking, in seconds |
QUESTION_RATE | double | NULL | The average number of questions the rep asked in the call |
TALK_RATIO | double | NULL | The percentage of time the user spoke in the call |
USER_ID | number | Unchanged | The ID of the user who participated in the call (from the users table) |
IS_DELETED | boolean | Unchanged | Indicates that the stats were deleted in Gong. The stats are also deleted in Snowflake when a conversation is deleted. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Workspaces
The WORKSPACES
table contains a list of the workspaces in your org and includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
NAME | varchar | NULL | The name of the workspace |
WORKSPACE_ID | varchar | Unchanged | The workspace ID |
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Trackers
Trackers are tools that identify when words, phrases or concepts are mentioned in calls, allowing you to know what your reps and customers are talking about. In addition to out-of-the-box trackers that come with Gong, you can set up your own trackers, according to your company’s business priorities, and what you want to capture insights around. See Trackers: Overview for more details.
The TRACKERS
table includes both smart trackers and keyword trackers. A new row is added to the table for each tracker in the system.
The TRACKERS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
KEYWORDS | varchar | NULL | The list of keywords in the tracker (JSON array). |
NAME | varchar | NULL | The name of the tracker, such as Pricing. |
TRACKER_ID | varchar | Unchanged | The unique tracker ID |
TRACKER_TYPE | varchar | NULL | The tracker type:
|
WORKSPACE_ID | varchar | NULL | The workspace the tracker is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
In the Snowflake database, a record is inserted for the tracker with all the keywords defined and in addition for each keyword in the keyword tracker. For example, if you have a tracker which is named pricing which includes the keywords, budget, price and discount, the tracker is entered to the database as follows:
tracker_id | name | keywords | type |
---|---|---|---|
t_1 | Pricing | [budget, price, discount] | keyword_tracker |
t_2 | Pricing / budget | [budget] | keyword_tracker |
t_3 | Pricing / price | [price] | keyword_tracker |
t_4 | Pricing / discount | [discount] | keyword_tracker |
Smart trackers are added to the table as follows:
tracker_id | name | keywords | type |
---|---|---|---|
t_6 | My Smart Tracker | NULL | smart_tracker |
Conversation_trackers
The CONVERSATION_TRACKERS
table is used to associate conversations with trackers and contains the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
CONVERSATION_KEY | varchar | Unchanged | The ID for the conversation (foreign key) |
COUNT | int | NULL | The number of times the tracker occurs. |
TRACKER_ID | varchar | Unchanged | The tracker ID (foreign key) |
WORKSPACE_ID | varchar | NULL | The workspace the tracker is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the record was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
The following is an example of how the keyword trackers are added to the CONVERSATION_TRACKERS
table. When the TRACKERS
table has the following entries:
tracker_id | name | keywords | type |
---|---|---|---|
t_1 | Pricing | [budget, price, discount] | keyword_tracker |
t_2 | Pricing / budget | [budget] | keyword_tracker |
t_3 | Pricing / price | [price] | keyword_tracker |
t_4 | Pricing / discount | [discount] | keyword_tracker |
t_6 | My Smart Tracker | NULL | smart_tracker |
In a call where the following trackers are identified:
"Budget" found twice
“Price” found once
“My Smart Tracker” found five times
The CONVERSATION_TRACKERS
table will have the following entries:
conversation_key | tracker_id | count |
---|---|---|
c_1 | t_1 (Pricing) | 3 |
c_1 | t_2 (Pricing / budget) | 2 |
c_1 | t_3 (Pricing / price) | 1 |
c_1 | t_6 (My Smart Tracker) | 5 |
The Pricing tracker (t_1) is counted three times in the conversation, as it includes mentions of the terms budget and price. The Pricing/budget (t_2) tracker is counted twice in the conversation, as this tracker only covers the term budget. The Pricing/price (t_3) tracker is counted once in the conversation, as this tracker only covers the term price.
Conversation_contexts
The CONVERSATION_CONTEXTS
table enables associating a CRM object, such as an account, deal or lead, with a conversation. A conversation can be associated with multiple CRM objects. Each association is added as a new record in the CONVERSATION_CONTEXTS
table.
The CONVERSATION_CONTEXTS
table includes the following:
Column | Type | Value on delete | Description |
---|---|---|---|
CONVERSATION_KEY | varchar | Unchanged | The key for the conversation |
FIELDS_SNAPSHOT | variant | NULL | A snapshot of the object's fields, that are imported to Gong, at the time of the conversation, excluding those in the |
MAPPED_FIELDS_SNAPSHOT | variant | NULL | Gong maps some fields in the CRM to other fields. For a list of mapped fields per CRM object see ??? |
OBJECT_ID | varchar | Unchanged | The ID of the object in the CRM |
OBJECT_TYPE | varchar | Unchanged | The object type. Options are (in lowercase):
|
IS_DELETED | boolean | Unchanged | Indicates whether the conversation context was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
The following table shows how CRM fields are mapped in Gong:
CRM object | Mapped fields in Gong |
---|---|
Account | name industry type |
Opportunity (Deal) | owner name amount stage isStageClose isStageWon proababilityPercent forecastCategory |
Lead | status |
Emails
The EMAILS
table contains a row for each email and the workspaces the email is associated with. The EMAILS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
AUTO_SUBMITTED_TYPE | varchar | NULL | Indicates the type of email for auto generated emails. Options are:
|
CONVERSATION_ID | varchar | NULL | The Gong conversation id. This ID does not have to be unique. An email conversation can have the same CONVERSATION_ID as a call conversation. However, two conversations of the same type cannot have the same CONVERSATION_ID. |
CONVERSATION_KEY | varchar | Unchanged | The primary key for the conversation in Snowflake. As there are different types of conversations, such as calls or emails, this value is unique for all conversation types. |
DIRECTION | varchar | NULL | INBOUND or OUTBOUND. Whether the email originated from a customer (inbound) or is an email to the customer (outbound) |
IS_AUTO_SUBMITTED | boolean | NULL | When true, indicates that the email is submitted automatically |
IS_MEETING_INVITE | boolean | NULL | When true, indicates the email is an invitation for a meeting |
OOO_RETURN_DATE | dateTime | NULL | Indicates the return date of an out of office email. NULL for non OOO emails. |
SENT_DATETIME | timestamp_tz | NULL | The timestamp for when the email was sent |
WORKSPACE_IDS | array of strings | NULL | A list of the workspace IDs the email is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the email was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Gong_usage
The GONG_USAGE
table contains information on how team members use Gong on a daily basis. Each row contains the number of times an action was done on a specified day.
The table includes the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
USER_ID | varchar | Unchanged | The user’s Gong ID |
USER_NAME | varchar | NULL | The user’s full name |
USAGE_DATE | timestamp_tz | NULL | The date the usage data is for |
RECORDED_CALLS | integer | NULL | Number of calls recorded in Gong for this user |
CALLS_LISTENED_TO | integer | NULL | Number of calls the user listened to in Gong |
MINUTES_LISTENED_TO_CALLS | integer | NULL | Number of minutes the user listened to calls in Gong |
REVIEWED_CALLS | integer | NULL | Number of calls the user reviewed |
SHARED_CALLS | integer | NULL | Number of calls the user shared either internally or externally |
VIEWED_CALL_SPOTLIGHT | integer | NULL | Number of calls the user viewed the call spotlight for |
INTERACTED_WITH_CALL_SPOTLIGHT | integer | NULL | Number of calls the user did an action on the call spotlight such as clicking, moving between tabs or scrolling |
COMMENTED_ON_CALLS | integer | NULL | Number of comments the user made on calls |
ASKED_ANYTHING_ABOUT_A_CALL | integer | NULL | Number of questions the user asked anything about a call |
CALL_SCORECARDS_GIVEN | integer | NULL | Only shows data if the user is a manager. Number of scorecards the user filled in. |
REVIEWED_PIPELINE | integer | NULL | Number of times the user clicked on anything in the deal page |
CONDUCTED_FOLLOW_UP_STEPS | integer | NULL | Number of follow-up steps such as inline edits, the user did on a deal |
INSPECTED_DEALS | integer | NULL | Number of deals the user looked at in detail (opened the deal panel) |
REVIEWED_DEAL_ANALYTICS | integer | NULL | Number of times the user viewed one of the deal analytics reports (win/loss, deal drivers) |
ASKED_ANYTHING_ABOUT_A_DEAL_OR_ACCOUNT | integer | NULL | Number of questions the user asked anything about a deal or account |
VIEWED_ANALYTIC_REPORTS | integer | NULL | Number of times the user viewed a report in Insights |
VIEWED_INITIATIVE_BOARDS | integer | NULL | Number of times the user viewed an initiative board |
REVIEWED_FORECAST | integer | NULL | Number of times the user did an action in the Forecast page, not including loading the page |
SUBMITTED_FORECASTS | integer | NULL | Number of times the user submitted or updated a forecast |
USED_FORECAST_ANALYTICS | integer | NULL | Number of times the user performed an action in the Forecast analytics page, not including loading the page |
SENT_EMAILS_VIA_GONG | integer | NULL | Number of emails the user sent via the Gong email composer |
CALLED_WITH_GONG_DIALER | integer | NULL | Number of calls the user made with the Gong dialer |
ADDED_PEOPLE_TO_FLOWS | integer | NULL | Number of times the user added a person to a flow in Engage |
COMPLETED_TO_DOS | integer | NULL | Number of Engage to-dos completed |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table |
Meetings
The MEETINGS
table contains a row for each calendar meeting. Meetings may or may not have an associated call. When a meeting includes a call, the call_conversation_key
contains the key for the call. For details on meetings, see View meetings without scheduled recordings . The MEETINGS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
CALL_CONVERSATION_KEY | varchar | NULL | The conversation key of the call for the meeting. Null when there is no call associated with the meeting. |
CALL_ID | varchar | NULL | The call ID |
CONVERSATION_ID | varchar | NULL | The Gong conversation id. This ID does not have to be unique. A meeting can have the same CONVERSATION_ID as a call. However, two conversations of the same type cannot have the same CONVERSATION_ID. |
CONVERSATION_KEY | varchar | Unchanged | The primary key for the meeting in Snowflake. (Unique) |
CREATED_DATETIME | timestamp_tz | NULL | The date and time the meeting created |
END_DATETIME | timestamp_tz | NULL | The date and time the meeting is schedule to end |
IS_ALL_DAY | boolean | NULL | When true, indicates the meeting will last the whole day |
IS_CANCELED | boolean | NULL | When true, indicates the meeting was cancelled |
IS_INTERNAL | boolean | NULL | When true, indicates the meeting is internal |
IS_RECURRING | boolean | NULL | When true, sets that this is a recurring meeting |
MODIFIED_DATETIME | timestamp_tz | NULL | The last date and time the meeting was modified |
ORGANIZER_USER_ID | varchar | NULL | The Gong user ID of the person who organized the meeting |
START_DATETIME | timestamp_tz | NULL | The date and time the meeting is scheduled to start |
TITLE | varchar | NULL | The title of the meeting |
WORKSPACE_IDS | array of strings | NULL | A list of the workspace IDs the meeting is associated with |
IS_DELETED | boolean | Unchanged | Indicates whether the meeting was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Conversation_participants
The CONVERSATION_PARTICIPANTS
table contains a row for each email recipient and a row for each call or meeting participant. The CONVERSATION_PARTICIPANTS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
AFFILIATION | varchar | Unchanged | The company the participant is affiliated with. Options are:
|
ASSOCIATED_OBJECT_TYPE | varchar | NULL | The object type of the participant in the CRM. Options are:
|
CONVERSATION_KEY | varchar | Unchanged | The key for the conversation the call is associated with. (Unique) |
EMAIL_ADDRESS | varchar | NULL | The email address of the participant |
FIELDS_SNAPSHOT | variant | NULL | A snapshot of the object's fields, that are imported to Gong, at the time of the conversation, excluding those in the |
INVITEE_STATUS | varchar | Unchanged | The invitees response to the meeting invitation. Null when conversation is not a meeting. Options are:
|
MAPPED_FIELDS_SNAPSHOT | variant | NULL | Gong maps some fields in the CRM to other fields. For a list of mapped fields per CRM object see mapped fields |
NAME | varchar | NULL | The name of the participant in the conversation |
PHONE_NUMBER | varchar | NULL | The phone number of the participant |
SPEAKER_ID | varchar | NULL | The ID of the person speaking as listed in the call transcript. Transcripts are found in the |
TYPE | varchar | Unchanged | The participant type or role in the conversation. For emails options are:
For calls options are:
For meetings options are:
|
USER_ID | varchar | Unchanged | The participant's Gong user ID. Null if they are not a Gong user. |
IS_DELETED | boolean | Unchanged | Indicates whether the participant was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) | timestamp_tz | See ETL_MODIFIED_DATETIME instead | |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Comments
The COMMENTS
table contains a row for each public comment made on a call. The COMMENTS
table includes the following:
Column name | Type | Value on delete | Description |
---|---|---|---|
COMMENT_ID | varchar | Unchanged | The Id of the comment |
COMMENT | varchar | NULL | The comment |
COMMENT_TYPE | varchar | The type of comment | |
CONVERSATION_KEY | varchar | Unchanged | The unique identifier for the call the comment is associated with. (Unique) |
CREATED_DATETIME | timestamp_tz | NULL | The date and time the comment was made |
IS_DELETED | boolean | Unchanged | When true, the comment was deleted |
MENTIONS | array of varchars | NULL | A list of users tagged in the comment. Ids are separated with a comma |
REPLY_TO_COMMENT_ID | varchar | NULL | ID of the original comment this comment is replying to. |
TAGS | varchar | NULL | A list of tags set for the comment. Tags are phases prefixed with a #. Each tag in the list is separated with a comma |
TIME_IN_CALL_SEC | float | NULL | The time in the call the comment was made, in seconds. |
USER_ID | varchar | NULL | The Gong user ID for the person who made the comment. |
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Forecast_submissions
The FORECAST_SUBMISSIONS
table contains the most current team and individual forecasts submissions. To see previous submissions use the FORECAST_SUBMISSIONS_HISTORY
table.
Note:
This table shows manual user submissions. As forecasts in Gong may also include automated submissions, you may see forecast submissions in Gong which are not exported to Snowflake.
The table contains the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
FORECAST_AMOUNT_UNIT | varchar | NULL | The unit the forecast was made in |
FORECAST_CATEGORY_NAME | varchar | NULL | The forecast category according to the values defined in the forecast board |
IS_TEAM | boolean | NULL | When true, the forecast is a team forecast |
LINE_OF_BUSINESS | varchar | NULL | The name of the line of business the forecast is for |
LINE_OF_BUSINESS_ID | varchar | Unchanged | The Gong ID for the line of business |
NOTES | varchar | NULL | Notes the Gong user made on the forecast submission |
PERIOD_NUMBER | integer | NULL | The number representing the period the forecast is for. For example, if the forecast is for Q3, this value is 3. If the forecast is for August, this value is 8. |
PERIOD_TYPE | varchar | NULL | The period the forecast covers. Options are:
|
PERIOD_YEAR | integer | NULL | The fiscal year the forecast covers |
SUBMIT_DATE | timestamp_tz | NULL | The date the forecast was submitted |
SUBMIT_BY_USER_ID | varchar | NULL | The Gong user id of the user who submitted the forecast |
SUBMISSION_TYPE | |||
USER_ID | varchar | NULL | The user Id of the Gong user the forecast is for. If a manager submits a forecast for their team member, the USER_ID is the user Id of the team member. If the forecast is a team forecast, this is the team manager's user Id. |
VALUE | float | NULL | The forecast value |
WEEK | integer | NULL | The week during the quarter that the forecast was submitted |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Forecast_submissions_history
The FORECAST_SUBMISSIONS_HISTORY
table contains current and previous team and individual forecasts submissions. Use the SUBMIT_DATE
to determine which is the most recent submission.
Note:
This table shows manual user submissions. As forecasts in Gong may also include automated submissions, you may see forecast submissions in Gong which are not exported to Snowflake.
The table contains the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
FORECAST_AMOUNT_UNIT | varchar | NULL | The unit the forecast was made in |
FORECAST_CATEGORY_NAME | varchar | NULL | The forecast category according to the values defined in the forecast board |
IS_TEAM | boolean | NULL | When true, the forecast is a team forecast |
LINE_OF_BUSINESS | varchar | NULL | The name of the line of business the forecast is for |
LINE_OF_BUSINESS_ID | varchar | Unchanged | The Gong ID for the line of business |
NOTES | varchar | NULL | Notes the Gong user made on the forecast submission |
PERIOD_NUMBER | integer | NULL | The number representing the period the forecast is for. For example, if the forecast is for Q3, this value is 3. If the forecast is for August, this value is 8. |
PERIOD_TYPE | varchar | NULL | The period the forecast covers. Options are:
|
PERIOD_YEAR | integer | NULL | The fiscal year the forecast covers |
SUBMIT_DATE | timestamp_tz | NULL | The date the forecast was submitted |
SUBMIT_BY_USER_ID | varchar | NULL | The Gong user id of the user who submitted the forecast |
USER_ID | varchar | NULL | The user Id of the Gong user the forecast is for. If a manager submits a forecast for their team member, the USER_ID is the user Id of the team member. If the forecast is a team forecast, this is the team manager's user Id. |
VALUE | float | NULL | The forecast value |
WEEK | integer | NULL | The week during the quarter that the forecast was submitted |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Forecast_targets
The FORECAST_TARGETS
table contains targets set for each team or for specific users. The table contains the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
IS_TEAM | boolean | NULL | When true, the target is a team target |
LINE_OF_BUSINESS | varchar | NULL | The name of the line of business the forecast is for |
LINE_OF_BUSINESS_ID | varchar | Unchanged | The Gong ID for the line of business |
PERIOD_NUMBER | integer | NULL | The number representing the period the forecast is for. For example, if the forecast is for Q3, this value is 3. If the forecast is for August, this value is 8. |
PERIOD_TYPE | varchar | NULL | The period the forecast covers. Options are:
|
PERIOD_YEAR | integer | NULL | The fiscal year the forecast covers |
SUBMIT_DATE | timestamp_tz | NULL | The date the forecast was submitted |
SUBMIT_BY_USER_ID | varchar | NULL | The Gong user id of the user who submitted the forecast |
TARGET_AMOUNT_UNIT | varchar | NULL | The currency code the forecast is submitted in |
USER_ID | varchar | NULL | The user Id of the Gong user the forecast is for. If a manager submits a forecast for their team member, the USER_ID is the user Id of the team member. If the forecast is a team forecast, this is the team manager's user Id. |
VALUE | float | NULL | The forecast value |
IS_DELETED | boolean | Unchanged | Indicates whether the conversation was deleted in Gong. Values are:
|
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Scorecard_questions
The SCORECARD_QUESTIONS
table contains a row for each question in a scorecard. The row includes the scorecard data such as the scorecard name and the date it was created. The answers for the questions are stored in the SCORECARD_ANSWERS
table. The table contains the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
IS_DELETED | boolean | Unchanged | Indicates whether the scorecard or the question were deleted |
QUESTION_CREATED_DATETIME | timestamp_tz | NULL | The date and time the question was defined |
QUESTION_ID | varchar | Unchanged | The Id of a question included in the scorecard |
QUESTION_IS_OVERALL_SCORE | boolean | NULL | Indicates whether the question enables providing an overall assessment of the call |
QUESTION_MAX_RANGE | number | NULL | For questions with a numerical score, the maximum number that can be chosen |
QUESTION_MIN_RANGE | number | NULL | For questions with a numerical score, the minimum number that can be chosen |
QUESTION_MODIFIED_BY_USER_ID | varchar | NULL | The Id of the user who modified the question |
QUESTION_MODIFIED_DATETIME | timestamp_tz | NULL | The date and time the question was last modified |
QUESTION_RESPONSE_OPTIONS | variant | NULL | The possible options in a multiple choice question |
QUESTION_TEXT | varchar | NULL | The text of the question |
QUESTION_TYPE | varchar | NULL | The type of question. Options are:
|
SCORECARD_CREATED_DATETIME | timestamp_tz | NULL | The date and time the scorecard was created |
SCORECARD_ID | varchar | Unchanged | The scorecard Id |
SCORECARD_IS_ENABLED | boolean | NULL | Indicates whether the scorecard is enabled or not |
SCORECARD_MODIFIED_BY_USER_ID | varchar | NULL | The Id of the Gong user who last modified the scorecard |
SCORECARD_MODIFIED_DATETIME | timestamp_tz | NULL | The date and time the scorecard was last modified |
SCORECARD_NAME | varchar | NULL | The scorecard title |
WORKSPACE_ID | varchar | NULL | The Id of the workspace the scorecard is associated with |
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was modified |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |
Scorecard_answers
The SCORECARD_ANSWERS
table contains a row for each answer given in the scorecard. The row includes scorecard details, the question details and the answer given. The table contains the following fields:
Column name | Type | Value on delete | Description |
---|---|---|---|
ACCESSIBLE_TO | varchar | NULL | The users who have permissions to view the scorecard. Options are:
|
ANSWER_ID | varchar | Unchanged | The ID for the answer |
ANSWER_CREATED_DATETIME | timestamp_tz | NULL | The date and time the answer was created |
ANSWER_MODIFIED_DATETIME | timestamp_tz | The date and time the answer was last modified | |
ANSWER_NOT_APPLICABLE | boolean | Unchanged | Indicates if the answer is not applicable |
ANSWER_SELECTED_OPTIONS | array | NULL | The options selected in a multiple choice question |
ANSWER_SCORE | number | NULL | The score given to the question |
ANSWER_TEXT | varchar | NULL | The text of the answer |
CONVERSATION_KEY | varchar | Unchanged | The key for the conversation the scorecard is being filled in for |
GAVE_SCORECARD_USER_ID | varchar | NULL | The Id of the user who filled in the scorecard |
LAST_PUBLISHED_DATETIME | timestamp_tz | NULL | The date and time the answer was last published |
QUESTION_ID | varchar | NULL | The Id of the question |
QUESTION_IS_OVERALL_SCORE | boolean | NULL | Indicates whether the question enables providing an overall assessment of the call |
QUESTION_MAX_RANGE | number | NULL | For questions with a numerical score, the maximum number that can be chosen |
QUESTION_MIN_RANGE | number | NULL | For questions with a numerical score, the minimum number that can be chosen |
QUESTION_RESPONSE_OPTIONS | variant | NULL | The possible options in a multiple choice question |
QUESTION_TEXT | varchar | NULL | The text of the question |
QUESTION_TYPE | varchar | NULL | The type of question. Options are:
|
RECEIVED_SCORECARD_USER_ID | varchar | NULL | The Id of the user who the scorecard was for |
SCORECARD_ID | varchar | Unchanged | The scorecard Id. FK from the SCORECARD_QUESTIONS table. |
SCORECARD_NAME | varchar | NULL | The name of the scorecard |
WORKSPACE_ID | varchar | NULL | The Id of the workspace the scorecard is associated with |
ETL_MODIFIED_DATETIME | timestamp_tz | Unchanged | The date and time the data was changed |
ROW_ID | varchar | Unchanged | The ID to identify the row in the table. |