Prerequisites
- For Pro and Enterprise plans only
- You have an Admin or Architect role in MadKudu
- You know what an Aggregation is
- You know what the Event mapping is
Before starting ...
Please make sure an Event mapping is configured in the app (Mapping > Event mapping). This allows us to transform the behavioral data MadKudu pulls from your integrations into the right format so that aggregations can be built in the Data Studio.
Step 1: Create an Aggregation
- Click on Aggregations in the main navigation bar
- Click on New Aggregation.
- Select if this aggregation should count behavioral data for a person (email) or for a company (account). Click Next.
- Select what data the aggregation should be counting.
Options #1 and #3 are not event-specific.
They count all type of activity for the email or account.
Options #2 and #4 are useful if you want to track a specific event. For instance, option 4 enables you to track: "Logged In X times in the last 10 days".
Click Next.
- Select the timeframe of the aggregation which is the window used to count the behavioral data. Enter a number between 1 and 90 days. Click Next.
- If you have selected a standard aggregation type (not counting a specific event or group of events), the API name of the aggregation will appear. This cannot be changed.
Click Save and proceed to step 2 (deploy computation).
- If you have selected an aggregation type based on a specific event or group of events, you'll see a section to define which events to include in this aggregation using the output of the Event mapping (called meta_events or MK event).
Important: use the exact same name as the one in the event mapping otherwise the aggregation won't work.
Configure the aggregation.
The example configuration below means: "count the number of times the person performed the event: [Attended a Trade show OR Attended a Road show OR Attended a Local meetup].
- Give a name to the aggregation.
- Click Save
Repeat the same for all the Aggregations you would like to create.
Step 2: Deploy the Aggregation(s)
Now you should be back on the Aggregations list page.
You have just created an aggregation, which means you have added it to the library of aggregations.
Now you can use the aggregations either:
- directly exported in your CRM (please submit a support ticket to our support team to help you make this happen)
- in the likelihood to buy model (see next step on how to build Aggregated events)
Either way, you will first need to:
- Deploy the aggregation on the aggregations page.
- then in the Overview tab of model you'd like to use this aggregation, click on "Reload aggregations" to compute them on the dataset.
Congratulations! You've created an aggregation ;)
Editing Aggregations
Once your aggregation is deployed, you can update its name or definition at any time.
However, if the aggregation is used in a live model or pushed to your CRM, the name will be locked. In order to edit the name of a live aggregation, you should first remove it from your live model.
Frequently Asked Questions
How are defined the standard aggregations?
- Number of active emails last X days: number of persons in the past X who generated at least one positive user activity
- Number of active days in last X days: number of days in the past X days where the person/account generated any positive user activity
- Number of active days last X days with app usage: number of days in the past X days where the person/account generated any positive user activities of type 'App Usage'