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:
How to connect Salesforce?
With OAuth (preferred)
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 Username / Password / Security Token (rare)
This setup is useful if you want to connect to a Sandbox account first, but is not recommended long-term. The password and security token expire regularly and break the connection between MadKudu and Salesforce.
To connect with Username / Password
- Log in your salesforce account and click on your name at the top right of the screen, and then “My Settings”.
2. Click on “Personal” in the left navigation bar, then “Reset My Security Token”, and finally “Reset Security Token”.
3. Open your emails and find the salesforce security token in the message
4. Log in MadKudu, click “Integrations” and then “Salesforce”.
5. Copy/paste the information and click “save”.
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
email@example.com if your username is
firstname.lastname@example.org 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?
For simplicity, we recommend that the user connecting to Salesforce be given the following permissions:
- API Enabled - Access any Salesforce.com API
- 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…)
- [Username/Password only] Api Only User - Access Salesforce.com only through a Salesforce.com API.
- [Username/Password only] Password Never Expires - Prevent the user’s password from expiring.
If you prefer more fine-grained settings, You may restrict to the following:
- Lead/Contact/Account/Opportunity: Read all data, modify the MadKudu fields.
- Other fields above: Read all data.
In this scenario, you will need to create the MadKudu fields yourself. Please contact email@example.com for the exact field specifications.
Can I restrict what data you can access on Lead/Contact/Account?
Yes. If your Contact/Lead/Account contains HR data, or anything you would like to restrict access to, you can restrict access to only the "relevant" fields on those objects. In this scenario, please contact your Customer Success Manager to decide what fields to give access to.
Where do I check these permissions?
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
Does MadKudu ever creates/deletes records in Salesforce?
MadKudu does not create any new leads or delete any records. It also does not write to any field that was not created by MadKudu.
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:
- Campaign Member
Additional data (including salesforce custom objects) can pulled if you are on the enterprise plan.
Can MadKudu connect with Salesforce if we leverage SSO?
Yes, we have customers using tools like Okta to manage their credentials and our integration will work. However connecting to Sandbox accounts will require a different authentication login.