# Filter events

Filters stop matching events from being sent to a destination.

Littledata discards the event in the pipeline, so nothing reaches the platform.

## When to use filters

* Exclude internal test orders.
* Stop orders from a specific sales channel or app.
* Prevent employee purchases from inflating conversion data.

## How filters work

When Littledata processes a Shopify event, it checks for saved filters first.

If the event matches the filter conditions, Littledata discards it immediately.

{% hint style="info" %}
Filters run before modify and clone customisations. A matched filter stops all later customisations.
{% endhint %}

## Create a filter

{% stepper %}
{% step %}

### Open the destination Events tab

Go to **Settings** for the integration you want to update.

Then open **Events**.
{% endstep %}

{% step %}

### Open an event

Click the event you want to filter, such as `order_created`.
{% endstep %}

{% step %}

### Add a filter

Open the overflow menu and select **Add filter**.
{% endstep %}

{% step %}

### Add trigger conditions

Define one or more [trigger conditions](/event-customiser/trigger-conditions.md) for the filter.
{% endstep %}

{% step %}

### Save the customisation

Click **Save** to activate the filter.
{% endstep %}
{% endstepper %}

## Example: Exclude test orders by email

| Field       | Value                             |
| ----------- | --------------------------------- |
| Event       | `order_created`                   |
| Destination | Google Analytics 4                |
| Type        | Filter                            |
| Condition   | `email` **is** `test@example.com` |

## Example: Exclude orders from a specific app

| Field     | Value                                      |
| --------- | ------------------------------------------ |
| Condition | `app.name` **is** `Recharge Subscriptions` |

## Multiple conditions

All conditions use **AND** logic.

The filter only applies when every condition passes.

If you need **OR** logic, create separate filters for the same event.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/event-customiser/filter-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.