Madkudu Destination

Segment makes it easy to send your data to Madkudu (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Madkudu in the format they understand. Learn more about how to use Madkudu with Segment.

This destination is built and supported by MadKudu. If you run into any issues with the destination, please reach out to their support team.

Getting Started

How it works

MadKudu receives your customer data from Segment, enriches it, and updates your CRM profiles.

The enriched CRM profiles solves 2 problems for your sales reps:

  • Reduces wasted time on unqualified leads.
  • Prevents reps from missing high-value leads.

MadKudu’s solution

Unlike traditional lead scoring solutions, MadKudu requires no manual effort or guesswork. MadKudu uses rigorous statistical methods based on data science to identify the most qualified leads based on customer demographics.

Additionally, MadKudu uses a customer’s in-app behavior to detect sales opportunities such as closing, churn, or upsell.

Getting Started

It takes < 30 mins to begin accelerating your sales with MadKudu

  1. Connect MadKudu to one of your Segment sources (5 min.)
  2. Add your CRM credentials to MadKudu (5 min.)
  3. Schedule a sales acceleration consultation with MadKudu to review your data and project revenue impacts (15 min.)


MadKudu ingests identify, track, page, and group events from Segment.

These events are enriched with other data, aggregated, and pushed to appropriate fields in your CRM.


More details available on MadKudu’s website or email


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


Please enter your Madkudu API key

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!