All Collections
Integrations
QuotaPath Integrations Overview
QuotaPath Integrations Overview

Learn about the types of integrations and how to setup

Updated over a week ago

QuotaPath supports integrations with many systems so you can automatically import data into your workspace to calculate commissions and determine payouts. You can connect multiple systems to import multiple data sources and types. There are two primary types of inbound data that can be integrated into your workspace: deal create and payouts eligibility.

Depending on the types of data you'll be importing and where the data is located, the implementation process will vary. Here is a process overview:

Keep reading for a detailed overview of the two types of data in QuotaPath and a step-by-step implementation guide.


Data Types

Deal Create

The first and required data type to use QuotaPath is the source used to create commissions records, or 'Deals'. This data can be used for all of the deal/compensation stages:

  • Closed Won: The commission has been earned and applied to quota attainment

  • Pipeline: The commission could be earned

  • Closed Lost: The commission has not been earned

This data can be combined, or joined, with the second data type, Payouts Eligibility, but it is not required.

Payouts Eligibility

The second data type, which is NOT required, is used to automate the conditions for when a commission is eligible to be paid out after it has already been closed won, or earned. For example, a commission may only be eligible to be paid out when a customer has paid their invoice, or when onboarding has been completed.

The conditions can be created from two types of fields:

  • Eligibility by Date (Date field): 1 or more date fields can be used to create the conditions for payout eligibility. For each date field, you can specify what percentage of the total earned commission is eligible to be paid out:

  • Eligibility by Invoice (Amount field): A single amount field can be used to automatically release the proportional amount of eligible commission. This works by comparing the eligible amount field to the original Deal Amount field. For example, if the Deal Amount is $5,000 and the payouts eligibility amount is $2,500, then 50% of the commissions will become eligible.


Implementation Overview

Step 1. Connect System

The first step in integrating your data sources is to connect the systems via oAuthentication. Navigate to Settings in the left hand navigation, and then to Integrations. From there, connect one or more systems for any deal create or payouts eligibility use cases.

Supported Systems

QuotaPath currently supports self-service authentication for the following systems for BOTH deal create and payouts eligibility use cases:

  • Salesforce

  • HubSpot

  • Close

  • Copper

  • Pipedrive

  • ZohoCRM

  • Quickbooks*

  • Stripe

  • Google Sheets

*Due to limitations with Quickbooks API, data MUST be combined with another system to provide required data for commissions calculations like the Deal Owner

QuotaPath also supports integrations with the following systems, but these must be connected with the help of the QuotaPath support team:

  • Netsuite

  • Snowflake

  • Maxio

  • Tableau

  • Smartsheets

  • Keap

  • Looker

  • Microsoft Excel/OneDrive

  • Leaflink

If different plans have different data sources, you can even connect more than two systems! However, every combination of deal create and payouts eligibility data from different object types in each system will need to be combined. For more information on combining data, keep reading below.

Visit the Connecting System section of the Integrations documentation for step-by-step guides on connecting each system.

Step 2. Identify Types of Data

After connecting all systems, you'll need to identify the types of data you'll be integrating into QuotaPath and the correct implementation process.

  1. If you will only be connecting for Deal Create, you do NOT need to join data. Proceed to Step 5 and starting syncing data to your plans.

  2. If you will be connecting data for both Deal Create and Payouts Eligibility and the data is from the same object in the same source, you do NOT need to join data. Proceed to Step 5 and starting syncing data to your plans.

  3. If you will be connecting data for both Deal Create and Payouts Eligibility, and the data is from different objects in the same source OR from different sources, you will need to join data. Proceed to Step 3 to identify how to connect the data.

Step 3. Identify Connecting ID

If you will be combining data from different objects in the same source OR from different sources for deal create and payout eligibility data, you'll need to identify a unique ID that associates the deal create record to the corresponding payout eligibility record(s).

An example would be combining Deal records in HubSpot to Invoice records in QuickBooks. A 'HubSpot ID' in Quickbooks could be used to match the Invoice back to the corresponding Deal in HubSpot.

There are two scenarios in which the data may be combined:

  • One:One - 1 Deal Create record corresponds to 1 Payout Eligibility Record

    • e.g. 1 Deal β†’ 1 Invoice

  • One:Many - 1 Deal Create record corresponds to Many Payout Eligibility Records

    • e.g. 1 Deal β†’ 4 Quarterly Invoices

Step 4. Combining Deal Create & Payouts Eligibility Data

After identifying the unique ID that will connect the deal create record to the payout eligibility record(s), the data will need to be combined by the QuotaPath support team.

Step 5. Syncing Plans to Data

After the data has been combined, you can proceed to the Plans page to start syncing data. The first step is to sync the data that will be used for Deal Create, and then after, you'll define the Payout Eligibility data and rules.

Visit the Syncing Data section of the Integrations documentation for step-by-step guides on syncing plans to each system.

Step 6. Define Payout Eligibility Rules

Once data has been synced for a path, you can then define the Payouts Eligibility rules, and the data source.

Did this answer your question?