Madkudu quick info
Madkudu accepts device-mode data only from Analytics.js.
This destination is built and supported by MadKudu. If you run into any issues with the destination, contact their support team.
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.
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.
It takes < 30 mins to begin accelerating your sales with MadKudu
- Connect MadKudu to one of your Segment sources (5 min.)
- Add your CRM credentials to MadKudu (5 min.)
- Schedule a sales acceleration consultation with MadKudu to review your data and project revenue impacts (15 min.)
group events from Segment.
These events are enriched with other data, aggregated, and pushed to appropriate fields in your CRM.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property
order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Supported Sources and Connection Modes
Before you start, make sure Madkudu supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
Segment offers an optional Device-based Connection Mode for Mobile data going to Madkudu, so that you can use Madkudu features that collect data directly from the mobile device. To do this, you must package the Segment-Madkudu mobile SDK with the Segment mobile library.
Segment lets you change these destination settings from the Segment app without having to touch any code.
|Direct Integration Channels||
The channels this direct integration supports.
|Direct Integration Endpoint||
The API endpoint of the direct integration.
This page was last modified: 09 Jun 2020
Questions? Problems? Need more info? Contact us, and we can help!