This article explains how to configure the integration between Gainsight PX and Salesforce.
The Gainsight PX Salesforce Integration allows you to fetch data from Salesforce to Gainsight PX and vice versa for the Account and Contact records. If a matching SFDC record is found for a given Gainsight PX record, then the chosen fields on the field mapping screen are copied from the Salesforce object to the matched Gainsight PX record.
With this integration in place, you can slice and dice the product data based on Salesforce attributes. You can also use these granular levels of details to create in-application messaging and personalize Engagements for a specific segment of end-users. In addition, you can implement product usage from accounts and contacts in Salesforce reports and views.
Salesforce integration in Gainsight PX increases the effectiveness of your product by keeping your customers engaged within their applications. This empowers customer success as you can now learn about your customers’ health score at a very early stage and that helps teams improve the quality to ensure that your customers keep coming back.
Our integration is not available on the AppExchange, and it is not a Managed Package Integration. This makes the integration simple
WARNING: For the integration to work properly, it is critical to ensure that there are no duplicates of the key field used to link Gainsight PX and Salesforce. If there are two records in PX with the same Salesforce ID, the data from both PX records attempts to update the same record in SFDC, in no particular order.
Gainsight PX admin helps you to set the application and run it in your application within the given time. Only the admin can configure in order to fetch data. You must ensure that the existing integration set is working. Before you explore more about the Salesforce Integration in Gainsight PX, ensure that the following points have been taken care of:
- You must ensure that the sync is working correctly. It should show when it was synced.
- You must authenticate the Salesforce users
Data is fetched from Salesforce every day at midnight GMT and mapped to Gainsight PX data at 4 AM GMT. Data is pushed to Salesforce every day at 3 AM, 11 AM, and 7 PM GMT. You can also manually sync the data at any point in Gainsight PX by clicking the Synchronize button.
Note: Check whether your sync is working correctly. You should see a recent Last Pull date and Last Push date and the status (here it is Mapped).
As a Salesforce admin, you must have access to the required objects. You need admin access to configure Data pushed for Account/Contact or equivalent SFDC Custom Object. Perform the following steps:
Login to Gainsight PX with your personal credentials.
Navigate to Administration > Integrations.
- Click the Settings icon on the Salesforce card. The Matching Logic window appears.
- Enable the Accounts switch under the Retrieve from Salesforce section.
- Select the Custom Field Matching checkbox.
- Select the required Fields for both Gainsight PX and Salesforce to perform mapping.
- Select the Website Domain checkbox. Checking this option enables you to associate Salesforce Account and PX account only if they have the same domain on both objects.
In addition, Gainsight PX allows you to map feature metrics.
If you enable and/or Contacts option as shown in the image above, you need to select the Email checkbox for the Gainsight PX user email to match with the Salesforce Contact email in order to map.
The Mapped Fields option allows you to map the field(s) in SFDC that you want to push to Gainsight PX.
Supported Field Types
The following are the type of fields supported for mapping:
- DATE_TIME types in PX can map to the following field types in SFDC
- DATE, DATETIME, TIME
- STRING types in PX can map to the following field types in SFDC
- STRING, TEXTAREA, PICKLIST, MULTIPICKLIST, COMBOBOX, EMAIL, URL, ID, PHONE
- NUMBER types in PX can map to the following field types in SFDC
- INT, DOUBLE, PERCENT, CURRENCY
- BOOLEAN types in PX can map to the following field types in SFDC
Data Pulled from Salesforce
Perform the following steps to configure the Mapped Fields window on Account/Contact records. For more information about Account Match Scenario and Contact Match Scenario, refer to the Appendix section in this article.
- Navigate to Administration > Integrations.If Salesforce is enabled for your account, you will see the Salesforce Integration on the right-hand side.
IMPORTANT: To use the Gainsight PX/Salesforce Integration, you need to sign into Salesforce as a user with Read access to the Accounts object and Contacts object.
- Click on the Map Fields icon on the Salesforce card. The Mapping fields window displays.
- Select Account and/or Contact tab(s) where data will be pulled from/pushed to Salesforce.
- Select the → data pulled from option.
- Select the fields that you want to map.
- Click Apply.
Once you have linked your Salesforce data, you can use it throughout Gainsight PX. Specifically, you can slice and dice your data, filter, and analyze Engagements based on Salesforce attributes. The following image shows how to add a filter based on Salesforce accounts.
Data Pushed to Salesforce
Prerequisite: Before you can push Account records, SFDC ID must be available on Accounts Explorer and to push Contact records, SFDC Contact ID must be available on Audience Explorer.
When you select the → data pushed to option as shown in the following image, the data is pushed from Gainsight PX Account and Contact records to Salesforce.
This enables you to have the Gainsight PX data inside Salesforce for workflows, creating tasks, sending notifications, reporting, and other integrations. For example, you can,
- Schedule an Engagement when a customer is within 90 days of renewal.
- Create tasks for CSMs when an activity needs attention.
- Use Gainsight PX data with Salesforce support data to create a health score.
When pushing Accounts data, Gainsight PX allows you to push Account KPI metrics, which are calculated and not part of the Account object.
The following is the list of calculated fields that are supported:
- Month over Month (MoM) Change
- Weekly Active Users (WAU) Count
- Quarterly Active Users (QAU) Count
- Quarter over Quarter (QoQ) Change
- Week over Week (WoW) Change
- Last Week NPS® Score
- WoW NPS® Score
- Last Week NPS® Responses
- WoW NPS® Responses
- Last Quarter NPS® Score
- Last Month NPS® Score
- Last Quarter NPS® Responses
- Last Month NPS® Responses
- QoQ NPS® Score
- QoQ NPS® Responses
- MoM NPS® Score
- Monthly Active Users (MAU) Count
- MoM NPS® Responses
Using Salesforce Custom Objects
You can now select a custom object as the Salesforce object for the sync operation. If you do not use the standard SFDC Account and/or standard SFDC Contact objects and instead have your Accounts and Contacts defined in an SFDC Custom Object, this integration also allows you to specify any SFDC Custom Object as the SFDC Source object. If you select a custom object, that object type is used for all sync operations (pull and push).
The dropdown on the right-hand side of the mapping screen allows you to select a target for your sync operation for either accounts or users.
As a best practice, you can continue to sync PX accounts SFDC Accounts and PX users to SFDC Contacts.
- Requires Salesforce API access with Enterprise, Unlimited or a paid upgrade to Professional with API access added.
- Currently supports syncing the Accounts and Contacts standard Salesforce Objects.
- Gainsight PX only pushes the data to fields contains "PX_" as prefix. For example, PX_Test_String, etc.
Account Match Scenario
- For all Gainsight PX account records: If account has been matched before and the account.sfdcId field matches the id that was matched previously, then Gainsight PX will retain the previous match, and skip remaining matching logic.
- Otherwise: The integration will find the SFDC account that matches the "best" by applying a weighted value to how well it matches the criteria that are selected in the SFDC integration screen in the application.
If there are multiple SFDC accounts that match, the account with the highest cumulative score is considered a match.
|sfdcId to Salesforce ID||account.sfdcId equal to sfdcAccount.id||2.0|
|Custom Field Matching||Matching value in the two given fields||2.0||
Fields must be of the same type, only strings and integral (whole number) numerics are supported.
|Website Domain||account.website domain equal to sfdcAccount.website domain||1.0|
|Name||account.name equal to sfdcAccount.name||1.0|
|Recent user domain||user.email domain equal to sfdcAccount.website domain||1.0||Retrieves 100 most recently seen users and extracts they domains from their email addresses. If there is a mixture of email domains, the score is weighted by the portion of the users that have the same domain.|
Contact Match Scenario
- For all Gainsight PX user records: If a contact has been matched before and the user.sfdcContactId matches the id that was matched previously: Gainsight PX will retain the previous match, and skip remaining matching logic.
- Otherwise: Find the first matching contact by iterating through the matching criteria that are selected in the SFDC integration screen. The first contact found that matches is chosen.
The matching is performed in the following order:
|sfdcContactId to Salesforce Contact ID||
user.sfdcContactID equal to contact.id
|Custom Field Matching||Matching value in the two given fields||Fields must be of the same type, only strings and integral (whole number) numeric are supported.|
|user.email equal to contact.email||If more than one matching email on SFDC, not considered a match|
|Phone||user.phone equal to contact.phone||If more than one matching phone on SFDC, not considered a match|
KPIs for Push to Salesforce (in addition to Custom Attributes)
Currently, the NPS® is only on the Account level. When a user map contact, only contact’s attributes can be pulled/pushed, no KPIs or individual NPS® responses can be pulled/pushed.
- Account boolean
- Account numeric
- AWS S3 Enabled (?)
- CEO Name
- City Name
- Continent Code
- Country Code
- Country Name
- NAICS Code
- Active engagements count
- Number of engagements field
- 90 day NPS® Score (Reworded)
- 90 day NPS® Responses (Reworded)
- 30 day NPS® Score (Reworded)
- 30 day NPS® Responses (Reworded)
- 7 day NPS® Score (Reworded)
- 7 day NPS® Responses (Reworded)
Note: For 90 day it is called as “90 day NPS® Delta” which shows the score for the previous period of time.
For features, the following way options are organized:
Feature Users Last 90 Days
- Feature Users Last 30 Days
- Feature Users Last 7 dDays
- -------------- (dividing line)
- 90 Day Feature Users Delta
- 30 Day Feature Users Delta
- 7 Day Feature Users Delta
- 90 Day Active User Count
- 90 Day Active User Delta
- 30 Day Active User Count
- 30 Day Active User Delta
- 7 Day Active User Count
- 7 Day Active User Delta
Raw list of KPIs Currently In App
- Feature usage last 30 days
- Feature usage last 30 days
- Feature usage last 7 days
- Feature usage monthly change
- Feature usage quarterly change
- Feature usage weekly change
- Last month NPS® responses
- Last month NPS® score
- Last quarter NPS® responses
- Last quarter NPS® score
- Last Week NPS® responses
- Last Week NPS® score
- Month over month NPS® responses
- Month over month NPS® score
- Monthly active users
- Monthly active users change
- Quarter over quarter NPS® responses
- Quarter over quarter NPS® score
- Quarterly active users
- Quarterly active users change
- Week over week NPS® responses
- Week over week NPS® score
- Weekly active users
- Weekly active users change
Knowledge Base Integration
When PX is configured with Salesforce, you can view and search all the articles available in Salesforce through PX Knowledge Center Bot. For more information, refer to the Integrate Salesforce Knowledge Base with Knowledge Center Bot article from the Additional Resources section.
|Integrate Salesforce Knowledge Base with Knowledge Center Bot|
|NPS, Net Promoter, and Net Promoter Score are registered trademarks of Satmetrix Systems, Inc., Bain & Company and Fred Reichheld|