Filtering events

Unwanted events tracked from applications can be filtered out from being transported to different destinations.

Challenges#

Sometimes we know for sure that certain events are no longer needed to be tracked.

And in a large organizations, it is not always easy to track down and remove them from all the places they are being tracked from. They challenges can range from either technical difficulties, deployment frequency, or simply not being able to get the teams to take action quickly.

Filtering out in events#

If you are interested in filtering out a specific event going to a certain destination, you can update the event definition directly:

# ...
destinations:
  myDestinationName: false

Or, you can just delete the event definition entirely. This will result in applications tracking an unknown event, ending up nowhere and they will also get a validation warning in the console.

Learn more in events page.

Filtering out in destinations#

You can also filter out the events in the specific destination definition:

# ...
conditions:
  - source: eventName
    operator: notIn
    value:
      - button_click

Learn more in destinations page.

Benefits#

Because Eventvisor can take control of how tracked events are transported to different destinations via remotely fetched configuration in the form of datafiles, you can achieve this at a central place.