Quantive

Last updated on Jan 23, 2023

Quantive (formerly known as Gtmhub), allows organizations to achieve their strategic potential. It helps companies increase revenue growth by supporting the synchronization of individual and team performance.
You can replicate the data from your Quantive account to a Destination database or data warehouse using Hevo Pipelines. Quantive uses an account ID and API token to identify Hevo and authorize the request for accessing account data. Hevo ingests the data in Full Load mode. Refer to section, Data Model for the list of supported objects.


Prerequisites

  • An active Quantive account from which data is to be ingested exists.

  • The Account ID and API Token are available to authenticate Hevo on your Quantive account.

  • You are logged in as an Admin user, to obtain the account ID and API token. Else, you can obtain these from your administrator. Read User Types to know about the different types of user accounts and permissions related to them in Quantive.


Obtaining the Account ID and API Token

Hevo uses an account ID and API token to authenticate itself on your account. These credentials do not expire and can be reused for all your Pipelines.

Note: You must be logged in as an Admin user to perform these steps.

  1. Log in to your Quantive account.

  2. In the Overview page, click Settings in the left pane.

    Settings

  3. In the Settings page, Configuration tab, select API Tokens.

    Config-tab-API-Tokens

  4. In the API Tokens page, do one of the following:

    • Create an API token:

      1. Click Issue token to create an API token.

        Issue-token

      2. In the pop-up dialog, specify a unique name for this API token, and click Generate API Token.

        Generate-API-Token

      3. In the API Tokens page, click Copy to copy the Account ID and save it securely like any other password.

        Account-ID

      4. In the API Tokens page, hover over the API TOKEN field and click Copy to copy the API token and save it like any other password.

        API-token

    • Use an existing access token:

      1. In the API Tokens page, click Copy to copy the Account ID and save it securely like any other password.

        Account-ID

      2. In the API Tokens page, hover over the API TOKEN field and click Copy to copy the API token and save it like any other password.

        API-token

You can use these credentials while configuring your Pipeline.


Configuring Quantive as a Source

Perform the following steps to configure Quantive as the Source in your Pipeline:

  1. Click PIPELINES in the Asset Palette.

  2. Click + CREATE in the Pipelines List View.

  3. In the Select Source Type page, select Quantive.

  4. In the Configure your Quantive Source page, specify the following:

    Source-Config

    • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

    • API token: The API Token that you obtained and copied from your Quantive account.

    • Account ID: The account ID of the account from which data is to be ingested.

    • Region: The region in which your Quantive account resides.

  5. Click TEST & CONTINUE.

  6. Proceed to configuring the data ingestion and setting up the Destination.


Data Replication

Default Ingestion Frequency Minimum Ingestion Frequency Maximum Ingestion Frequency Custom Ingestion Range (Hrs)
1 Hr 1 Hr 24 Hrs 1-24

Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

Hevo fetches all the objects in Full Load mode in each run of the Pipeline.


Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination database:


Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object Description
Assignees Contains details of the user (or team) to whom an objective or task has been assigned.
Badges Contains details of all the recognition a user has received from colleagues for their work.
DashboardParameters Contains details of all the objectives and tasks, such as, their assignees, and time required to finish them. These allow you to filter the objectives and tasks and get more clarity about their progress.
Dashboards Contains the list of all the objectives or tasks grouped together according to their status. Dashboard is a centralized hub for accessing and managing your objectives and tasks.
Employees Contains the list of all the employees in your organization.
KPIs (Key Performance Indicator) Contains details of the employees’ performance in completing the objectives.
KPI Groups Contains details of all the key performance indicators (KPIs) grouped together for better performance evaluation.
Key Results Contains details of all the milestones that an assignee needs to complete in order to accomplish a task or objective.
Lists Contains the list of all the objectives, key results, and tasks.
Objectives Contains details of the tasks assigned to employees within your organization.
Roles Contains the list of roles available to users in your Quantive account.
Score Policies Contains the list of the policies associated with an OKR score.
Sessions Contains details of the time period in which a group of tasks or objectives are meant to be achieved.
Tags Contains the list of labels that can be attached to tasks in Quantive.
Tasks Contains details of the tasks assigned to employees within your organization.
Teams Contains details of all the user groups in a workspace who work toward accomplishing a common objective.
Team Report Contains details about the team’s performance.
Users Contains list of users who can access your Quantive workspace.
User Report Contains details about the individual user performance.

Source Considerations

  • Pagination: An API response for each Quantive Results object fetches one page with up to 100 records.

  • Rate limit: Quantive imposes a limit of 100 API calls per minute to ensure that their system remains stable for usage by all users. Read API Rate Limits to know more about rate limits in Quantive, and configure a suitable ingestion frequency for your Pipeline.


Limitations

  • Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.

  • Hevo does not provide you with the option to select the historical sync duration for loading historical data. All the historical data in your Quantive account is loaded.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Jan-23-2023 2.06 New document.

Tell us what went wrong