Signals displayed in your CRM are meant to provide information that explains the score of a lead. The Likelihood to Buy signals surface the latest activities performed by the Lead or Account and can also surface some activity statistics (see Aggregations).
The recent activities displayed come from the person or account behavioral activity on your website, app or marketing interactions that you track. MadKudu pulls these activities from your connected integrations (Segment, Amplitude, Marketo...) and maps them in the Event mapping to create user-friendly event names (called meta events or MK events throughout the platform) that will be displayed in the behavioral signals.
How to know where an event comes from?
Events are mapped from your different behavioral data sources into a standard and unique format that is more user-friendly. This makes it possible to easily build the Likelihood to Buy model and surface these events in the signals. The definition of each event can be found in the Event mapping.
How to remove an event from the Signals?
Some events may be polluting the list of most recent activities because they happen too frequently. In other words, these events probably do not provide any relevant information to your Sales team who will be reading these signals.
You can remove such events in the Data Studio following these instructions.
Note: removing from the signals does not mean the event is removed from the model. For example, you would still want to associate scoring points to these events, but you just don't want the event in the signals. Or vice versa. The allocation of points and the configuration of the signals are independent.
Step 1: Exclude events from Signals
- In an existing draft model or duplicate from a live model, navigate to Model > Signals
- In the section "Events to exclude" list from signals, list one by one the events you would like to exclude. Use the name you see in the Spot check tab or see the list of events in your Event mapping
- Click on Save
We recommend excluding 'Other [integration] activity' events from your signals. These are referred to as catch-all events, automatically created by MadKudu to receive all events coming from your integration but that you didn't explicitly map in your event mapping.
Step 2: Review changes
Before looking at a sample of records scored with their signals in the spot check tab, reload the validation dataset by going to the Review > Performance tab
Then go to the Sample tab and review the results to see that these events do not appear anymore in the signals.
Step 3: Deploy changes
Keep these considerations in mind when deploying changes in the signals:
- All your Leads, Contacts, or Accounts that are usually scored by MadKudu and have performed the events impacted by the signal changes you just made will get rescored with the next batch scoring (see when the next Analysis then Sync process should run in the Processes Page).
- Adding, editing, or deleting signals that change a prospect's signals may trigger automated workflows, which are based on the Likelihood to Buy score, in your CRM. These workflows are set up by your team and are out of MadKudu's control.
When you are ready, go to the Deployment tab and hit the Deploy button.
In the spot check, I'm seeing signals coming from unmapped product events, why?
For the connector Amplitude, Segment, MixPanel, or Kissmetrics, each event that is not mapped in the event mapping will fall into the catch-all event "Other [Connector] Activity". But by design, MadKudu is displaying the granularity of all unmapped events in the Signals. This enables you to have a better understanding of the activities performed by a lead.
If you wish to remove an unmapped activity from the Signals, add the event in the "Events to Exclude" in your Signals configuration page.