- Accepts Page, Alias, Group, Identify, and Track calls
- Refer to it as Madkudu in the Integrations object
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.
More details available on MadKudu’s website or email email@example.com.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
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, Engage 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), Engage sets that value to
When you first create an audience, Engage 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.
Real-time to batch destination sync frequency
Real-time audience syncs to MadKudu may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
This page was last modified: 29 Mar 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!