What does this integration do?
MadKudu has a great integration with Salesforce. Depending on your MadKudu plan, connecting Salesforce will allow you to do things like:
update your salesforce lead and contact profiles with your MadKudu predictive analytics (see here for details).
have sales notifications be sent to the right person, ie. the person who owns the lead (eg. Slack notifications)
How to connect Salesforce?
Click on the OAuth button. You will be redirected to Salesforce. Follow the instructions give us access. You will be redirected back to MadKudu once done.
With Password / Security Token
Log in your salesforce account and click on your name at the top right of the screen, and then “My Settings”.
Click on “Personal” in the left navigation bar, then “Reset My Security Token”, and finally “Reset Security Token”.
Open your emails and find the salesforce security token in the message
Log in MadKudu, click “Integrations” and then “Salesforce”.
Copy/paste the information and click “save”.
You’re all set!
A common practice is to add behavioral and predictive information to your lead profiles. That way, your SDRs or your AEs have information that will make their outreach much more relevant and effective.
Instead of calling and say “I am calling because you’ve been identified as a lead likely to buy”, you can now say “I noticed that you added 7 users to your trials yesterday. I though I would reach out to offer some tips on how to train and onboard those users. Do you want to tell me more so that I can be helpful?”.
We usually recommend using a two column layout. Organize your fields so that the predictive attributes are on the left, while context on this lead can be found on the right.
Open up any profile of a Lead or Contact and then click on “Edit Layout”.
Drag and drop a new “section” to where you want the MadKudu intelligence to show.
Name the new section “MadKudu Intelligence”.
Drag and drop the MadKudu fields you’d like to see.
Save your layout.
Creating Relevant Views
Ready to buy Leads
SDRs usually love this view! Those leads are customers currently in a trial, who have a good likelihood to buy, and have a size that makes a high-touch assist worth-while.
- My Unconverted Leads
- MK Likelihood to Buy = very high, high
- MK Customer Fit Segment = very good, good, medium
New Qualified Inbound Leads
This view is used to qualify new leads and make sure time is spent engaging with leads who have enough potential value.
- My Unconverted Leads
- MK Customer Fit Segment = very good, good
- Created Date = THIS WEEK
Can I test MadKudu using my Salesforce Sandbox first?
Yes. In the Salesforce integration page, check the “Sandbox?” option to have MadKudu sync data using your Salesforce Sandbox environment.
Note: If you’re using your sandbox, your username should be
username.[name_of_your_sandbox], for example
firstname.lastname@example.org if your username is
email@example.com and your sandbox is called test.
What OAuth scope does your application use?
Our OAuth application requests the following scopes:
In plain english, this means that the application will have permission to:
- Perform requests on your behalf at any time
- Access and manage your data
The OAuth flow will provide us with a refresh_token that is valid until explicitly revoked.
Importantly, the actions our application can take are limited to the permissions of the user who authorized it.
What Salesforce permissions do I need?
The salesforce user you use to connect MadKudu to salesforce requires the following permissions:
- API Enabled - Access any Salesforce.com API.
- Api Only User - Access Salesforce.com only through a Salesforce.com API.
- Password Never Expires - Prevent the user’s password from expiring.
- Lead: Modify All - Create, edit, and delete all lead data, regardless of sharing settings.
- Contact: Modify All - Create, edit, and delete all contact data, regardless of sharing settings.
- Account: Modify All - Create, edit, and delete all account data, regardless of sharing settings.
- Opportunity: Modify All - Create, edit, and delete all opportunity data, regardless of sharing settings. If not possible, we need at least read on all opportunity data to train the models
- Opportunity History: Read all data. This is used to train the models
- Opportunity Field History: Read all data. This is used to identify at risk opportunities (not required)
- Task: Read all data. This is used to feed into the models
- Lead and Contact History: Read all data. This is used to train the model (find which leads became an SQL before going to nurture…)
MadKudu does not delete any records not write to any field that was not created by MadKudu. You may restrict settings to Read All and Modify only on the custom fields MadKudu creates
To find out whether or not your user has those permissions, start by going into the Salesforce “Setup” section.
Then go to the user section and click on the “profile” of the user you want to check permissions for.
Scroll down the the “Administrative permissions” section and make sure the proper settings are checked.
This user will be used for the following
- read data from Salesforce (leads, contacts, accounts, opportunities, users and changes)
- update information in Salesforce
What data will this integration obtain from Salesforce?
We limit ourselves to the minimum information needed to run our predictions.
By default, MadKudu pulls the following objects (and their history) along with their standard attributes:
Additional data (including salesforce custom objects) can pulled if you are on the enterprise plan.