Saving ingestion costs

Eventvisor's filtering and sampling capabilities can help save data ingestion costs in your organization significantly in a highly controlled and predictable manner.

Filtering vs Sampling#

• Filtering: allows you to filter in or out certain events from being tracked altogether
• Sampling: allows you to ingest a certain percentage of the events being tracked

It's not an either-or scenario. You can use both together to achieve your desired outcome.

Filtering events#

You can add conditions to the events or at destinations level to filter out certain events from being tracked:

# ...
conditions:
  - source: eventName
    operator: in
    value:
      - pageView
      - buttonClick

Tracked events that are neither pageView nor buttonClick will be filtered out.

Learn more in destinations page.

Sampling events#

Sampling is useful when you still wish to track all the events, but only for a certain percentage of your users.

The idea is to get a representative sample (like for 10% of users) to get an understanding of the overall behaviour of the application.

This helps avoid ingesting too much data and saving on ingestion and bandwidth costs.

# ...
sample:
  by: attributes.userId
  percentage: 10

Above, we are sampling 10% of the events based on the userId attribute. Because of sampling against a consistent value (the user's ID), we make sure that our sampled data is consistent for the same user across different devices and sessions.

Learn more in sampling page.