MadKudu has a great integration with Salesforce. Depending on your MadKudu plan, connecting Salesforce will allow you to do things like:

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.

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

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.

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.

Filter by

This view is used to qualify new leads and make sure time is spent engaging with leads who have enough potential value.

Filter by

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 bob@madkudu.com.test if your username is bob@madkudu.com and your sandbox is called test.

Our OAuth application requests the following scopes:

In plain english, this means that the application will have permission to:

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.

For simplicity, we recommend that the user connecting to Salesforce be given the following permissions:

If you prefer more fine-grained settings, You may restrict to the following:

In this scenario, you will need to create the MadKudu fields yourself. Please contact support@madkudu.com for the exact field specifications.

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.

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

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. 

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.