No, there is no impact to how events filter.

Whendeveloping against Analytics 2.0, the plugins you write can augment functionality, enrich data, and control the flow and delivery of events. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.

Whenyou develop against Analytics 2.0, the plugins you write can augment functionality, enrich data, and control the flow and delivery of events. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.

Plugins are bound by Analytics 2.0 which handles operations such as observability, retries, and error handling. There are two different categories of plugins:

***Critical Plugins**: Analytics.js expects this plugin to be loaded before starting event delivery. Failure to load a critical plugin halts event delivery. Use this category sparingly, and only for plugins that are critical to your tracking.

***Non-critical Plugins**: Analytics.js can start event delivery before this plugin finishes loading. This means your plugin can fail to load independently from all other plugins. For example, every Analytics.js destination is a non-critical plugin. This makes it possible for Analytics.js to continue workingin casea partner destination fails to load, orin case users have ad blockers turned on that are targeting specific destinations.

***Non-critical Plugins**: Analytics.js can start event delivery before this plugin finishes loading. This means your plugin can fail to load independently from all other plugins. For example, every Analytics.js destination is a non-critical plugin. This makes it possible for Analytics.js to continue workingifa partner destination fails to load, orif users have ad blockers turned on that are targeting specific destinations.

`utility` | Executes only with manual calls such as Logging. <br><br>These are plugins that change the Analytics 2.0 functionality. Utility plugins run outside of the event pipeline, and only execute once.

Here's an example of a plugin that converts all track event names to lowercase before the eventgets sent through the rest of the pipeline:

Here's an example of a plugin that converts all track event names to lowercase before the eventgoes through the rest of the pipeline:

exportconst lowercase:Plugin= {

constidentity= {

name:'Identity Stitching',

type:'enrichment',

You can view Segment's[existing plugins](https://github.com/segmentio/analytics-next/tree/master/src/plugins) to see more examples.

Registering plugins enable you to modify your analytics implementation to best fit your needs. You can register a plugin using this: