Data Cloud Updates

The following changes were made:

• For BigQuery, Databricks, Redshift, and S3 data warehouses/destinations, numeric fields that were configured as decimals are now defined as BIGINT. For a list of fields, see Numeric field type updates in the Gong data cloud. The __NEXT fields will be deleted in June.
• You can now connect Snowflake to more than one instance of Gong. Each Gong instance is a separate database in Snowflake.

The following changes were made:

• USERS table: The HOME_WORKSPACE_ID field was added.
• Forecast submission data is now updated once an hour.
• The Spotlight usage columns have been removed from the GONG_USAGE table. For more details, see Call brief metrics instead of spotlight usage data.

For BigQuery, Databricks, Redshift, and S3 data warehouses/destinations, some numeric fields that should be integers are currently configured as decimal types. These fields have been duplicated, given the suffix of __NEXT and are set as integers.

In May 2026, the type of the original fields will be updated to integer, and the duplicated __NEXT fields will be removed. For more details, see Numeric field type updates in the Gong data cloud.

The following changes were made:

• CALLS table: The SKIP_REASON field was added. For details on the skip reasons, see Skip codes for unrecorded calls.
• CONVERSATION_TRACKERS table: Data about deleted keyword trackers is now reflected.
• MEETINGS table: A new record is now added for each meeting that occurs as part of a series of recurring meetings.
• USER_CONVERSATION_GONG_ACTIVITIES table: The recieved_scorecard value in the GONG_ACTIVITY_TYPE field has been removed.

• Improved navigation: Access to data cloud integrations is now via a single entry point in the Admin center. Learn more
• Deprecate END_TIMETIME in CALL_RECORDING table: The END_TIMETIME column is being deprecated and will be deleted in February 2026. Use END_DATE_TIME instead.

The following changes were made to the GONG_USAGE table:

• The had_gong_activity field was added. When true, it indicates that the user was active in Gong on that date, even if the action was not captured by existing metrics.
• Records where all metrics were zero/null were removed from the table.

• The GONG_USAGE table includes details of how team members use features such as asking anything and briefs. The new columns are:
  • ACCOUNTS_ASKED_ANYTHING
  • ACCOUNTS_WITH_BRIEFS_VIEWS
  • AI_EMAILS_GENERATED
  • CALLS_ASKED_ANYTHING
  • CALLS_WITH_BRIEFS_VIEWS
  • CONTACTS_ASKED_ANYTHING
  • CONTACTS_WITH_BRIEFS_VIEWS
  • DEAL_BOARD_WITH_PLAYBOOK_VIEWS
  • DEALS_WITH_BRIEFS_VIEWS
  • PLAYBOOK_FIELDS_AI_SUGGESTIONS_USED
  • PLAYBOOK_FIELDS_MANUAL_UPDATES
• The FORECAST_SUBMISSIONS_HISTORY and FORECAST_SUBMISSIONS tables now include forecast submissions that are automated by Gong. The submission types are:
  • AUTOSUM
  • AUTOFILL
  • CARRY_OVER
• Missing keyword tracker data for emails added to CONVERSATION_TRACKERS table: Some keyword tracker data for emails was not available in the Gong data cloud. The table has been updated with the missing historical data. The data includes keyword trackers that have been deleted.

• Schema cleanup: We've removed some redundant columns from tables in Redshift, S3, Databricks, and BigQuery. If you were using any of these columns in your queries, refer to the Gong database reference and replace them as needed.

• Changes to the SCORECARD_ANSWERS table: To support scorecards that can be answered by Gong AI:
  • The GAVE_SCORECARD_USER_ID column is empty when Gong AI answers the question.
  • The IS_AUTO_SCORECARD field was added to indicate whether the scorecard can be answered by Gong AI. When true, it can be answered both by Gong AI and manually. When false, all questions must be answered manually.
• Duplicate rows in CONVERSATION_PARTICIPANTS table removed: We fixed an issue that caused duplicate row IDs to appear in the conversation_participants table. The duplicates have been removed.
• Changes to the USER_CRM_IDS table: When deleting the mapping between a gong user ID and a CRM ID, if there were multiple entries for the gong user, all records are deleted, apart from one, where the gong user ID is changed to 0.

