The integration between Aha! Ideas and Salesforce is one of our most popular, and for good reason. The integration brings feedback into your ideas portal from sales and support teams (often the people who work most closely to help your customers grow). Those teams do not need to learn another tool or manage another login, and you do not need to become a Salesforce administrator. Instead, everyone works in their preferred tool — and insights flow seamlessly between the two.
When you first configure the integration, though, you may have questions about how to link Aha! Ideas votes and ideas to Salesforce opportunities or accounts (If you add the Aha! widget in Salesforce to the case record type, Salesforce cases will be mapped automatically). This article discusses some of the most common ways to link these two tools.
This article discusses functionality that is included in the Aha! Ideas Advanced plan. Please contact us if you would like a live demo or want to try using it in your account.
Click any of the following links to skip ahead:
How to think about mappings
This integration is intentionally flexible — you can map Aha! Ideas to Salesforce records and fields in a variety of equally valid ways. So it is important to carefully consider how you want Aha! Ideas and Salesforce to work together.
Consider these questions as you get started:
How do sales and support teams organize your customers in Salesforce today?
What information in Salesforce will help you prioritize customer feedback and visualize customer demand?
Is there information from Salesforce accounts that you would like to see in Aha! ideas?
Use ideas portals in your Aha! account to centralize feedback and keep customers informed about status changes. Sync data from Salesforce — quantitative data like size and revenue mixed with qualitative insights from sales and support teams — to better understand an idea's revenue potential and the customer behind it.
Organizations and opportunity data are a one-way sync from Salesforce to Aha! Ideas. Only data from mapped fields will be sent to Aha! Ideas, and any changes you make to organization or opportunity fields in Aha! will not display in Salesforce.
Overview
Unlike our recommended mappings for other integrations like Jira or Azure DevOps, the mappings options we discuss here are additive.
Option one, mapping Salesforce accounts to Aha! Ideas organizations, is mandatory for the integration to function. You can choose to map additional fields if you want to, but at minimum accounts and organizations need to be linked.
Next, add the Aha! widget to different Salesforce objects, like accounts, opportunities, or cases. You can choose to add the widgets to some or all of the available object types. This way when Salesforce users create ideas through the integration, those ideas will come across already linked to the relevant Salesforce object.
After you have completed these steps, you can choose to add additional mappings:
If you add the Aha! widget to Salesforce opportunities, you can map those to Aha! Ideas proxy votes. This is useful, since Salesforce opportunities often carry information that provides context for a proxy vote, such as likelihood, value, or status.
If you want to track feedback from individual people, you can also choose to map Salesforce and Aha! Ideas contacts together. This gives you a granularity you cannot get from a higher-level account-to-organizations setup.
Enable key Aha! Ideas fields
Regardless of how you connect Aha! Ideas to Salesforce, we recommend using these fields in your field mappings to enhance the the integration:
Aha! Ideas field |
Benefit |
Build a participant database in your Aha! Discovery account with contacts and organizations you have stored in Salesforce. |
|
|
Generate a dashboard of information covering ideas that are most important to specific organizations. Report on all organizations to look at the ideas most valuable to a specific customer segment. Import customer organizations from Salesforce. Moving forward, your Aha! Ideas organization list will always stay in sync with any updates made in Salesforce. |
|
Revenue |
Track customer revenue to populate the Salesforce opportunity report, where you can quantify the value of ideas by development stage and identify the most valuable ideas in your portal. |
Adjust the Aha! Ideas proxy vote layout
When sales and support teams leave feedback through the integration, it will appear on an idea as a proxy vote. You can customize the information collected on the proxy vote layout, including adding custom fields for priority, level of effort, or anything else that is critical to your business case.
Sales and support teams can add proxy votes directly from Salesforce!
Option 1: Salesforce accounts to Aha! Ideas organizations
For this option, you need to create several custom fields in Aha! Ideas to store information about individual Salesforce accounts, then add those fields to your Aha! Ideas organization custom layout.
Every working integration requires Salesforce accounts to be mapped to Aha! Ideas organizations, at minimum. Optionally, you can map additional fields like those listed here.
Salesforce |
Aha! Ideas |
Accounts |
Organizations |
Name |
Name |
Email domain |
Email domain |
Revenue |
Revenue |
Account manager |
Account manager [custom field] |
Location |
Location [custom field] |
Plan type |
Plan type [custom field] |
Choose this option if:
Your product team receives ideas after a sale closes and the Salesforce opportunity becomes a paying customer. Accounts are used in Salesforce to store information about customers or individuals you do business with.
You want to use segments to understand what similar customers are requesting within Aha! Ideas.
The Aha! component on the Salesforce account page will include any ideas that are linked to that account's opportunities or cases. That means you can see all of an account's linked ideas in one consolidated view.
Option 2: Aha! Ideas proxy votes to Salesforce opportunities
For this option, you need to create several custom fields in Aha! Ideas to store information about individual Salesforce opportunities, then add those fields to your Aha! Ideas proxy vote custom layout.
For this option to work, you first need to add the Aha! widget to the Salesforce opportunity layout. That will link proxy votes and opportunities, and you choose to map additional fields like those listed here.
Aha! Ideas |
Salesforce |
Proxy votes |
Opportunities |
Amount |
Amount |
Status |
Status |
Probability |
Probability [custom field] |
Expected close date |
Expected close date [custom field] |
Choose this option if:
Your product team receives ideas (also known as "pre-sales requests") as part of the sales process.
You want to see the revenue potential of an idea before you implement it. When you connect Aha! ideas to Salesforce opportunities, you can use the Salesforce opportunity report.
The Salesforce opportunity report requires component installation at the Salesforce opportunity level and within the Salesforce opportunity stage value to be mapped within the integration.
Option 3: Salesforce contacts to Aha! Ideas contacts
For this option, you need to create several custom fields in Aha! Ideas to store information about individual Salesforce contacts, then add those fields to your Aha! Ideas contact custom layout.
Salesforce |
Aha! Ideas |
Contacts |
Contacts |
Name |
Name |
Phone number |
Phone number [custom field] |
Role |
Role [custom field] |
Choose this option if:
You want to review feedback from individual Salesforce contacts in your ideas portal.
You want Salesforce contacts to be able to log in to your ideas portal.
You want to be able to add proxy votes on behalf of a Salesforce contact.
If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.