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 and emails 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
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.
Details about emails are stored in the
CONVERSATION_PARTICIPANTS tables. Conversation participants for both calls and emails are stored in the
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
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.