A key benefit of mParticle is the ability to collect your data only once, no matter how many places you need to use it. However, you probably don’t want all of your data going to every output service you use. For this reason, mParticle provides the Data Filter as a simple way to control the flow of data to your outputs.
The Data Filter displays a complete list of all data points (a data point can be an event, an attribute of a user or event, or a user identifier) collected in your workspace, and allows you to disable forwarding of any individual data point to any of your output services.
The first time you visit the Data Filter, you will see an empty grid. To start filtering you need to:
You can filter event data at 3 levels: Event Type, Event Name and Event Attributes.
The Filter allows you to disable any current data point from being forwarded to any current output service. However, as you continue to use mParticle, update your app instrumentation, and add inputs, you will continue to generate new data points. One of the most important decisions to make in the Filter is how to handle new data points for each output service. By default, mParticle will automatically forward new data points to each output service. If you uncheck the Send new data points by default box, no new data points will be forwarded to that output until you explicitly enable it in the Filter.
New data points will be added to the Data Filter the first time mParticle receives them. It should only take a few minutes from mParticle receiving a data point for it to be visible in the Data Filter.
A mature mParticle project may have hundreds of events. That’s a lot of filter switches. To save you time, we provide some convenience methods to help you set your filters quickly. To access the shortcuts for an output service, click the elipsis near the top of the column.
From this menu you can:
Was this page helpful?