Once an integration/data source has been successfully connected on the Integrations page, you can start syncing your built plans to your synced integration data.
QuotaPath refers to this as "mapping." Your mappings are the connection between your plans and your data that allows for accurate earnings and attainment calculation.
There are two ways in which you can use integration data -- for creating deals in order to calculate commissions or for informing when a commission is eligible for payout (Payout eligibility). For more information on the types of integrations and detailed definitions of Deal Create and Payouts Eligibility, please visit this article.
How map your plan components
Go to the Plans page in your QuotaPath workspace and click the plan you'd like to sync data to (i.e. map). All components that are NOT Quota or Draw components will need a mapping to generate earnings. The one possible exception would be a component built specifically for manual deal uploads.
Once on the plan details page, open a component and click 'Map data source':
In the pop-up modal, choose whether you would like to use an existing mapping, or create a new mapping. Mappings are individual assets that can be reused as many times as needed across your different plans and components. But remember, if a mapping is shared across multiple plans and components, making a change to it can potentially affect earnings and attainment across all plans and components.
If you want to use a previously existing mapping, or you want to start with an existing mapping as a template to create a new mapping, choose Use Existing Mapping. This is helpful for saving time and repurposing work you have already done.
Use Existing Mapping
If you choose to use an existing mapping, on the following screen select the mapping you'd like to use, or to start with as a template:
Next, choose whether you would like to 'Apply' the mapping to the component without any changes, or select 'Use as new mapping' to make edits to the existing mapping in order to create a new mapping. If you choose to make edits, you'll then follow the steps in the next section, Create New Mapping.
Create New Mapping
If you chose to create a new mapping, then on the following screen you'll first choose the data source from your list of integrated sources.
Next, you'll choose the object that contains the data for this component mapping. If you are not seeing the object, head back to the Integrations page and click 'Objects' in the integration source card to ensure the object is being imported.
After choosing the object, you'll need to map the data source fields to be used for the Deal Name, Deal Amount, Deal Date and Deal Owner in QuotaPath:
Important notes:
Deal Amount or Record Count - In the screenshot above, the deal amount is the ARR field that is showing on the left, which has been mapped to the amount field from the workspace's opportunity object. If you are using a count of records or actions instead of a dollar amount as your attainment and/or earnings amount (like in the example of paying per meetings booked), you would have "Meetings booked" showing instead of ARR. You could map it instead to the option record count on the right, instead of a CRM data field. This would simply count the number of records that meet the criteria defined in the rest of the mapping and use that value for attainment and/or earnings.
Deal owner - Below Deal Owner, there are two boxes. You must choose one:
The box on the left is for "Match Deal Data to Plan Assignee". It will require that a plan assignee matches the user indicated in the deal owner mapping in order to generate commission for that user. In the example above, the commission or attainment would go to the one plan assignee whose owner ID is in the deal owner field in the CRM. This is the standard option used by most components. Put simply, only the deal owner gets credit with this setting.
The option on the right, "Add Deals to All Plan Assignees or add Deal Owner filters later", will generate earnings or attainment credit for all plan assignees for each deal that meets the rest of the mapping criteria, regardless of owner. This would be used in the case of a CRO, for example, who will earn on all new business deals regardless of who the owner is, or for a solutions engineering team, where each SE earns a small commission on all deals closed by the sales team.
Troubleshooting owner credit: If you have earnings being attributed to one person where you expected them to be attributed across a team, or vice versa (where a team is earning but you expected the earnings to go to one person), you should check this setting in your mapping.
After mapping the core fields, you'll select the field(s) and value(s) to define each of the 3 deal stages in QuotaPath for Closed won, Pipeline and Closed lost. It is only required to define the criteria for closed/won. Pipeline and closed lost stage definitions are used to give your members pipeline and deal flow to forecast potential earnings and attainment. If your members have no pipeline deals showing on their earnings or attainment page, check their component mappings to make sure these stages have been defined.
Lastly, add additional filters as needed. Common examples of additional filters include Opportunity Type, Contract Term, Lead Source, etc.
When finished, click 'Sync' to start syncing data into the component on the plan. If there are additional components in the plan, repeat the above steps to map every component in the plan. After every component is synced, you've assigned QuotaPath workspace members to the plan and you have published the plan to Active, head to the Earnings page to start viewing commissions!
If you click "Sync and Setup Payout Rules", your data will begin to sync to your component, and you will be taken to set up payout eligibility criteria as shown below.
How to set up Payouts Eligibility integration mappings
If you'll also be syncing integration data to use for payouts eligibility in addition to deal creation, review this article for detailed information around combining data from multiple system.
If you have already completed the above step and/or you are using the same integration source for both deal create and payouts eligibility, or if the data has already been combined, continue reading here to learn how to set up the payouts eligibility rules.
Payout eligibility rules are tied to the mapping that you attach them to. If you build a new component and choose to use an existing mapping that has payout eligibility already set up in conjunction with it, those eligibility rules will carry over to your new component as well.