RudderStack’s client-side event filtering feature lets you specify which events should be discarded or allowed to flow through by allowlisting or denylisting them.
Note that:
Client-side event filtering is applicable only for track calls. In case of mobile SDKs, it also applies to the following application lifecycle events:
Application Installed
Application Opened
Application Backgrounded
Application Updated
You can use this feature for all RudderStack destinations that support sending events via device mode.
To use this feature with the latest JavaScript SDK, note that:
Empty and non-string event names are not allowlisted anymore.
RudderStack gives you the ability to configure your event filtering options while setting up your device mode destination in the dashboard:
You will see the following dropdown options under Event Filtering, in the Connection Settings page:
Disable
Event filtering will be disabled if you select this option from the dropdown. In this case, RudderStack will not filter any events and allow all events to flow through.
Allowlist
Upon selecting the Allowlist option from the dropdown, you can specify the names of the events that you want RudderStack to allow or flow through to the destination.
If you choose the Allowlist option for event filtering, any events specified in the Denylist field will be ignored.
You can add as many events as you want to the allowlist by clicking the Add More option.
RudderStack will discard any event that is not specified in the allowlist. If you do not specify any events in the allowlist, all the calls will be discarded.
Denylist
Upon selecting the Denylist option from the dropdown, you can specify the names of the events that you want RudderStack to discard. These events will not be sent to the destination.
If you choose the Denylist option for event filtering, any events specified in the Allowlist field will be ignored.
You can add as many events as you want to the denylist by clicking on the Add More option.
RudderStack will only discard events explicitly specified in the denylist. If you do not specify any events in the denylist, then all calls will be allowed through.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.