Database design

This diagram shows the relationship between conversations and other entities such as users and stats:

The following diagram displays the relationships between the tables representing conversation data including emails and calls.

The database lets you see call details such as the date and time of the call as well as any activities performed on the call, such as comments and feedback, or whether the call was shared.

Calls, emails, and meetings are stored in the CONVERSATIONS table, where they are associated with a workspace and given a conversation type. Details relevant only to calls, such as the URL for the call are stored in the CALLS table. Each call is saved once in the CALLS table and is associated with the CONVERSATIONS table using the CONVERSATIONS_KEY. The CALLS table includes details of the call spotlight.

Once the call has been recorded it is added to the CALL_RECORDINGS table, with details such as the language the call took place in and the duration of the call. Any activities done on the call, such as feedback or comments are stored in the USER_CONVERSATION_GONG_ACTIVITIES table. The USER_CONVERSATION_GONG_ACTIVITIES table holds the ID of the user who did the activity, as well as the date and time and the activity type.

Email and meeting details are stored in the EMAILS and MEETINGS tables respectively. Call, email, and meeting participants are found in the CONVERSATION_PARTICIPANTS table.

The CALL_TRANSCRIPT table contains a JSON of the transcript. The call is split up according to who spoke when during the conversation. The JSON includes a speaker ID which represents the person speaking at that time. Comments made on calls are available in the COMMENTS table.

All users are stored in the USERS table which includes user details such as their first name, last name and email address. This table maintains history for the user so you can see details such as who was a manager when a specific call took place. In addition, to support the situation where a Gong user has multiple CRM IDs, the USER_CRM_IDS table contains the CRM IDs for each user.

Trackers are tools that identify when words, phrases or concepts are mentioned in calls and emails, allowing you to know what your reps and customers are talking about. Smart trackers and keyword trackers are stored in the TRACKERS table and each tracker identified in a conversation is added to the CONVERSATIONS_TRACKERS table.

You can see data on who has filled out scorecards and their assessment of the call. The SCORECARD_QUESTIONS table contains a row for each question in the scorecard together with the scorecard details, such as the scorecard name and when it was created. The SCORECARD_ANSWERS table contains a row for each question and answer given and includes the Id of the call the scorecard was given for.

You can associate your CRM objects, such as opportunities, deals, or leads, with your Gong conversations using the CONVERSATION_CONTEXTS table. A conversation can be associated with multiple CRM objects. For example, a conversation can be associated with a deal or opportunity and an account.

You can get statistics on your reps activities and how they manage calls in the USER_CONVERSATION_GONG_ACTIVITIES and INTERACTION_STATS. These tables give you details on what kind of actions a user did on a call, such as asking for feedback and statistics on metrics such as how long they speak on a call or how many questions they ask.

Getting Forecast data

The following diagram displays the relationships between the tables containing forecast data:

Forecast data includes forecast submissions and targets.

In the FORECAST_SUBMISSIONS and FORECAST_TARGETS tables, you can see each user's forecast and targets for a specific period. These can be for an individual sales rep, or for a team. When the value is the team forecast or target, the IS_TEAM field is set to true. The period the forecast or target is for is set according to the PERIOD_TYPE, PERIOD_YEAR and PERIOD_NUMBER. The period type designates whether the forecast is for a month or a quarter, the period year sets the year and the period number sets which quarter or month in the year the forecast and target are for.

Note:

The FORECAST_SUBMISSIONS table shows manual submissions only. As forecasts in Gong may also include automated submissions, there may be discrepancies between the forecast submissions in Gong and the forecast submission data in the Gong data cloud.

Deal likelihood scores

Gong assesses each deal and gives it a score indicating how likely the deal will be closed-won in its expected quarter compared to other deals in the pipeline. The DEAL_LIKELIHOOD_SCORES  table contains each deal’s score, score category (Low, Fair, or High) and the last time the score was updated. The details of a deal can be retrieved from the CRM using the CRM_DEAL_ID.