The following was added:

• Gong data in Redshift and S3: Make your Gong data available in Redshift and S3 where you can then connect to your preferred BI tool.
• Improved tracker data: Changes were made to the following tables:
  • TRACKERS table: the is_deleted field is set to true when either a phrase or the entire smart/keyword tracker is deleted
  • CONVERSATION_TRACKERS table:
    • The is_deleted field is set to true when either a phrase or the entire smart/keyword tracker is deleted
    • Improved logic for identifying the relevant smart tracker for a phrase in a call

• The DEAL_LIKELIHOOD_SCORES table was added. Provides the most recent deal likelihood score for each deal in the CRM.

• FORECAST_SUBMISSIONS_HISTORY table: Table populated with previous and current forecast submissions.
• PERIOD_YEAR field: The PERIOD_YEAR field now represents your fiscal year instead of the calendar year. This field is in the FORECAST_SUBMISSIONS, FORECAST_SUBMISSIONS_HISTORY and FORECAST_TARGETS tables.
• ROW_ID: The ROW_ID column added to each table is no longer in beta and can be used.

• Gong data in BigQuery and Databricks: Make your Gong data available in BigQuery and Databricks where you can then connect to your preferred BI tool. Learn more
• gong_usage table: The gong_usage table was added to provide data on how your users are using Gong.

• Calls table: To enable exporting data from all telephony calls to Snowflake, the PHONE_NUMBER and CALL_CONNECTED columns were added.
• Call_participants table: To enable exporting data from all telephony calls to Snowflake, the PHONE_NUMBER column was added.
• All tables: The ROW_ID column was added to all tables to enable support for exporting Gong data to other data warehouses. This is currently in beta and should not be used.

• Comments table: The mentions and tags fields were added. The mentions field contains the Gong userId of all users mentioned in the comment with a @ sign. UserIds are separated by a comma. The tags field contains all phrases in the comment that start with a #. Each tag is separated by a comma.
• Calls table: On March 15th, the source field will be deleted from the Snowflake database. Currently, the source field is deprecated and has been replaced with the source_system field. This is to avoid having fields named with terms which are reserved words in some data warehouses. Existing data in the source field will be copied to the source_system field.

• Conversation participants: The conversation_participants table now includes the speaker ID. This enables you to associate the participant's Gong user with everything they say in a call. The speakerId is the speaker of each monologue in the TRANSCRIPT table.

Indication of whether a record was deleted: Previously, deleted data was deleted from Snowflake. Now, records will no longer be deleted, instead they will be marked as having been deleted in Gong. The is_deleted field was added to the following tables:

• conversations
• conversation_contexts
• conversation_participants
• conversation_trackers
• interaction_stats
• meetings
• emails
• call_recordings

New data available in Snowflake: The following data is now available in Snowflake:

• Comments: Analyzing comments can be used to assess coaching quality, and also to filter calls with specific hashtags or tags. Public comments made on calls are now available in the COMMENTS table in Snowflake.

New data available in Snowflake: The following has been added:

• Call transcripts: You can now get call transcripts in Snowflake. Transcripts are saved in a JSON format in the new CALL_TRANSCRIPTS table.
• Call spotlight: Call spotlight details, including the call brief, outline, next steps, call outcome are now stored in the CALLS table.

• Ability to connect conversation participants with the relevant CRM contact: You can now connect conversation participants to the contact or lead in your CRM.

• Scorecard data now available: See who is filling in scorecards and how calls are scored for different reps. The SCORECARD_QUESTIONS and SCORECARD_ANSWERS tables were added to the Gong data cloud.
• Additional call data available: You can now get more detailed call information and run detailed analysis on calls. The following fields were added to the CALLS table:
  • direction
  • system
  • scope
  • disposition
  • call_owner_webcam_on_duration_sec
  • customer_webcam_on_duration_sec
  • company_question_count
  • customer_question_count