Are you getting irrelevant activities or events in Copilot? In this article, we'll describe how you can get rid of them.
Case #1: The events you want to exclude are already mapped
First, make sure you're not using them in your live scoring model: it's not possible to exclude events from Copilot while still using them in your Likelihood to Buy Model.
Then you'll simply need to edit the event mapping and select the "Non User Activity" Activity type for them in the event mapping dropdown. This will ensure these events are never considered in the Models, in the Signals or in the Copilot activities feed.
- Create a new draft event mapping by clicking "start draft"
- Edit the relevant events' activity type
- Save your draft, then click "publish"
Case #2: The events you want to exclude are not yet mapped, but they create noise in Copilot
Madkudu has built-in logic to make sure we don't miss out on anything interesting from your integration. Unmapped events thus fall in a bucket called 'Other [integration] activity' (referred to as a 'catch-all' since it catches all events not explicitly mapped) that is automatically created by MadKudu. This catch-all event is not visible in the event mapping but you will see this event in the Data Studio and in Copilot. This is probably why you're getting a lot of noise.
In that case, first check what events are currently being unmapped in the Event Mapping Output report.
Map the ones you want to exclude and make sure to select the "Non User Activity" type, as mentioned in the steps above.
Need to learn more about the event mapping? We've got you covered here: How to create or edit the Event mapping?