{"componentChunkName":"component---src-templates-markdown-template-jsx","path":"/guides/data-platform/data-filter/","result":{"data":{"pageMetadata":{"title":"Filters","path":"/guides/data-platform/data-filter/","sourceCode":null,"metadataParent":{"title":"Data Platform","path":"/guides/data-platform/","sourceCode":null,"hasVersionPicker":null,"metadataChildren":[{"title":"Trends","path":"/guides/data-platform/trends/","order":1,"label":null},{"title":"Setup","path":"/guides/data-platform/setup/","order":2,"label":null},{"title":"Live Stream","path":"/guides/data-platform/live-stream/","order":3,"label":null},{"title":"Data Catalog","path":"/guides/data-platform/catalog/","order":4,"label":null},{"title":"Rules","path":"/guides/data-platform/rules/","order":5,"label":null},{"title":"Plans","path":"/guides/data-platform/data-planning/","order":6,"label":null},{"title":"Filters","path":"/guides/data-platform/data-filter/","order":7,"label":null},{"title":"Event Forwarding","path":"/guides/data-platform/event-forwarding/","order":8,"label":null},{"title":"Event Match Quality","path":"/guides/data-platform/event-match-quality/","order":9,"label":null},{"title":"Data Retention","path":"/guides/data-platform/data-retention/","order":10,"label":null},{"title":"Tiered Events","path":"/guides/data-platform/tiered-events/","order":11,"label":null},{"title":"Blocked Data Backfill Guide","path":"/guides/data-platform/blocked-data-backfill-guide/","order":12,"label":null}],"metadataParent":{"title":"Guides","path":"/guides/","metadataChildren":[{"title":"Platform Overview","path":"/guides/platform-overview/","order":0.5,"label":null},{"title":"Getting Started","path":"/guides/getting-started/","order":1,"label":null},{"title":"mParticle Agent","path":"/guides/mparticle-agent/","order":1.5,"label":null},{"title":"Oversight","path":"/guides/oversight/","order":2,"label":null},{"title":"Data Platform","path":"/guides/data-platform/","order":3,"label":null},{"title":"Data Warehouse","path":"/guides/data-warehouse/","order":4,"label":null},{"title":"Customer 360","path":"/guides/customer-360/","order":5,"label":null},{"title":"Analytics","path":"/guides/analytics/","order":6,"label":null},{"title":"Audiences","path":"/guides/audiences/","order":7,"label":null},{"title":"Settings","path":"/guides/settings/","order":8,"label":null},{"title":"Troubleshooting mParticle","path":"/guides/troubleshooting/","order":10,"label":null},{"title":"Default Service Limits","path":"/guides/default-service-limits/","order":11,"label":null},{"title":"Glossary","path":"/guides/glossary/","order":12,"label":null}],"metadataParent":null}}},"markdownRemark":{"html":"

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.

\n

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.

\n

\n \n \n \n \n \n \n \n Configure filters

\n

There are two categories of filters: platform filters for filtering data from your platform inputs, and feed filters for filtering data from your feed inputs. The process of managing filters is the same for both, so the rest of this documentation will demonstrate managing platform filters.

\n

To find your filter settings:

\n

In the mParticle UI, go to Data Platform > Filters > Platform/Feed Filters.

\n

\n

The Filters page is separated into tabs for each data type you can create filters for:

\n\n

The first time you visit the Data Filter, you will see a list of data types with toggle switches on the left, and several empty columns on the right.

\n

To start creating filters for your outputs, you need to select one or more output integrations by clicking the Choose Integrations to View button. In the modal that appears, search for and select the specific output integrations you want to configure filters for.

\n

\n

This adds each output integration you select to one of the columns, allowing you to begin filtering certain data points OFF.

\n

\n\n

\n \n \n \n \n \n \n \n Disable Data Points

\n

You can filter event data at 3 levels: Event Type, Event Name and Event Attributes.

\n\n\n

\n \n \n \n \n \n \n \n New Data Points

\n

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.

\n

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.

\n

\n

\n \n \n \n \n \n \n \n Shortcuts

\n

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 three dot action icon near the top of the column.

\n

\n

From this menu you can:

\n","frontmatter":{"title":"Filters","order":7,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/data-platform/data-filter/"}},"staticQueryHashes":["2950460867"]}