This section details the tables and columns available in the Gong-Snowflake database.
Conversations
The CONVERSATIONS
table contains a row for each conversation. A conversation can be an email or a call. The CONVERSATIONS
table includes the following:
Column name |
Type |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
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_ID |
varchar |
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. |
WORKSPACE_IDS |
array (string) |
The IDs of the workspaces the conversation is associated with |
CONVERSATION_TYPE |
varchar |
The type of the conversation. Either call or email. |
CONVERSATION_DATETIME |
timestamp_tz |
The date and time the conversation occured |
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
Calls
The CALLS table contains a row for each call in the system, including scheduled calls that have not yet taken place. The CALLS
table includes the following:
Column name |
Type |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
The key for the conversation the call is associated with. (Unique) |
OWNER_ID |
number |
The owner of the call. (Foreign key, |
TITLE |
varchar |
The title of the call |
PLANNED_START_DATETIME |
timestamp_tz |
The date and time the call was planned to start. |
PLANNED_END_DATETIME |
timestamp_tz |
The date and time the call was planned to end. |
EFFECTIVE_START_DATETIME |
timestamp_tz |
The actual start date of the call |
CALL_URL |
varchar |
The URL for the call |
STATUS |
varchar |
Some reports might want to exclude or include calls based on their status. Possible values:
|
IS_PRIVATE |
boolean |
True if the call is a private call |
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
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 |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
The key for the conversation the call is associated with (Unique) |
DURATION |
number |
The duration of the call (in seconds) |
START_DATETIME |
timestamp_tz |
The actual start date and time of the call |
END_DATETIME |
timestamp_tz |
The actual date and time the call ended |
MEDIA_TYPE |
varchar |
Sets the media for the call. Options are:
|
LANGUAGE |
varchar |
The code for the language the call was made in |
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
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 |
Description |
---|---|---|
USER_ID |
number |
The ID of the user in Gong (unique). |
EMAIL_ADDRESS |
varchar |
The user's email address |
FIRST_NAME |
varchar |
The user's first name |
LAST_NAME |
varchar |
The user's last name |
TIME_ZONE |
varchar |
The timezone the user is in (TZ format, such as America/New_York) |
LOCALE |
varchar |
The user's locale |
MANAGER_ID |
varchar |
The id of the employee's manager |
TITLE |
varchar |
The employee's job title |
ACTIVE |
boolean |
Sets whether the user is active. Users are not deleted from the system, they become inactive |
LICENSED |
boolean |
Indicates whether the user has a paid license |
SHOULD_RECORD_WEB_CONFERENCE_CALLS |
boolean |
Indicates whether the user's web conference calls should be automatically recorded |
SHOULD_SYNC_EMAILS |
boolean |
Indicates whether the user's emails should be automatically imported to Gong |
SHOULD_IMPORT_TELEPHONY_CALLS |
boolean |
Indicates whether the user's calls recorded by an external telephony system should be automatically recorded and imported into Gong |
VALID_FROM_DATE_TIME |
timestamp_ntz |
(SCD type 2.0) The date the user started this position |
VALID_TO_DATE_TIME |
timestamp_ntz |
(SCD type 2.0) The date the user ended this position. A null value indicates that this is the current value for the user. |
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was changed |
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 |
Description |
---|---|---|
USER_ID |
number |
The ID of the user in Gong (unique). |
CRM_ID |
varchar |
The Gong user's ID in the CRM |
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 |
Description |
---|---|---|
USER_ID |
number |
The ID of the user who had the activity (from the users table) |
CONVERSATION_KEY |
varchar |
The ID of the conversation the user made the activity on (from the conversations table) |
GONG_ACTIVITY_DATETIME |
timestamp_tz |
The date and time of the activity |
GONG_ACTIVITY_TYPE |
varchar |
The activity type. Options are:
|
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
Workspaces
The WORKSPACES
table contains a list of the workspaces in your org and includes the following:
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 |
Description |
---|---|---|
WORKSPACE_ID |
varchar |
The workspace the tracker is associated with |
TRACKER_ID |
varchar |
The unique tracker ID |
NAME |
varchar |
The name of the tracker, such as Pricing. |
KEYWORDS |
varchar |
The list of keywords in the tracker (JSON array). |
TRACKER_TYPE |
varchar |
The tracker type:
|
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
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 |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
The ID for the conversation (foreign key) |
TRACKER_ID |
varchar |
The tracker ID (foreign key) |
WORKSPACE_ID |
varchar |
The workspace the tracker is associated with |
COUNT |
int |
The number of times the tracker occurs. |
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
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 |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
The key for the conversation |
OBJECT_ID |
varchar |
The ID of the object in the CRM |
OBJECT_TYPE |
varchar |
The object type. Options are (in lowercase):
|
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
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 |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
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_ID |
varchar |
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. |
WORKSPACE_IDS |
array of strings |
A list of the workspace IDs the email is associated with |
SENT_DATETIME |
datetime_tz |
The timestamp for when the email was sent |
DIRECTION |
varchar |
INBOUND or OUTBOUND. Whether the email originated from a customer (inbound) or is an email to the customer (outbound) |
IS_MEETING_INVITE |
boolean |
When true, indicates the email is an invitation for a meeting |
OOO_RETURN_DATE |
dateTime |
Indicates the return date of an out of office email. NULL for non OOO emails. |
AUTO_SUBMITTED_TYPE |
varchar |
Indicates the type of email for auto generated emails. Options are:
|
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |
Conversation_participants
The CONVERSATION_PARTICIPANTS table contains a row for each email recipient. Call participants are currently not included. The CONVERSATION_PARTICIPANTS
table includes the following:
Column name |
Type |
Description |
---|---|---|
CONVERSATION_KEY |
varchar |
The key for the conversation the call is associated with. (Unique) |
NAME |
varchar |
The name of the participant in the conversation |
EMAIL_ADDRESS |
varchar |
The email address of the participant |
TYPE |
varchar |
The participant type or role in the conversation. For emails options are:
|
AFFILIATION |
varchar |
The company the participant is affiliated with. Options are:
|
USER_ID |
number |
The participants Gong user ID. Null if they are not a Gong user. |
ETL_MODIFIED_DATETIME |
timestamp_tz |
The date and time the data was modified |
ROW_LOAD_DATETIME (deprecated) |
timestamp_tz |
See ETL_MODIFIED_DATETIME instead |