The result of the event mapping is available in this super useful report.
Supported event tracking integrations:
- HubSpot (Form Submissions and Email clicks only)**
- Salesforce (Campaigns and Tasks only)*
- Amazon S3 (connector for Snowflake, Redshift, BigQuery...)
*MadKudu does not support mapping data from Salesforce Custom objects, Marketo Programs, nor Marketo custom objects.
**HubSpot API design does not allow MadKudu to pull web visits, therefore this data is not available to use in the event mapping and behavioral model. Learn more
- You have a Likelihood To Buy model
- You know about the event mapping
What is this?
The event mapping output report displays information about the events you mapped from your CRM and MAP to MadKudu through the event mapping. It allows you to check that your event mapping returns volumes that make sense.
We recommend checking this report every month to make sure all important events are included in your Likelihood To Buy model.
Where do I find this?
In the App, under Mapping > Event mapping > Check volumes
How do I use this report?
If you're seeing an unexpected volume this means you should review your event mapping: you may have changed the way you're tracking the event in your tracking system. If you also notice that some events have not happened recently you should think about updating the logic of the event in the event mapping to make sure you're still catching it in MadKudu.
How do I read this report?
Refresh the report
First, make sure the report is up to date by checking the date in the upper right corner.
If it's not, click the refresh button.
Events mapped - volume and recency
We count the number of occurrences for each event mapped in the event mapping (meta event). We count the number of events that happened in the last 90 days and we also display the number of days since last seen.
Activity type mapped over time
We count the number of occurences for each events mapped in the event mapping grouping them by activity type (Web activity, App Usage, Marketing Activity...). We count the number of events that happened the last 9 months.
This allows you to check that your event mapping returns volumes that make sense. If you notice a drop in the volume of a certain activity type that means probably that you changed the way you're tracking the activity. The event mapping should be updated to make sure the scores take into account all the activity.
If you want to use this data for internal analysis, feel free to download the raw data as CSV.
We look at events that currently fall into a catch-all (i.e. an event that is not explicitly mapped in your event mapping). The goal of this report is to check for any potential blindspots in mapped events.
Look at the most frequent events that fall into catch-alls and map them separately on the event mapping page.
This table looks at the last day an event (mapped in the event mapping from the behavioral data pulled from your integration) was logged into MadKudu database
Why has this event not been seen recently? Did you change the way you track it? Did you change the name of the form? Did you create a new campaign instead? Consider reviewing the definition of these events in the event mapping if your tracking has changed or delete them if they are obsolete.
Events over time by conversion
The graph calculates for each event the number of occurrences for a given conversion model or across all populations.
First, pick an event to investigate. The 'All populations' bar shows the total activity for this event for each month. The other bars represent the activities performed by converted emails (Open Opp, Closed Won, or SQO) (only events in the 90 days before the conversion date are counted). You can now see for the months and conversion chosen in your dataset whether you should expect to see occurrences of the selected event in your model. Click on the legend to remove populations you do not want to see.
If you see anything you'd like to update but you're not sure where to start: