You may have heard about Gainsight’s new and improved PX Connector designed to provide a more seamless and straight-forward connection between PX and CS. Check out some tips below for getting used to using the new Connector:
UI Change
You may notice that things look a little different upon navigating to the Connectors2.0 page:
- Now you’ll see all of Gainsight’s products in the Gainsight Connections section (PX, CC, CE) and all other connections under External Connections.
- If you already have an established PX+CS connection by way of the legacy connector, you’ll see that the PX card displays “connected” with the option to setup the new connector. Clicking Setup will enable the new Connector. Note: Enabling the new connector will not stop the existing jobs, although they may no longer be needed. After ensuring there are no dependencies on the existing PX Connector jobs, you can manually disable them.
- To view/edit/disable existing PX Connector jobs, navigate to Connectors2.0 > Jobs and filter the Connection to PX Connector
Preview
When choosing common identifiers between PX and CS, you can now preview the data to ensure you’ve selected the most appropriate identifiers without having to import all of the data first. This is a huge game changer!
New Objects
- Once the new connection is established, you get a whole slew of new objects to play with! These objects hold calculated metrics (i.e., 1,7,30 days active users, % change, etc.) to save admins valuable time. Check out the fields in Report Builder to see what you can do.
- You can also import additional data, like specific feature usage at the Account and User level
- Fear not! If you have an existing Adoption Explorer project established and you’re familiar with the Company/Person Information and Company/Person Times Series Daily/Weekly objects or have lots of dependencies built upon these objects, you don’t have to fear the New Connector. These objects remain intact and continue to receive new data, even after disabling the old PX Connector jobs.
Relationship Association
Currently, the new PX Connector supports setup at the Company level. If your organization uses Relationships in CS to organize data by Product, it is recommended that you create a rule to load the PX Account ID and Product Key from the new Tracked Account Product object to the existing Relationship object. This will ensure PX usage data is organized by Product at the Relationship level. Note: Replicate this for Relationship Person, grabbing the PX User ID from the Tracked User Product Object
Have you used the new connector yet? Feel free to drop some of your own tips & tricks, feedback, or questions below. 👇