Skip to content

Solution Integration Settings

In the Solution Integration Settings menu, you can configure and manage integrations between external solutions and the Hive Console. You can select a project to configure data transmission integration and sign-in authentication integration, enabling more efficient analysis and operations based on data collected from external solutions.

Currently, the Solution Integration feature supports ThinkingData integration, and additional solutions may be supported in the future.

ThinkingData

Check ThinkingData Integration Information

  1. Sign in to the Thinking Engine (TE) system and navigate to Project Management > Integration Settings for the project you want to integrate.
  2. Copy the APP_ID and the Data Collection Address > Public Network Address.
    1. This information is used only in Data Analytics Settings.

Enter Integration Information in the Hive Console

Data Analytics Settings

You can configure settings to send events and data to ThinkingData. If integration is disabled, data generated after the disablement will not be transmitted.

  • APP_ID: Enter the project-level APP_ID issued by ThinkingData.
  • Data Transmission Address: Enter the Public Network Address URL copied from ThinkingData.

Sign-in Integration Settings

Sign-in Integration Settings allow you to register and manage the authentication information required for sign-in integration with external solution programs. You can enter or issue the Redirect URL and authentication information required for sign-in integration and use them for integration.

  • Redirect URL: The page address to which users are redirected after completing authentication. You must enter the exact ThinkingData Console (Thinking Engine) URL for authentication to be processed correctly.
  • Authentication Information: Click the Create button to issue a Client ID and Client Secret. Provide the issued information to ThinkingData to complete the sign-in integration setup.
    • Click the copy icon on the right to easily copy the value.
    • Authentication information is managed at the company level. Once generated, the same authentication information is used across all projects within the same company.
    • This information must be managed securely to prevent external exposure.