Gong Data Cloud

All trackers are now exported to the data cloud. Previously only trackers with a status of published or deactivated were exported. The export is applied retroactively to existing trackers.

Multiple new metrics added to the GONG_USAGE table to track AI feature adoption:

• ASSISTANT_CHATS: Number of chats started by a user on a specific date
• THEME_SPOTTER_ANALYSIS_GENERATED: Number of AI Theme Spotter analyses generated by a user -…

Seven new AI metrics were added to the GONG_USAGE table: ASSISTANT_CHATS, THEME_SPOTTER_ANALYSIS_GENERATED, THEME_SPOTTER_ANALYSIS_USED, MEETING_PREPARATION_USED, PRACTICES_STARTED, TRAININGS_SUBMITTED, and TRAININGS_STARTED. The __NEXT fields have been removed from all Gong Data Cloud tables.

The following metrics were added to the GONG_USAGE table:

The following changes were made:

The following changes were made:

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.

The following changes were made:

• 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…

The following changes were made to the GONG_USAGE 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 -…

• 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…

The following was added:

• 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,…

• 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…

• 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…

• 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…

• 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.