In this article:
- Which custom fields should I import from SalesForce to use the dynamic segmentation feature?
- Can I automatically import SalesForce company data without a CSV file?
- Which fields are not supported with the SalesForce Integration?
- How does the SalesForce integration handle duplicate companies?
- When mapping SalesForce fields to Productboard's custom fields, am I able to grab data via lookup relationships across objects?
- How frequently does the SalesForce integration poll the API in a 24 hour window?
- If an Account is deleted in SalesForce, will the account be deleted from Productboard?
- Can I set up a sandbox instance to test the SalesForce integration?
- Why am I receiving an "OAUTH_APP_ACCESS_DENIED" error message when I try to set up my integration?
Which custom fields should I import from SalesForce to use the dynamic segmentation feature?
That depends on how you segment your customer base! By bringing in custom fields from SalesForce, you can create segments in Productboard which represent the customer cohorts that are most meaningful for your business.
Another way to approach this question is to ask, "What do I want to learn about my customer segments?"
For example, if you wanted to answer the question, "What features have been requested by UK companies in the SaaS industry with MRR >$500?" you'd need to create three custom fields: "Country", "Industry" and "MRR".
If you wanted to answer the question, "What problems have my Enterprise customers been mentioning?" you'd have to define which customers are considered Enterprise. Is "Enterprise" based on the number of employees at that company? The number of seats they're paying for? Their ARR? Whatever fields you use to define your Enterprise segment, you'd create those custom fields in Productboard.
Once you create the appropriate custom fields in Productboard, you're ready to create your dynamic segments.
P.S. Looking for ideas about which segments to build? We have some suggestions.
Can I automatically import SalesForce company data without a CSV file?
Makers can use the SalesForce integration to import company-level data (called Accounts in SalesForce) to Productboard.
At this time, there is no automatic sync between SalesForce to Productboard. In order to keep company data up-to-date, makers will need to update their data by re-importing from SalesForce. To re-import data manually, navigate to Settings > Integrations > SalesForce, then scroll down to the Update import section:
Which fields are not supported with the SalesForce Integration?
Currently, there are a number of SalesForce fields that we do not support with the integration.
The following fields are not supported:
- Lookup fields - For example, we would not be able to grab data from other objects like Opportunities.
- RecordType object fields - Some of our customers use these fields to specify Account type (e.g. Prospect, Customer, Partner).
- multi picklist field type - only able to use the "is", "is not" or "has any value" operators, not possible to choose a few values of a certain field e.g. "Contains: trials; customer," as the contains function is not supported.
- Reference fields (except Account name and Opportunity owner), location, and encrypted fields are not supported.
How does the SalesForce integration handle duplicate companies?
Productboard doesn’t merge companies. Even if the companies' names and websites are matching Productboard creates separate entities for them. In this way you will get a similar company list as your SalesForce accounts list you decided to import.
If you would like to avoid importing duplicate companies in Productboard you can use the filters for the import process to filter out unnecessary data. It's essential to identify the correct filters because, at present, there is no automatic process in place that allows you to delete or merge those duplicated companies.
When mapping SalesForce fields to Productboard's custom fields, am I able to grab data via lookup relationships across objects?
We currently do not support Lookup fields. For example, we would not be able to grab data from other objects like Opportunities.
We currently do not support RecordType object fields. Some of our customers use these fields to specify Account type (e.g. Prospect, Customer, Partner).
How frequently does the SalesForce integration poll the API in a 24 hour window?
This depends on the number of accounts that need to be imported. We use 1 API call per batch of 5000 accounts, and we poll the status of the job created by Bulk API every 5 seconds.
Also, we use API calls to the REST API to fetch the metadata about the available fields for the Account object and the count of the Account records for configuration purposes.
If an Account is deleted in SalesForce, will the account be deleted from Productboard?
No. Currently, when a SalesForce Account is deleted, the company remains in Productboard.
Can I set up a sandbox instance to test the SalesForce integration?
At this time, the SalesForce <> Productboard integration does not support use with a SalesForce sandbox space.
Why am I receiving an "OAUTH_APP_ACCESS_DENIED" error message when I try to set up my integration?
Encountering this error when setting up your SalesForce integration?
This issue occurs when a connected app is created, but the API user is not authorized to access it. Due to the way the connected app was set up, all users that want to authenticate themselves through the app need to be approved by an admin.
To solve this issue, you can follow these simple steps:
1. From Setup, type 'Connected Apps' in the Quick Find box, then select Manage Connected Apps.
2. Click Edit next to the connected app for which you are configuring access.
3. Under OAuth Policies, click the Permitted Users dropdown menu and select All users may self-authorize, which allows all users in the org to authorize the app after successfully signing in. Users must approve the app the first time they access it.
Now you can try the authorization again.
If you are still having problems after completing this process, please check this SalesForce help page for more information.