> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/advanced/measurements-explained/gating/custom-gating.md).

# Custom gating

A gate built with SBT, for samples that BacTotal-10 does not fit.

Use [BacTotal-10](/advanced/measurements-explained/gating/bactotal-10.md) unless you have a specific reason not to. It fits most samples.

Some samples need a different gate, for example:

* Bacteria killed by heat or alcohol, such as in bacterins and postbiotics. See [Inactivated bacteria](/advanced/measurements-explained/gating/inactivated-bacteria.md).
* Aged cultures of some Gram-positive species
* Bacterial endospores
* A medium with particles that overlap with cells. See [Check medium background](/more/how-to-guides/check-medium-background.md).

Building a gate is development work rather than a setting you can change, so SBT offers it as a paid [custom solution](/advanced/what-is-a-custom-solution.md). We scope the work with you first. [Contact us](https://sbtinstruments.com/contact).

Custom gating does not give you a live-dead count. See [BacTotal-10](/advanced/measurements-explained/gating/bactotal-10.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sbtinstruments.com/advanced/measurements-explained/gating/custom-gating.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.