> For the complete documentation index, see [llms.txt](https://docs.verbdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verbdata.com/data-sources/data-synchronization/row-filtering.md).

# Row Filtering

Verb plans use managed data volume as one of the pricing factors.  As such, there are situations where you may not want Verb to ingest all of your data.  Row filters give you the ability to filter out records that should not be included.

For example, your system may use local deletes where deleted records are flagged for deletion rather than being physically removed.  In this case you may opt to filter all records that are flagged as deleted in your database.  You can do so using the filters section of the data source editor.  This feature allows you to compose additional SQL that will be applied when your database is queried for changes.

![](/files/cNJ32X1OpkwRKnl9JmJ5)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.verbdata.com/data-sources/data-synchronization/row-filtering.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.