Mapping G2 Buyer Intent data to Salesforce accounts and leads

Buyer Intent captures enriched data about buyers researching your product across G2. Buyer Intent signals can be triggered by a variety of actions, including interacting with your product profile page, comparing your product to a competitor, or viewing alternatives to your product. This data enables your sales, marketing, and customer success teams to identify where a buyer or current customer is on their buyer journey.

Auto-mapping Buyer Intent signals

The G2 CRM Connector for Salesforce continuously pushes new Buyer Intent signals into your Salesforce environment.

Buyer Intent signals are automatically mapped (auto-mapped) to accounts in Salesforce by matching the organization’s Buyer Intent website domain with the website domain on their corresponding account in Salesforce. Once auto-mapping has been performed for a new signal, future signals will continue to map to the same account.

If an account does not already exist in Salesforce, a new one is not created and you must map the signal to the account manually.

To identify which signals have been auto-mapped to your Salesforce accounts, navigate to the G2 Buyer Intent tab in Salesforce. The Mapped Accounts column lists the Salesforce accounts that have been mapped to the associated Buyer Intent signals.

(Optional) Bulk mapping existing Buyer Intent signals to Salesforce accounts

After setting up the G2 CRM Connector for Salesforce, new Buyer Intent signals auto-map to their corresponding accounts in Salesforce. However, Buyer Intent signals generated before activation of the integration are not auto-mapped to Salesforce accounts. To bulk map existing Buyer Intent data to your Salesforce accounts, G2 recommends using the Salesforce Data Loader to upsert your data.

To bulk map Buyer Intent data:

1. Make a copy of the Salesforce Data Loader G2 Mapping template You can download the file directly, or make a copy of the Google Sheet.
2. Follow the instructions included in the mapping template to prepare your data for the upsert process. Once completed, your CSV file should contain the Remote Organization ID and the Matched Account ID.
3. Open the Salesforce Data Loader. In the Welcome to Data Loader screen, select Upsert, then log in to your Salesforce environment.
4. In the Select data objects screen, select the G2 Visiting Organization (G2Crowd__G2_Visiting_Organization__c) object. In the Choose CSV file field, select Browse and open the CSV file from step 2. Select Next.
5. In the Choose your field to use for matching screen, select Id from the dropdown, then select Next.

6. In the Choose your related objects screen, leave the three dropdowns set to Not Selected, then select Next.
7. In the Mapping screen, select Create or Edit a Map.
8. In the Mapping Dialog pop-up:
   • Select and drag the G2Crowd__Account__c field to match with the Matched Account ID column header.
   • Select and drag the G2Crowd__Remote_Organization_ID__c field to match with the Remote Organization ID column header.

9. Select Next.
10. Select Finish, and then select Yes in the Warning pop-up to proceed with updating the Salesforce records.
11. Wait for the upsert process to finish, and then select OK. Your G2 Buyer Intent data is now mapped to the corresponding Salesforce accounts in your environment.

(Optional) One-time auto-mapping G2 Buyer Intent data to Salesforce leads

In addition to auto-mapping Buyer Intent data to Salesforce accounts, the G2 CRM Connector for Salesforce can perform a one-time auto-mapping of data to Salesforce leads based on domain matches.

To enable this one-time auto-mapping for your Salesforce leads, inform your G2 representative during the integration implementation process and let them know the maximum number of leads you want to associate with your Buyer Intent signals (also referred to as the “maximum associated records”).

There is no limit on the amount of leads that can be mapped during this process. By default, G2 sets the maximum associated records value to three. If there are more than three leads that correspond to a domain, the three leads with the most recent Salesforce activity are chosen for mapping. If a new lead is later identified with the same domain, G2 will not auto-map data to that new lead.