Preparing for implementation
  • 09 May 2022
  • 4 Minutes to read
  • Dark
    Light

Preparing for implementation

  • Dark
    Light

Questions to consider

To determine whether the G2 CRM Connector is the right option for your organization, and to ensure a successful implementation process if so, use the following questions to guide your decisions.

Question Information
What Salesforce subscription level does your organization hold? Organizations must have a Salesforce Enterprise or Unlimited subscription to take advantage of the G2 Salesforce integration. Without the appropriate Salesforce subscription, the G2 Salesforce Connector app will not be available.
Who will be involved in the implementation process? Internal marketing or sales ops representatives? Third-party Salesforce consultants? Only a Salesforce sys admin can complete the implementation process. Review the Implementation section for full details.
Is your Salesforce structure already in place? Are Salesforce accounts, leads, and opportunities set up in the way you want? G2 customers should delay implementing the G2 CRM Connector in their Salesforce environments until a general structure is in place, particularly in regards to Salesforce accounts. This structure will be critical for the purposes of auto-mapping (and manually mapping) G2 Buyer Intent data.
Does your organization’s Salesforce environment contain duplicate accounts? While it is possible to manually map multiple secondary accounts to a Buyer Intent signal via the G2 Buyer Intent tab, the bulk mapping process only maps one signal to one Salesforce account by default. User organizations can potentially undergo the process of cleaning up duplicate Salesforce accounts before proceeding with the implementation, or explore other options for auto-matching with a G2 representative.
What is the Salesforce account creation process for your organization? Who creates accounts, and how often are accounts created? G2 Buyer Intent data auto-maps to Salesforce accounts based solely on the domain field, so you need to understand how the account creation process intersects with the data mapping process.
What roles are the Salesforce accounts owners? Sales representatives? CSMs? Only one Salesforce user can be an account owner, and account owners play a role in how G2 data can be used (for example, creating Salesforce reports with G2 data based on the Salesforce account owners). Identifying the Salesforce account owners in a user organization helps understand how G2 data can be used.
Does your organization use LeanData? LeanData is a third-party service that enables additional auto-mapping opportunities for the G2 CRM Connector. G2 offers an integration with LeanData.
Does your organization currently use G2 Reviews or Reference Pages in any capacity? The G2 CRM Connector offers ways to highlight user reviews from G2.com and use existing (or build new) Reference Pages. For instance, you can find positive G2 reviews to highlight as part of a nurture campaign for a marketing team, or build Reference Pages featuring reviews from certain company sizes to target sales prospects of the same size.
If your organization does not have clear plans for how G2 data will be used in Salesforce, thinking about the following questions might help inform your conversation with G2:
  • How does outbound sales prioritize prospecting?
  • How are leads qualified?
  • How does marketing determine companies to target?
How does your organization plan to use G2 data in Salesforce? For example, if HubSpot is going to be the primary platform where G2 data will be used in your organization, the better option might be utilizing G2’s direct integration with HubSpot. The Integrations Hub tab on your my.G2 admin dashboard should show all the G2 integration options, so it is a good idea to understand everything that is available to ensure the Salesforce integration is the best choice for your organization.
Does your organization plan to push G2 data from Salesforce to another platform? While it is possible to daisy chain integrations, G2 representatives only support core integration functionality between G2 and Salesforce. If your organization wants to use Salesforce as a single-source-of-data-truth, to have that G2 data flow out of Salesforce into another integration option (for example, HubSpot), any issues encountered would mean relying on either Salesforce or the third-party integration vendor’s support.

General integration timelines

Timelines can change for a variety of reasons, but the following information should give a general idea of the effort required as part of the implementation process.

An experienced Salesforce admin can expect to spend 3-4 working hours implementing the G2 CRM Connector. This work includes:

  • Implementing the G2 CRM Connector
  • Assigning licenses and permission sets to Salesforce users
  • Communicating with other teams about the functionality included with this integration
  • (Optional) Customizing the pre-built Salesforce reports, or creating new Salesforce reports using G2 data
  • Troubleshooting could add time to this process

The Salesforce admin implementing the G2 CRM Connector might also spend additional time using this documentation to learn how to create custom Salesforce notifications and dashboards using G2 data.

For general teams, the following effort is potentially required:

  • Kick-off call: This call is meant to provide the user organization with implementation materials, answer questions about the G2 CRM Connector, and undergo the initial discovery process.
  • Post-implementation or Buyer Intent call: In this call, G2 helps verify that the integration is working appropriately, walks through the components included with the G2 CRM Connector, and operationalizes the integration via education on the included Salesforce reports.
  • Training(optional): G2 provides additional training for user organizations that need more education on the integration.

Delays in this process are mainly due to resources constraints, availability of the Salesforce admin or user completing the implementation, and the consideration of strategic decisions by user organizations.


Was this article helpful?

What's Next