- You have connected Segment to MadKudu.
- You are on a Business plan with Segment
- from your workspace source(s): your website, app backend and/or front end... Please make sure it includes Identify, Track, Page, Group depending on what is needed.
- to the MadKudu destination
- for the time period of 9 months
- Start date: 9 months before the day you've connected Segment and MadKudu
- End date: current time
- All events or only a subset?
- If you include too many events, there might be delays happening in the data transfer, so we advise you to curate the list of events you want to send to MadKudu.
- Make sure to only send App usage data from Segment, not webpage visits or hand-raising events if they can be tracked elsewhere (from SFDC campaigns or Marketo for example).
- Make sure MadKudu doesn’t pull Non-user activities: system events that are not actions performed by users (like enrichment_provider).
- Make sure MadKudu doesn’t pull low-value activities: any notification, background event, system event, any event performed lots of times but with a low value (example: clicking an unimportant button).
- Make sure MK doesn’t pull obsolete events that didn't happen in the past 90 days.
- Please remove all these activities from your Segment Replay.
Depending on the volume of data to transfer, it may take from a few hours to a few weeks (>500M records) given the Segment API rate limit of the Replay to S3 and the limit rate of the pull from S3 to MadKudu. We recommend to only send the Segment events necessary to configure MadKudu and to filter out events with no relevance to your behavioral models and with high volumes (e.g. non-user events, very minor events, etc.), otherwise your implementation may be delayed until we get the full history of data. The Segment rate that we recommend ranges between 80 to 150 events per second. Please refer to this documentation or consult our implementation team at email@example.com to understand what are relevant events versus irrelevant events to configure your scoring.